I've been running FreeNAS bare metal on dual XEON CPUs, 48 GB RAM and LSI 9211-8i HBA card (w/ IT firmware) + Intel SAS Expander for up to 24 drives. As you can imagine the specs are gross overkill for FreeNAS, especially since it has turned out to be an archive server. I'd like to utilize more of the server's resources, throw ESXi on there and move virtual FreeNAS. Is it as simple as using passthrough/VT-d to give the FreeNAS VM the HBA card & drives, performing a fresh install, importing the config file via the web UI, importing the pools or is there more stuff involved than that? Also, what specs should I give the FreeNAS VM?
-
Important Announcement for the TrueNAS Community.
The TrueNAS Community has now been moved. This forum will now become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums
migrate FreeNAS to VM
- Thread starter digity
- Start date
- Status
- Joined
- Jan 1, 2016
- Messages
- 9,703
You shouldn't need to import the pools if you restore the config.
FreeNAS loves RAM (so it's just a question of what will you take away from it to use elsewhere), but doesn't really need a lot of CPU unless you do things like transcoding in Plex, so 2 VCores could be OK. (I give mine 4, but don't really need to)
FreeNAS loves RAM (so it's just a question of what will you take away from it to use elsewhere), but doesn't really need a lot of CPU unless you do things like transcoding in Plex, so 2 VCores could be OK. (I give mine 4, but don't really need to)
kdragon75
Wizard
- Joined
- Aug 7, 2016
- Messages
- 2,457
Start with the recommended minimums and 2 cores. Make sure your using vmxnet3 vNICs.
Last edited:
- Status
Similar threads
