Search results for query: boot GPU

sure. here is my current config: agent: 1 args: -cpu...

OK - I will experiment with disabling fast boot, as well as putting OpROMs to disabled, all though I suspect in doing so I will loose access to my firmware configuration, because my server doesn't have an integrated GPU. (Does have a serial port, but I don't think it can output BIOS screens to...

On my supermicro I can disable all OpROMs, but I don't have a GPU, so unfortunately I also don't know. Maybe try to disable fast boot, this is known to cause issues with Linux, especially the MSI implementation of it.

OK. I will try this again when I have physical access to the box again. The last I tried, I put Video OpROM to UEFI (it was legacy), and lost all video output - had to reset it back to gain access even to the firmware configuration. I am not too familiar with OpROM's, I can't remember if there...

IMHO CSM creates more problems than it solves. AFAIK CSM only helps with booting in UEFI but not being able to Secure boot. Since that is not the case for Proxmox, this does not apply. So I would set it to UEFI only and CSM disabled to get a UEFI and secure boot enabled Proxmox install. Your...

Could you send me the ROM for the graphics card and sound card? Unfortunately, I don't know if I can do it myself, but then I would have it ready and could help you test what the problem might be :)

Please try unplug and then reconnect the HDMI cable to see if it works.

btw i got the display to work somewhat. when the vm boots i see the boot process up until the windows login on the display and then it craps out and shows garbage on the screen. to get that far i needed to extract the specific rom file for the H255 using the tools here...

Hi everyone! I just wanted to write a guide for those (like myself) trying out GPU passthrough with the HP ProDesk 600 G1 in 2025... I needed to enable VT-d using the "Replicated setup" method (previously mentioned here) in the UEFI/BIOS as the VT-d option was not present in the menus (GUI)...

Obviously, your hookscript has problems in the pre-start phase. Looks like it is trying to do stuff to the GPU. Maybe disable the hookscript for now? The "stuck in D3" indicated that the GPU does not reset properly. Are you sure that the GPU is not used during the boot process? Is vfio-pci (and...

Set the motherboard BIOS to boot with the integrated graphics. Make sure it shows output (like the motherboard logo and boot loader) on a display connected to the integrated graphics, and to show nothing on a display connected to the 9060XT. Also, early bind vfio-pci to the 9060XT so no driver...

I have a cpu with onboard graphics, if you can point me to a guide to make sure nothing touches the gpu during boot.

This is not uncommon as many devices don't reset properly and does not have to be a problem. If your GPU does not reset properly (which is most likely the case) then you need to make sure nothing touches the GPU during the Proxmox boot process (use another GPU to boot from or use the...

error writing '1' to '/sys/bus/pci/devices/0000:03:00.0/reset': Inappropriate ioctl for device failed to reset PCI device '0000:03:00.0', but trying to continue as not all devices need a reset kvm: ../hw/pci/pci.c:1815: pci_irq_handler: Assertion `0 <= irq_num && irq_num < PCI_NUM_PINS' failed...

Does your VM experience a performance decrease when using args: -cpu 'host,-hypervisor,kvm=off' compared to when they are not used?

Ok, So the exclamation mark is gone. I followed this reddit post , https://www.reddit.com/r/MiniPCs/comments/1pl8h29/gmktec_k12_780m_igpu_and_proxmox_9_passthru/ here is my conf agent: 1 args: -cpu 'host,-hypervisor,kvm=off' bios: ovmf boot: order=ide0;scsi0 cores: 8 cpu: host efidisk0...

Hello, I used to be able to upload isos from the web ui. This is a basic feature, of course it worked, never had a problem with pve 8. Somewhere since PVE9, maybe 9.1, I can no longer upload isos. The system io stall goes up to 90 and the upload stops dead. it is pretty consistent that it...

You would have to show the entire configuration, what exactly you changed and what you added. Generally, Windows itself will work without any problems, the only issue is with restarting. The question is also why you are using AMDGopDriver.rom instead of AMDGopDriver_8845hs.rom, and it would be...

I haven't tried using a Linux VM instead of a Windows VM, though that would probs be a good thing to try. The issue with that is I don't exactly have enough space to do that at the moment, but I will test that when I get the ability to. I know that ejecting the GPU before shutting down the VM...

Maybe the drivers leave the GPU in a state that the same driver does not expect or cannot handle on the next VM boot. Have you tried a recent Linux VM to see if it has the same problem. Maybe starting a Linux VM after the Windows VM helps as a work-around. Or maybe ejecting the GPU before...