ARM64 VM startet nicht mehr unter ProxMox9

[logopk]

Hallo,

ich habe eine debian bookworm arm64 VM, die unter Proxmox 8 tadellos startete.

Nun bekomme ich immer die Fehlermeldung

qemu-system-aarch64: Property 'virt-10.1-machine.hpet' not found
TASK ERROR: start failed: QEMU exited with code 1

Offenbar erzeugt proxmox beim Start immer das falsche inkompatible Kommando:

/usr/bin/qemu-system-aarch64 -id 122 -name 'debian-arm64,debug-threads=on' -no-shutdown -chardev 'socket,id=qmp,path=/var/run/qemu-server/122.qmp,server=on,wait=off' -mon 'chardev=qmp,mode=control' -chardev 'socket,id=qmp-event,path=/var/run/qmeventd.sock,reconnect-ms=5000' -mon 'chardev=qmp-event,mode=control' -pidfile /var/run/qemu-server/122.pid -daemonize -smbios 'type=1,uuid=8b1daf91-09c5-4c78-97df-153675939810' -object '{"id":"throttle-drive-efidisk0","limits":{},"qom-type":"throttle-group"}' -blockdev '{"driver":"raw","file":{"driver":"file","filename":"/usr/share/pve-edk2-firmware//AAVMF_CODE.fd"},"node-name":"pflash0","read-only":true}' -blockdev '{"detect-zeroes":"on","discard":"ignore","driver":"throttle","file":{"cache":{"direct":false,"no-flush":false},"detect-zeroes":"on","discard":"ignore","driver":"raw","file":{"aio":"io_uring","cache":{"direct":false,"no-flush":false},"detect-zeroes":"on","discard":"ignore","driver":"host_device","filename":"/dev/vmdata2/vm-122-disk-0","node-name":"eb559b7dd06a05b6b16c60a8917b6ec","read-only":false},"node-name":"fb559b7dd06a05b6b16c60a8917b6ec","read-only":false,"size":67108864},"node-name":"drive-efidisk0","read-only":false,"throttle-group":"throttle-drive-efidisk0"}' -smp '2,sockets=1,cores=2,maxcpus=2' -nodefaults -boot 'menu=on,strict=on,reboot-timeout=1000,splash=/usr/share/qemu-server/bootsplash.jpg' -nographic -cpu max -m 2048 -object '{"id":"throttle-drive-scsi0","limits":{},"qom-type":"throttle-group"}' -global 'PIIX4_PM.disable_s3=1' -global 'PIIX4_PM.disable_s4=1' -device 'pci-bridge,id=pci.1,chassis_nr=1,bus=pcie.0,addr=0x1e' -device 'pci-bridge,id=pci.2,chassis_nr=2,bus=pcie.0,addr=0x1f' -device 'usb-ehci,id=ehci,bus=pcie.0,addr=0x1' -chardev 'socket,id=serial0,path=/var/run/qemu-server/122.serial0,server=on,wait=off' -serial chardev:serial0 -chardev 'socket,path=/var/run/qemu-server/122.qga,server=on,wait=off,id=qga0' -device 'virtio-serial,id=qga0,bus=pcie.0,addr=0x8' -device 'virtserialport,chardev=qga0,name=org.qemu.guest_agent.0' -device 'virtio-balloon-pci,id=balloon0,bus=pcie.0,addr=0x3,free-page-reporting=on' -iscsi 'initiator-name=iqn.1993-08.org.debian:01:c5d7d1eae5c1' -device 'virtio-scsi-pci,id=scsihw0,bus=pcie.0,addr=0x5' -blockdev '{"detect-zeroes":"on","discard":"ignore","driver":"throttle","file":{"cache":{"direct":true,"no-flush":false},"detect-zeroes":"on","discard":"ignore","driver":"raw","file":{"aio":"io_uring","cache":{"direct":true,"no-flush":false},"detect-zeroes":"on","discard":"ignore","driver":"host_device","filename":"/dev/vmdata2/vm-122-disk-1","node-name":"ea499402fb158a2ea3bea8963fc3e95","read-only":false},"node-name":"fa499402fb158a2ea3bea8963fc3e95","read-only":false},"node-name":"drive-scsi0","read-only":false,"throttle-group":"throttle-drive-scsi0"}' -device 'scsi-hd,bus=scsihw0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0,id=scsi0,device_id=drive-scsi0,bootindex=101,write-cache=on' -device 'scsi-cd,bus=scsihw0.0,channel=0,scsi-id=0,lun=1,id=scsi1,device_id=drive-scsi1,bootindex=100' -netdev 'type=tap,id=net0,ifname=tap122i0,script=/usr/libexec/qemu-server/pve-bridge,downscript=/usr/libexec/qemu-server/pve-bridgedown' -device 'virtio-net-pci,mac=9A:51:AC:47:C6:67,netdev=net0,bus=pcie.0,addr=0x12,id=net0,rx_queue_size=1024,tx_queue_size=256,bootindex=102,host_mtu=1500' -machine 'pflash0=pflash0,pflash1=drive-efidisk0,hpet=off,accel=tcg,type=virt+pve0'

Wenn ich in der CLI

hpet=off

entferne, startet die VM. Bis auf die folgenden Warnungen:

qemu-system-aarch64: warning: global PIIX4_PM.disable_s3 has invalid class name
qemu-system-aarch64: warning: global PIIX4_PM.disable_s4 has invalid class name

Die Konfiguration ist:

agent: 1
arch: aarch64
bios: ovmf
boot: order=scsi1;scsi0;net0
cores: 2
cpu: max
machine: virt
efidisk0: SSD-Extension-lvm:vm-122-disk-0,efitype=4m,pre-enrolled-keys=1,size=64M
memory: 2048
meta: creation-qemu=7.2.0,ctime=1689347817
name: debian-arm64
net0: virtio=9A:51:AC:47:C6:67,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: SSD-Extension-lvm:vm-122-disk-1,size=32G
scsi1: none,media=cdrom
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=8b1daf91-09c5-4c78-97df-153675939810
sockets: 1
tags: debian;tryout
vga: serial0

Damit das überhaupt funktionierte, musste ich in Proxmox 9

machine: virt
cpu: max

hinzufügen.

Weiß jemand, wo das Problem herkommt und wie man es dauerhaft ohne manuelles Starten lösen kann?

Danke!

Peter

 

[fschauer]

Wenn ich in der CLI
hpet=off entferne, startet die VM.

Danke für den Hinweis. Das sieht nach einem Bug in qemu-server.git:src/PVE/QemuServer/Cfg2Cmd/Timer.pm aus, da HPET auf Arm nicht existiert.
Könntest du bitte einen Bug Report dazu unter https://bugzilla.proxmox.com/ erstellen

Als Workaround sollte es daweil mit ostype: other funktionieren.