VNC Console error Grub

[andaga]

Hello!

There is a bug that I really can't understand with ProxMox!

Almost all our VMs with Ubuntu 22.04 at startup get stuck on the following message:

GRUB_FORCE_PARTUUID set, attempting initrdless boot.

So impossible to access in console mode to the VM!

On the other hand, the VM works perfectly and you can access it with SSH and all the services run normally.

If we change the console to use the version: xterm.js, no problem everything works normally. It's only with the default console of ProxMox!

We use the latest version of ProxMox 7.3-6

Any idea why?

 

[fiona]

Hi,
please share the output of pveversion -v and qm config <ID> with the ID of the VM. What is the kernel commandline inside the VMs?

 

[andaga]

root@pve1:~# pveversion -v
proxmox-ve: 7.3-1 (running kernel: 5.15.102-1-pve)
pve-manager: 7.3-6 (running version: 7.3-6/723bb6ec)
pve-kernel-helper: 7.3-8
pve-kernel-5.15: 7.3-3
pve-kernel-5.15.102-1-pve: 5.15.102-1
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.15.64-1-pve: 5.15.64-1
pve-kernel-5.15.60-2-pve: 5.15.60-2
pve-kernel-5.15.60-1-pve: 5.15.60-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.3-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-2
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-6
libpve-storage-perl: 7.3-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.3.3-1
proxmox-backup-file-restore: 2.3.3-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.1-1
proxmox-widget-toolkit: 3.5.5
pve-cluster: 7.3-2
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20221111-1
pve-firewall: 4.2-7
pve-firmware: 3.6-4
pve-ha-manager: 3.5.1
pve-i18n: 2.8-3
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.9-pve1


root@pve1:~# qm config 1074
agent: 1
boot: order=scsi0
cipassword: **********
ciuser: root
cores: 4
cpu: host
cpulimit: 4
cpuunits: 1
description: 77.37.8.92
ide0: PVE-NFS:1074/vm-1074-cloudinit.qcow2,discard=on,media=cdrom,size=4M
ide2: none,media=cdrom
ipconfig0: ip=171.33.243.9/24,gw=171.33.243.1
memory: 12288
meta: creation-qemu=7.0.0,ctime=1667754862
name: en2.maxihoster.com
net0: virtio=ea:33:08:0d:c3:75,bridge=vmbr1,firewall=1,tag=20
numa: 0
onboot: 1
ostype: l26
scsi0: PVE-NFS:1074/vm-1074-disk-0.qcow2,discard=on,size=500G
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=29acb3e9-3b5f-4205-b2fa-fc17e9db44fd
sockets: 1
vmgenid: 931d30e8-2257-4a4a-930a-b052a146c12b
root@pve1:~#

 

[andaga]

root@en2:~# uname -r
5.15.0-1029-kvm
root@en2:~# cat /proc/version
Linux version 5.15.0-1029-kvm (buildd@lcy02-amd64-119) (gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #34-Ubuntu SMP Wed Feb 8 18:31:06 UTC 2023
root@en2:~#

 

[fiona]

root@pve1:~# qm config 1074
...
serial0: socket
...

Does it work if you use the Serial terminal 0 setting for Display in the VM's Hardware tab in the UI?

You can see the kernel commandline with cat /proc/cmdline.

 

[andaga]

BOOT_IMAGE=/boot/vmlinuz-5.15.0-1029-kvm root=PARTUUID=46568545-2bc2-4517-a15c-0c9b8c4398fb ro console=tty1 console=ttyS0 panic=-1

And yes it work with the serial terminal 0 in the display of the settings hardware....

 

[fiona]

BOOT_IMAGE=/boot/vmlinuz-5.15.0-1029-kvm root=PARTUUID=46568545-2bc2-4517-a15c-0c9b8c4398fb ro console=tty1 console=ttyS0 panic=-1

And yes it work with the serial terminal 0 in the display of the settings hardware....

Not sure why it doesn't work with the default display in your case, because the console=tty1 is there. I have a VM with a similar configuration and there it does work with both display settings.

 

[andaga]

I can' tell you why! Some vm work some other not!
This behaviour is since I have updated proxmox to the last version 2-3 days ago!

 

[fiona]

I can' tell you why! Some vm work some other not!
This behaviour is since I have updated proxmox to the last version 2-3 days ago!

Can you try and downgrade pve-qemu-kvm to the version that was installed before and see if it works with that? You can check /var/log/apt/history.log to see what happened during the upgrade.

 

[andaga]

How to do this?

 

[fiona]

How to do this?

As already, said check in /var/log/apt/history.log for the version and then run apt install pve-qemu-kvm=w.x.y-z