From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Debugging console Date: Tue, 29 Dec 2015 13:00:25 +0000 Message-ID: <568283E9.1090404@citrix.com> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3019147534753785045==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Carl Patenaude Poulin , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============3019147534753785045== Content-Type: multipart/alternative; boundary="------------000504090308000304080603" This is a multi-part message in MIME format. --------------000504090308000304080603 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit On 28/12/2015 16:30, Carl Patenaude Poulin wrote: > Hi all, > > We've got __HYPERVISOR_console_io working on our unikernel! The only > issue is that it prints to `xl dmesg`. Is there a way to get it to > print to `xl console`? No. They are two very different consoles. `xl dmesg` reads the hypervisor console, which is where __HYPERVISOR_console_io hypercalls end up (in debug builds of Xen). `xl console` however is the paravirtual console. Each domain has a page of RAM (the PV console), which is mapped by the xenconsoled daemon in dom0. xenconsoled performs duties such as logging and creation of a pty master for two-way interaction. `xl console` connects to the pty master for the appropriate domain. To get messages appearing in `xl console`, you must implement the guest side of the PV console interface. ~Andrew --------------000504090308000304080603 Content-Type: text/html; charset=windows-1252 Content-Length: 1564 Content-Transfer-Encoding: quoted-printable On 28/12/2015 16:30, Carl Patenaude Poulin wrote:

Hi all,

We've got __HYPERVISOR_console_io working on our unikernel! The only

issue is that it prints to `xl dmesg`. Is there a way to get it to

print to `xl console`=3F

No.=A0 They are two very different consoles.

`xl dmesg` reads the hypervisor console, which is where __HYPERVISOR_console_io hypercalls end up (in debug builds of Xen).

`xl console` however is the paravirtual console.=A0 Each domain has a page of RAM (the PV console), which is mapped by the xenconsoled daemon in dom0.=A0 xenconsoled performs duties such as logging and creation of a pty master for two-way interaction.=A0 `xl console` connects to the pty master for the appropriate domain.

To get messages appearing in `xl console`, you must implement the guest side of the PV console interface.

~Andrew
--------------000504090308000304080603-- --===============3019147534753785045== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============3019147534753785045==--