There's a new QEMU 9.0 available on the no-subscription repository.
Internal testing for that version started with the release candidates over two months ago, and our engineers could contribute several complex fixes to the stable release. Today our QEMU 9.0 package has been made available on the pve-no-subscription repository.
Our QEMU package version
FYI, we decided to skip pushing out QEMU 8.2 due to the timing of our last point release and to reduce the amount of updates and regression (that version had some bigger internal refactoring half-way done), but we still uploaded a build of it so that you can more easily narrow down when any potential difference or even regression got introduced.
Note: While our workloads run stable on this version of QEMU, we cannot test every possible hardware and configuration combination, so we recommend testing the upgrade before applying it to mission-critical setups. As a reminder, we recommend using the most stable Enterprise repository for such production setups.
To upgrade, make sure you have configured the Proxmox VE No Subscription or Test repositories.
Either use the web-interface to refresh and then upgrade using the Node -> Updates panel, or use a console with the following standard apt commands:
The output of
Note, as with all QEMU updates: A VM must either be completely restarted (shut it down then start it again, or use the restart command via the CLI or web-interface) or, to avoid downtime, consider live-migrating to a host that has already been upgraded to the new QEMU package version.
While we have been successfully running our production and many test loads on this version for some time now, no software is bug-free, and often such issues are related to the specific setup. So if you encounter regressions that are definitely caused by installing the new QEMU version (and not some other change), please always include the affected VM configuration and some basic HW (e.g. CPU model) and memory details.
We welcome your feedback!
Known issues:
Internal testing for that version started with the release candidates over two months ago, and our engineers could contribute several complex fixes to the stable release. Today our QEMU 9.0 package has been made available on the pve-no-subscription repository.
Our QEMU package version
9.0.0-3 contains some important stable fixes that have been developed since the original 9.0.0 release. This exact build has been in QA and the testing repository for over three weeks now, and powers most of our own production loads.FYI, we decided to skip pushing out QEMU 8.2 due to the timing of our last point release and to reduce the amount of updates and regression (that version had some bigger internal refactoring half-way done), but we still uploaded a build of it so that you can more easily narrow down when any potential difference or even regression got introduced.
Note: While our workloads run stable on this version of QEMU, we cannot test every possible hardware and configuration combination, so we recommend testing the upgrade before applying it to mission-critical setups. As a reminder, we recommend using the most stable Enterprise repository for such production setups.
To upgrade, make sure you have configured the Proxmox VE No Subscription or Test repositories.
Either use the web-interface to refresh and then upgrade using the Node -> Updates panel, or use a console with the following standard apt commands:
Bash:
apt update
apt full-upgradeThe output of
pveversion -v (or the web-interface's Node Summary -> Packages versions) should then include something like pve-qemu-kvm: 9.0.0-3Note, as with all QEMU updates: A VM must either be completely restarted (shut it down then start it again, or use the restart command via the CLI or web-interface) or, to avoid downtime, consider live-migrating to a host that has already been upgraded to the new QEMU package version.
While we have been successfully running our production and many test loads on this version for some time now, no software is bug-free, and often such issues are related to the specific setup. So if you encounter regressions that are definitely caused by installing the new QEMU version (and not some other change), please always include the affected VM configuration and some basic HW (e.g. CPU model) and memory details.
We welcome your feedback!
Known issues:
- Because of newer SeaBIOS, certain 32-bit guests (in particular Linux with PAE) are broken For references and workarounds see this forum post here.
Last edited:
