My VMs can't boot after shutdown AFTER UPDATE FOR 7.3.3

Nov 22, 2021
48
0
11
44

After I shutdown a VM it won't boot again if I don't restart the server. No idea where or how to look for a solution.​


Before update version 7.3.3
 
Hi,

please post the configuration of your VM (qm config xyz). Do you see any errors when trying to start the VM? Is there anything noteworthy in the syslog? Starting it over the command line (qm start xyz) might also provide you with some additional output.
 
root@ORACULO:~# qm config 103
agent: 1
boot: order=sata0
cores: 4
cpu: host
ide2: none,media=cdrom
memory: 4096
meta: creation-qemu=6.2.0,ctime=1660485287
name: VIDEO
net0: virtio=9E:2D:00:BA:03:92,bridge=vmbr2,firewall=1
numa: 0
ostype: l26
sata0: HD-VMs-1:103/vm-103-disk-0.qcow2,size=1T
scsihw: virtio-scsi-pci
smbios1: uuid=632b2ce9-5905-4d1f-8eb3-297699501e30
sockets: 4
startup: order=7,up=200
vmgenid: 423f8aa7-d9d3-4bb9-9df1-73eb6ca21701
root@ORACULO:~#

After update for version 7.3.3, my VMs dont start anymore..

Message: No bootable disk found.
 
Could you post the full output of pveversion -v? Preferably inside [CODE][/CODE] tags. What version did you upgrade from?
 
Could you post the full output of pveversion -v? Preferably inside [CODE][/CODE] tags. What version did you upgrade from?
Hi, look:

root@ORACULO:~# pveversion -v
proxmox-ve: 7.3-1 (running kernel: 5.15.74-1-pve)
pve-manager: 7.3-3 (running version: 7.3-3/c3928077)
pve-kernel-5.15: 7.2-14
pve-kernel-helper: 7.2-14
pve-kernel-5.4: 6.4-19
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.15.64-1-pve: 5.15.64-1
pve-kernel-5.4.195-1-pve: 5.4.195-1
ceph-fuse: 14.2.21-1
corosync: 3.1.7-pve1
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.24-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-1
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.3-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.3.1-1
proxmox-backup-file-restore: 2.3.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.0-1
proxmox-widget-toolkit: 3.5.3
pve-cluster: 7.3-1
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.5-6
pve-ha-manager: 3.5.1
pve-i18n: 2.8-1
pve-qemu-kvm: 7.1.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-1
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1
root@ORACULO:~#
 
Look, if I install a new Ubuntu Linux VM, then yes, it can boot normally.

That is, I lost my other VM, it does not boot at all after I updated to PROXMOX 7.3.3

All my Linux VMs won't boot anymore.

But if I install a new VM, it boots normally.

I've never really seen this happen on PROXMOX.
 
That does sound strange. I would maybe try comparing the configuration files of a VM that works (i.e., one that you newly created) and one that doesn't work, and try to see if there's any noticeable differences.
What version did you upgrade from?
?
 
That does sound strange. I would maybe try comparing the configuration files of a VM that works (i.e., one that you newly created) and one that doesn't work, and try to see if there's any noticeable differences.

?
don't remember exactly which version it was, otherwise I'm mistaken it was the penultimate version.

I already did that, I compared a VM that is OK, with the one that doesn't boot anymore, but the two are identical.
 
hello guys, another VM stopped working.
it dawned stuck, so I had to run the kill -9 command on the VM service to force it to stop.

and now when I start it, the boot says that there is no disk to boot.

wow, I'm getting discouraged from this PROXMOX, for so many years it ran very well, now these constant Updates are always causing problems and I'm seriously thinking about going back to Hyper-V.

The VM that stopped working is now a Windows Server.

Before this problem only happened with Linux, so the only solution I had was to reinstall the Linux VM and reconfigure everything, now the Windows VM has the same problem....
 
I have 18 Windows VMs, I'm now desperate if they restart and then don't boot anymore....

ended my Christmas and New Year this PROXMOX.
 
* anything in the journal of your proxmox machine which might give a hint at what the issue is?
That is, I lost my other VM, it does not boot at all after I updated to PROXMOX 7.3.3
what happens when you try to start such a machine - maybe a screenshot or (if possible preferred) a text dump of what's printed on the console?
 
* anything in the journal of your proxmox machine which might give a hint at what the issue is?

what happens when you try to start such a machine - maybe a screenshot or (if possible preferred) a text dump of what's printed on the console?
Look here, I recorded the screen for you to see the error.

I thought it was only happening with Linux VMs, but now I see that with Windows VMs too.

And I don't know where to read the logs to see what this error is.

https://www.youtube.com/watch?v=gk2prYCH2gE
 
One thing I'm fixing right now.

In a newly created VM, in HARDWARE in the MACHINE config it is like MACHINE= q35

And on VMs that are older than PROXMOX 7.3.3 the MACHINE field is pc-q35-7.0

But I can't switch to LATEST (this LATEST option only appears for the new VMs I installed after I updated the server)
 
Windows-VMs do not have the option "Latest" for the machine-type, but Linux-VMs do have. This is intended.

But not sure, what this now should have to do with your vdisk problem...
 

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!