Yes, but remember, no-subscription is also not intended for production systems, see the docsReality is though, nobody is going to do that
I'm guessing we can just disable the pve-test repo and enable the no-subscription one?
Proxmox VE 9.0 BETA released!
- Thread starter t.lamprecht
- Start date
Hi bossHi,
if you want to continue using it as a test system, you can simply upgrade using apt:
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#system_software_updates
For production systems you shouldn't have used the beta to begin with
For upgrading systems with Proxmox VE 8 or installing new systems, see the official upgrade guide: https://pve.proxmox.com/wiki/Upgrade_from_8_to_9
and the release announcement:
Do you mean if I have a new installation for Peoxmox now, I can use 9.0.3 for production?
Yes, that is what being released means
. For actual production use, you need a subscription to access the enterprise repository. Other repositories can be used without subscription, but are not recommended for production use, see:https://pve.proxmox.com/wiki/Package_Repositories#sysadmin_enterprise_repo
If you want to be cautious, you can monitor the release announcement thread for a while for any issues that might affect you before upgrading. With the wide range of hardware and configurations we cannot possibly catch all issues before the release. But with the beta, the new version already had quite a bit of exposure.
Anyone try building https://github.com/strongtz/i915-sriov-dkms into the latest kernel for multi iGPU support on new Ultra CPUs?
Im getting an invalid kernel header:
Im getting an invalid kernel header:
Code:
Error! Your kernel headers for kernel 6.14.8-2-bpo12-pve cannot be found at /lib/modules/6.14.8-2-bpo12-pve/build or /lib/modules/6.14.8-2-bpo12-pve/source.
Code:
root@proxmox:~/i915# uname -r
6.14.8-2-bpo12-pve
Last edited:
Hi,
if you are on Proxmox VE 9 (based on Debian 13), you should not run the kernel for Proxmox VE 8 (based on Debian 12, the
bpo12 means the package was backported for Debian 12). Also make sure the proxmox-default-headers package is installed.ran update-initramfs and that set the correct kernel.
vGPU seems to work on Proxmox 9 for an Ultra 265k CPU
Code:
lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Arrow Lake-S [Intel Graphics] (rev 06)
00:02.1 VGA compatible controller: Intel Corporation Arrow Lake-S [Intel Graphics] (rev 06)
00:02.2 VGA compatible controller: Intel Corporation Arrow Lake-S [Intel Graphics] (rev 06)
00:02.3 VGA compatible controller: Intel Corporation Arrow Lake-S [Intel Graphics] (rev 06)
00:02.4 VGA compatible controller: Intel Corporation Arrow Lake-S [Intel Graphics] (rev 06)
00:02.5 VGA compatible controller: Intel Corporation Arrow Lake-S [Intel Graphics] (rev 06)
00:02.6 VGA compatible controller: Intel Corporation Arrow Lake-S [Intel Graphics] (rev 06)
00:02.7 VGA compatible controller: Intel Corporation Arrow Lake-S [Intel Graphics] (rev 06)
Last edited:
Should not be necessary to run manually usually. What does
proxmox-boot-tool kernel list say?Glad to hear
Glad to see everything is working for the Intel iGPU vGPU. I assume you're using the i915 DKMS driver? If you are, did you have to do anything odd to make it work, or are the standard instructions on the GitHub still good?
(There's an open bug report over there re: PVE 9 compatibility. It'd be nice to add a post with a known working config.
)I didn't have to do anything special. No. I'm not sure where, there, is.Glad to see everything is working for the Intel iGPU vGPU. I assume you're using the i915 DKMS driver? If you are, did you have to do anything odd to make it work, or are the standard instructions on the GitHub still good?
(There's an open bug report over there re: PVE 9 compatibility. It'd be nice to add a post with a known working config.
Last edited:
My update failed cause I had a custom module in there when I tried to upgrade. gasket dkms and the apt process died then, so I think it simply didn't get a chance to update the kernel when i ran through that process initially. I backed out the gasket custom piece and then it was able to finish. At least that's what I recall.Should not be necessary to run manually usually. What doesproxmox-boot-tool kernel listsay?
Glad to hear