So... I can tell your using VMs... Care to mention what kind of VMs? You know, like the hypervisor? Also we need FULL details of your entire system including model numbers.
Once we have that information we might be able to better help you.;)
I'm assuming you are refering to Windows 2016 running as a guest in bhyve. Is this correct?It's a server 2016 build.
Are you getting any errors, messages, or any other indication that its not booting?I've created zfs pools for the storage I'm trying to attach but it won't boot once they are on.
Lots of people run FreeNAS for xen, vSphere, hyper-v, and even kvm. Sometimes this is even attempted in nested environments.Bhyve? There aren't any options as far as which hypervisor.
So the VM was running with the disk but then crashed?Stability wise - I think it was crashing to the off state when the cpu was hammered for extended periods of time. I've given it 6 cores and 6Gb of ram. I'll find some time to look for how to's re checking bhyve logs soon. Nothing on the GUI which makes it harder for a newbie to FreeNAS.
I'm a bit lost with your explanations. Did the VM ever power on with the disk added or not?Any combo for adding a disk from the GUI has resulted in failed boots - ie VNC opens a new tab but it shows page won't load. Creating a zvol first, adding it as AHCI or VirtIO.
Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 cores)
Consider trying 4 cores. Without getting into how CPU scheduling works with VMs, just trust me. Sometimes less is more.I've given it 6 cores
ok - will do.Consider trying 4 cores. Without getting into how CPU scheduling works with VMs, just trust me. Sometimes less is more.
I still don't understand this statement. You are implying the system was up "for extended periods of time" but you are saying the VM does not start at all.Stability wise - I think it was crashing to the off state when the cpu was hammered for extended periods of time. I've given it 6 cores and 6Gb of ram. I'll find some time to look for how to's re checking bhyve logs soon. Nothing on the GUI which makes it harder for a newbie to FreeNAS.
I see the misunderstanding. I hit a wall whenever I try to add a disk - with a new disk added it has never booted.I still don't understand this statement. Your implying the system was up "for extended periods of time" but you saying the VM does not start at all.
Are you saying re vShpere they run FreeNAS for iSCSI or an NFS share for datastores or can you actually run a vSphere instance alongside FreeNAS from the base FreeBSD OS? I'm familiar with vShpere - just not this bhyve system.Lots of people run FreeNAS for xen, vSphere, hyper-v, and even kvm. Sometimes this is even attempted in nested environments.
There is no way to take VM application consistent snapshots from within FreeNAS.