Recent content by jf2021

Thanks a lot @sbraz for the detailed fix and explanantions. I edited my first post to recommend reading yours !

Hi. After struggling a little to upgrade from Proxmox 8 to 9 on bare metal servers hosted by OVH, I thought I'd explain how I succeeded. First of all, this is not a generic tutorial, this is just how I could solve my problem on my 2 servers (one "So-yo-start SYS-LE-2" and one "ADVANCE-1 | AMD...

@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.

Seems to be stable. Marked as solved.

@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...