So today I tried to spin up am VM on a Hetzner Dedicated server to evaluate RDP performance in a VirGL-GPU accelerated VM.
Unfortunatly the host crashes as soon as inside the VM the switch to the login console would happen.
I just confirmed that it's crashing with a KVM attached, but on the host system the cursor just stops blinking and after a few seconds the BIOS boot messages start appearing.
Unfortunatly their KVM doesn't provide serial console, so since the gpu seems to be crashing I not able to get any crashlogs if there are any.
Also journald doesn't contribute anything.
That system's out cold...
CPU: AMD Ryzen 7 PRO 8700GE w/ Radeon 780M Graphics
Maybe this is already known, maybe not.
I don't even think this is proxmox related, but with autostart this can easily become a boot loop.
For now i'm gonna
Maybe someone has a local homelab with said CPU with access to serial console.
Unfortunatly the host crashes as soon as inside the VM the switch to the login console would happen.
I just confirmed that it's crashing with a KVM attached, but on the host system the cursor just stops blinking and after a few seconds the BIOS boot messages start appearing.
Unfortunatly their KVM doesn't provide serial console, so since the gpu seems to be crashing I not able to get any crashlogs if there are any.
Also journald doesn't contribute anything.
That system's out cold...
CPU: AMD Ryzen 7 PRO 8700GE w/ Radeon 780M Graphics
Maybe this is already known, maybe not.
I don't even think this is proxmox related, but with autostart this can easily become a boot loop.
For now i'm gonna
apt purge libgl1 libegl1 and will avoid that for now.Maybe someone has a local homelab with said CPU with access to serial console.