steven6282
Dabbler
- Joined
- Jul 22, 2014
- Messages
- 39
Hey everyone,
I'm building a new FreeNas based server. I was messing around earlier with FreeNas 11.2 Beta and the VM support in it seems to be a lot more fleshed out than in 11.1, so I guess that is one of the things being worked on in 11.2. However I ran into a problem when trying to create a VM with a python index out of range error. I figured this must be due to the Beta state so I installed 11.1 STABLE. Now in 11.1 stable, I apparently have to manually create all the devices for the VM. However, when I go to add a disk, it's only giving me the option to select a ZVol. Why would this be limited to ZVols only?
I configured my new system with a 240 GB M.2 nvme drive as the boot drive with the intention of running some VMs on it as well. The plan was to run the root file systems of the guest VMs on this drive, and then any critical data stored in them would be stored in a mount from a share in my storage array. This way I can benefit from the speed of the SSD while keeping actual data secure. Some VMs I simply don't need data redundancy on. Like a small VPN tunnel that has no data to store. There is no reason to use space on a ZVol for that VM. I suppose I could probably run FreeNAS on a usb drive in order to have it look at this SSD as a valid usable disk for other things, but that seems silly to put FreeNAS on a cheap slow USB stick. I've also had 3 USB sticks fail on my current FreeNAS system before I moved to a small SSD for it, USB sticks just aren't built to handle 24 x 7 data reads and writes in my expenrience.
So, is there any way to force the system to let me put a VM disk on the boot disk?
I'm building a new FreeNas based server. I was messing around earlier with FreeNas 11.2 Beta and the VM support in it seems to be a lot more fleshed out than in 11.1, so I guess that is one of the things being worked on in 11.2. However I ran into a problem when trying to create a VM with a python index out of range error. I figured this must be due to the Beta state so I installed 11.1 STABLE. Now in 11.1 stable, I apparently have to manually create all the devices for the VM. However, when I go to add a disk, it's only giving me the option to select a ZVol. Why would this be limited to ZVols only?
I configured my new system with a 240 GB M.2 nvme drive as the boot drive with the intention of running some VMs on it as well. The plan was to run the root file systems of the guest VMs on this drive, and then any critical data stored in them would be stored in a mount from a share in my storage array. This way I can benefit from the speed of the SSD while keeping actual data secure. Some VMs I simply don't need data redundancy on. Like a small VPN tunnel that has no data to store. There is no reason to use space on a ZVol for that VM. I suppose I could probably run FreeNAS on a usb drive in order to have it look at this SSD as a valid usable disk for other things, but that seems silly to put FreeNAS on a cheap slow USB stick. I've also had 3 USB sticks fail on my current FreeNAS system before I moved to a small SSD for it, USB sticks just aren't built to handle 24 x 7 data reads and writes in my expenrience.
So, is there any way to force the system to let me put a VM disk on the boot disk?