Recent content by udo

of course it's not tivial - especialy if you have cephfs and radosgw running too (like me).

Hi, there is an critical security issue on ceph https://notcve.org/cve/CVE-2025-30156 I assume you are working on new packages. Can you estimate when they'll be ready? Best regards Udo

Hi, yes you are right! I took an older grml to test the cpu-flags. With the actual one (kernel 6.19.13) the lahf_lm flag was visible inside the VM on amd too. Best regards Udo

Hello Arthur, of course… lahf-am is there: qemu-system-x86_64 -cpu help Available CPUs: 486 (alias configured by machine type) 486-v1 Broadwell (alias configured by machine type) Broadwell-IBRS (alias of Broadwell-v3)...

Hi Arthur, thanks for the info. The lahf-lm flag is strange. Have testet a limitied cpu with "flags +aes;+lahf-lm" on an Intel-Node (E5-2640 v4) and the flag is visible inside the VM. Then I migrate the VM back to an AMD-Node (EPYC 9454P) and start the VM there… and the lahf-lm flag is gone! The...

Hi, we have cluster with mixed CPUs and we use as cpu-settings something like this (amd) cpu: x86-64-v3,flags=+ibpb;+virt-ssbd;+amd-ssbd to avoid to select the additional flags I tried to define an custom cpu type. Two things are not working: 1. the cpu type x86-64-v3 isn't supported (unable...

Found the issue - was my fault - from an prior installation on other hardware (without boss card), there was still "GRUB_CMDLINE_LINUX="root=ZFS=rpool/ROOT/pve-1 boot=zfs" in the grub-default-file… Thanks for comments!!

Hi, perhaps that has something to do with the issue. On another similiar R6615 which I upgrade this morning, the packages are not installed. On the node with the issue, was systemd-boot removed, but systemd-boot-efi installed… dpkg -l | grep systemd-boot rc systemd-boot...

Hi, secure boot is disabled in the bios. Strange, then efibootmgr shows \EFI\Proxmox\shimx64.efi I updated another Node this morning, also on a R6615 with Boss-Raid-1-Card, which runs well. On this Node Secure Boot is also disabled and efibootmgr shows \EFI\proxmox\grubx64.efi First I try to...

Hi, of course efibootmgr -v BootCurrent: 0001 Timeout: 0 seconds BootOrder: 0004,0003,0000,0001 Boot0000 Virtual Floppy PciRoot(0x3)/Pci(0x7,0x1)/Pci(0x0,0x4)/USB(0,0)/USB(3,0)/USB(0,0)/Unit(1) dp: 02 01 0c 00 d0 41 03 0a 03 00 00 00 / 01 01 06 00 01 07 / 01 01 06 00 04 00 / 03 05...

Yes, I mean the same. The server aren't bootet and was not available on the network. Not with the interface for clustercommunication, nor with the openvswitch-bonds…

Yes, the console message from iDRac is correct - the node aren't booted without display output.

My fault! There was still an "root=ZFS=rpool/ROOT/pve-1 boot=zfs" in the default-grub file due an prior installation on other Hardware without boss-card. Hi, this mornig I've upgrade 3 Nodes of an Cluster to proxmox-ve: 9.2.0 (running kernel: 7.0.14-8-pve). On a Dell R6615 with Boss-Card...

Thanks, curiously enough is reserved_memory only 8k! lvmconfig activation/reserved_memory reserved_memory=8192 I've extend to 64k. Best regards Udo

Hi, we had an error massage during snapshotting an switched off VM: snapshotting 'drive-scsi0' (ssd-lvm:vm-1117-disk-0) Logical volume "snap_vm-1117-disk-0_xxx" created. Internal error: Reserved memory (31006720) not enough: used 31928320. Increase activation/reserved_memory? pveversion...