10 messages in com.xensource.lists.xen-develRe: [Xen-devel] How does hypervisor h...
FromSent OnAttachments
K.C. Chiu10 May 2004 06:55 
Steven Hand10 May 2004 07:16 
Rolf Neugebauer10 May 2004 07:22 
K.C. Chiu10 May 2004 19:53 
Ian Pratt10 May 2004 23:17 
K.C. Chiu10 May 2004 23:58 
Ian Pratt11 May 2004 00:15 
Kip Macy11 May 2004 21:44 
K.C. Chiu23 May 2004 10:08 
Keir Fraser23 May 2004 11:20 
Subject:Re: [Xen-devel] How does hypervisor handle the hypercalls fromguest OSes?
From:Ian Pratt (Ian.@cl.cam.ac.uk)
Date:05/10/2004 11:17:47 PM
List:com.xensource.lists.xen-devel

But I have another question, how do I debug in the Xen hypervisor side?

Just "printk" ?

Connect something (e.g. another computer) to the serial console, and boot Xen with serial console enabled.

As well as printk, Xen has a GDB stub. This is quite powerful, and can be used for debugging domains and processes too.

However I could not find out any print message in /var/log/message and the xen_read_console ?

"xen_dmesg.py" in dom0 will show you the console output from *Xen*. (//var/log/messages and xen_read_console are domain console tools).

For any serious debugging, get yourself a serial line. xen_dmesg isn't much use if either Xen or domain 0 are already blown to bits.

BTW: What does your new hypercall do?

Ian