Proxmox Virtual Environment 9.0 released!

Andrii.B said:
I don't know how you checked it, but on pve 9.0.6 it still doesn't work.
Click to expand...
There were the following updates last night. Maybe this covers that fix?
Code: 
Package Name    Installed Version    Available Version
librrd8t64        1.7.2-4.2+pve2        1.7.2-4.2+pve3
librrds-perl      1.7.2-4.2+pve2        1.7.2-4.2+pve3
rrdcached         1.7.2-4.2+pve2        1.7.2-4.2+pve3
 
  • Like
Reactions: Andrii.B
Andrii.B said:
Can you tell me when this update will be published to get this update?
Click to expand...
Patches are applied and will be part of the next release of the following packages:

qemu-server newer than 9.0.19
pve-container newer than 6.0.9
 
  • Like
Reactions: Andrii.B and gfngfn256
gfngfn256 said:
There were the following updates last night. Maybe this covers that fix?
Code: 
Package Name    Installed Version    Available Version
librrd8t64        1.7.2-4.2+pve2        1.7.2-4.2+pve3
librrds-perl      1.7.2-4.2+pve2        1.7.2-4.2+pve3
rrdcached         1.7.2-4.2+pve2        1.7.2-4.2+pve3
Click to expand...
These packages aren't available on my side yet.
 
Andrii.B said:
I have no newer versions yet. There isn't updated. I'm using the enterprise repositories.
Click to expand...
the patch has just been applied. a newer version is not yet released. But once you have a version newer than the mentioned ones, they will include the fix.
 
  • Like
Reactions: Andrii.B
miguelwill said:
I was testing the affinity rules, and they worked correctly.
I only noticed that in the "node affinity rules" rules, if a rule is disabled, then when trying to "reactivate" it, it doesn't update the status. I was only able to reactivate it by editing the "/etc/pve/ha/rules.cfg" file and removing the "disabled" line from that rule.
Click to expand...
Thanks for the report! This is fixed with pve-manager >= 9.0.7 [0], which should be packaged soon for pve-no-subscription.

[0] https://git.proxmox.com/?p=pve-manager.git;a=commit;h=4008a6472ada2bbd0f21c15fd7f5b047d71fcbd3
 
Last edited:
Stoiko Ivanov said:
We tried to make those checks as safe as possible so this should not cause issues.

A bit of background - currently systems:
* having root on ZFS or BTRFS
* booting using UEFI (not legacy bios boot)
* not having secure-boot enabled
use systemd-boot for booting
`proxmox-boot-tool status` should provide some helpful information

Additionally the `systemd-boot` package got split up a bit further in trixie - and proxmox-boot-tool only needs `systemd-boot-tools` and `systemd-boot-efi` - the `systemd-boot` meta-package is currently incompatible (as it tries updating the EFI, despite it not being mounted, which causes an error upon upgrade)

I hope this helps!
Click to expand...
Hi,

pve8to9 suggests to remove `systemd-boot` package, but my root is on a ZFS mirror. BIOS is set to "UEFI and Legacy Boot" and apparantly legacy boot is used.

Code: 
# proxmox-boot-tool status
Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace..
System currently booted with legacy bios
B7A1-2FB3 is configured with: grub (versions: 6.5.13-6-pve, 6.8.12-11-pve, 6.8.12-13-pve, 6.8.12-8-pve)
B7A3-6204 is configured with: grub (versions: 6.5.13-6-pve, 6.8.12-11-pve, 6.8.12-13-pve, 6.8.12-8-pve)

What's the problem with legacy boot and root on ZFS?
 
  • Like
Reactions: sjjh
ivenae said:
I get the following warning from pve8to9:


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


But if i try to install i get:
apt install intel-microcode
E: Unable to locate package intel-microcode

Edit: Had to add non-free-firmware to the repository
Click to expand...
I get the error

Package 'intel-microcode' has no installation candidate

How can i fix this?
 
Last edited:
Anyone have a problem with import VM's form ESXi using built-in tool?
I have Proxmox 9.0.6 cluster (no-subscribtion) and when I'm trying to migrate VM i still got error:

`TASK ERROR: unable to create VM 101 - cannot import from 'esx4:ha-datacenter/esx4-local/Ubnt.Srv/Ubnt.Srv.vmdk' - copy failed: command '/usr/bin/qemu-img convert -p -n -f vmdk -O raw /run/pve/import/esxi/esx4/mnt/ha-datacenter/esx4-local/Ubnt.Srv/Ubnt.Srv.vmdk zeroinit:/var/lib/pve/local-btrfs/images/101/vm-101-disk-0/disk.raw' failed: exit code 1`

It doesn't matter if storage on proxmox is local or shared (ISCSI);

