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...
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.
I will do that for the moment.
I do not use ZFS.
The CPU ist set to "kvm64". Same with "host". Do you want me to try anything else?
I tried to install Debian in a VM. Got traps: expr[5186] general protection ip:7f35232519bd sp:7ffebee96de0 error:0 in libc.so.6[7f35231ef000+148000] inside the...
Same symptom with 5.3.1-1-pve, which seems to be the first kernel after 5.0.21-5-pve. So probably something with the 5.3 series.
See attached dmesg.log (from 5.3.13-1-pve). This seems to happen one time only, after I boot the VM for the first time. Can't reproduce it without rebooting the...
I upgraded from 6.0 to 6.1 and now my Window VMs are bluescreening all over the place with several different messages like:
KERNEL SECURITY CHECK FAILURE
IRQL LESS OR EQUAL
KMODE EXCEPTION NOT HANDLED
CRITICAL PROCESS DIED
SYSTEM SERVICE EXCEPTION
UNEXPECTED STORE EXCEPTION
The CPU of the host...
I upgraded from 6.0 to 6.1 and now my Window VMs are bluescreening all over the place with several different symptoms like "KERNEL SECURITY CHECK FAILURE".
I would like to try and downgrade to 6.0, but "# apt-get install proxmox-ve=6.0-2" gives me proxmox-ve 6.0 and everything else is from 6.1...
Hi,
I am planning to set up a PVE host in a remote location. The owner of the location will provide me with internet access at one of the LAN interfaces of my host. Through this interface my host will establish a VPN tunnel through which I will be able to access the PVE installation.
My...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.