Proxmox 6.2 with older VMs

Digitaldaz

Active Member
Feb 19, 2014
54
2
28
Is anyone experiencing problems with older VMs?

I've only just installed 6.2 and started migrating VMs but I'm getting a Debian Jessie constantly crashing with a kernel panic relating to some scsci thing or other and I now have an Ubuntu 8.04 VM that almost immediately after bootup loses network connectivity when using virtio, I have switched it to e1000 and this seems to have fixed it.

TIA
Daz
 

Digitaldaz

Active Member
Feb 19, 2014
54
2
28
I am having problems with ZFS, all sorts of things are going wrong, mysql failing with too may open files etc. I have had to migrate this vm to a box I just rented and installed 5.4 on. This looks bad though as 5.4 is going EOL.
 
Mar 4, 2020
9
1
3
44
Ok, I found out that my problem seems to be this bug https://bugzilla.proxmox.com/show_bug.cgi?id=2311

When a vm is running with CEPH/KRBD it uses a block device for the vms image. I’ve not tried to run Proxmox with ZFS but my guess is that it also uses a block-device for the vm image. If you have the discard flag on, it would be interesting to see if you still get the problems if you turn discard off. In case it’s stable for you without discard when I would say it may be the same bug.
 

Digitaldaz

Active Member
Feb 19, 2014
54
2
28
My issue with the sql was actually related to me upgrading to wheezy from jessie to try and fix the issue. The my.cnf file was the problem so actually nothing to do with proxmox.

My other two issues where networking and a kernel panic relating to the scsi driver.

My networking issue was fixed by switching to e1000 instead of virtio and the iscsi panic should now be resolved by switching to the megasas driver.

It seems I now have workarounds for all my issues so far. :)
 

Erk

Active Member
Dec 11, 2009
165
6
38
I moved a FreeBSD 9.3-RELEASE vm across from a Proxmox 6.1.5 server to a fresh 6.2.4 server, just using local drive (xfs) storage for the VM and it seg faults just after the FreeBSD kernel loads on 6.2.4.

It's just the FreeBSD amd64 GENERIC kernel.

bootdisk: ide0
cores: 2
cpu: kvm64,flags=-pcid;-spec-ctrl;-ibpb;-amd-ssbd;-amd-no-ssb;-aes
ide0: vm:100/vm-100-disk-0.qcow2,size=80G
machine: pc-i440fx-1.7
memory: 3008

net1: e1000=AE:38:7D:6F:31:C4,bridge=vmbr0
numa: 0
ostype: other
sockets: 1
startup: order=1


Unfortunately the text scrolls up the console screen too fast for me to see if there is any more lines after the kernel load before the dump. I don't know what to try to solve this. I need to run that old FreeBSD version until the programs on it are upgraded. I can stay on an earlier Proxmox, but I would like to know why the crash is happening.
 

LnxBil

Famous Member
Feb 21, 2015
6,660
878
163
Saarland, Germany
Unfortunately the text scrolls up the console screen too fast for me to see if there is any more lines after the kernel load before the dump. I don't know what to try to solve this. I need to run that old FreeBSD version until the programs on it are upgraded. I can stay on an earlier Proxmox, but I would like to know why the crash is happening.

If you want or need to debug this further, think about the serial line as output target, so that you'll get all information displayed, but as text. I often use this approach as last resort for debugging early kernel problems.
 

LnxBil

Famous Member
Feb 21, 2015
6,660
878
163
Saarland, Germany
I just bootet the FreeBSD 9.2 install ISO to get a trace and in fact, it panics directly:

Code:
Booting...
Copyright (c) 1992-2013 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.2-RELEASE #0 r255898: Thu Sep 26 22:50:31 UTC 2013
    root@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
