This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] domU on x86_64 xenlinux problems

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] domU on x86_64 xenlinux problems
From: "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
Date: Tue, 30 Aug 2005 10:27:46 -0700
Delivery-date: Tue, 30 Aug 2005 17:27:11 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcWtiCMJ8sHkd1+TQY6MzUDnbEcefg==
Thread-topic: domU on x86_64 xenlinux problems
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@xxxxxxxxxxxxxxxxxxxx
date:        Fri Aug 26 10:57:09 2005 +0000
summary:     Refactor sync_lazy_execstate_cpu() into the more sensible

Intel Open Source Technology Center 

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>