Hey guys,
I am planning to build a home-server running Nas4Free on ESXi as a vm along with other vm's (webserver, buildserver, etc.) so that I do not need serveral machines (for each task) running 24/7. I was just discussing the hardware configuration in another forum, where s.b. mentioned that I might get performance or even driver problems running Nas4Free in this constellation. So I decided to join a more specific forum...
Big question: Will it be possible running Nas4Free stable/secure on ESXi?
Hardware (if relevant):
Motherboard with Intel Atom C2750 SoC (not quite sure which one)
16GB ECC RAM
2x 120GB SSD, Raid-1 (via onboard- or pci-controller)
4x 2/3TB WD Red
(If possible) ESXi is going to be installed on the SSD's; the HDD's are for N4F only
Sorry for my (bad) english.
This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
Installation on ESXi
-
b0ssman
- Forum Moderator
- Posts: 2438
- Joined: 14 Feb 2013 08:34
- Location: Munich, Germany
- Status: Offline
Re: Installation on ESXi
Nas4Free 11.1.0.4.4517. Supermicro X10SLL-F, 16gb ECC, i3 4130, IBM M1015 with IT firmware. 4x 3tb WD Red, 4x 2TB Samsung F4, both GEOM AES 256 encrypted.
-
00Roush
- Starter
- Posts: 64
- Joined: 15 Sep 2013 09:27
- Status: Offline
Re: Installation on ESXi
I have had pretty good luck running NAS4Free in a VM on ESXi 5.0/5.1. ESXi 5.5 has some issues for me with pass thru of devices.
I would recommend making sure you find a motherboard setup that for sure supports VT-d passthrough of devices. This should allow for a whole disk controller to be passed to NAS4Free VM so that ZFS can directly control hard drives as it is designed to do. My opinion is this is the safest method. Passing virtualized disks can work but there is much greater risk that data would be lost if problems arise.
For me I am running a Xeon E3-1230 CPU on a Supermicro X9SCM-F motherboard and I am passing the onboard Intel SATA controller to NAS4Free VM. NAS4Free has built in VMware Tools and seems to support all of the virtualized hardware just fine. At least when using ESXi 5.0/5.1.
00Roush
I would recommend making sure you find a motherboard setup that for sure supports VT-d passthrough of devices. This should allow for a whole disk controller to be passed to NAS4Free VM so that ZFS can directly control hard drives as it is designed to do. My opinion is this is the safest method. Passing virtualized disks can work but there is much greater risk that data would be lost if problems arise.
For me I am running a Xeon E3-1230 CPU on a Supermicro X9SCM-F motherboard and I am passing the onboard Intel SATA controller to NAS4Free VM. NAS4Free has built in VMware Tools and seems to support all of the virtualized hardware just fine. At least when using ESXi 5.0/5.1.
00Roush
-
P4R4N0I4
- NewUser
- Posts: 2
- Joined: 08 Aug 2014 17:51
- Status: Offline
Re: Installation on ESXi
Okay, so I have to reconsider my configuration and find a way to bring VT-d support into my system... But why is the risk to lose data still much greater as in a non-virtualized environment? Is there anything else to think about that might bring more stability?
Are you satisfied with your system at all?
Are you satisfied with your system at all?
-
00Roush
- Starter
- Posts: 64
- Joined: 15 Sep 2013 09:27
- Status: Offline
Re: Installation on ESXi
In a normal setup with no virtualization the OS and ZFS directly control the hard drives and hard drive controljy:,,,,aww,lers. ZFS expects that it has direct control of disks and it is designed to work this way. Q
A11
Virtualization without VT-d means that a VM can't directly control hardware but instead accesses hardware virtually. With most hardware this works okay but with storage it can cause issues and more risk because you end up with mo!!!!qqre layers. With the additional layers ZFS no longer can detect and correct errors like it is designed to. Essentially if errors do happen and ZFS can't control the hardware directly the chances of loosing a whole ZFS pool are higher.
Yes I have been happy with my system but I still have not made it my main storage unit. I have a windows server as my main storage. #1 reason I haven't switched is just being lazy. I think it would work just fine but I am always testing different things and still not sure I want to have my main storage on a setup I test with too.
00Roush
A11
Virtualization without VT-d means that a VM can't directly control hardware but instead accesses hardware virtually. With most hardware this works okay but with storage it can cause issues and more risk because you end up with mo!!!!qqre layers. With the additional layers ZFS no longer can detect and correct errors like it is designed to. Essentially if errors do happen and ZFS can't control the hardware directly the chances of loosing a whole ZFS pool are higher.
Yes I have been happy with my system but I still have not made it my main storage unit. I have a windows server as my main storage. #1 reason I haven't switched is just being lazy. I think it would work just fine but I am always testing different things and still not sure I want to have my main storage on a setup I test with too.
00Roush