March 12, 20179 yr I am not 100% sure what the issue is... so I built machine with i7-4790K and Z97 mobo but didnt build parity yet as I intended to swap out the mobo and CPU. All dockers etc ran fine in this config. I swapped out Xeon 2683 V3 and X99 mobo and started to set up VMs. Seemed OK so I started parity creation and went to bed. Woke to machine powered off (unlikely to be manual unless my cats have new ninja skills with pressing the power button - has happened but I had it covered!). Found my Win10 VM which was running now had no IMG file at all. So went to recreate. And 20mins in (of course while I am not there physically) the VM has locked and cannot be killed. I can SSH in but even sudo reboot does nothing except claim it is going down. Virsh destroy fails to kill the VM. There are some logs however (I had log Window open on another machine) which indicate kernel crashes from KVM? Does that mean its an issue with unRAID or my hardware? Full specs: Gigabyte GA-X99P-SLI latest BIOS Xeon E5-2683 v3 (14C/28T) 32Gb DDR4 @ 2133 Samsung 960Evo (with Unassigned Devices plugin - stopped trying to create VM on that for final run) Samsung 850Evo & Toshiba TR150 - cache pool 8 * 5Tb Toshiba 5Tb HDDs 2 * 6Tb Toshiba 6Tb HDDs 2 x 250 Gb * 1 x 500 Gb misc HDDs not in array - Unassigned Devices Was trying Win10 VM with 10Gb Ram, last 10 cores & paired HT isolated, 4 assigned to the VM Log file attached crash.txt
Archived
This topic is now archived and is closed to further replies.