Been running into a number of issues with upgrading proxmox5.
Issue #1
- Update to latest proxmox5 and after the update the kvm_intel kernel module is not being loaded. I see a message like this when starting the VM.
Could not access KVM kernel module: No such file or directory
failed to initialize KVM: No such file or directory
If I run "modprobe kvm_intel" the VM will start until the next reboot. Everything was working as expected before the update.
To get away from this issue, I load the kvm_intel kernel module, then update-grub and update-initramfs -u. Reboot and everything seems ok. Sometimes I have to do this twice before it sticks. This has happened in prox4 -> prox5 and prox5 -> prox5 upgrades.
Issue #2
- Update to latest proxmox5 results in different kernel versions. In my test 3 node cluster I updated this morning, 2 nodes ended up with 4.13.13-5-pve and 1 node ended up with 4.13.13-4-pve.
root@testprox2:~# uname -r
4.13.13-4-pve
root@testprox2:~# apt-get update
Ign:1 http://ftp.us.debian.org/debian stretch InRelease
Hit:2 http://security.debian.org stretch/updates InRelease
Hit:3 http://ftp.us.debian.org/debian stretch Release
Hit:5 https://enterprise.proxmox.com/debian/pve stretch InRelease
Reading package lists... Done
root@testprox2:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Issue #1
- Update to latest proxmox5 and after the update the kvm_intel kernel module is not being loaded. I see a message like this when starting the VM.
Could not access KVM kernel module: No such file or directory
failed to initialize KVM: No such file or directory
If I run "modprobe kvm_intel" the VM will start until the next reboot. Everything was working as expected before the update.
To get away from this issue, I load the kvm_intel kernel module, then update-grub and update-initramfs -u. Reboot and everything seems ok. Sometimes I have to do this twice before it sticks. This has happened in prox4 -> prox5 and prox5 -> prox5 upgrades.
Issue #2
- Update to latest proxmox5 results in different kernel versions. In my test 3 node cluster I updated this morning, 2 nodes ended up with 4.13.13-5-pve and 1 node ended up with 4.13.13-4-pve.
root@testprox2:~# uname -r
4.13.13-4-pve
root@testprox2:~# apt-get update
Ign:1 http://ftp.us.debian.org/debian stretch InRelease
Hit:2 http://security.debian.org stretch/updates InRelease
Hit:3 http://ftp.us.debian.org/debian stretch Release
Hit:5 https://enterprise.proxmox.com/debian/pve stretch InRelease
Reading package lists... Done
root@testprox2:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Last edited:
