debian vms won't start anymore

H

herm

Member
Nov 10, 2021
13
6
8
50
Hi,

after activating my new licence key, update the system with apt upgrade followed by a reboot no vm was able to boot anymore. after some research i found out that i have to configure their "Display" option to "Default" in order to be able to start them again.
Before upgrading the system using the pve-enterprise repository i was able to start the vm's with Display set to "none".

herm
 
hi,

setting display to "none" should still work (the VM will boot but you won't be able to interact graphically).
if you are getting an error message please post it here, along with the output from pveversion -v command.
pasting the VM configuration (from qm config VMID) would be also interesting to see
 
it seems the vm stucks somewhere at the boot process ... but as i have no display i can't see where ;-) but i swear it worked before upgrading with the enterprise repository :-)

root@micromaster ~ # qm status 102
status: running



root@micromaster ~ # qm config 102
agent: 1,fstrim_cloned_disks=1
balloon: 0
boot: order=scsi0;net0
cores: 2
machine: q35
memory: 12288
name: ms
net0: virtio=CA:D8:14:AE:31:53,bridge=vmbr0
numa: 0
onboot: 1
ostype: l26
scsi0: local-zfs:vm-102-disk-0,discard=on,size=10G,ssd=1
scsi1: vg04:vm-102-disk-0,backup=0,discard=on,size=953856M,ssd=1
scsi2: vg06:vm-102-disk-0,backup=0,size=5589G
scsi3: vg05:vm-102-disk-0,discard=on,size=450G,ssd=1
scsihw: virtio-scsi-pci
smbios1: uuid=233b93c8-2d4a-4303-80c6-5696853d1560
sockets: 1
startup: order=2
vga: none
vmgenid: e63c861d-26a5-4cdd-a0f7-629fa2b4d0bd

root@micromaster ~ # pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-5-pve)
pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e)
pve-kernel-helper: 7.1-2
pve-kernel-5.11: 7.0-8
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-4-pve: 5.11.22-9
ceph-fuse: 15.2.14-pve1
corosync: 3.1.5-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.22-pve1
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-10
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-3
libpve-storage-perl: 7.0-12
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.11-1
proxmox-backup-file-restore: 2.0.11-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.1-1
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-4
pve-firmware: 3.3-2
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-4
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-14
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1
 
hi, updated the configs .... now they start flawlessly :)

thx for your quick help!
herm
 
You must log in or register to reply here.
Top Bottom