upgrading from 8 to 9 cpu microcode

robertkwild

Member
Jun 17, 2022
36
1
13
hi all,

im running the command "pve8to9 --full" from here

https://pve.proxmox.com/wiki/Upgrade_from_8_to_9

and i get one warning

Code:
WARN: The matching CPU microcode package 'intel-microcode' could not be found! Consider installing it to receive the latest security and bug fixes for your CPU.
        Ensure you enable the 'non-free-firmware' component in the apt sources and run:
        apt install intel-microcode

but im using the free version of pve, i dont want to use the non free ie paid, is this ok to do, if so how do i do it please

thanks,
rob
 
HI,

in this case, non-free refers to the license of the microcode package, in that is isn't open-source and/or freely modifiable (or encumbered by patents, for example). It doesn't have anything to do with whether you got a support subscription or not.

See also the Debian documentation on that: https://www.debian.org/doc/debian-policy/ch-archive#s-non-free
And on firmware on Debian in general: https://wiki.debian.org/Firmware

In any case, if you want, you can simply enable the non-free-firmware component to your repository configuration and run the command as given :)
 
done...

Code:
cat /etc/apt/sources.list
deb http://ftp.uk.debian.org/debian bookworm non-free-firmware main contrib

deb http://ftp.uk.debian.org/debian bookworm-updates non-free-firmware main contrib

# Proxmox VE pve-no-subscription repository provided by proxmox.com,
# NOT recommended for production use
deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription

# security updates
deb http://security.debian.org bookworm-security non-free-firmware main contrib
 
do i need to do this

Code:
Add the Proxmox VE 9 Package Repository

If you are using the enterprise repository, you can add the Proxmox VE 9 enterprise repository in the new deb822 style. Run the following command to create the related pve-enterprise.sources file:

cat > /etc/apt/sources.list.d/pve-enterprise.sources << EOF
Types: deb
URIs: https://enterprise.proxmox.com/debian/pve
Suites: trixie
Components: pve-enterprise
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOF

After you added the new enterprise repository as above, check that apt picks it up correctly. You can do so by first running apt update followed by apt policy. Make sure that no errors are shown and that apt policy only outputs the desired repositories. Then you can remove the old /etc/apt/sources.list.d/pve-enterprise.list file. Run apt update and apt policy again to be certain that the old repo has been removed.

If using the no-subscription repository, see Package Repositories. You should be able to add the Proxmox VE 9 no-subscription repository with this command:

cat > /etc/apt/sources.list.d/proxmox.sources << EOF
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOF

As with the enterprise repository, make sure that apt picks it up correctly with apt update followed by apt policy. Then remove the previous Proxmox VE 8 no-subscription repository from either the /etc/apt/sources.list, /etc/apt/sources-list.d/pve-install-repo.list or any other .list file you may have added it to. Run apt update and apt policy again to be certain that the old repo has been removed.
Update the Ceph Package Repository

Note: For hyper-converged ceph setups only, check the ceph panel and configured repositories in the Web UI of this node, if unsure.

Replace any ceph.com repositories with proxmox.com ceph repositories.

Note: At this point a hyper-converged Ceph cluster installed directly in Proxmox VE must run Ceph 19.2 Squid, otherwise you need to upgrade Ceph first before upgrading to Proxmox VE 9 on Debian 13 Trixie! You can check the current Ceph version in the Ceph panel of each node in the Web UI of Proxmox VE.

Since Proxmox VE 8 there also exists an enterprise repository for ceph, providing the best choice for production setups. Execute the command below to add the Trixie-based Ceph enterprise repository in the new deb822 style:

cat > /etc/apt/sources.list.d/ceph.sources << EOF
Types: deb
URIs: https://enterprise.proxmox.com/debian/ceph-squid
Suites: trixie
Components: enterprise
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOF

Make sure that apt picks it up correctly by running apt update first and then apt policy. There should be no errors and the new repository should show up correctly in the output of apt policy. Then you can remove the old /etc/apt/sources.list.d/ceph.list file. You can run apt update and then apt policy again to make sure it has been properly removed.

If updating fails with a 401 error, you might need to refresh the subscription first to ensure new access to ceph is granted, do this via the Web UI or pvesubscription update --force.

If you do not have any subscription you can use the no-subscription repository, add it with the following command in the new deb822 style:

cat > /etc/apt/sources.list.d/ceph.sources << EOF
Types: deb
URIs: http://download.proxmox.com/debian/ceph-squid
Suites: trixie
Components: no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOF

As with the enterprise repository, make sure that apt picks it up correctly with apt update followed by apt policy. Then you can remove the old /etc/apt/sources.list.d/ceph.list file.

If there is a backports line, remove it - the upgrade has not been tested with packages from the backports repository installed.

so obviously i dont need to do the "enterprise" but the "no-subscription"

do i do section about "ceph"
 
Last edited: