New to Proxmox - Lubuntu VM's dont boot without reset

[TheBokke]

Hi all,

Great forums and great product, still getting my head round Proxmox but it looks like a very powerful product and I'm enjoying the learning curve.

I've created a couple of Lubuntu 18.04 Guests and have configured them. Seems to work fine, but when I stop and restart the VM's I just get a black screen on the console, summary shows VM's running but nothing in SPice or noVNC. If I reset from within the console/Spice window I get the GRUB loader screen and the VM boots fine.Seems to be an issue with the virtual disk drive? VM's are pretty basic, dual core, 32GB, 4Gb Ram, Virt-IO SCSI disk. One will be used for Unifi video as an NVR so I need it to boot if the server restarts. At the moment it requires a manual intervention which is not ideal

What am I doing wrong - Is there a setting that helps this? .

Thanks in advance

 

[fireon]

Hello

please post the vmconfig by command:

qm config <vmid>

and your Proxmoxversio:

pveversion -v

Also disable bootsplash for the vm to see the messages by edit the file "/etc/default/grub". Exampleline:

GRUB_CMDLINE_LINUX_DEFAULT="verbose nosplash noplymouth fsck.repair=preen"

After that update the bootloaden:

update-grub

On the next reboot you see all messages. You can search backwards in the logs for errors too:

journalctl -r -p3

 

[TheBokke]

Thanks for the reply Fireon,

Output as requested:

# qm config 103

agent: 1
args: -device intel-hda,id=sound5,bus=pci.0,addr=0x18 -device hda-micro,id=sound5-codec0,bus=sound5.0,cad=0 -device hda-duplex,id=sound5-codec1,bus=sound5.0,cad=1
boot: dnc
bootdisk: virtio0
cores: 2
ide2: none,media=cdrom
memory: 4096
name: SecurityVMR
net0: virtio=A2:15:90:FA:0B4,bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
scsihw: virtio-scsi-pci
smbios1: uuid=adb582ed-e5b1-47c0-a2f9-83373cffe38b
sockets: 1
usb0: spice
vga: qxl
virtio0: VMStorage:vm-103-disk-0,cache=writethrough,size=32G
vmgenid: 1a398725-4451-46e5-aa2f-d0d38594d652

For the Proxmox Version:

~# pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.18-7-pve)
pve-manager: 5.2-11 (running version: 5.2-11/13c2da63)
pve-kernel-4.15: 5.2-10
pve-kernel-4.15.18-7-pve: 4.15.18-27
pve-kernel-4.15.17-1-pve: 4.15.17-9
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-1
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-41
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-30
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-3
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-29
pve-docs: 5.2-10
pve-edk2-firmware: 1.20181023-1
pve-firewall: 3.0-14
pve-firmware: 2.0-6
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.14.1-1
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-40
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.12-pve1~bpo1

Thanks for the advice on disabling the bootsplash, I've made those changes. Does this allow errors for reboot of Proxmox host to be read or the VM itself? If the VM, how di I read this?

I ran the command on the host and have the following:

Mar 11 21:57:08 pve postfix/local[14579]: error: open database /etc/aliases.db: No such file or directory
Mar 11 21:52:09 pve iscsid[4295]: iSCSI daemon with pid=4299 started!
Mar 11 21:52:08 pve smartd[4031]: Device: /dev/sdi [SAT], 88 Currently unreadable (pending) sectors
Mar 11 21:51:59 pve kernel: Error: Driver 'pcspkr' is already registered, aborting...
Mar 11 21:51:58 pve kernel: Couldn't get size: 0x800000000000000e
Mar 11 21:51:58 pve kernel: Couldn't get size: 0x800000000000000e
Mar 11 21:51:58 pve kernel: MODSIGN: Couldn't get UEFI db list
Mar 11 21:51:58 pve kernel: Couldn't get size: 0x800000000000000e

Thanks once again for your help with this.