*New 12.1 series Release:
2019-11-08: XigmaNAS - released!

*New 11.3 series Release:
2019-10-19: XigmaNAS - released

We really need "Your" help on XigmaNAS https://translations.launchpad.net/xigmanas translations. Please help today!

Producing and hosting XigmaNAS costs money. Please consider donating for our project so that we can continue to offer you the best.
We need your support! eg: PAYPAL

From ESXi to Xigmanas. Good or Bad?

VirtualBox, VM config and HDD images.
Forum rules
Set-Up GuideFAQsForum Rules
Post Reply
Posts: 1
Joined: 03 Dec 2019 01:17
Status: Offline

From ESXi to Xigmanas. Good or Bad?


Post by BumbleBII » 03 Dec 2019 01:33

Hi, I have been using XigmaNas for a while now as a VM in my VMware ESXi host. And it's all good and dandy. But now I am going to upgrade my storage and without PCI passthought it's a bad idea to run it as a VM. So I am thining about running Xigmanas as my Hyperviser insted of ESXi. Is it a bad Ide?

Advanced User
Advanced User
Posts: 177
Joined: 23 Mar 2014 02:58
Location: UK
Status: Offline

Re: From ESXi to Xigmanas. Good or Bad?


Post by cookiemonster » 04 Dec 2019 23:13

Hi and welcome. Many people run XN as an ESXi guest like you did. It is only not recommended to use XN without raw access to the hard drives due to ZFS working best to protect your data without raid cards creating a layer of complication down the road.
Depends on your harware setup a lot and what you want to achieve, Maybe you could list your hardware and requirements to see if you could get a better answer?
Main: Xigmanas x64-full-RootOnZFS on Supermicro X8DT3. zroot on mirrorred pair of CRUCIAL_CT64M225. Memory: 72GB ECC; 2 Xeon E5645 CPUs; Storage: (HBA) - LSI SAS 9211-4i with 3 SATA x 1 Tb in raidZ1, 1 x 3 Tb SAS drive as single stripe.
Spare1: HP DL580 G5; 128 GB ECC RAM; 4 CPU; 8 x 500 GB disks on H210i
Spare2: HP DL360 G7; 6 GB ECC RAM; 1 Xeon CPU; 5 x 500 GB disks on H210i
Spare3: HP DL380 G7; 24 GB ECC RAM; 2 Xeon E5645 CPUs; 8 x 500 GB disks on IBM M1015 flashed to LSI9211-IT

Post Reply

Return to “VM|VirtualBox”