On Proxmox 8.4 everything works fine :)
 
Hi,
mlukasik said:
Anyone have a problem with import VM's form ESXi using built-in tool?
I have Proxmox 9.0.6 cluster (no-subscribtion) and when I'm trying to migrate VM i still got error:

`TASK ERROR: unable to create VM 101 - cannot import from 'esx4:ha-datacenter/esx4-local/Ubnt.Srv/Ubnt.Srv.vmdk' - copy failed: command '/usr/bin/qemu-img convert -p -n -f vmdk -O raw /run/pve/import/esxi/esx4/mnt/ha-datacenter/esx4-local/Ubnt.Srv/Ubnt.Srv.vmdk zeroinit:/var/lib/pve/local-btrfs/images/101/vm-101-disk-0/disk.raw' failed: exit code 1`

It doesn't matter if storage on proxmox is local or shared (ISCSI);

On Proxmox 8.4 everything works fine :)
Click to expand...
please share the full task log and output of pveversion -v. Is there anything in the system journal around the time the issue happens?
 
fiona said:
Hi,

please share the full task log and output of pveversion -v. Is there anything in the system journal around the time the issue happens?
Click to expand...
Hi,
full log task:
create full clone of drive (esx4:ha-datacenter/esx4-local/RMS.Ubnt.Srv/RMS.Ubnt.Srv.vmdk)
transferred 0.0 B of 128.0 GiB (0.00%)
transferred 1.3 GiB of 128.0 GiB (1.00%)
transferred 2.6 GiB of 128.0 GiB (2.00%)
transferred 3.8 GiB of 128.0 GiB (3.00%)
transferred 5.1 GiB of 128.0 GiB (4.00%)
transferred 6.4 GiB of 128.0 GiB (5.00%)
transferred 7.7 GiB of 128.0 GiB (6.01%)
transferred 9.0 GiB of 128.0 GiB (7.01%)
qemu-img: error while reading at byte 10301208576: Input/output error
TASK ERROR: unable to create VM 101 - cannot import from 'esx4:ha-datacenter/esx4-local/Ubnt.Srv/Ubnt.Srv.vmdk' - copy failed: command '/usr/bin/qemu-img convert -p -n -f vmdk -O raw /run/pve/import/esxi/esx4/mnt/ha-datacenter/esx4-local/Ubnt.Srv/Ubnt.Srv.vmdk zeroinit:/var/lib/pve/local-btrfs/images/101/vm-101-disk-0/disk.raw' failed: exit code 1

pveversion -v:
root@proxmox-gl-01:~# pveversion -v
proxmox-ve: 9.0.0 (running kernel: 6.14.11-1-pve)
pve-manager: 9.0.6 (running version: 9.0.6/49c767b70aeb6648)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.14.11-1-pve-signed: 6.14.11-1
proxmox-kernel-6.14: 6.14.11-1
proxmox-kernel-6.8.12-14-pve-signed: 6.8.12-14
proxmox-kernel-6.8: 6.8.12-14
proxmox-kernel-6.8.12-9-pve-signed: 6.8.12-9
ceph-fuse: 19.2.3-pve1
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx10
intel-microcode: 3.20250512.1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.3
libpve-apiclient-perl: 3.4.0
libpve-cluster-api-perl: 9.0.6
libpve-cluster-perl: 9.0.6
libpve-common-perl: 9.0.9
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.4
libpve-network-perl: 1.1.6
libpve-rs-perl: 0.10.10
libpve-storage-perl: 9.0.13
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-1
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.14-1
proxmox-backup-file-restore: 4.0.14-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.1.2
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.1
proxmox-widget-toolkit: 5.0.5
pve-cluster: 9.0.6
pve-container: 6.0.10
pve-docs: 9.0.8
pve-edk2-firmware: 4.2025.02-4
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.3
pve-firmware: 3.16-4
pve-ha-manager: 5.0.4
pve-i18n: 3.5.2
pve-qemu-kvm: 10.0.2-4
pve-xtermjs: 5.5.0-2
qemu-server: 9.0.19
smartmontools: 7.4-pve1
spiceterm: 3.4.0
swtpm: 0.8.0+pve2
vncterm: 1.9.0
zfsutils-linux: 2.3.4-pve1

and log from journalctl

Sep 10 09:42:40 proxmox-gl-01 esxi-folder-fus[1836]: proxmox-gl-01 esxi-folder-fuse[1836]: error handling request: cached read failed: error reading a body from connection

