Recent content by Robert Dahlem

"Host CPU usage" and "Host Memory used" are fine. But "Host storage used" has a lot of duplicates in it: 7.41 TB is (roughly) the sum of all shared storage (NFS + Ceph), added for each node that can access it and local storages are not counted in. Also it would be nice if we could see the...

That is the Remote ID. You should use it as the name of the data center. Unfortunately not editable yet.

Well, not while one is removed (detached). :-) But that is the point where I see that the boot entry has been removed already. And it does not return, when I re-attach the disk and check its box in the VMs options.

Hello, I'm trying a software RAID1 setup with a Debian12 VM. My 2 disks have each a 1 GB partition, type Linux RAID, bound together as /dev/md0, for /boot a 1 GB partition for ESP a Linux LVM partition, bound together in one VG, providing LVs for root and swap UEFI does not know about RAID1...

It is not solved, I just posted a workaround. It would be solved when I could shutdown the system without the nouveau module hanging.

Running Proxmox VE 8.2.2, out of the box, freshly installed from ISO. At reboot, the system hangs at nouveau 0000:01:00.0: Enabling HDD controller. You can't see that unless you remove "quiet" from GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and run update-grub. Then your system just hangs...

You might perhaps like to adjust your perspective on what "normal" is. :) We are not talking about Debian (I use RHEL), we are not talking about a network image or a Live ISO, but about an initrd, which must support whatever hardware is found an the target system (which could be completely...

That initrd is built by ReaR (Relax and Recover). It is intentionally that big because the rescue system includes all modules the original system knows about. This way it has a chance to run even if the target is a completely different machine than the original.

Fun fact: I copied bin/virtio-net.rom from iPXE over /usr/share/kvm/efi-virtio.rom and now my VM boots "iPXE 1.12.1+ (g119c4)". AND: my original problem is gone! :) Let's lose a word about that: I'm using ReaR (Relax and Recover) for Backup & Restore purposes. In PXE-Restore mode basically it...

Hello, first: I know about Problems with iPXE pxe-virtio.rom and https. I'm on the latest Proxmox VE with no outstanding upgrades as of today. I have a problem (which I will describe only if asked to because it is irrelevant to this case) with the delivered iPXE 1.20.1+ which I hope to solve...

Ouch! Port 80 was forwarded to a different machine. I should have checked that tcpdump actually saw incoming traffic.

Hello, I'm on 6.4-13. All of a sudden Letsencrypt certificate renewals are failing: Getting authorization details from 'https://acme-v02.api.letsencrypt.org/acme/authz-v3/17197269920' The validation for my.fqdn is pending! Setting up webserver Triggering validation Sleeping for 5 seconds...

I can confirm that this is no longer a problem under pve-kernel-5.3.18-3-pve (which seems to be the latest one for Proxmox 6.1) nor under pve-kernel-5.4.41-1-pve (which is the current one for Proxmox 6.2).

No, this bug is not relevant. Over the last days I isolated the bug to something that happened with kernel version 5.2.5 and then bisected it to this patch: KVM: X86: Fix fpu state crash in kvm guest. Ironically, the patch was written to overcome FPU related bluescreens in Windows 10 VMs. I...

I installed linux-image-5.3.0-0.bpo.2-amd64, the Debian backported 5.3 kernel. That makes me believe it has something to do with kernel 5.3, nothing PVE specific.