[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Mini-OS and serial output


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxxxxxxx>
  • Date: Mon, 9 Jul 2007 10:55:21 +0200
  • Cc: lists@xxxxxxxxx, Keir Fraser <keir@xxxxxxxxxxxxx>
  • Delivery-date: Mon, 09 Jul 2007 01:53:11 -0700
  • Domainkey-signature: s=s768; d=fujitsu-siemens.com; c=nofws; q=dns; b=o6bKktFT/3aRhN4iwqk4SdUkfBwvQ00M4pH2OxYMVk9NJ9T3Mg9aZUpUjvNOhemtWD8bPd33h94pm5iZy2RvKTcJbur5l2yNBtIV63ndwZTDQohxQj1CHtgkqvuQmTCw;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Am Montag, 9. Juli 2007 schrieb Keir Fraser:
> On 9/7/07 09:42, "Michael Frey" <lists@xxxxxxxxx> wrote:
> > I've built Xen with "make debug=y" and added some necessary lines to
> > grub.conf. Furthermore I've connected a second workstation via serial to
> > the Xen workstation and I got the the output from the boot process and
> > various other things. I start the mini-os domain and I get no
> > "Bootstrapping .." line as defined in extras/mini-os/kernel.c
> >
> > So I have a debug build of Xen (I suggest) and I get some output via
> > serial console, but the mini-os serial output doesn't seem to work.
> > Suggestions?
>
> Add some tracing to the hypercall inside Xen, conditional on calling domain
> id being != 0, to confirm that the hypercall is actually being invoked, and
> to discover why the messages are being dropped.

You must build Xen with the VERBOSE flag switched on. 
This is done by make verbose=y (see Rules.mk)
You may have a look at xen/drivers/char/console.c
In function do_console_io() you can see, that per default the hypervisor 
console calls from domU's are ignored.

Dietmar.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.