Caused by:
Connection reset by peer (os error 104)
Sep 10 09:42:40 proxmox-gl-01 pvedaemon[240542]: VM 101 creating disks failed
Sep 10 09:42:40 proxmox-gl-01 pvedaemon[240542]: unable to create VM 101 - cannot import from 'esx4:ha-datacenter/esx4-local/Ubnt.Srv/Ubnt.Srv.vmdk' - copy failed: command '/usr/bin/qemu-img convert -p -n -f vmdk -O raw /run/pve/import/esxi/esx4/mnt/ha-datacenter/esx4-local/Ubnt.Srv/Ubnt.Srv.vmdk zeroinit:/var/lib/pve/local-btrfs/images/101/vm-101-disk-0/disk.raw' failed: exit code 1
Sep 10 09:42:40 proxmox-gl-01 pvedaemon[87462]: <root@pam> end task UPID:proxmox-gl-01:0003AB9E:007973B9:68C12B0A:qmcreate:101:root@pam: unable to create VM 101 - cannot import from 'esx4:ha-datacenter/esx4-local/Ubnt.Srv/Ubnt.Srv.vmdk' - copy failed: command '/usr/bin/qemu-img convert -p -n -f vmdk -O raw /run/pve/import/esxi/esx4/mnt/ha-datacenter/esx4-local/Ubnt.Srv/Ubnt.Srv.vmdk zeroinit:/var/lib/pve/local-btrfs/images/101/vm-101-disk-0/disk.raw' failed: exit code 1
 
mlukasik said:
Sep 10 09:42:40 proxmox-gl-01 esxi-folder-fus[1836]: proxmox-gl-01 esxi-folder-fuse[1836]: error handling request: cached read failed: error reading a body from connection
Click to expand...
mlukasik said:
Connection reset by peer (os error 104)
Click to expand...
As the initial guess, it seems like there is an issue related to the network communication.

Does it always fail at the same offset, i.e. around 9.0 GiB?
 
Hi,
I have a cluster of 5 nodes with ocfs2 filesystems. Today I tried to upgrade first node to 9.0 but node started without ocfs2 filesystems attached and many lines in logs:

Code: 
pvestatd[2832]: unable to activate storage 'lun1' - directory is expected to be a mount point but is not mounted: '/mnt/lun1'

mount -a shows this error:
Code: 
Error "mount.ocfs2: Invalid name for a cluster while trying to join the group"

I found that it seems to be my issue reported on Oracle forum here . Solution is to manually restart o2cb service and remount filesystems:

Code: 
systemctl restart o2cb.service

I can add this to cron temporary but it it's rather lame solution. I would like to fix this before upgrading the rest of nodes. Please help.

===UPDATE===
Problem solved (enable services to get it working)
 
Last edited:
  • Like
Reactions: mlukasik
Here is my proxmox 9 reinstall story. I had proxmox 8 and then upgraded it to 9, but virtual machines were not getting passed through correctly ( possibly due to something IOMMU Related.) I am reinstalling 9 per A suggestion from someone on how to fix it. Here is my story.

using a cmp51 and windows vm i created a ventoy thumbstick and then configured it for proxmox storage. i then used download from link feature to download an iso for pve 9 and 8.

BLUF:
I booted from the thumb drive and tried each installer. the graphical installer works for version 8, but not 9. I was able to install version 9 using grub command line installer and ran into issues, but was eventually able to get it to boot.

DETAILS:
When I rebooted into proxmox i got the following error.
error could not insert polyval_clmulni and no device with valid iso found

So, I rebooted the machine again and selected ventoy - grub2 mode - proxmox terminal install

after install and reboot on the blue screen for proxmox. hit c key for command line

GNU GRUB ersion 2.12-9+pmx2
At the grub> prompt:

1. Search for the kernel file (vmlinuz)

search -f /boot/vmlinuz-*-pve

This will print the device (like (hd0,gpt2)) where the kernel lives.

2. Search for the initrd file

search -f /boot/initrd.img-*-pve

3. Set that as root

set root=(hd0,gpt2) # replace with the device you found. for me both returned lvm/pve-root

4. find out your exact version

ls /boot/

5. Boot manually (without rdinit=/vtoy/vtoy) be sure to change the numbers below with your output from ls /boot/

step a.
#these next two lines contain a space not a return. very important

linux /boot/vmlinuz-6.8.12-3-pve root=/dev/mapper/pve-root ro quiet

step b. again, make sure you use the correct version from your output

initrd /boot/initrd.img-6.8.12-3-pve

step c.
boot

Making these changes permanent:

Once inside Proxmox:

Remove the bad rdinit=/vtoy/vtoy from /etc/default/grub.d/installer.cfg

nano /etc/default/grub.d/installer.cfg

Rebuild grub with:

grub-mkconfig -o /boot/grub/grub.cfg

reboot

This worked for me (but not yet with zfs), and I hope it helps someone else
 
Last edited:
  • Like
Reactions: Johannes S
You must log in or register to reply here.
Top Bottom
Back