Windows 10 VM runs slow

[Eth0]

Hello.

im new to Freenas, but learning by trying :)

i have got plex and all the other plugins to work just fine.

but i have made a 50 Gib Zvol off a 256 Gb SSD and created a Windows 10 VM. install and settings are all good.
but the problem is that the VM runs like its runs off a Pention 3 processor.
the Usage is 99/100% all the time and i am only running Chrome.

the problem is that i runs for that in 30-40 mins then it crash with no error. in Freenas VM it says that it is running?

i have tryed to assign 8 core to the VM and didnt help.
i have assigned 4 Gb ram to the VM.

what am i doing wrong?

my system is

Intel Xeon E5-2670 x2
Kingston ECC 8x8 - 64 Gb
WD Red 4 Tb x 8 in a Raidz2 config
Samsung SSD 850 Pro 256 GB using for VM

 

[Nomar1245]

My guess is the crash is caused by Intel NIC instead of using Virtio(and its 1.1.118 Driver), and the perceived slowness is caused by VNC. Have you tried running the machine through RDP instead?

 

[dirkme]

I am not kidding, but that is because Windows 10 is sluggish.

I bought a Gaming Laptop and it came with Windows 10, it was slower than my 10 years old laptop running Debian on it. No question, Windows Mal & Spyware OS had to go to the trash where it belongs, no1 can read and sign the EULA from Micro$oft.

 

[Alex98234]

I had the same problem with a Windows Server 2016 VM. I fixed the VM crash problem by using the VirtIO NIC device and driver.

Also make sure you have setup your tunables for CPU topology correctly in FreeNAS when using that many cores/threads.

By default, Bhyve (the FreeBSD hyper-visor used in FreeNAS) assigns a single socket/package per core assigned. This can cause issues with Windows 10 because the max sockets/packages allowed is 2, and even then I believe it has to be Windows 10 Pro.

How many sockets/cores/threads appear in task or device manager?

I have a 4 core 8 thread CPU so my FreeNAS tunables look like so:
hw.vmm.topology.cores_per_package: 4
hw.vmm.topology.threads_per_core: 2

I set these up in System > Tunables.

For you it would be:
hw.vmm.topology.cores_per_package: 8
hw.vmm.topology.threads_per_core: 2 (providing that hyper-threading is enabled)

 

[jmatt3685]

Did you ever get this fixed? I'm running an E3-220 v5 and having the EXACT same issue...