[SOLVED] TASK ERROR: start failed: QEMU exited with code 1

[cdsJerry]

Important update: I restored a backup file created before the power failure. It will not start either. I'm now convinced that something in Proxmox has changed that's causing the VMs not to start since both this VM and the backup VM had been running fine. It looks like some sort of audio driver issue but I'm not sure how to fix it. I use a browser window to access the console and I believe that means I can't use the SPICE driver. Is that correct? I've tried adding the None - dummy device, which is the only other option. That didn't work.

I did find that I can start the VM normally on an old version of Proxmox (8.0.4) so I'm certain this has to do with a change in Proxmox. I just don't know how to fix it.

***************************

We had a power failure last night and exhausted our backup power as well. This morning I have on VM which won't start but the others all started fine. Proxmox was doing backups when the power failed however the VM that was currently being backed up at the time of the failure was a different VM and it started fine.

I have tried running qm unlock 108 command but the vm still will not start. Below is the information I think you'll need to assist me.

Task viewer: VM 108 - Start




OutputStatus



StopDownload



kvm: -device hda-micro,id=sound5-codec0,bus=sound5.0,cad=0: no default audio driver available
TASK ERROR: start failed: QEMU exited with code 1

journalctl -f
Dec 05 07:57:26 pve kernel: fwpr108p0 (unregistering): left allmulticast mode
Dec 05 07:57:26 pve kernel: fwpr108p0 (unregistering): left promiscuous mode
Dec 05 07:57:26 pve kernel: vmbr0: port 6(fwpr108p0) entered disabled state
Dec 05 07:57:26 pve pvedaemon[1481]: VM 108 qmp command failed - VM 108 not runn                                     ing
Dec 05 07:57:26 pve pvestatd[1461]: VM 108 qmp command failed - VM 108 not runni                                     ng
Dec 05 07:57:26 pve systemd[1]: 108.scope: Deactivated successfully.
Dec 05 07:57:26 pve systemd[1]: 108.scope: Consumed 3.250s CPU time.
Dec 05 07:57:26 pve pvedaemon[65366]: start failed: QEMU exited with code 1
Dec 05 07:57:26 pve pvedaemon[1480]: <root@pam> end task UPID:pve:0000FF56:00198                                     6F3:6751A332:qmstart:108:root@pam: start failed: QEMU exited with code 1
Dec 05 07:58:31 pve pvedaemon[1481]: <root@pam> successful auth for user 'root@p 


pveversion -v
proxmox-ve: 8.3.0 (running kernel: 6.8.12-4-pve)
pve-manager: 8.3.0 (running version: 8.3.0/c1689ccb1065a83b)
proxmox-kernel-helper: 8.1.0
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.8: 6.8.12-4
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
proxmox-kernel-6.8.12-2-pve-signed: 6.8.12-2
proxmox-kernel-6.8.8-4-pve-signed: 6.8.8-4
proxmox-kernel-6.8.8-2-pve-signed: 6.8.8-2
proxmox-kernel-6.8.4-3-pve-signed: 6.8.4-3
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
proxmox-kernel-6.5.13-6-pve-signed: 6.5.13-6
proxmox-kernel-6.5: 6.5.13-6
proxmox-kernel-6.5.13-5-pve-signed: 6.5.13-5
proxmox-kernel-6.5.13-1-pve-signed: 6.5.13-1
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.5.11-6-pve-signed: 6.5.11-6
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
proxmox-kernel-6.2.16-19-pve: 6.2.16-19
proxmox-kernel-6.2.16-18-pve: 6.2.16-18
proxmox-kernel-6.2.16-15-pve: 6.2.16-15
proxmox-kernel-6.2.16-12-pve: 6.2.16-12
proxmox-kernel-6.2.16-10-pve: 6.2.16-10
proxmox-kernel-6.2.16-8-pve: 6.2.16-8
proxmox-kernel-6.2.16-6-pve: 6.2.16-7
pve-kernel-6.2.16-5-pve: 6.2.16-6
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.2.0
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.10
libpve-cluster-perl: 8.0.10
libpve-common-perl: 8.2.9
libpve-guest-common-perl: 5.1.6
libpve-http-server-perl: 5.1.2
libpve-network-perl: 0.10.0
libpve-rs-perl: 0.9.0
libpve-storage-perl: 8.2.9
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.5.0-1
proxmox-backup-client: 3.2.9-1
proxmox-backup-file-restore: 3.2.9-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.3.1
pve-cluster: 8.0.10
pve-container: 5.2.2
pve-docs: 8.3.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.1.0
pve-firmware: 3.14-1
pve-ha-manager: 4.0.6
pve-i18n: 3.3.1
pve-qemu-kvm: 9.0.2-4
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.0
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1


