I went to remote into my machine and it wasn't connecting. I checked the dashboard and it wasn't started. I assumed it had crashed. I went to start it back up again but it immediately shut down. I don't think it crashed because the log shows this:

 

2016-06-24 02:24:11.548+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'Windows 10' -S -machine pc-q35-2.5,accel=kvm,usb=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -m 24064 -realtime mlock=off -smp 6,sockets=1,cores=3,threads=2 -uuid 049a251e-de3c-00cd-f1e0-bcb6943522fa -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0x1e -device pci-bridge,chassis_nr=2,id=pci.2,bus=pci.1,addr=0x1 -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,ad-k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pcie.0,addr=0x1 -device virtio-balloon-pci,id=balloon0,bus=pci.2,addr=0x4 -msg timestamp=on
Domain id=1 is tainted: high-privileges
Domain id=1 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2016-06-27 02:05:14.074+0000: shutting down
2016-06-27 05:15:16.982+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'Windows 10' -S -machine pc-q35-2.5,accel=kvm,usb=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -m 24064 -realtime mlock=off -smp 6,sockets=1,cores=3,threads=2 -uuid 049a251e-de3c-00cd-f1e0-bcb6943522fa -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0x1e -device pci-bridge,chassis_nr=2,id=pci.2,bus=pci.1,addr=0x1 -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,ad-k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pcie.0,addr=0x1 -device virtio-balloon-pci,id=balloon0,bus=pci.2,addr=0x4 -msg timestamp=on
Domain id=2 is tainted: high-privileges
Domain id=2 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2016-06-27 05:16:10.835+0000: shutting down
2016-06-27 05:16:47.592+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'Windows 10' -S -machine pc-q35-2.5,accel=kvm,usb=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -m 24064 -realtime mlock=off -smp 6,sockets=1,cores=3,threads=2 -uuid 049a251e-de3c-00cd-f1e0-bcb6943522fa -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0x1e -device pci-bridge,chassis_nr=2,id=pci.2,bus=pci.1,addr=0x1 -device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,ad-k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vgamem_mb=16,bus=pcie.0,addr=0x1 -device virtio-balloon-pci,id=balloon0,bus=pci.2,addr=0x4 -msg timestamp=on
Domain id=3 is tainted: high-privileges
Domain id=3 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2016-06-27 05:17:08.354+0000: shutting down

 

Any ideas on what's happening? Looks like a shutdown signal is being sent but no idea why. Any idea on how to do a safe boot? I don't have GPU pass through set up yet; I've just been using RDP for now.

I have a similar problem.

Win 7 and I get random shut downs.

Could be within seconds or days!

 

Here is my log

 

2016-07-04 13:01:27.837+0000: starting up libvirt version: 1.2.18, qemu version: 2.3.0

LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/bin/qemu-system-x86_64 -name Windows 7 -S -machine pc-i440fx-2.3,accel=kvm,usb=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -m 1536 -realtime mlock=on -smp 4,sockets=1,cores=4,threads=1 -uuid 3087e37d-3692-94b7-8af5-5869b1c0b438 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Windows 7.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive file=/mnt/cache/Virtualfiles/vDisks/Windows/vdisk.img,if=none,id=drive-virtio-disk2,format=raw,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1 -drive file=/mnt/cache/Virtualfiles/vDisks/Windows/dropboxfolders/vdisk2.img,if=none,id=drem_mb=16,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 -msg timestamp=on

Domain id=5 is tainted: high-privileges

Domain id=5 is tainted: host-cpu

char device redirected to /dev/pts/0 (label charserial0)

2016-07-04 13:02:41.499+0000: shutting down

How much RAM do you have and how much RAM do you assign to the VM?

I had this issue.  Are you by any chance using an i7-2600k?

 

If so add this to the XML, replacing the existing cpu mode section:

 

  <cpu mode='custom' match='exact'>
    <model fallback='forbid'>SandyBridge</model>
    <feature policy='disable' name='x2apic'/>
  </cpu>

I have an i7-4771 and 24gb RAm assigned to it. I resolved this by doing ctrl+alt+delete as soon as possible and restarting safely before it crashed.

I have

 

CPU: Intel® Xeon® CPU E3-1230 v3 @ 3.30GHz

Memory: 4096 MB

 

and assigned 1.5Gb to the VM

 

(sorry for the delay)

I have

 

CPU: Intel® Xeon® CPU E3-1230 v3 @ 3.30GHz

Memory: 4096 MB

 

and assigned 1.5Gb to the VM

 

(sorry for the delay)

 

karateo, you've not got much RAM, so I don't necessarily think this is the same issue.  You may be running into the fact that if the host OS needs RAM (and you've only left 2.5GB for Unraid) it'll kill the VM to get it.  The fix is to add more RAM.  In general Unraid itself on V6 needs at least 4GB.

I have

 

CPU: Intel® Xeon® CPU E3-1230 v3 @ 3.30GHz

Memory: 4096 MB

 

and assigned 1.5Gb to the VM

 

(sorry for the delay)

 

karateo, you've not got much RAM, so I don't necessarily think this is the same issue.  You may be running into the fact that if the host OS needs RAM (and you've only left 2.5GB for Unraid) it'll kill the VM to get it.  The fix is to add more RAM.  In general Unraid itself on V6 needs at least 4GB.

 

I know I need more memory but it's difficult to find here in Greece

PC3-10600E Unbuffered DIMM ECC

 

Should't there be any log entry somewhere to make sure that it's this the cause?

Should't there be any log entry somewhere to make sure that it's this the cause?

It would be in the syslog (tools - diagnostics)