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] could not reboot domU in latest xen-unstable

To: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] could not reboot domU in latest xen-unstable
From: Wensheng Wang <wenshengwang@xxxxxxxxx>
Date: Tue, 8 Nov 2005 18:52:19 -0600
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 09 Nov 2005 00:52:26 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JjU0VM1r+oLhQbDOjfcu6sLhCwuWWlnrDIistz+QZLAXyKaqdHiiV26rDJEcJSpnukXPnW6fiM3whKtY3wSNo7Lz7nGt7cNMrKYyKHxkeC+eWVsfPZBJsR61uUYkUQXNGFdAIBzMik7s6ryzqtkGbO/nkGjkp7ISscaIel+Th14=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20051108113950.GH842@xxxxxxxxxxxxxxxxxxxxxx>
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: <7b22037d0511052330p429eb000oeddb00886e77027@xxxxxxxxxxxxxx> <20051106092218.GA18075@xxxxxxxxxxxxxxxxxxxxxx> <20051106110236.GB18075@xxxxxxxxxxxxxxxxxxxxxx> <7b22037d0511062234r1c2c8ebfh98ac9c8b0d6a903a@xxxxxxxxxxxxxx> <20051108113950.GH842@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
That works, thank you for fixing it.

Today I noticed another case of this when I tried to create a domU:
Device 0 (vif) could not be connected. Hotplug scripts not working

I got it when I don't specify vif in my domU config file or when I
specify but incorrectly had a xen-br0(should be xenbr0) in vif line.
If I correctly specify vif,  that errer goes away.


Wensheng Wang


On 11/8/05, Ewan Mellor <ewan@xxxxxxxxxxxxx> wrote:
> On Mon, Nov 07, 2005 at 12:34:20AM -0600, Wensheng Wang wrote:
>
> > Hi, Ewan,
> > Thank for for the help.
> >
> > I looked at my /var/log/message
> > The last line when the xend unable to restart domain is:
> > Nov  7 00:08:07 m8 logger: /etc/xen/scripts/block: xenstore-read
> > backend/vbd/2/2049/type failed.
> >
> > I attached part of xend.log file,  the timeline in that log file is:
> > 23:57:47 machine booted
> > 00:05:21 xm create fc4
> > 00:06:07 xm shutdown -R fc4
> > 1minute after, I did a "xm list", it hangs, another minute later, the
> > prompt came back showing only domain-0
>
> This was assigned bug #387, and is now fixed, as of changeset
> 7651:7e3faea076ec.
>
> Cheers,
>
> Ewan.
>

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