tech mailinglists
2013-Feb-22 09:04 UTC
[Possible Regression] FreeBSD 9.1 i386 in PV mode can not boot on Xen 4.2.1
Hello all,
I tried to setup a FreeBSD i386 guest in PV mode. So I compiled a FreeBSD
Xen Kernel with the XEN kernel configuration from 9.1 revision 247145.
The detailed information from "svn info" looks like this:
Path: .
Working Copy Root Path: /usr/src
URL: svn://svn.freebsd.org/base/release/9.1.0
Repository Root: svn://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 247145
Node Kind: directory
Schedule: normal
Last Changed Author: kensmith
Last Changed Rev: 243808
Last Changed Date: 2012-12-03 06:03:33 +0100 (Mon, 03 Dec 2012)
When I try to start the domain the kernel runs into a panic. The output is
this:
Parsing config from /root/xen/freebsd-test.cfg
libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 19 device
model: spawn failed (rc=-3)
libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: No
such file or directory
Daemon running with PID 4181
WARNING: loader(8) metadata is missing!
GDB: no debug ports present
KDB: debugger backends: ddb
KDB: current backend: ddb
APIC: Using the MPTable enumerator.
SMP: Added CPU 0 (BSP)
Copyright (c) 1992-2012 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.1-RELEASE #0 r247145M: Fri Feb 22 09:19:40 CET 2013
root at build:/usr/obj/usr/src/sys/XEN i386
WARNING: WITNESS option enabled, expect reduced performance.
Xen reported: 3341.754 MHz processor.
Timecounter "ixen" frequency 1953125 Hz quality 0
CPU: Intel(R) Core(TM) i7 CPU 975 @ 3.33GHz (3341.75-MHz 686-class
CPU)
Origin = "GenuineIntel" Id = 0x106a5 Family = 6 Model = 1a
Stepping 5
Features=0xbfe3fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Features2=0x98e3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT>
AMD Features=0x28100000<NX,RDTSCP,LM>
AMD Features2=0x1<LAHF>
Data TLB: 4 KB pages, 4-way set associative, 64 entries
1st-level data cache: 32 KB, 8-way set associative, 64 byte line size
L2 cache: 256 kbytes, 8-way associative, 64 bytes/line
real memory = 536870912 (512 MB)
Physical memory chunk(s):
0x000000000082c000 - 0x000000001f628fff, 517984256 bytes (126461 pages)
avail memory = 514850816 (491 MB)
INTR: Adding local APIC 0 as a target
ULE: setup cpu 0
[XEN] IPI cpu=0 irq=128 vector=RESCHEDULE_VECTOR (0)
[XEN] IPI cpu=0 irq=129 vector=CALL_FUNCTION_VECTOR (1)
Event-channel device installed.
io: <I/O>
random: <entropy source, Software, Yarrow>
mem: <memory>
Pentium Pro MTRR support enabled
null: <null device, zero device>
nfslock: pseudo-device
[XEN] xen_rtc_probe: probing Hypervisor RTC clock
rtc0: <Xen Hypervisor Clock> on motherboard
[XEN] xen_rtc_attach: attaching Hypervisor RTC clock
rtc0: registered as a time-of-day clock (resolution 1000000us, adjustment
0.500000000s)
xenstore0: <XenStore> on motherboard
Grant table initialized
xc0: <Xen Console> on motherboard
Device configuration finished.
procfs registered
Event timer "ixen" quality 600
Timecounters tick every 10.000 msec
lo0: bpf attached
xenbusb_front0: <Xen Frontend Devices> on xenstore0
xenbusb_add_device: Device device/suspend/event-channel ignored. State 6
xenbusb_back0: <Xen Backend Devices> on xenstore0
xctrl0: <Xen Control Device> on xenstore0
[XEN] hypervisor wallclock nudged; nudging TOD.
run_interrupt_driven_hooks: still waiting after 60 seconds for
xenbus_free_evtchn
run_interrupt_driven_hooks: still waiting after 120 seconds for
xenbus_free_evtchn
run_interrupt_driven_hooks: still waiting after 180 seconds for
xenbus_free_evtchn
run_interrupt_driven_hooks: still waiting after 240 seconds for
xenbus_free_evtchn
[XEN] hypervisor wallclock nudged; nudging TOD.
run_interrupt_driven_hooks: still waiting after 300 seconds for
xenbus_free_evtchn
panic: run_interrupt_driven_config_hooks: waited too long
cpuid = 0
KDB: enter: panic
[ thread pid 0 tid 100000 ]
Stopped at kdb_enter+0x3a: movl $0,kdb_why
db>
The xen configuration file looks like this:
kernel = '/home/kernel1'
extra = 'boot_verbose=1,kern.hz=100'
vcpus = '1'
memory = '512'
disk = [
'file:/home/test/disk.img,xvda1,w',
]
name = 'freebsd'
vif = [ '' ]
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
I can not say where the problem is located. The configuration I used is
located in the source tree at /usr/src/sys/i386/conf/XEN
I search a while on the web and found that it helped in 8.x to comment out
different things. Primary this threads are said such things on the forums:
http://forums.freebsd.org/showthread.php?t=10268
http://forums.freebsd.org/showthread.php?t=33435
So it would be great when someone could help me to figure out the boot
panic.
A second thing is that I use a ZFS formated image. Is it possible to run /
on ZFS with a Xen kernel? ZFS is in a module when I am right and I thing I
have to boot the guest with PV GRUB to get this working am I right?
Best Regards