Search results

Can someone check this:

Can someone tell me how to "reinstall the efi bootloader" for the affected VMs ?

Well, looks like mine are "hard" lockups ... everything freezes, and not a single line @ any of the logs..,, I've enabled crash dumps.. hopefully at least they will provide something..

Well, I lasted about 2 days and whoa - machine froze again, the first GPU shut off (windows vm), the 2nd (kali) was still displaying, but totally unresponsive. Total network connection lost towards the host. And of course - not a single thing in the logs, nada, zip... Any way of forcing...

So, a guide for this is available somewhere?

It would've been nice if all machine types were selectable through the UI...

For me this only happened on 1 VM - Debian 10, all other VMs worked fine.

Actually I managed to get this fixed by switching q35 to pc-q35-3.1, no idea why on q35 it continues to get stuck on uefi shell.

So, after experiencing complete machine freeze several times on the 5.3 kernels, I've installed the 5.4 kernel hoping this gets resolved.. Hardware is: ASUS TRX40-PRO (latest bios) Threadripper 3960x 8x8G ddr4 3200MHz (no ECC) 320G hdd (pve installed on it) -- NO zfs 1T XPG GAMMIX S5 nvme (VM...

Yes, I'm using the no-sub repo. proxmox-ve: 6.1-2 (running kernel: 5.3.18-3-pve) pve-manager: 6.1-11 (running version: 6.1-11/f2f18736) pve-kernel-helper: 6.1-9 pve-kernel-5.3: 6.1-6 pve-kernel-5.0: 6.0-11 pve-kernel-5.3.18-3-pve: 5.3.18-3 pve-kernel-5.3.18-2-pve: 5.3.18-2...

After today's update one of my VMs got stuck on uefi shell. It's Debian 10 x64. Here is the config: agent: 1 balloon: 0 bios: ovmf boot: c bootdisk: virtio0 cores: 12 cpu: host,flags=+pdpe1gb;+aes efidisk0: NVME_STORAGE:vm-105-disk-1,size=4M ide2: none,media=cdrom machine: q35 memory: 8192...

Well, I didn't reach the kernel testing stage... After today's PVE update one of my VM's stopped working (stuck on uefi shell). I"ll open a new topic about this and link it here -- https://forum.proxmox.com/threads/problem-vm-stuck-on-uefi-shell-after-todays-pve-update.69393/

I'm also running a desktop hardware (TR 3960x, ASUS TRX40-PRO w.latest bios), will test later if 5.4 kernel has any issues on my hw. Actually something weird happened today after I updated the bios to last version - the nvme drive disappeared for some reason, few reboots later it appeared &...

That actually helped.. thanks :)

The guest was working perfectly fine. No updates were installed on it prior to the problem. So, I don't think this is a "guest" problem.

So, any info on this?

Anyone ?

The VM that has this problem is 18.04.4 4.15.0-91. I don't have another ubuntu VM at the moment (no disk space available for a new VM).

Well, I'm running debian 10 in another VM and don't have any issues with it. Only the ubuntu vm has this noVNC problem.

This will probably take a while, COVID-19 ....