Another Proxmox Empty/Blank Console

[akos]

Hi All
I have a similar issue with an existing VM that I can no longer access. It is a PopOS 22.04 VM created from the the PopOS install image (so not an LXC container) and have been running in my PVE v7.4-17. Trying to access it through the noVNC console results in a successful boot-up by am greeted with a dark screen with no username/password prompt to log in. I can see the pointer chasing my mouse actions in the screen, but pressing real or virtual keyboard keys and combinations provides no login fields. The VM is configured with an encrypted LVM filesystem so no (easy) I have access to the raw files to set up (change or disable) any files and I have ufw only allowing egress traffic from the VM, I can't ssh in from outside. I tried to set up serial console access, ...

qm set <vmid> -serial0 socket
<restart VM>
qm terminal <vmid> -iface serial0

but my getty process hasn't been set up so the serial access also hangs, and I can't access my GRUB prompt underneat the encrypted file system.

Is there any easy way to recover my existing GUI based (or text based) login prompt?
TIA!

 

[Gilberto Ferreira]

Hi
Can you send the output of
qm config VMID
?

 

[akos]

Thanks for the response, here you are:
root@pve03:~# qm config 100100

agent: 1,fstrim_cloned_disks=1
balloon: 4096
boot: order=scsi0
cores: 2
memory: 24576
meta: creation-qemu=7.2.0,ctime=1680347317
name: PopOS
net0: virtio=8A:82:81:56:34:12,bridge=vmbr0,firewall=1,tag=14
net1: virtio=F2:3F:75:68:87:99,bridge=vmbr0,firewall=1,tag=21
numa: 0
ostype: l26
scsi0: local:100100/vm-100100-disk-0.raw,iothread=1,size=128G
scsihw: virtio-scsi-single
smbios1: uuid=dc4889ed-bf42-467e-a064-ba3e8483e8d2
sockets: 2
vmgenid: 2695fae7-1d43-4287-af80-b777d5047e77

 

[Gilberto Ferreira]

Thanks for the response, here you are:
root@pve03:~# qm config 100100

agent: 1,fstrim_cloned_disks=1
balloon: 4096
boot: order=scsi0
cores: 2
memory: 24576
meta: creation-qemu=7.2.0,ctime=1680347317
name: PopOS
net0: virtio=8A:82:81:56:34:12,bridge=vmbr0,firewall=1,tag=14
net1: virtio=F2:3F:75:68:87:99,bridge=vmbr0,firewall=1,tag=21
numa: 0
ostype: l26
scsi0: local:100100/vm-100100-disk-0.raw,iothread=1,size=128G
scsihw: virtio-scsi-single
smbios1: uuid=dc4889ed-bf42-467e-a064-ba3e8483e8d2
sockets: 2
vmgenid: 2695fae7-1d43-4287-af80-b777d5047e77

If you trying to use qm terminal, you definitely need to set a serial port to your VM.Compare to mine here:

root@pve01:~# qm config 100
boot: order=scsi0;ide2;net0
cores: 1
cpu: x86-64-v2-AES
ide2: local:iso/pop-os_22.04_amd64_intel_39.iso,media=cdrom,size=2646432K
memory: 2048
meta: creation-qemu=8.1.5,ctime=1710346838
name: teste
net0: virtio=BC:24:11:80:38:AA,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: local:100/vm-100-disk-0.qcow2,iothread=1,size=32G
scsihw: virtio-scsi-single
serial0: socket
smbios1: uuid=e14f9e79-4475-4cb6-bc82-118406705329
sockets: 1
vmgenid: f793a5ee-60e9-4a37-8397-7a9a13aaa7b8

Check it out: https://pve.proxmox.com/wiki/Serial_Terminal

 

[akos]

If you trying to use qm terminal, you definitely need to set a serial port to your VM.Compare to mine here:

root@pve01:~# qm config 100
boot: order=scsi0;ide2;net0
cores: 1
cpu: x86-64-v2-AES
ide2: local:iso/pop-os_22.04_amd64_intel_39.iso,media=cdrom,size=2646432K
memory: 2048
meta: creation-qemu=8.1.5,ctime=1710346838
name: teste
net0: virtio=BC:24:11:80:38:AA,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: local:100/vm-100-disk-0.qcow2,iothread=1,size=32G
scsihw: virtio-scsi-single
serial0: socket
smbios1: uuid=e14f9e79-4475-4cb6-bc82-118406705329
sockets: 1
vmgenid: f793a5ee-60e9-4a37-8397-7a9a13aaa7b8

Check it out: https://pve.proxmox.com/wiki/Serial_Terminal

Yeah I did that, followed the same document, but it made my non-functioning (as I haven't set it up within the VM before) serial console the default, hence I removed it (before my `qm config 100100` capture just now)