All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Jacob Gorm Hansen <jacobg@diku.dk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Minimal fileset for Xenstore domU boot
Date: Tue, 27 Sep 2005 13:10:01 -0500	[thread overview]
Message-ID: <43398AF9.30702@us.ibm.com> (raw)
In-Reply-To: <e08041f30509270655464e00f0@mail.gmail.com>

Jacob Gorm Hansen wrote:

>On 9/27/05, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
>  
>
>>Yes, you do, and xenconsoled requires xenstored. And your tools must
>>introduce xenstored to the new domain when it is built.
>>
>>Without xenconsoled the new domain will stall waiting for the console
>>ring to empty, which never happens.
>>    
>>
>
>Thanks, I removed the domU console driver for now and my domain boots.
>xc_linux_build() takes a console_evtchn as argument, what is the
>strategy for obtaining that value from xenconsoled?
>  
>
Setting up the console is just like setting up xenstore.  The tools have 
to create an interdomain evtchn between domain-0 and the remote domain.  
The xc_linux_build function will return to MFNs.  You have to introduce 
the domain with the local evtchn for the store and the store MFN.  Then 
you have to write the local console evtchn and console MFN to the store.

Regards,

Anthony Liguori

>Jacob
>--
>Save time and bandwidth with EDelta: http://www.diku.dk/~jacobg/edelta/
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>  
>

      parent reply	other threads:[~2005-09-27 18:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27 13:24 Minimal fileset for Xenstore domU boot Jacob Gorm Hansen
2005-09-27 13:43 ` Keir Fraser
2005-09-27 13:55   ` Jacob Gorm Hansen
2005-09-27 14:07     ` Keir Fraser
2005-09-27 18:10     ` Anthony Liguori [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43398AF9.30702@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=jacobg@diku.dk \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.