Hi, does the serial console output via "HYPERVISOR_console_io(..)" works? I''ve enabled with ''make debug=y'' the serial output and get a output to the serial interface while the system boots. I''ve started mini-os and expected to see the line "Bootstrapping..." as defined in kernel.c, but my minicom session prints no such line. Maybe somebody can tell me whats wrong or maybe what I have to do to get serial output working for mini-os? Thanks in advance! Michael Frey _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 8/7/07 23:44, "lists@mfrey.net" <lists@mfrey.net> wrote:> does the serial console output via "HYPERVISOR_console_io(..)" works? I''ve > enabled with ''make debug=y'' the serial output and get a output to the > serial interface while the system boots. I''ve started mini-os and expected > to see the line "Bootstrapping..." as defined in kernel.c, but my minicom > session prints no such line. > > Maybe somebody can tell me whats wrong or maybe what I have to do to get > serial output working for mini-os?You should get serial output via that hypercall if you have a debug build of Xen. Otherwise only dom0 is allowed to use that hypercall and you need to perform inter-domain communication to dom0 to output to the text console. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi,> You should get serial output via that hypercall if you have a debug build > of Xen. Otherwise only dom0 is allowed to use that hypercall and youneed to> perform inter-domain communication to dom0 to output to the text console.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? Thanks in advance! Best Regards Michael Frey _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 9/7/07 09:42, "Michael Frey" <lists@mfrey.net> 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. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Am Montag, 9. Juli 2007 schrieb Keir Fraser:> On 9/7/07 09:42, "Michael Frey" <lists@mfrey.net> 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@lists.xensource.com http://lists.xensource.com/xen-devel
Hi,> You must build Xen with the VERBOSE flag switched on. > This is done by make verbose=y (see Rules.mk)Hm. Maybe I''m wrong, but doesn''t Section 11.2 in the Xen User Manual say that if you enable debug by make debug=y it also enables verbose=y implicit? My complete make options were: "make verbose=y debug=y optimize=0 crash_debug=y CMDLINE="console=com1 gdb=com1 earlygdb=y""> 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.I will have look at console.c Thanks! Best Regards Michael _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel