One VM started crashing after upgrade cluster to 6.4-15

M

Minotaur

Member
Jun 20, 2019
10
1
23
43
Hello!

I've upgraded cluster from 5.4 to 6.4-15 today. After that one VM, which smoothly worked before, with quite old FreeBSD 9.3-RELEASE (amd64) started crashing on boot. I've tried different CPU types, different Machine options, different RAM sizes, different Displays - nothing helps. On FreeBSD Bugzilla I've found this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190529
Any chance to get this VM running? Maybe it is possible to use older SeaBIOS version?

Please advise! Thank you!
 

Attachments

  • firefox_5e9f7XNVte.png
    firefox_5e9f7XNVte.png
    154.4 KB · Views: 4
hi,

can you post the output from pveversion -v and qm config VMID (for your VM)
 
Hello!

Code: 
root@proxmox1:~# pveversion -v
proxmox-ve: 6.4-1 (running kernel: 5.4.189-2-pve)
pve-manager: 6.4-15 (running version: 6.4-15/af7986e6)
pve-kernel-5.4: 6.4-18
pve-kernel-helper: 6.4-18
pve-kernel-5.4.189-2-pve: 5.4.189-2
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
pve-kernel-4.13.13-2-pve: 4.13.13-33
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.5-pve2~bpo10+1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.22-pve2~bpo10+1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.1.0-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-5
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-5
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.14-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.6-2
pve-cluster: 6.4-1
pve-container: 3.3-6
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.3-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-8
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.7-pve1

Code: 
root@proxmox1:~# qm config 101
bios: seabios
boot: order=ide2
cores: 4
ide2: local:iso/FreeBSD-9.3-RELEASE-amd64-disc1.iso,media=cdrom,size=655422K
kvm: 0
memory: 8192
name: noc
net0: e1000=62:F9:26:CD:B5:B6,bridge=vmbr0,tag=50
net1: e1000=66:29:90:76:1C:32,bridge=vmbr0
numa: 0
onboot: 1
ostype: other
sata0: SystemDisks:vm-101-disk-1,cache=writethrough,size=300G
scsihw: virtio-scsi-pci
smbios1: uuid=d6626562-1ea1-424e-9bf5-0bca2315bcca
sockets: 1
 
Thank you for confirmation! The issue seems to be related to VESA extensions. I had options VESA # Add support for VESA BIOS Extensions (VBE) in my FreeBSD 9.3 kernel configuration. It's present in GENERIC as well. I've managed to compile it out on other box and replace kernel in problematic VM. Now it starts fine.
 
  • Like
Reactions: oguz
You must log in or register to reply here.
Top Bottom