lukeren
Explorer
- Joined
- Apr 13, 2017
- Messages
- 62
I've been running FreeNAS for quite a while, but recently upgraded my hardware to a SuperMicro X9DAi with an E5-2650 and 52GB RAM (it's a mix of sticks I'm looking to sort out).
Since I'm basically the only user of the system, it seemed a bit of a waste to dedicate all that to FreeNAS. I'd like to run a few VMs too, but the bhyve hypervisor wasn't really doing it for me.
I read the following posts before starting out and decided to go ahead despite all the warnings ;)
http://www.freenas.org/blog/yes-you-can-virtualize-freenas/
https://b3n.org/freenas-9-3-on-vmware-esxi-6-0-guide/
https://forums.freenas.org/index.ph...nas-in-production-as-a-virtual-machine.12484/
https://forums.freenas.org/index.php?threads/my-dream-system-i-think.41072/ (this one was a beast, but @joeschmuck had a lot of good info there)
I created a VM with 8 vCPUs, 24GB RAM and a 10GB disk. Installed FreeNAS and checked it was booting with no issues.
Then I passed the HBA through and checked dmesg to see if it was actually working, it was.
At that point all that remained was to actually connect the drives, I did and imported my config from a backup.
After a few reboots my system was running again, but my jails didn't get any network connectivity. @jgreco had the answer in this thread though.
It didn't work for me after enabling "Allow forged transmits", I had to also enable "Allow promiscuous mode". This may be down to me being impatient, I don't know how long it takes for the changes to apply.
What I noticed after this all was set up, was that it appeared the server didn't draw as much power under ESXi as it did under FreeNAS. It may just be me seeing things though.
I'd like to disable the scrubs on the boot volume, since it's not directly connected to the VM, should I do that? Also, how do I do that? :)
Since I'm basically the only user of the system, it seemed a bit of a waste to dedicate all that to FreeNAS. I'd like to run a few VMs too, but the bhyve hypervisor wasn't really doing it for me.
I read the following posts before starting out and decided to go ahead despite all the warnings ;)
http://www.freenas.org/blog/yes-you-can-virtualize-freenas/
https://b3n.org/freenas-9-3-on-vmware-esxi-6-0-guide/
https://forums.freenas.org/index.ph...nas-in-production-as-a-virtual-machine.12484/
https://forums.freenas.org/index.php?threads/my-dream-system-i-think.41072/ (this one was a beast, but @joeschmuck had a lot of good info there)
I created a VM with 8 vCPUs, 24GB RAM and a 10GB disk. Installed FreeNAS and checked it was booting with no issues.
Then I passed the HBA through and checked dmesg to see if it was actually working, it was.
At that point all that remained was to actually connect the drives, I did and imported my config from a backup.
After a few reboots my system was running again, but my jails didn't get any network connectivity. @jgreco had the answer in this thread though.
It didn't work for me after enabling "Allow forged transmits", I had to also enable "Allow promiscuous mode". This may be down to me being impatient, I don't know how long it takes for the changes to apply.
What I noticed after this all was set up, was that it appeared the server didn't draw as much power under ESXi as it did under FreeNAS. It may just be me seeing things though.
I'd like to disable the scrubs on the boot volume, since it's not directly connected to the VM, should I do that? Also, how do I do that? :)