[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] Trouble booting FreeBSD i386 PV DomU
Am 23.02.2013 09:13, schrieb Roger Pau Monné:
On 22/02/13 19:30, tech mailinglists wrote:
Hello Roger,
I tried a further thing in the kernel configuration. I remove the option
KBD_INSTALL_CDEV and now I am no longer getting dropped to a minimal
console. The boot now looks like this:
Parsing config from /root/xen/freebsd-test.cfg
libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20
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 4383
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 #1 r247145M: Fri Feb 22 18:26:55 CET 2013
root@build:/usr/obj/usr/src/sys/XEN i386
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):
0x0000000000670000 - 0x000000001f628fff, 519802880 bytes (126905 pages)
avail memory = 516833280 (492 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.
random: <entropy source, Software, Yarrow>
io: <I/O>
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
xn0: <Virtual Network Interface> at device/vif/0 on xenbusb_front0
xn0: bpf attached
xn0: Ethernet address: 00:16:3e:44:b1:b9
xenbusb_back0: <Xen Backend Devices> on xenstore0
xctrl0: <Xen Control Device> on xenstore0
xn0: backend features: feature-sg feature-gso-tcp4
[XEN] hypervisor wallclock nudged; nudging TOD.
run_interrupt_driven_hooks: still waiting after 60 seconds for
xenbus_free_evtchn
[XEN] hypervisor wallclock nudged; nudging TOD.
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
[XEN] hypervisor wallclock nudged; nudging TOD.
[XEN] hypervisor wallclock nudged; nudging TOD.
[XEN] hypervisor wallclock nudged; nudging TOD.
I will test HVM and PVHVM but in the past I had no problems with this.
It would be greate to have pure PV mode. The only thing which confuses
me is the libxl related error on the domain creation:
Parsing config from /root/xen/freebsd-test.cfg
libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 20
device model: spawn failed (rc=-3)
libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error:
No such file or directory
I know that in a few cases PV guests have QEmu process but I can not say
while this failes. Eventually there is something not compiled in, into
Xen or the toolstack?
PV guests use Qemu to provide a block backend for raw file images, so if
Qemu fails to start your PV guest won't we able to access the hard
drive, that could be the reason why the FreeBSD PV guest is unable to
boot. Could you check Qemu log in /var/log/xen/qemu-dm-freebsd.log?
I saw that you have made a talk on FOSDEM about BSD and PVH. I
downloaded the slide PDF but I am not able to open the document. It says
that the document is corrupted. Am I doing a mistake? Or is there a
problem with the document on the FOSDEM page.
I've just checked and the slides look OK to me, I'm able to open them
without problems. SHA1 sum:
0b0070149e0b4cf0b5557230793acccd1291ccde new_xen_paravirt_mode.pdf
I was able to fix the Qemu related problem, it was simply a missing
dependency. After I installed this I could start the guest to the point
that it can't find the root partition (ZFS). I thought that I have to do
it with PV-GRUB but the normal PV-GRUB don't support ZFS so I searched
and found this on github: https://github.com/aszeszo/pv-grub
I was able to cross compile this to x86_32 and so it can read the ZFS
disk. But when I try to boot the kernel from /boot/kernel/kernel I get
into the mountroot prompt. And when I try chainloading (I read that this
would be the only way) I get this error:
xc: error: panic: xc_dom_core.c:587: xc_dom_find_loader: no loader
found: Invalid kernel
xc_dom_parse_image returned -1
close(3)
Error 9: Unknown boot failure
So is there a way to parse a kernel parameter to help the kernel to find
the ZFS volume or can a loader so like (/boot/loader, /boot/zfsloader)
be loaded with PV-GRUB?
Would be great when someone could help me I think I am not far away to
have a working PV FreeBSD DomU with a filesystem which is support by
FreeBSD and Linux so this would be very great.
Best Regards
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users
|