gcc version 4.2.1 20070831 patched [FreeBSD]
CPU: Common KVM processor (1497.66-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0xf61  Family = 0xf  Model = 0x6  Stepping = 1
  Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
  Features2=0x80202001<SSE3,CX16,x2APIC,HV>
  AMD Features=0x20100800<SYSCALL,NX,LM>
  AMD Features2=0x1<LAHF>
  TSC: P-state invariant
real memory  = 2147483648 (2048 MB)
avail memory = 2042494976 (1947 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: <BOCHS  BXPCAPIC>
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ioapic0 <Version 1.1> irqs 0-23 on motherboard
kbd1 at kbdmux0
kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x0
fault code              = supervisor write data, page not present
instruction pointer     = 0x20:0xffffffff80d10b8f
stack pointer           = 0x28:0xffffffff817bf770
frame pointer           = 0x28:0xffffffff817bf950
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = resume, IOPL = 0
current process         = 0 (swapper)
trap number             = 12
panic: page fault
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff80947986 at kdb_backtrace+0x66
#1 0xffffffff8090d9ae at panic+0x1ce
#2 0xffffffff80cf20d0 at trap_fatal+0x290
#3 0xffffffff80cf2431 at trap_pfault+0x211
#4 0xffffffff80cf29e4 at trap+0x344
#5 0xffffffff80cdbd13 at calltrap+0x8
#6 0xffffffff80d11120 at vesa_mod_event+0x110
#7 0xffffffff808f80c8 at module_register_init+0xa8
#8 0xffffffff808ba947 at mi_startup+0x77
#9 0xffffffff802e1f6c at btext+0x2c
Uptime: 1s
Automatic reboot in 15 seconds - press a key on the console to abort

It seems to be this FreeBSD bug which it is quite old and has no solution besides using a newer FreeBSD version. The 10.2 mentioned in the bug report works.
 
  • Like
Reactions: Erk

Erk

Active Member
Dec 11, 2009
165
6
38
I just bootet the FreeBSD 9.2 install ISO to get a trace and in fact, it panics directly:

Code:
Booting...
Copyright (c) 1992-2013 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 9.2-RELEASE #0 r255898: Thu Sep 26 22:50:31 UTC 2013
    root@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
gcc version 4.2.1 20070831 patched [FreeBSD]
CPU: Common KVM processor (1497.66-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0xf61  Family = 0xf  Model = 0x6  Stepping = 1
  Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
  Features2=0x80202001<SSE3,CX16,x2APIC,HV>
  AMD Features=0x20100800<SYSCALL,NX,LM>
  AMD Features2=0x1<LAHF>
  TSC: P-state invariant
real memory  = 2147483648 (2048 MB)
avail memory = 2042494976 (1947 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: <BOCHS  BXPCAPIC>
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
cpu0 (BSP): APIC ID:  0
cpu1 (AP): APIC ID:  1
ioapic0 <Version 1.1> irqs 0-23 on motherboard
kbd1 at kbdmux0
kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x0
fault code              = supervisor write data, page not present
instruction pointer     = 0x20:0xffffffff80d10b8f
stack pointer           = 0x28:0xffffffff817bf770
frame pointer           = 0x28:0xffffffff817bf950
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = resume, IOPL = 0
current process         = 0 (swapper)
trap number             = 12
panic: page fault
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff80947986 at kdb_backtrace+0x66
#1 0xffffffff8090d9ae at panic+0x1ce
#2 0xffffffff80cf20d0 at trap_fatal+0x290
#3 0xffffffff80cf2431 at trap_pfault+0x211
#4 0xffffffff80cf29e4 at trap+0x344
#5 0xffffffff80cdbd13 at calltrap+0x8
#6 0xffffffff80d11120 at vesa_mod_event+0x110
#7 0xffffffff808f80c8 at module_register_init+0xa8
#8 0xffffffff808ba947 at mi_startup+0x77
#9 0xffffffff802e1f6c at btext+0x2c
Uptime: 1s
Automatic reboot in 15 seconds - press a key on the console to abort

It seems to be this FreeBSD bug which it is quite old and has no solution besides using a newer FreeBSD version. The 10.2 mentioned in the bug report works.
That link you posted describes a FreeBSD 10.1 bug, and it says the bug doesn't happen with 9.3-RELEASE. You have got me curious now, I am going to try some of the other FreeBSD installers to see which ones crash on Proxmox 6.2.4 and which work. I can update my FreeBSD 9.3-RELEASE system, but it's a tedious process compared to a linux distro, can take many hours of work.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!