Proxmox VE 8.0 released!
- Thread starter martin
- Start date
Driver is rebuilt every kernel update (as long as the headers are available) The non-free part is just to be able to download the R8168-DKMS driver, otherwise it can't be found
Last edited:
Hi all,
I've been using Proxmox 7.4 for about a year, and today, I've installed Proxmox 8.0 on a new OVH dedicated server. However, I've encountered an issue. When I access the shell and type in:
Has anyone else experienced this issue?
Is it possible that cron is not available by default on Debian 12 or Proxmox 8.0?
Thank you for your assistance!
I've been using Proxmox 7.4 for about a year, and today, I've installed Proxmox 8.0 on a new OVH dedicated server. However, I've encountered an issue. When I access the shell and type in:
Bash:
crontab -e
bash: crontab: command not foundHas anyone else experienced this issue?
Is it possible that cron is not available by default on Debian 12 or Proxmox 8.0?
Thank you for your assistance!
I'm getting this WARNING when running pve7to8 --full
while if I check the systemd version
The CT is running Fedora 38.
What should I do ?
Code:
WARN: Found at least one CT (100) which does not support running in a unified cgroup v2 layout
Consider upgrading the Containers distro or set systemd.unified_cgroup_hierarchy=0 in the Proxmox VE hosts' kernel cmdline! Skipping further CT compat checks.while if I check the systemd version
Code:
[root@proxy ~]# systemctl --version
systemd 253 (253.7-1.fc38)
+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP -GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unifiedThe CT is running Fedora 38.
What should I do ?
Hi,
If you are running a version with the patch, please share the container configuration.
EDIT: apparently, the original patch did not work for Fedora 38: https://forum.proxmox.com/threads/pve7to8-cgroup-warning-incorrect.128721/post-584609
are you running the latest version of 7.x? There is a patch in
pve-manager >= 7.4-14 for improving detection: https://git.proxmox.com/?p=pve-manager.git;a=commit;h=591f411f729e2f9c2f1fd45540a4d777c16b3245If you are running a version with the patch, please share the container configuration.
EDIT: apparently, the original patch did not work for Fedora 38: https://forum.proxmox.com/threads/pve7to8-cgroup-warning-incorrect.128721/post-584609
Last edited:
II have the same problem when using Hetzner KVM. I downloaded the ISO file from the official website, zfs file system (RAID0)..... I doubt that you should use a flash drive....
Can you give more details here?
E.g., about your
- used hardware (network cards, CPUs, server vendor, ...) from both source and target nodes (are they homogenous/identical?)
- which kernel you used on Proxmox VE 7
- if it had the latest software updates (can you attach
/var/log/apt/history.logand/var/log/apt/history.log.1?) - if the hosts had subscriptions with access to the production-ready enterprise repository
- what the VM configs looked like
- any errors in the VM guest OS or on the Proxmox VE host logs?
The last available software was installed on all servers. But was not rebooted from the latest kernel. Also I tried to migrate from the kernel 5.15.35-2-pve and from 5.15.74-1-pve.
Uses the same HW. All servers have the subscription.
and pve8:
Uses the same HW. All servers have the subscription.
and pve8:
You only answered half of my questions.. please open a new thread an answer them all.
So I guess you did not follow the official upgrade guide, or at least not run the
pve7to8 checker tool which warns about such stuff?https://pve.proxmox.com/wiki/Upgrade_from_7_to_8
There even was some fix in the kernel for hanging VMs on migrations under some specific situations a bit ago (without the full info like asked it's hard to tell if yours is one of those situations), but one needs to have both source and target up-to-date for such things to work.
Hello, just tried to update to 8, following the guide. after full upgrade on 7 i first ran ran
output was
and pve7to8 --full resulted in all green.
at the end of the upgrade process i get:
I'm guessing i should delete linux-headers-6.1.0-11-amd64 ?
But i just wanted to ask here if it's something serious i'm not seeing? Thx.
Code:
apt --purge autoremove
pve7to8 --full
pveversion
Code:
pve-manager/7.4-16/0f39f621 (running kernel: 6.2.16-11-bpo11-pve)at the end of the upgrade process i get:
Code:
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.2.16-12-pve
cryptsetup: ERROR: Couldn't resolve device rpool/ROOT/pve-1
cryptsetup: WARNING: Couldn't determine root device
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/8515-4738
Copying kernel and creating boot-entry for 5.15.116-1-pve
Copying kernel and creating boot-entry for 6.2.16-11-bpo11-pve
Copying kernel and creating boot-entry for 6.2.16-12-pve
Processing triggers for dbus (1.14.8-2~deb12u1) ...
Processing triggers for pve-ha-manager (4.0.2) ...
Errors were encountered while processing:
linux-headers-6.1.0-11-amd64
linux-headers-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)I'm guessing i should delete linux-headers-6.1.0-11-amd64 ?
But i just wanted to ask here if it's something serious i'm not seeing? Thx.
Hi,
I'm not using cryptsetup so I wouldn't know, but do you usually have those complains from cryptsetup? Those are not what apt complained about below though:
If you want to check, the actual errors are likely further up in the log (see
/var/log/apt/term.log).But yes, you shouldn't need those headers. For Proxmox, the relevant header packages are
proxmox-headers-<version>, not linux-headers(-<version>)-amd64.