I am using VNC and sometimes I can see Windows starting up, but a few seconds, as different stages of Windows starting up before Windows fully loaded, the VNC connection suddenly dropped out and I lost the connection and the VM shows as "Stopped"

 

The only relevant message I can see from  qemu log is:

"shutting down, reason=crashed"

 

And here is the full log for today:

Quote

2021-12-09 07:18:00.696+0000: starting up libvirt version: 6.5.0, qemu version: 5.1.0, kernel: 5.10.28-Unraid, hostname: Tower
LC_ALL=C \
PATH=/bin:/sbin:/usr/bin:/usr/sbin \
HOME='/var/lib/libvirt/qemu/domain-27-Windows 10' \
XDG_DATA_HOME='/var/lib/libvirt/qemu/domain-27-Windows 10/.local/share' \
XDG_CACHE_HOME='/var/lib/libvirt/qemu/domain-27-Windows 10/.cache' \
XDG_CONFIG_HOME='/var/lib/libvirt/qemu/domain-27-Windows 10/.config' \
QEMU_AUDIO_DRV=none \
/usr/local/sbin/qemu \
-name 'guest=Windows 10,debug-threads=on' \
-S \
-object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-27-Windows 10/master-key.aes' \
-blockdev '{"driver":"file","filename":"/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \
-blockdev '{"driver":"file","filename":"/etc/libvirt/qemu/nvram/efba1d52-fbef-6bda-c1fa-046a5e8db2f2_VARS-pure-efi.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}' \
-machine pc-i440fx-5.1,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format \
-cpu host,migratable=on,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff,hv-vendor-id=none,host-cache-info=on,l3-cache=off \
-m 16896 \
-overcommit mem-lock=off \
-smp 10,sockets=1,dies=1,cores=5,threads=2 \
-uuid efba1d52-fbef-6bda-c1fa-046a5e8db2f2 \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=39,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=localtime \
-no-hpet \
-no-shutdown \
-boot strict=on \
-device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.0,addr=0x7 \
-device ahci,id=sata0,bus=pci.0,addr=0x4 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5 \
-blockdev '{"driver":"file","filename":"/mnt/user/domains/Windows 10/vdisk1.img","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \
-device virtio-blk-pci,bus=pci.0,addr=0x6,drive=libvirt-3-format,id=virtio-disk2,bootindex=1,write-cache=on \
-blockdev '{"driver":"file","filename":"/mnt/user/isos/Win10_21H1_EnglishInternational_x64.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \
-device ide-cd,bus=sata0.0,drive=libvirt-2-format,id=sata0-0-0,bootindex=2 \
-blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.185.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \
-device ide-cd,bus=sata0.1,drive=libvirt-1-format,id=sata0-0-1 \
-netdev tap,fd=41,id=hostnet0 \
-device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:1a:20:fb,bus=pci.0,addr=0x3 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=42,server,nowait \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device usb-tablet,id=input0,bus=usb.0,port=1 \
-vnc 0.0.0.0:3,websocket=5703 \
-k en-us \
-device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 \
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2021-12-09 07:18:00.696+0000: Domain id=27 is tainted: high-privileges
2021-12-09 07:18:00.696+0000: Domain id=27 is tainted: host-cpu
char device redirected to /dev/pts/3 (label charserial0)
2021-12-09 07:18:18.694+0000: shutting down, reason=crashed

 

The only reason I can think of is a power outrage a couple of weeks ago, the Unraid server was shut down and after that I probably never started the Windows VM, but the Unraid server itself seems fine and a couple of Linux VM started as normal.

 

So How do I got more diagnostic information about the reason for the Windows VM cannot start, can I somehow get more log, or the VM into the Windows recover mode?

 

Edited December 10, 20214 yr by pliu

It's getting more interesting: I tried to create a fresh Windows 10 VM, and almost exact same issue, I can go as far as the white spinner in the black screen, and as soon as it went into the blue screen ( I think is the initial setup screen for Windows installation) the VNC connection failed, and log showing the exact same entry "2021-12-09 08:06:46.128+0000: shutting down, reason=crashed". Nothing else.

Think I've found the issue:

 

Dec  8 08:52:00 Tower kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=vcpu0,mems_allowed=0,global_oom,task_memcg=/machine/qemu-26-Windows10.libvirt-qemu,task=qemu-system-x86,pid=15998,uid=0
Dec  8 08:52:00 Tower kernel: Out of memory: Killed process 15998 (qemu-system-x86) total-vm:18026704kB, anon-rss:12470132kB, file-rss:88kB, shmem-rss:22844kB, UID:0 pgtables:25496kB oom_score_adj:0

 

Looks like I've over-committed, too many testing VM's running. Kill a couple of extra ones and both the Windows one can started.

 

The mean kernel is ruthless!