Windows 10 VM blank console on PVE 6.x

[krikey]

I've just completed an upgrade of PVE from 5.x to 6.x and all went (mostly) smoothly. Thanks for the great help at https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0

I have a Windows 10 VM that was running on PVE5 before the upgrade and I was able to view the screen using the NoVNC console and also using RDP.

After the upgrade the WIndows 10 VM is still running and I can acess using RDP, but the NoVNC console simply shows a blank. I've tried a few keypresses to see if I can get it to spring to life but its still black. Any ideas?

 

[Moayad]

Hi,

did you tried a different browser?

also please post output of pveversion -v and VM config qm config <VMID>

 

[krikey]

Yes Ive tried Firefox and Google Chrome with the same results:

pveversion -v

proxmox-ve: 6.2-2 (running kernel: 5.4.60-1-pve)
pve-manager: 6.2-11 (running version: 6.2-11/22fb4983)
pve-kernel-5.4: 6.2-6
pve-kernel-helper: 6.2-6
pve-kernel-5.4.60-1-pve: 5.4.60-2
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
pve-kernel-4.15.18-27-pve: 4.15.18-55
pve-kernel-4.15.18-20-pve: 4.15.18-46
pve-kernel-4.15.17-1-pve: 4.15.17-9
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libpve-access-control: 6.1-2
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-2
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-6
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-12
pve-cluster: 6.1-8
pve-container: 3.2-1
pve-docs: 6.2-5
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-1
pve-qemu-kvm: 5.1.0-2
pve-xtermjs: 4.7.0-2
qemu-server: 6.2-14
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.4-pve1

qm config 108

bootdisk: sata0
cores: 4
cpulimit: 4
cpuunits: 512
memory: 4096
name: clevelandswin10
net0: e1000=12:10:AB:95:5E:5F,bridge=vmbr0,firewall=1,rate=13
numa: 0
onboot: 1
ostype: l26
sata0: local-lvm:vm-108-disk-0,size=50G
smbios1: uuid=99c33284-950b-4b3d-9580-8ad5f7756bc8
sockets: 1
vcpus: 4
vmgenid: 140c51c4-5b9c-4c40-8855-3b7490a612a9

 

[Moayad]

Only Windows VM have black screen or all?

please on Google Chrome hit Ctrl+Shift+J to open developer tools then go to Network tab and see if there any error

 

[krikey]

Only the Windows VM seems to have the black screen. Two other VMs (not LXCs) seem to be fine and display a command line prompt or a linux desktop as expected.

CTRL-SHIFT-J doesnt seem to work on the NoVNC window from within Chrome, but I was able to access the developer tools from Firefox. There was one error:

The Components object is deprecated. It will soon be removed.

but this also seems to be present on other NoVNC screens of working consoles too, so not sure that this is the issue.