Clean install of Win10 Pro - latest ISO from Microsoft

 

All installs OK, activates, drivers on correctly, done a few reboots to make sure its all good. 

 

Then after about 10 mins of leaving it, i cant reconnect to it - the VNC session disconnects, and i cant ping it, or connect by RDP or anything - the only thing i can do is force restart it. It then stays ok for a bit, then carries on

 

My VM Log is below, and i keep getting these qemu-system-x86_64: warning: guest updated active QH at the end, which im guessing is the problem. 

 

I thought there were problems with how i built the VM, as this started when i built my first yesterday, so i trashed it, rebuilt it, and its still the same 

 

Any ideas?

thanks

 

-no-hpet \
-no-shutdown \
-boot strict=on \
-device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 \
-drive 'file=/mnt/cache/vms/Windows 10/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback' \
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1,write-cache=on \
-drive file=/mnt/user/isos/Win10_1903_V2_English_x64.iso,format=raw,if=none,id=drive-ide0-0-0,readonly=on \
-device ide-cd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=2 \
-drive file=/mnt/user/isos/virtio-win-0.1.160-1.iso,format=raw,if=none,id=drive-ide0-0-1,readonly=on \
-device ide-cd,bus=ide.0,unit=1,drive=drive-ide0-0-1,id=ide0-0-1 \
-netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=29 \
-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:1b:f5:e4,bus=pci.0,addr=0x3 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=30,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:1,websocket=5701 \
-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=0x6 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2019-10-24 10:09:56.697+0000: Domain id=13 is tainted: high-privileges
2019-10-24 10:09:56.697+0000: Domain id=13 is tainted: host-cpu
char device redirected to /dev/pts/1 (label charserial0)
2019-10-24T10:18:01.221797Z qemu-system-x86_64: warning: guest updated active QH
2019-10-24T10:22:00.463133Z qemu-system-x86_64: warning: guest updated active QH
2019-10-24T10:23:17.937838Z qemu-system-x86_64: warning: guest updated active QH
2019-10-24T10:41:25.024489Z qemu-system-x86_64: warning: guest updated active QH
2019-10-24T10:43:24.756554Z qemu-system-x86_64: warning: guest updated active QH
2019-10-24T10:48:45.270993Z qemu-system-x86_64: warning: guest updated active QH
2019-10-24T10:49:44.660416Z qemu-system-x86_64: warning: guest updated active QH
2019-10-24T10:50:05.738320Z qemu-system-x86_64: warning: guest updated active QH
2019-10-24T10:50:26.487107Z qemu-system-x86_64: warning: guest updated active QH
2019-10-24T11:00:09.811881Z qemu-system-x86_64: warning: guest updated active QH

 

VM is on a 500gb NVME drive, and 36gb used of the disk, so loads of space left. 

 

i created a 50GB disk, and looking on the windows VM, 31.5gb free

further update, i can get it to happen when i disconnect a VNC session, as soon as i try to reconnect - no good

when this happens, i don't have the qemu-system-x86_64: warning: guest updated active QH at the end in the VM log...

@rorton Did you tried to change the Windows power settings from balanced to performance? I've not had the exact same error as you in the past, but with the balanced power plan after some idle time windows falls a sleep for me and couldn't wake up again. Can't tell you which version of Windows I was on back than, but changing to performance solved my issue.

hi, thanks for the reply - yep ,ive set to performance, turned off all traces of sleep/suspend 

 

Sometimes, when i boot i just cant get onto the system at all, other times i can, then it just stops responding to connections. 

 

interestingly, it may well be the vnc 

 

Ive just enabled remote desktop, disconnected my VNC session, tried to reconnect the vnc session, and failed 

 

used remote desktop, and im straight in - so the vm is up n running. 

 

Im using a mac to connect, and tried using chicken of the vnc - didn't work at all, VNC Viewer, iTeleport 

Strange. In general VNC connection errors via the web-vnc unraid comes with are really rare. I think one of the latest 6.8 RC versions some people reported having some issues with the web-vnc not connecting. Which version of Unraid you're on?

yeah odd - im running stable 6.72 at the moment. 

Did you installed the qxl driver for the gpu by hand? On default Win10 uses a basic driver and shows "basic graphics adapter" in the device manager without errors. Try to install the driver for the GPU from the virtio iso.

 

i also have a centos VM running, and that seems fine, tbh i never need the VNC connect to the centos, but every time i try the vnc connection, its perfectly fine, it just seems to be to this windows 10 vm

 

Just now, bastl said:

Did you installed the qxl driver for the gpu by hand? On default Win10 uses a basic driver and shows "basic graphics adapter" in the device manager without errors. Try to install the driver for the GPU from the virtio iso.

 

posting at the same time

 

Yeah, i installed the driver from the QXLDOD directory, im sure when i was trying to get these going first, i tried the 'normal' QXL directory, and that caused the machine not to work (unless it was the same symptoms)

 

 

Could be the default driver from windows causing this. Each version of windows indroduced lots of changes and new bugs. Might be you have an iso that comes with errors or has some corrupted files on it. Wouldn't be the first time I'am seeing this from Microsoft 😂

 

I had a freshly 1903 iso downloaded with the creation tool from microsoft which for f*** sake won't boot. Redownloaded the file the same day with the same tool and it worked. Same size, different hash. If you have an older iso which worked in the past, try this.

Could be also possible the browser you are using causing this.

1 minute ago, bastl said:

Could be the default driver from windows causing this. Each version of windows indroduced lots of changes and new bugs. Might be you have an iso that comes with errors or has some corrupted files on it. Wouldn't be the first time I'am seeing this from Microsoft 😂

 

I had a freshly 1903 iso downloaded with the creation tool from microsoft which for f*** sake won't boot. Redownloaded the file the same day with the same tool and it worked. Same size, different hash. If you have an older iso which worked in the past, try this.

good call - will try 

 

Just now, bastl said:

Could be also possible the browser you are using causing this.

im using a fat client for the vnc, browser doesn't work at all

Still no better  i re-downloaded the ISO from Microsoft (oddly it was version 1809Oct_v2 where as i was using 1903_v2)

 

I also downloaded what seem to be the latest VirtIO drivers (0.1.171) but still the same problem

 

Build the machine, works fine, disconnect the vnc, and then the vnc won't recount, but the machine is accessible via RDP

 

 

Did you ever figure out what was causing this problem? I am having the very same problem.

On 10/16/2021 at 4:48 PM, clambert said:

Did you ever figure out what was causing this problem? I am having the very same problem.

Hi clambert,

the message

warning: guest updated active QH

is related to the free disk space for the VM's image.

It has been discussed here: https://forums.unraid.net/topic/55391-solved-vm-is-always-paused/?do=findComment&comment=542810

In my case I had no free disk space for the "raw" image on BTRFS filesystem. I increased disk capacity and now it seems to be OK.