VMs not booting anymore

___sKo___

New Member
Dec 6, 2024
1
0
1
Hi all,

today I logged in my local pve istance via web console to test some procedures and all my VMs aren't booting.

These are the only log rows I found with # journalctl:
Jan 17 15:25:29 ipipve001 pvedaemon[52568]: start VM 105: UPID:ipipve001:0000CD58:000F22C6:678A6859:qmstart:105:root@pam:
Jan 17 15:25:29 ipipve001 pvedaemon[1144]: <root@pam> starting task UPID:ipipve001:0000CD58:000F22C6:678A6859:qmstart:105:root@pam:
Jan 17 15:25:30 ipipve001 systemd[1]: Started 105.scope.
Jan 17 15:25:31 ipipve001 pvedaemon[52575]: stopping swtpm instance (pid 52583) due to QEMU startup error
Jan 17 15:25:31 ipipve001 systemd[1]: 105.scope: Deactivated successfully.
Jan 17 15:25:31 ipipve001 systemd[1]: 105.scope: Consumed 1.381s CPU time.
Jan 17 15:25:31 ipipve001 pvedaemon[52568]: start failed: QEMU exited with code 1
Jan 17 15:25:31 ipipve001 pvedaemon[1144]: <root@pam> end task UPID:ipipve001:0000CD58:000F22C6:678A6859:qmstart:105:root@pam: start failed: QEMU exited with code 1

I can't find any hint about the problem, maybe someone here can help me to find a solution.

thanks!
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!