All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: domU on x86_64 xenlinux problems
Date: Tue, 30 Aug 2005 15:19:09 -0500	[thread overview]
Message-ID: <4314BF3D.2050109@us.ibm.com> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D37200173050B4FE1@scsmsx402.amr.corp.intel.com>

Hey Jun,

Some major console changes were checked in.  I'm investigating these 
problems right now.  While we've seen this error message before, it's 
never been under these circumstances (previously, it was because 
xenconsoled wasn't running, here it seems to be a new race condition).

Regards,

Anthony Liguori

Nakajima, Jun wrote:

>Before I dig deeper to debug, I'm wondering if I'm missing some setup
>things. I see some improvements with the domU side last night (I used to
>get an error from xend, and xm failed), but I still see problems like:
>
>Using config file "/root/xmexample1".
>Started domain domU
>xenconsole: Could not read tty from store: No such file or directory
>
>I used the latest tree,
>changeset:   6453:3bbc9384be3f
>tag:         tip
>user:        kaf24@firebug.cl.cam.ac.uk
>date:        Fri Aug 26 10:57:09 2005 +0000
>summary:     Refactor sync_lazy_execstate_cpu() into the more sensible
>
>Jun
>---
>Intel Open Source Technology Center 
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
>
>  
>

  parent reply	other threads:[~2005-08-30 20:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30 17:27 domU on x86_64 xenlinux problems Nakajima, Jun
2005-08-30 18:01 ` Keir Fraser
2005-08-30 20:19 ` Anthony Liguori [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-30 18:36 Nakajima, Jun
2005-08-30 20:34 ` Ryan Harper
2005-08-31  7:48 ` Keir Fraser

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=4314BF3D.2050109@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=jun.nakajima@intel.com \
    --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.