[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] pv_ops dom0 testing
I solved this one by adding "console=hvc0 earlyprintk=xen" to the dom0 kernel boot line (thanks to Jeremy Fitzhardinge [jeremy@xxxxxxxx]). -----Original Message----- From: Todd Deshane [mailto:deshantm@xxxxxxxxx] Sent: Sunday, November 30, 2008 12:16 AM To: xen-devel mailing list Cc: Aviv Grafi Subject: Re: [Xen-devel] pv_ops dom0 testing On Sat, Nov 29, 2008 at 4:38 PM, Aviv Grafi <aviv@xxxxxxxxxxxx> wrote: > I had the same issue few days ago: try to boot the vmlinux (and not > vmlinuz) image that you can find in your kernel build directory. > You can verify that you are booting the right image file by using the > readelf tool. > Thanks for the tip Aviv. That got me a little farther. The debug output now ends with: (XEN) ioapic_guest_write: apic=0, pin=4, old_irq=4, new_irq=4 (XEN) ioapic_guest_write: old_entry=000009f1, new_entry=000189f1 (XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ! Full output attached. Do I need to either modify more of the default kernel settings or pass some more options to Xen or the dom0 kernel? When running non-debug mode, I don't see any dom0 output on the screen,. I tried a few different console= lines tty0, xvc0, hvc0.... but only Xen hypervisor output ending with: (XEN) Xen is relinquishing VGA console Can someone post a working .config and grub config and/or the instructions to get to that point beyond the default setup? Cheers, Todd _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |