opnsense router on kvm-based Virtual machine

[aab]

Hi all,
 I currently have my opnsense installed & configured on a physical machine as a router, I am thinking to move it to a KVM-based virtual machine, has anyone already tried it ?
I am thinking to dedicate two physical interfaces of the physical machine to the virtual machine, install the opnsense to that virtual machine and then restore the backup from the opnsense which is my current router on a physical machine to this virtual machine.
Has anyone tried this already ? are there some limitations ?

Regards

[bigverm23]

were you able to accomplish this? i'm in the same boat...

[bunchofreeds]

Not exactly the same but close...

I run OPNsense as a VM on Proxmox (Highly recommend this) as my KVM based Hyper Visor.
Been running it like this quite successfully for a couple of Years.
This is for my Home and Home LAB.
Dedicated NIC's for WAN and LAN as linux bridges/virtual switches.

I find absolutely no performance impact when running this setup for a 1000/500 WAN, but have the advantages of very little downtime for OPNsense as you can live migrate between hosts when updating the hosts.
Also running additional VM's and containers ad hoc is great.
Add to this the snapshots and backups.

My two hosts are HP 800 G3 mini's with Realtek USB adapters
Running SSD and NVME.
Works really well for me as low power, quiet and they have intel AMT for management.

Is this going to be migrated to a new machine or are you rebuilding the existing one?
Just wondering how much planning you need to do, or can you test in parallel.

I have done the backup / restore configuration also and it's pretty solid (was a while ago though).
Just make sure of your plugins as you will need to re-install those. I seem to remember this not being that much of an issue, as it just warns they are not installed after a restore, so you go about adding them.
Some services have config stored separately like haproxy which you will need to export (if you use these additional services).
Also the interfaces will likely have different names so you will be re associating those after the restore through interfaces>assignments.
Oh and remember to add the qemu guest agent afterwards.