[SOLVED] Console is using SPICE instead of noVNC

larsen

Well-Known Member
Feb 28, 2020
160
19
58
Hello,

when opening a console of a VM, it used to open noVNC per default. Now, probably after the update from 7.1 to 7.2, PVE downloads a spice file "pve-spice.vv".

According to https://pve.proxmox.com/wiki/SPICE:
"Spice is not enabled by default. To enable it set the Display in the Hardware section of the VM to Spice"
VM display is set to "VirtIO-GPU", so SPICE should not be used afaiu.

I can manually open the noVNC console, but that is tedious compared to the above mentioned ways. I couldn't find a way to configure this in my personal settings.

Buggy? Feature? User error?
 
Sorry to revive this old thread, but this is still a problem.

I have a new Proxmox install (v8.4.1). I created a Windows 11 VM, it has been working fine. I spent some time testing and comparing the different Display hardware options (Standard VGA, VirtIO-GPU, VirGL-GPU, etc). They all worked fine and the console button opened in VNC.

Then I decided to try Spice. It didn't work very well and I didn't like it, so I reverted the config by removing all SPICE hardware (VGA, usb, audio). But now the main console button still tries to open with Spice when I have VirtIO-GPU or VirGL-GPU selected as display. Setting to "Standard VGA" makes the console button open in VNC, but VirtIO and VirGL still go to spice.

Setting Datacenter > Console Viewer to noVNC does work, but then my linux containers will also open in VNC instead of xterm.js (which is also not optimal). So, using "default" would be better, but something locked the VM into a Spice Console, even though I am not using spice there anymore.

I even tried creating a backup of the VM and restoring it into a new ID, but the results were the same. It still gives me a virt-viewer file download when I click in console. Any ideas? I didn't find anything that seems to be a problem in the VM config. Disabling spiceproxy also had no effect.

This is the VM config:
Code:
# cat /etc/pve/qemu-server/500.conf
agent: 1
audio0: device=ich9-intel-hda,driver=none
bios: ovmf
boot: order=scsi0;ide2;ide0;net0
cores: 12
cpu: host,flags=+hv-evmcs;+aes
efidisk0: storage:vm-500-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
ide0: storage-vz:iso/virtio-win-0.1.271.iso,media=cdrom,size=709474K
ide2: none,media=cdrom
machine: pc-q35-9.2+pve1,viommu=intel
memory: 16384
meta: creation-qemu=9.2.0,ctime=1748637966
name: Win11
net0: virtio=BC:24:11:6D:C0:6D,bridge=vmbr0,firewall=1
numa: 1
onboot: 1
ostype: win11
scsi0: storage:vm-500-disk-1,discard=on,iothread=1,size=120G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=87b0f439-b57b-4754-9ad7-dcc42e1d6846
sockets: 1
startup: order=10,up=2,down=2
tpmstate0: storage:vm-500-disk-2,size=4M,version=v2.0
vga: virtio,clipboard=vnc,memory=512
vmgenid: 95f73a95-5c8f-4c40-9f2a-a2be001deaa6

This is annoying me so much that I am considering reinstalling the whole thing (Proxmox and the VM) and then never touching anything "spice" ever again. Makes little sense.

EDIT: I also tried cleaning the browser cache and to using another browser and it has no effect.

EDIT2: I was able to pinpoint the problem and created a new thread explaining it here:
 
Last edited: