[Bug 190529] New: Kernel panic in KVM after recent Linux host upgrade
no-reply-bugzilla-daemon at freebsd.org
no-reply-bugzilla-daemon at freebsd.org
Mon Jun 2 19:04:38 UTC 2014
http://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190529
Bug ID: 190529
Summary: Kernel panic in KVM after recent Linux host upgrade
Product: Base System
Version: unspecified
Hardware: Any
OS: Any
Status: Needs Triage
Severity: Affects Only Me
Priority: ---
Component: bin
Assignee: freebsd-bugs at FreeBSD.org
Reporter: andrej at podzimek.org
After a regular weekly update of the Linux host, all FreeBSD KVM machines panic
on boot, despite the fact that
* the same FreeBSD KVM machines worked perfectly fine before one of the recent
host updates.
* all other KVM machines (OpenIndiana, 3 Linux distributions) still work fine
as usual.
The FreeBSD machines are installed on and boot from ZFS. (Not sure if that's
relevant to the problem -- all the ZFS modules get loaded as usual, the crash
occurs much later.)
Kernel panic message:
fault code = supervisor write data, page not present
instruction pointer = 0x20:0xffffffff80cfb869
stack pointer = 0x28:0xffffffff81a4a6a0
frame pointer = 0x28:0xffffffff81a4a8e0
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 0xffffffff808e7e70 at kdb_backtrace+0x60
#1 0xffffffff808af955 at panic+0x155
#2 0xffffffff80c8e732 at trap_fatal+0x3a2
#3 0xffffffff80c8ea09 at trap_pfault+0x2c9
#4 0xffffffff80c8e196 at trap+0x5e6
#5 0xffffffff80c75432 at calltrap+0x8
#6 0xffffffff80cfa7e6 at vesa_mod_event+0x166
#7 0xffffffff8089b2bb at module_register_init+0xfb
#8 0xffffffff808612d8 at mi_startup+0x118
#9 0xffffffff802d3e0c at btext+0x2c
Uptime: 1s
Automatic reboot in 15 seconds - press a key on the console to abort
Configuration of the KVM machine:
<!--
WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
OVERWRITTEN AND LOST. Changes to this xml configuration should be made using:
virsh edit maple
or other application using the libvirt API.
-->
<domain type='kvm'>
<name>maple</name>
<uuid>0a266182-b840-ac74-af2f-73d6c18daf60</uuid>
<description>FreeBSD</description>
<memory unit='KiB'>10485760</memory>
<currentMemory unit='KiB'>10485760</currentMemory>
<vcpu placement='static'>4</vcpu>
<os>
<type arch='x86_64' machine='pc-i440fx-1.7'>hvm</type>
<boot dev='hd'/>
<bootmenu enable='no'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<cpu mode='custom' match='exact'>
<model fallback='allow'>Westmere</model>
<vendor>Intel</vendor>
<feature policy='require' name='pbe'/>
<feature policy='require' name='rdtscp'/>
<feature policy='require' name='est'/>
<feature policy='require' name='vmx'/>
<feature policy='require' name='ds'/>
<feature policy='require' name='smx'/>
<feature policy='require' name='ss'/>
<feature policy='require' name='vme'/>
<feature policy='require' name='dtes64'/>
<feature policy='require' name='tm2'/>
<feature policy='require' name='ht'/>
<feature policy='require' name='dca'/>
<feature policy='require' name='pcid'/>
<feature policy='require' name='tm'/>
<feature policy='require' name='pdcm'/>
<feature policy='require' name='pdpe1gb'/>
<feature policy='require' name='ds_cpl'/>
<feature policy='require' name='pclmuldq'/>
<feature policy='require' name='xtpr'/>
<feature policy='require' name='acpi'/>
<feature policy='require' name='monitor'/>
</cpu>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/bin/qemu-system-x86_64</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='raw' cache='writeback'/>
<source file='/var/lib/libvirt/images/maple.img'/>
<target dev='vda' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07'
function='0x0'/>
</disk>
<disk type='block' device='cdrom'>
<driver name='qemu' type='raw' cache='none'/>
<target dev='hdc' bus='ide'/>
<readonly/>
<address type='drive' controller='0' bus='1' target='0' unit='0'/>
</disk>
<controller type='usb' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01'
function='0x2'/>
</controller>
<controller type='ide' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01'
function='0x1'/>
</controller>
<controller type='virtio-serial' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04'
function='0x0'/>
</controller>
<controller type='sata' index='0'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05'
function='0x0'/>
</controller>
<controller type='pci' index='0' model='pci-root'/>
<interface type='bridge'>
<mac address='52:54:00:6d:f0:30'/>
<source bridge='kvmbr0'/>
<model type='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03'
function='0x0'/>
</interface>
<serial type='pty'>
<target port='0'/>
</serial>
<console type='pty'>
<target type='serial' port='0'/>
</console>
<channel type='spicevmc'>
<target type='virtio' name='com.redhat.spice.0'/>
<address type='virtio-serial' controller='0' bus='0' port='1'/>
</channel>
<input type='mouse' bus='ps2'/>
<input type='keyboard' bus='ps2'/>
<graphics type='spice' autoport='yes'/>
<video>
<model type='vga' vram='9216' heads='1'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02'
function='0x0'/>
</video>
<memballoon model='virtio'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06'
function='0x0'/>
</memballoon>
</devices>
</domain>
Environment:
Not really possible at the moment ... the machine panics.
On the KVM host:
$ uname -a
Linux dustbin 3.14.4-1-ARCH #1 SMP PREEMPT Tue May 13 16:41:39 CEST 2014 x86_64
GNU/Linux
How-To-Repeat:
Try to boot a FreeBSD KVM machine.
Fix:
None thus far. Tried to downgrade the virtual machine from its usual 4 CPUs to
a uniprocessor, but that didn't help.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list