You need to add the test repository first.Hello,
Any steps or instructions to update to 5.15?
Below steps doesn't work for me, as the 'apt' is not able to find the kernel version.
apt update
apt install pve-kernel-5.15
You need to add the test repository first.Hello,
Any steps or instructions to update to 5.15?
Below steps doesn't work for me, as the 'apt' is not able to find the kernel version.
apt update
apt install pve-kernel-5.15
The apt update and install should be enough.It's not required to enable thepvetest
repository, the opt-in kernel package is available on all repositories.
Thank you Dunuin.You need to add the test repository first.
Loading Linux 5.15.19-1-pve
Loading initial ramdisk.....
UBSAN: array-index-out-of-bounds in drivers/scsi/megaraid/megaraid_sas_fp.c:103:32
[ 1.672599] index 1 is out of range for type 'MR_LD_SPAN_MAP [1]'
Sound like problems with the raid drivers of the 5.15 kernel:
https://www.mail-archive.com/linux-scsi@vger.kernel.org/msg80296.html
It's never like this. You're just seeing an unfortunate series of events as you're onboarding. I've been using Proxmox for 2+ years without issue. Major VE changes might occasionally have an issue (I do seem to recall an issue with PCI passthrough back during one of the major or minor PVE 6.x updates), but they're not usually breaking changes like this.You are very famous member and should be using Proxmox for few months. I am about to use Proxmox for some of my work related to Homelab, Home Automation, NAS, Media Server etc..
I am facing issues after one another in the last couple of week with Proxmox, getting VMs, setting up zfs, getting NAS server up, installing windows etc..
Is this how it usually is? I am reconsidering my decision to use Proxmox and wanted to evaluate any other similar products.
Can you please share your Proxmox experiences?
Thanks,
Jup. Its hard to setup everything right but when its running it is rock solid...even if you just use the no-subscription repository. Community support is great and when bugs are reported they are usually fixed within a few days or even hours. But if your uptime is important its always a good idea to get a subscription to be able to access the enterprise repository. Its always some weeks behind and therefore better tested, because bugs hit the no-subscription repo users first, they complain about them and bugs get fixed before the update gets added to the enterprise repo.It's never like this. You're just seeing an unfortunate series of events as you're onboarding. I've been using Proxmox for 2+ years without issue. Major VE changes might occasionally have an issue (I do seem to recall an issue with PCI passthrough back during one of the major or minor PVE 6.x updates), but they're not usually breaking changes like this.
Don't let this scare you off. I still think Proxmox is the best tool for the job, if for no other reason than its backend stack of KVM/qemu. With other hypervisors, you start to run into the territory of closed source and a lack of community support.
That's very encouraging to hear. We learn from the experiences and when the community helps from their learnings, its really good.It's never like this. You're just seeing an unfortunate series of events as you're onboarding. I've been using Proxmox for 2+ years without issue. Major VE changes might occasionally have an issue (I do seem to recall an issue with PCI passthrough back during one of the major or minor PVE 6.x updates), but they're not usually breaking changes like this.
Don't let this scare you off. I still think Proxmox is the best tool for the job, if for no other reason than its backend stack of KVM/qemu. With other hypervisors, you start to run into the territory of closed source and a lack of community support.
Today morning one of the user creating a ticket and within few minutes, one of the staff member acknowledging the PCI passthrough issues. Thanks for helping out.Jup. Its hard to setup everything right but when its running it is rock solid...even if you just use the no-subscription repository. Community support is great and when bugs are reported they are usually fixed within a few days or even hours. But if your uptime is important its always a good idea to get a subscription to be able to access the enterprise repository. Its always some weeks behind and therefore better tested, because bugs hit the no-subscription repo users first, they complain about them and bugs get fixed before the update gets added to the enterprise repo.
I really like that everything is transparent. You can watch the mailing list, watch the progress in the bug tracker and the staff is also reporting back in the forums and point to the updates/patches after the bug is fixed.
FYI: That's a backport request from 2019, that patch is in our kernels since ages, i.e., here the link to the commit in our 5.13/impish kernel mirror:Sound like problems with the raid drivers of the 5.15 kernel:
https://www.mail-archive.com/linux-scsi@vger.kernel.org/msg80296.html
root@pve:~# apt update
Get:1 http://download.proxmox.com/debian/pve bullseye InRelease [3,053 B]
Hit:2 http://security.debian.org bullseye-security InRelease
Hit:3 http://ftp.es.debian.org/debian bullseye InRelease
Hit:4 http://ftp.es.debian.org/debian bullseye-updates InRelease
Get:5 http://download.proxmox.com/debian/pve bullseye/pve-no-subscription amd64 Packages [213 kB]
Fetched 216 kB in 0s (451 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
5 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@pve:~# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
libpve-rs-perl libpve-storage-perl pve-firmware pve-kernel-5.13.19-4-pve pve-kernel-helper
5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 126 MB of archives.
After this operation, 10.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://download.proxmox.com/debian/pve bullseye/pve-no-subscription amd64 libpve-rs-perl amd64 0.5.1 [1,301 kB]
Get:2 http://download.proxmox.com/debian/pve bullseye/pve-no-subscription amd64 libpve-storage-perl all 7.1-1 [129 kB]
Get:3 http://download.proxmox.com/debian/pve bullseye/pve-no-subscription amd64 pve-firmware all 3.3-5 [57.5 MB]
Get:4 http://download.proxmox.com/debian/pve bullseye/pve-no-subscription amd64 pve-kernel-5.13.19-4-pve amd64 5.13.19-9 [66.9 MB]
Get:5 http://download.proxmox.com/debian/pve bullseye/pve-no-subscription amd64 pve-kernel-helper all 7.1-10 [12.4 kB]
Yeah, that was a 5.13 based one fixing an regression in the block device (disks) part of the kernel:Today there was an update and now the kernel it's working correctly. I think you can safely update now. Here's the log to check the versions
yesJust asking, is it safe to upgrade topve-kernel-5.13.19-4-pve
?