Any "Gotchas" restoring bare metal config to new virtual setup?
-
I'm looking to move my bare metal config over to a new VM I setup and I'm wondering if there are any gotchas I need to be aware of. I know I have to change the interfaces my VLANs are bound to since they will change from igb0/1 to vmx0/1. Anything else I should be aware of such as firewall rules/NAT, etc?
VM host is a VMware ESXi 5.5 box.
-
You didn't say which platform you're going to use, so nobody can give you any specific tips. VMware? Hyper-V? Xen? Proxmox? …
-
@KOM:
You didn't say which platform you're going to use, so nobody can give you any specific tips. VMware? Hyper-V? Xen? Proxmox? …
My bad. Host is ESXi 5.5.
-
Don't know if these are gotchas:
1: make sure you install the VM tools package and imo you should reboot the VM after install
2: recommended setup is to use vmxnet3 nics, you need to do this manually (custom VM setup)Otherwise it should be straightforward
-
This should get you started:
https://doc.pfsense.org/index.php/PfSense_2_on_VMware_ESXi_5
The only things that was special was if you were planning on a HA config using CARP, in which case you needed to enable promiscuous mode on your ESXi NICs.
Also, I think I remember recently people were having trouble with the VMX NICs under load, and that problem wasn't present with the E1000's. It is also debatable as to whether or not to install VMware Tools. FreeBSD base already has the NICs, so it's really only required if you must have the server heartbeat, and even then it is a trick to get them properly installed. Search this forum for other posts about VMware Tools/Open-VM-Tools.
-
@KOM:
Also, I think I remember recently people were having trouble with the VMX NICs under load, and that problem wasn't present with the E1000's. It is also debatable as to whether or not to install VMware Tools. FreeBSD base already has the NICs, so it's really only required if you must have the server heartbeat, and even then it is a trick to get them properly installed. Search this forum for other posts about VMware Tools/Open-VM-Tools.
Not sure if this makes a difference, but I've noticed the latest openvm tools made a bit of a difference re latency
