WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] xenconsole: Could not read tty from store: No such file

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] xenconsole: Could not read tty from store: No such file or directory
From: "Mahmoud Elhaddad" <m.elhaddad@xxxxxxxxx>
Date: Thu, 27 Jul 2006 16:39:16 -0700
Delivery-date: Thu, 27 Jul 2006 16:39:41 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references; b=ZxuzzKsb0r65QHVa2E9Iin+dv3qI48jaT8TU4+AvLKDQmpK/MoZZFqKOQlhmersJSdn2mL9eDTOvJN5TV5zar7Tg7yL2+3kpk8yBmP2J2bq8MxN0hKoCkQkBiXWAqwhP4K+8J6rz5JfjxrNhzdbnLsc/MQB8PwLGNavmK3TLMvA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <OFB7B90D2E.A3864236-ON052571B8.00549F53-052571B8.00553BF1@xxxxxxxxxx>
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>
References: <20060727144834.GA23914@xxxxxxxxxxxxxxxxxxxxxxx> <OFB7B90D2E.A3864236-ON052571B8.00549F53-052571B8.00553BF1@xxxxxxxxxx>
Reply-to: elhaddad@xxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thank you Natasha and Steve. I rebuilt using the latest changeset and aplied the patch. The patch did work...the SLES guest now boots but freezes while ReiserFS is "checking the transaction log".
It's not clear to me if it's another  problem with qemu.
The qemu.*.log now looks like this:
domid: 3
qemu: the number of cpus is 1
shared page at pfn:3ffff, mfn: 1d7e19
char device redirected to /dev/pts/2
Issued domain 3 poweroff
 
Thanks,
 -Mahmoud
 
On 7/27/06, Steve Dobbelstein < steved@xxxxxxxxxx> wrote:
natasha@xxxxxxxxxxxxxxxxxxxxxxx wrote on 07/27/2006 09:48:34 AM:

> Mahmoud,
>
> Often times this message occurs with hvm domains because qemu-dm
> does not start properly.  The file /var/log/qemu-dm.*.log is created
> when you try to start an hvm domain.  It should provide at least
> a hint to what the problem is.
>
> Also, a lot of qemu changes have been checked in recently.  You may
> want to update to a more recent changeset.
>
> Natasha

Mahmoud,

I saw the same message when my qemu-dm died.  I debugged it down to find it
was caused by an unitialized variable.  I posted a patch.  (
http://lists.xensource.com/archives/html/xen-devel/2006-07/msg00850.html)
You might try it to see if you are running into the same problem.  My patch
is a little over zealous in initializing variables, but that shouldn't
hurt.  Christian Limpach said he will apply a subset of the patch (
http://lists.xensource.com/archives/html/xen-devel/2006-07/msg00899.html ).
It hasn't hit the xen-unstable tree yet, but it should be coming soon.

Steve D.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>