[SOLVED] pve-qemu-kvm (2.11.1-3) breaks VMs

[Mindbang]

Hi folks,
I'm using proxmox on my personal rig with a couple of Windows and Linux VMs. I have an NVIDIA graphic card passed through to most of them. Things are working flawlessly - I've had this setup for almost two years now.

Since the latest pve-qemu-kvm (2.11.1-3) none of the VMs start anymore - neither Linux, nor Windows. They all get stuck on the bootup screen. The issue is easily reproducible for me - if I downgrade to "2.9.1-9" things are working again. When I update to "2.11.1-3" things are broken.


Usually I'm able to triage those kinds of issues by myself, but I do not find any hints as to where the issue might come from (nothing in logs - maybe I'm just blind and I missed something). Can you guys give me some pointers as to where I should look?

root@root ~ # pveversion -v
proxmox-ve: 5.1-41 (running kernel: 4.13.13-6-pve)
pve-manager: 5.1-47 (running version: 5.1-47/97a08ab2)
pve-kernel-4.13.13-6-pve: 4.13.13-41
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-4-pve: 4.13.13-35
pve-kernel-4.13.13-2-pve: 4.13.13-33
pve-kernel-4.13.4-1-pve: 4.13.4-26
pve-kernel-4.10.17-4-pve: 4.10.17-24
pve-kernel-4.10.17-2-pve: 4.10.17-20
pve-kernel-4.10.17-1-pve: 4.10.17-18
pve-kernel-4.10.15-1-pve: 4.10.15-15
pve-kernel-4.10.11-1-pve: 4.10.11-9
pve-kernel-4.10.8-1-pve: 4.10.8-7
pve-kernel-4.4.35-1-pve: 4.4.35-76
ceph: 12.2.4-pve1
corosync: 2.4.2-pve3
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-28
libpve-guest-common-perl: 2.0-14
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-17
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 2.1.1-3
lxcfs: 2.0.8-2
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-12
pve-cluster: 5.0-21
pve-container: 2.0-19
pve-docs: 5.1-16
pve-firewall: 3.0-5
pve-firmware: 2.0-3
pve-ha-manager: 2.0-5
pve-i18n: 1.0-4
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.9.1-9
pve-xtermjs: 1.0-2
qemu-server: 5.0-23
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.6-pve1~bpo9

Example pve config

agent: 1
balloon: 0
bios: ovmf
bootdisk: virtio0
cores: 6
efidisk0: local-lvm:vm-102-disk-2,size=4M
hostpci0: 02:00.0,pcie=1,x-vga=on
hostpci1: 00:14.0
hostpci2: 02:00.1
hostpci3: 00:1b.0
machine: q35
memory: 16384
name: work
net0: virtio=22:9B:B5:C0:8F:1B,bridge=vmbr0
numa: 0
ostype: win10
parent: everything_working_2017
scsihw: virtio-scsi-pci
smbios1: uuid=a2772030-25cb-4898-a77e-c4ddf63c773f
sockets: 1
virtio0: local-lvm:vm-102-disk-1,cache=writeback,size=256G

 

[Mindbang]

Does anybody have any suggestions as to how I could approach debugging this?

 

[tom]

Does anybody have any suggestions as to how I could approach debugging this?

Its a known issue with the current packages in our pvetest repository. Will be fixed in one of the upcoming package uploads.

 

[Mindbang]

Thanks, @tom . Is there a tracker that I could follow?

 

[tom]

See https://bugzilla.proxmox.com/show_bug.cgi?id=1687

 

[Mindbang]

Thank you so much!