Re: [Xen-users] Trouble booting FreeBSD i386 PV DomU

[Roger Pau Monné <roger.pau@xxxxxxxxxx>]

On 21/02/13 10:18, tech mailinglists wrote:
> Hello all,
> 
> I have created a FreeBSD PV DomU image formatted with ZFS. I compiled
> FreeBSD with KERNCONF=XEN for the kernel and the normal world and
> distribution target. Then I transfered it to a Debian Dom0 with Xen 4.2.1.
> 
> I tried to boot the image befor I migrate it to LVM and I now get teh
> following output:
> 
> Parsing config from freebsd-test.cfg
> libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 12
> 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 3451
> 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: Wed Feb 20 14:16:03 CET 2013
>     root@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  = 2147483648 (2048 MB)
> Physical memory chunk(s):
> 0x0000000000a58000 - 0x000000007d995fff, 2096357376 bytes (511806 pages)
> avail memory = 2092105728 (1995 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
> 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>

Hello,

I can tell you PVHVM (XENHVM) works fine with Xen 4.2.1 and -unstable
(both 9.1 and HEAD), but I'm afraid I haven't got time to test Xen PV
(i386) yet.

Can you check if this is a regression in the FreeBSD kernel or Xen itself?

Regards, Roger.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users