root@pve:~# qm config 108
agent: 1
args: -device intel-hda,id=sound5,bus=pci.0,addr=0x18 -device hda-micro,id=sound5-codec0,bus=sound5.0,cad=0 -device hda-duplex,id=sound5-codec1,bus=sound5.0,cad=1
boot: order=virtio0;net0
cores: 4
cpu: host
memory: 8192
name: ShipWin10
net0: virtio=A6:EA:25:EC:E7:4E,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=c59ed2ea-93b6-4103-9694-d8af400845de
sockets: 1
usb0: host=1-1.5,usb3=1
virtio0: vmraid:vm-108-disk-0,cache=writeback,size=150G
vmgenid: c2ad35a5-d7b2-4706-8dc9-d249c85cdc67


root@pve:~# kvm --version
QEMU emulator version 9.0.2 (pve-qemu-kvm_9.0.2-4)
Copyright (c) 2003-2024 Fabrice Bellard and the QEMU Project developers

 

[cdsJerry]

I have been unable to find a solution. I'm assuming the VM won't start because of an audio driver issue created when I updated Proxmox but I don't know that for sure. I've tried several combinations of audio drivers which does change the error, but so far I haven't found anything that allows it to start.

I was going to create a new backup of the VM and try to launch it from a backup Proxmox server but I can't even create a new backup. I guess it has to start the VM to create the backup so I can't even use that as a patch until I figure out how to actually fix the VM problem with the current Proxmox version. So I'm up to "Plan C" but I don't have a Plan C because I hadn't planned for both Plan A and B to fail.

If someone knows step by step how to solve this Code 1 problem I'd sure appreciate some help. I see several people have had a similar problem but the solutions posted seem to vary and so far none of the ones I've tried have worked.

I have tried setting the display to Standard and removing the audio driver. -kvm: -device hda-micro,id=sound5-codec0,bus=sound5.0,cad=0: no default audio driver available

I tried Display to default - kvm: -device hda-micro,id=sound5-codec0,bus=sound5.0,cad=0: no default audio driver available

I tried Display to default - Audio device AC97, driver Spice -
kvm: Cannot use spice audio without -spice

I tried adding an Audio Device ich9-intel-hda with Backend driver None -
kvm: -device hda-micro,id=sound5-codec0,bus=sound5.0,cad=0: no default audio driver available
Perhaps you wanted to use -audio or set audiodev=none-backend0?

I tried setting Display to Spice(qxl) and Audio device to ich9-intel-hda None -
kvm: -device hda-micro,id=sound5-codec0,bus=sound5.0,cad=0: no default audio driver available
Perhaps you wanted to use -audio or set audiodev=none-backend0?

I tried Display to Spice(qxl) and Audio Device to AC97 None-
kvm: -device hda-micro,id=sound5-codec0,bus=sound5.0,cad=0: no default audio driver available
Perhaps you wanted to use -audio or set audiodev=none-backend0?

I tried Display to Spice(qxl) and Audio Device to ich9-intel-hda, driver Spice -
kvm: -device hda-micro,id=sound5-codec0,bus=sound5.0,cad=0: no default audio driver available
Perhaps you wanted to use -audio or set audiodev=spice-backend0?

 

[cdsJerry]

I received help from Proxmox support and it worked. I'm posting their solution here because I've seen so many others with the same problem. One note: I don't need audio on this system. This solution worked.

In my case the VM with the issue was VM 108

***************************************
Please use SSH (or go to the web console of your PVE node) and move into the directory where the VM configs are located:

cd /etc/pve/qemu-server/


Make a copy of your VM config 108:

cp 108.conf 108.conf.bu


Then edit the VM config:

edit 108.conf


Since you do not really need audio at the moment, remove these two lines:

args: -device intel-hda,id=sound5,bus=pci.0,addr=0x18 -device hda-micro,id=sound5-codec0,bus=sound5.0,cad=0 -device hda-duplex,id=sound5-codec1,bus=sound5.0,cad=1
audio0: device=AC97,driver=spice


After that, save the file and try to start the VM:

qm start 108