VM won't start after upgrade to 7.1 from latest 7.0

[Polyphemus]

Hi all,

I'm quite new to Proxmox so please bear with me.

I'm running a couple of LXCs and a couple of VMs. After upgrading to 7.1 from the latest 7.0 this morning, my Home Assistant VM refuses to keep running for longer than 30 seconds because of the following error:

Nov 18 13:41:08 pve pvestatd[1139]: VM 106 qmp command failed - VM 106 qmp command 'query-proxmox-support' failed - unable to connect to VM 106 qmp socket - timeout after 31 retries

The VM runs a couple of seconds and then connection is lost. I have to kill the VM process to get it stopped.

I also see that my Coral mini-PCIe card, which I'm passing through the VM does not work anymore in the VM (maybe it's related).

apex ram did not enable within timeout (12000ms)

root@pve:~# qm config 106
agent: 1
balloon: 0
bios: ovmf
boot: order=sata0
cores: 1
cpu: kvm64
efidisk0: SSD1TB:106/vm-106-disk-0.qcow2,size=128K
hostpci0: 0000:02:00.0
memory: 5120
name: haosova-6.6
net0: virtio=32:E3:A8:91:63:DE,bridge=vmbr1,firewall=1
numa: 0
ostype: l26
sata0: SSD1TB:106/vm-106-disk-1.qcow2,size=160G
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=0dfba893-733f-4db4-b386-337a0e9f63a4
sockets: 3
usb1: host=0451:bef3
vga: virtio
vmgenid: 2b7a8f06-195d-4789-838b-ad7cb2d64070

root@pve:~# pveversion -v
proxmox-ve: 7.1-1 (running kernel: 5.13.19-1-pve)
pve-manager: 7.1-5 (running version: 7.1-5/6fe299a0)
pve-kernel-5.13: 7.1-4
pve-kernel-helper: 7.1-4
pve-kernel-5.11: 7.0-10
pve-kernel-5.4: 6.4-4
pve-kernel-5.13.19-1-pve: 5.13.19-2
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.4.124-1-pve: 5.4.124-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-3
libpve-storage-perl: 7.0-15
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.14-1
proxmox-backup-file-restore: 2.0.14-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.4-2
pve-cluster: 7.1-2
pve-container: 4.1-2
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-1
pve-qemu-kvm: 6.1.0-2
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-3
smartmontools: 7.2-pve2
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3

It now just hangs on the word "Autoboot" in the console...

Please help? Thank you.

 

[Polyphemus]

I just reduced the numbers of vCPU's from 3 to 1 and the type from host to KVM64 for the VM, and it runs fairly stable right now... I just do need the vCPU type of host...

 

[rekordskratch]

Having the same issue but KVM64 vs host didn't seem to make any difference. With the vCPU set to 1 it has been stable so far. I noticed some updates waiting for Homeassistant OS so will apply those and see if it makes any difference

 

[Polyphemus]

Having the same issue but KVM64 vs host didn't seem to make any difference. With the vCPU set to 1 it has been stable so far. I noticed some updates waiting for Homeassistant OS so will apply those and see if it makes any difference

I've found in another topic that you have to reconfigure the SATA interface:

https://forum.proxmox.com/threads/some-vms-arent-booting-after-upgrade-to-7-1.100039/#post-431853

That worked for my Home Assistant OS VM. And while I was at it, I changed the virtual drive adapter from SATA to VirtIO SCSI too.

 

[rekordskratch]

Thanks that seems to have done the trick. Back to my normal vCPU and hardware setup and running stable for a few hours now