VMs not starting under Hyper-V install

[JamesWorts]

Hi All,

This may seem a little strange, however.

I have had FreeNAS running on an old Dell desktop pc, I am now trying to move everything across to a Dell PE T710 Running Windows Server 2016.

I have webmin/virtualmin running on CentOS 7 in a VM on FreeNAS on the current system and several Jails.

I have installed FreeNAS 11.1 on the Dell PE T710 via Hyper-V, restored settings and swapped the physical drive into the new system, after a couple of tweaks all my "Jails" and Plugins work fine..

But... The VM does not start. everytime I try to starts it, it always always reports "Stopped" and the console displays:-
"Apr 7 12:08:46 freenas tap0: Ethernet address: 00:bd:21:8d:ff:00
Apr 7 12:08:46 freenas kernel: tap0: promiscuous mode enabled"

I am running Dual Hex Xeon E5670 and 48gb RAM.

Can anyone help?

I have tried the following but still no good.
"Set-VMProcessor -VMName Name-ExposeVirtualizationExtensions $true"

Any help or advise would be good.

Thanks

 

[kdragon75]

Docs.Microsoft.com

Virtualization applications other than Hyper-V are not supported in Hyper-V virtual machines, and are likely to fail. This includes any software that requires hardware virtualization extensions.

bhyve on FreeNAS is not mature and should not be expected to work in "specialty" situations like this. I would recommend a true type 1 hypervisor for this type of use case. *cough ESXi cough*