[SOLVED] Kernel Update Problem?

[cshill]

Good Morning/Evening,

I try to keep Proxmox as up-to-date as possible and have to schedule out kernel update reboots with departments. I've been working on learning everything I can about Proxmox for months now and I think it works fine but I get a lot of pushback that it's "not VMware though," kind of speech. I have played with ESXI, XCP-NG, Hyper-V, and harvester.io, and I like Proxmox the most. The challenge comes down to these little things that keep popping up and Proxmox kind of gets shot in the crossfire when stuff happens.

My situation today is that I ran updates Proxmox updates, I'll provide my pveversion below. I rebooted the Proxmox server after updates, turned on the virtual machines, and the one with Ubuntu 22.04.5 was unable to boot as it could not find the HD0. In order to rectify this I set the VM in Proxmox>Options>OS Type>Linux 2.4 Kernel. I boot the VM and it was having challenges finding the HD0 still. I rebooted the VM into advanced options and changed the kernel to an older version (I don't recall the version) and it booted up.

From what I understand this is more of a challenge with the Ubuntu Server VM itself and not necessarily the change with the Proxmox Kernel.

PVEVersion

proxmox-ve: 8.3.0 (running kernel: 6.8.12-8-pve)
pve-manager: 8.3.5 (running version: 8.3.5/dac3aa88bac3f300)
proxmox-kernel-helper: 8.1.1
proxmox-kernel-6.8: 6.8.12-8
proxmox-kernel-6.8.12-8-pve-signed: 6.8.12-8
proxmox-kernel-6.8.12-6-pve-signed: 6.8.12-6
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph-fuse: 18.2.4-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2+deb12u1
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.5.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.2.0
libpve-network-perl: 0.10.1
libpve-rs-perl: 0.9.1
libpve-storage-perl: 8.3.3
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.3.3-1
proxmox-backup-file-restore: 3.3.3-1
proxmox-firewall: 0.6.0
proxmox-kernel-helper: 8.1.1
proxmox-mail-forward: 0.3.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.6
pve-cluster: 8.0.10
pve-container: 5.2.4
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-3
pve-ha-manager: 4.0.6
pve-i18n: 3.4.0
pve-qemu-kvm: 9.0.2-5
pve-xtermjs: 5.3.0-3
qemu-server: 8.3.8
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve1

This is not the screenshot I took but one that should help indicate the problem.

 

[Kingneutron]

> I get a lot of pushback that it's "not VMware though"

Your next comeback: " It's not Vmware PRICES, either! "

/ that oughtta shut them down

 

[cshill]

> I get a lot of pushback that it's "not VMware though"

Your next comeback: " It's not Vmware PRICES, either! "

/ that oughtta shut them down

That's the obvious one and I've been making it work but nothing is harder than bringing about change.

 

[cshill]

I'm pretty sure I found out it has nothing to do with Proxmox.

You are missing the initramfs for that kernel. Choose another kernel from the GRUB menu under Advanced options for Ubuntu and run sudo update-initramfs -u -k version to generate the initrd for version (replace version with the kernel version string such as 4.15.0-36-generic) then sudo update-grub.