[SOLVED] VM not starting after upgrading kernel and reboot - timeout waiting on systemd

[peteb]

On ZFS installation systemd-boot is in use for booting not grub. So as it turns out you can define the default boot entry by selecting the entry in the systemd-boot menu and hit "d" for default. Would have been nice to to see this in the wiki-page.

This is a really good solution. The only issue is that one needs to have access to the video out or IPMI of the server to set the default boot.
Would be better to have a method to make a default boot setting via SSH etc. in a running Proxmox environment.

 

[peteb]

I am new to Proxmox and facing the same issue. Any steps on how to rollback to the previous kernel version? Thanks.

The easiest option right now is to reboot the Proxmox server and select the previous kernel at boot - you need access to the vga out of the server or use IPMI. You can set the default boot in systemd-boot as above - using 'd' during boot - if you really need to have a default. If you have grub boot, then it is a different process to make it default.

I'm sure a fix will come out soon - then just upgrade. Meantime just choose previous kernel at boot.

 

[TorqueWrench]

I am new to Proxmox and facing the same issue. Any steps on how to rollback to the previous kernel version? Thanks.

If you're using ZFS, see @peteb comment (which it looks like you already have). If you're using the standard Proxmox install (not using ZFS), here's how to rollback a Proxmox kernel update with GRUB. It may or may not be easier to follow for someone new than @vale.maio2's post above. (Though I hope it is, since I wrote it!)

 

[eshrath]

The easiest option right now is to reboot the Proxmox server and select the previous kernel at boot - you need access to the vga out of the server or use IPMI. You can set the default boot in systemd-boot as above - using 'd' during boot - if you really need to have a default. If you have grub boot, then it is a different process to make it default.

I'm sure a fix will come out soon - then just upgrade. Meantime just choose previous kernel at boot.

I tried to select the previous kernel at boot, but there is no previous version. I believe this could be because of the fresh Proxmox installation I did yesterday. I added the Proxmox test repository and trying to upgrade to 5.15.

Thanks for taking time to respond. I really appreciate it.

 

[eshrath]

If you're using ZFS, see @peteb comment (which it looks like you already have). If you're using the standard Proxmox install (not using ZFS), here's how to rollback a Proxmox kernel update with GRUB. It may or may not be easier to follow for someone new than @vale.maio2's post above. (Though I hope it is, since I wrote it!)

Thank you TorqueWrench.

The article is super helpful. Since I do not have any previous kernel installed, (this is a fresh Proxmox install done yesterday), so not sure if I can use that option.

 

[TorqueWrench]

Thank you TorqueWrench.

The article is super helpful. Since I do not have any previous kernel installed, (this is a fresh Proxmox install done yesterday), so not sure if I can use that option.

You should be able to install an older kernel. This should work to install the last known working kernel (5.13.19-3-pve):

apt update && apt install pve-kernel-5.13.19-3-pve

Let me know how that works out for you.

 

[eshrath]

You should be able to install an older kernel. This should work to install the last known working kernel (5.13.19-3-pve):

apt update && apt install pve-kernel-5.13.19-3-pve

Let me know how that works out for you.

I could not

root@proxmox:~# apt update && apt install pve-kernel-5.13.19-3-pve
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://ftp.us.debian.org/debian bullseye InRelease                                                              
Hit:3 http://ftp.us.debian.org/debian bullseye-updates InRelease                                       
Hit:4 http://download.proxmox.com/debian/pve bullseye InRelease                 
Err:5 https://enterprise.proxmox.com/debian/pve bullseye InRelease              
  401  Unauthorized [IP: 144.217.225.162 443]
Reading package lists... Done                             
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease  401  Unauthorized [IP: 144.217.225.162 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

 

[TorqueWrench]

I could not

root@proxmox:~# apt update && apt install pve-kernel-5.13.19-3-pve
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://ftp.us.debian.org/debian bullseye InRelease                                                             
Hit:3 http://ftp.us.debian.org/debian bullseye-updates InRelease                                      
Hit:4 http://download.proxmox.com/debian/pve bullseye InRelease                
Err:5 https://enterprise.proxmox.com/debian/pve bullseye InRelease             
  401  Unauthorized [IP: 144.217.225.162 443]
Reading package lists... Done                            
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease  401  Unauthorized [IP: 144.217.225.162 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

That's a different error. Looks like you're trying to use the enterprise repo which is only available if you have a license.

It's been a while, but here's how I remember fixing that:

Use nano /etc/apt/sources.list.d/pve-enterprise.list and comment out the line there by adding a hashtag in front: #deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise

Then:
nano /etc/apt/sources.list.d/pve-no-subscription.list
And add in:
deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription
Save and retry the steps in my last post.

 

[coffeedragonfly]

The most recent update appears to have fixed my issues with the affected VMs, just FYI for anyone else looking to update.

 

[paulprox]

The most recent update appears to have fixed my issues with the affected VMs, just FYI for anyone else looking to update.

Did nothing for me, same issue. Had to boot with older kernel again

 

[cheriyan945]

Hi every one, does proxmox released any patch to fix this bug or still only the solution to roll back the previous kernel