<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[PROXMOX : Migration de 8 à 9, les logs de pve8to9 avant la migration]]></title><description><![CDATA[<pre><code>#  pve8to9
= CHECKING VERSION INFORMATION FOR PVE PACKAGES =

Checking for package updates..
PASS: all packages up-to-date

Checking proxmox-ve package version..
PASS: proxmox-ve package has version &gt;= 8.4-0

Checking running kernel version..
PASS: running kernel '6.8.12-13-pve' is considered suitable for upgrade.

= CHECKING CLUSTER HEALTH/SETTINGS =

SKIP: standalone node.

= CHECKING HYPER-CONVERGED CEPH STATUS =

SKIP: no hyper-converged ceph setup detected!

= CHECKING CONFIGURED STORAGES =

PASS: storage 'datastore1' enabled and active.
PASS: storage 'datastore2' enabled and active.
PASS: storage 'datastoreSCSI' enabled and active.
PASS: storage 'local' enabled and active.
PASS: storage 'local-lvm' enabled and active.
INFO: Checking storage content type configuration..
PASS: no storage content problems found
PASS: no storage re-uses a directory for multiple content types.
INFO: Check for usage of native GlusterFS storage plugin...
PASS: No GlusterFS storage found.
INFO: Checking whether all external RBD storages have the 'keyring' option configured
SKIP: No RBD storage configured.

= VIRTUAL GUEST CHECKS =

INFO: Checking for running guests..
WARN: 11 running guest(s) detected - consider migrating or stopping them.
INFO: Checking if LXCFS is running with FUSE3 library, if already upgraded..
SKIP: not yet upgraded, no need to check the FUSE library version LXCFS uses
INFO: Checking for VirtIO devices that would change their MTU...
PASS: All guest config descriptions fit in the new limit of 8 KiB
INFO: Checking container configs for deprecated lxc.cgroup entries
PASS: No legacy 'lxc.cgroup' keys found.
INFO: Checking VM configurations for outdated machine versions
PASS: All VM machine versions are recent enough

= MISCELLANEOUS CHECKS =

INFO: Checking common daemon services..
PASS: systemd unit 'pveproxy.service' is in state 'active'
PASS: systemd unit 'pvedaemon.service' is in state 'active'
PASS: systemd unit 'pvescheduler.service' is in state 'active'
PASS: systemd unit 'pvestatd.service' is in state 'active'
INFO: Checking for supported &amp; active NTP service..
INFO: Debian deprecated and removed the ntp package for Bookworm, but the system will automatically migrate to the 'ntpsec' replacement package on upgrade.
INFO: Checking if the local node's hostname 'local' is resolvable..
INFO: Checking if resolved IP is configured on local node..
PASS: Resolved node IP '165.195.195.230' configured and active on single interface.
INFO: Check node certificate's RSA key size
PASS: Certificate 'pve-root-ca.pem' passed Debian Busters (and newer) security level for TLS connections (4096 &gt;= 2048)
PASS: Certificate 'pve-ssl.pem' passed Debian Busters (and newer) security level for TLS connections (2048 &gt;= 2048)
INFO: Checking backup retention settings..
PASS: no backup retention problems found.
INFO: checking CIFS credential location..
PASS: no CIFS credentials at outdated location found.
INFO: Checking permission system changes..
INFO: Checking custom role IDs
PASS: no custom roles defined
INFO: Checking node and guest description/note length..
PASS: All node config descriptions fit in the new limit of 64 KiB
INFO: Checking if the suite for the Debian security repository is correct..
PASS: found no suite mismatch
INFO: Checking for existence of NVIDIA vGPU Manager..
PASS: No NVIDIA vGPU Service found.
INFO: Checking bootloader configuration...
WARN: systemd-boot meta-package installed but the system does not seem to use it for booting. This can cause problems on upgrades of other boot-related packages. Consider removing 'systemd-boot'
PASS: bootloader packages installed correctly
INFO: Check for dkms modules...
WARN: dkms modules found, this might cause issues during upgrade.
INFO: Check for legacy 'filter' or 'group' sections in /etc/pve/notifications.cfg...
INFO: Check for legacy 'notification-policy' or 'notification-target' options in /etc/pve/jobs.cfg...
PASS: No legacy 'notification-policy' or 'notification-target' options found!
INFO: Check for LVM autoactivation settings on LVM and LVM-thin storages...
PASS: all guest volumes on storage 'local-lvm' have autoactivation disabled
PASS: No problematic volumes found.
INFO: Check space requirements for RRD migration...
PASS: Enough free disk space for increased RRD metric granularity requirements, which is roughly 23.30 MiB.
INFO: Checking for IPAM DB files that have not yet been migrated.
PASS: No legacy IPAM DB found.
PASS: No legacy MAC DB found.
INFO: Checking if the legacy sysctl file '/etc/sysctl.conf' needs to be migrated to new '/etc/sysctl.d/' path.
WARN: Deprecated config '/etc/sysctl.conf' contains settings - move them to a dedicated file in '/etc/sysctl.d/'.
INFO: Checking if matching CPU microcode package is installed.
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.
        apt install intel-microcode
SKIP: NOTE: Expensive checks, like CT cgroupv2 compat, not performed without '--full' parameter

= SUMMARY =

TOTAL:    44
PASSED:   34
SKIPPED:  5
WARNINGS: 5
FAILURES: 0

ATTENTION: Please check the output for detailed information!
</code></pre>
<p dir="auto">Pour la migration j’ai du faire en plus :</p>
<pre><code># apt list -a intel-microcode

# echo "deb http://deb.debian.org/debian/ unstable non-free-firmware" &gt; /etc/apt/sources.list.d/debian-unstable.list

# apt update

# apt install intel-microcode

# apt list -a intel-microcode
Listing... Done
intel-microcode/unstable,now 3.20250512.1 amd64 [installed]

# dpkg -r docker-compose-plugin

# apt-get --fix-broken install
</code></pre>
<p dir="auto">Je pense que docker-compose-plugin bloquait la migration.</p>
<p dir="auto">Voir : <a href="https://forum.proxmox.com/threads/running-docker-on-the-proxmox-host-not-in-vm-ct.147580/" rel="nofollow ugc">https://forum.proxmox.com/threads/running-docker-on-the-proxmox-host-not-in-vm-ct.147580/</a><br />
“It is not recommended to run docker directly on your Proxmox VE host.”</p>
]]></description><link>https://lemmy.cyber-neurones.org/topic/61/proxmox-migration-de-8-à-9-les-logs-de-pve8to9-avant-la-migration</link><generator>RSS for Node</generator><lastBuildDate>Thu, 30 Apr 2026 11:36:08 GMT</lastBuildDate><atom:link href="https://lemmy.cyber-neurones.org/topic/61.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 04 Sep 2025 13:37:06 GMT</pubDate><ttl>60</ttl></channel></rss>