Search results

Bumping an old thread to let people know that this also just helped me, and to keep it fresh for anyone else who might need it! Would it make sense for the GUI to 'remember' your last storage selection per VM so it stays on whatever you previously chose? Otherwise you need to re-select your...

This thread is older, but I can add some clarity here as I'm working through the same issue. OP mentioned that he's on an HP DL380P G8, which uses the Intel 5520 chipset. That chipset has a documented problem with interrupt remapping...

Ah ha! I was thinking it was already in HBA mode, but it's a P420i... apparently at one point I set each drive to its own raid0 as a workaround for not being able to boot from this controller when it's set to HBA. Nowadays I have it booting off a separate SSD running off one of the SATA ports...

Oddly, this is still an issue for me on a ProLiant DL380p Gen8, with a brand new install of Proxmox 8.0.3, with smartmontools 7.3-pve1: root@pve:~# pveversion -v proxmox-ve: 8.0.1 (running kernel: 6.2.16-3-pve) pve-manager: 8.0.3 (running version: 8.0.3/bbf3993334bfa916) pve-kernel-6.2: 8.0.2...

Same here, also getting several VMs failing to boot with: "no efidisk configured! Using temporary efivars disk." Oddly, it's not every VM, just roughly half. EDIT: Installing binutils as mentioned above solved it for all VMs except one.

Hello all, Is there a way to prioritize a VM/container to use *only* idle host CPU time? i.e, not affect the performance of any other containers and essentially freeze if the host CPU is 100% utilized by other processes/containers? Thanks!

I'm having a similar issue, this grub upgrade does need looking at on the Proxmox side:

I've written a maintenance mode script! I have a mix of VMs, some of which are set to start at boot, others which aren't. So I expanded on jf2021's one-liner so I can query each VM, check the onboot: setting, save a list of VMs with onboot: 1 to a file, and disable them. Now I can reboot to...

Also necroing this thread to add that I also have this issue, the keyboard becomes 'undetected' at the EULA screen. Works perfectly at BIOS/EFI before that point. The workaround I've found is to unplug/replug the keyboard. The device is then successfully redetected and installation can...