@fiona Thanks for the update !
After trying on 2 différent machines, I can confirm that with the latest kernel 5.15.107-1-pve, the bug doesn't occur anymore. Windows VM work as expected with hv-tlbflush on.
@milsav92 Thanks a lot for your suggestion, removing this flag seems to work. I still want to see on the long term how it goes and if it's stable, but I was able to log into the Windows VM and use it.
Also wondering why, since this option has been on forever and never caused problem with...
Hi. After upgrading to 5.15.104-1-pve (no-subscription package), Windows Server VM boot but they freeze/get stucked before login screen. I got some errors in the kern.log. It seems to happen to different machine with different hardware (Intel or AMD CPU).
Rolling back to 5.15.102-1-pve solved...
Everything looks fine here too with the updated kernel, Windows VMs are running normally, and no more error logs.
@t.lamprecht thanks a lot for your quick response to address the bug !
Sorry for the late reply. In case you need, here is my config
# qm config 105
agent: 0
bootdisk: ide0
cores: 4
cpu: host,flags=+hv-tlbflush
ide0: local:105/vm-105-disk-0.raw,size=200G
ide3: none,media=cdrom
localtime: 1
memory: 16384
name: winsrv105
net0: virtio=XX:XX:XX:XX:XX:XX,bridge=vmbr1...
I confirm the bug. In my case all CTs and Debian VMs start and work fine but Windows VMs seem to be stuck in a loop. I don't even get a console for those VM, however they appear as started in qm list. And syslog keep filling endless with errors like the one below
Mar 08 01:09:45 ns3192824...
@Obi_Yoann, @p1new &al HUUUUUGE thanks for your explanations. Copying the new grubx64.efi worked fine for me to fix the broken boot with "grub_is_lockdown" error after a 6 to 7 upgrade on OVH server.
I don't have much ideas to help you, but are you sure you were able to follow the procedure in the link I gave you to extract the ROM ? This requires to first install the GPU as a secondary on the VM, meaning that you need a working primary GPU for that VM. Then, you should be able to boot...
dmesg might help to understand what's going on, I'm not sure.
Also, Did you try with the dumped rom before using GopUpdate ?
GopUpd is necessary only if your original GPU rom doesn't have an EFI GOP (usually quite old models), in order to add one. That might not be the case of your Quadro, I...
I believe the second option is more future-proof but both work fine.
Maybe you could mark the thread as "solved". You just have to edit your first post and change the flag before the title to "solved"
Hi !
I'm not familiar with Quadro GPU, but I was struggling with an old GT640 giving me the infamous error 43 until I managed to extract properly the ROM file from my GPU.
Have a look at this thread, the given extraction method worked for me (then I had to add the GOP to the rom file using GOPUpd).
And here is a much cleaner / proper solution (also to be tested), using pct/qm command
# Disable autoboot for all CT
for ct in $(pct list | awk '{print $1}' | grep -Eo '[0-9]{1,3}'); do pct set $ct --onboot 0; done
# Disable autoboot for all VM
for vm in $(qm list | awk '{print $1}' | grep...
Hi,
You can replace the value for the "onboot" param in all the conf files at once with sed.
Here is an example. I didn't test it, so please use with care and try it carefully before using and/or backup your conf files...
# Disable autoboot for all CT
sed -i -e "s/^onboot: 1/onboot: 0/g"...
@Asano, thanks a lot for your tips ! It worked !
For all my previous attempts, I had extracted my "original" GPU rom with GPU-Z, and it seems that it wasn't working properly...
I used your method to extract the rom, then I updated it with GOPUpdate and I was finally able to use my old GT640...
Hi ! I've been able to passthrough a PCIe GTX1660 on a fresh install of Proxmox 7 with no problem, as well as many other devices : USB keyboard and mouse, a whole SATA HDD... My MB is a Gigabyte X570
I haven't tried on an upgraded Proxmox but I'd suspect some configuration changes, or device...
Hi !
I'm trying to set up a GPU passtrough to a Win10 VM. I've followed all instructions and procedures, and it's partially working, but I've got a weird case and no more clues...
The host has 2 video cards :
A GTX1660 on PCIe slot 1
A GT640 (Asus GT640-2GD3) on PCIe slot2
When I add the...
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.