On 23 May 2013 20:30, Outback Dingo outbackdi...@gmail.com wrote:
On Thu, May 23, 2013 at 9:33 AM, Roger Pau Monné roger@citrix.comwrote:
On 23/05/13 14:57, Jeroen van der Ham wrote:
Hi,
On 13 May 2013, at 20:32, Roger Pau Monné roger@citrix.com wrote:
Right now the code is in a state where it can be tested by users, so we
would like to encourage FreeBSD and Xen users to test it and provide
feedback.
I've just been able to install it on a VPS using the latest pvhvm_v9
branch.
The branch pvhvm_v9 contains an initial implementation of PV IPIs for
amd64. I've now finished it and I'm going to port it to i386 also, and
push a new branch to the repository.
This is good news, because the system I had before actually had trouble
with the HVM kernel from 9.1 [0].
I'm going to leave this running for a while and do some more tests on it.
Jeroen.
[0]: http://www.freebsd.org/cgi/query-pr.cgi?pr=175822
I built the rev_9 branch on a XCP host and rebooted, however I am seeing
on boot after ugen0.2: QEMU 0.10.2 at usbus0
run_interrupt_driven_hooks: still waiting after 60 seconds for
xenbus_nop_confighook_cb
run_interrupt_driven_hooks: still waiting after 120 seconds for
xenbus_nop_confighook_cb
run_interrupt_driven_hooks: still waiting after 180 seconds for
xenbus_nop_confighook_cb
run_interrupt_driven_hooks: still waiting after 240 seconds for
xenbus_nop_confighook_cb
run_interrupt_driven_hooks: still waiting after 300 seconds for
xenbus_nop_confighook_cb
panic: run_interrupt_driven_confighooks: waited too long
cpuid = 0
KDB: enter: panic
[ thread pid 0 tid 10 ]
Stropped at kdb_enter +0x3b: movq $0,0xad6522(%rip)
db
Can you recheck this on stock HEAD?
From your description this looks like a rather old bug seen with 8.2
or above and XCP (referenced in PR kern/164630). You can trigger it
when e.g. booting with empty cdrom.
--
wbr,
pluknet
___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org