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-users

Re: [Xen-users] Block devices stuck in dead domain?

To: "John Hannfield" <hal9020@xxxxxxxxx>
Subject: Re: [Xen-users] Block devices stuck in dead domain?
From: "Todd Deshane" <deshantm@xxxxxxxxx>
Date: Tue, 10 Jun 2008 18:06:49 -0400
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 10 Jun 2008 15:07:24 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:in-reply-to:mime-version:content-type:references; bh=lvhuDIONmWxzsK13c36BUqGN4mBofJgKBxKPeVO872M=; b=wS+cd1THeGrRYoze1j9WzBxRtMT5r5ALmN6yY78tHIEEOxF6HelbWheNAFr8vLPIa+ SccT0O0Rf5T2vIP2Hd5IFUvsdbbvU7iafoJN/ii/EK7k20Arls4Ke5XkbGUMWAG6Sr6u 6IfvwkTcTW2nIPyZZk/3AKxY+H754M2hwtsFs=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:references; b=cuHMAG1T4InbdXiEayOpBmWr+GQZPk/8ovGBkjDXqzEiCrJCr4FT/K/jLu+11lLs3G IpsaudK4lE51vCaGNrEhIlldgsWDNZuSuBhWFfIRLb6fJxpNMxTJ6TarTOl71pAlOG/y OvkEg6L6tqD+eVLw9C25MsoV0a+bJEXlDVJUY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4d95b0990806101458l704a30d9udfd18d9661a37614@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4d95b0990806101035i68d541ebr14ce95ab9f2c238d@xxxxxxxxxxxxxx> <1e16a9ed0806101438h2ddd30e4sbfd685845b471ccb@xxxxxxxxxxxxxx> <4d95b0990806101458l704a30d9udfd18d9661a37614@xxxxxxxxxxxxxx>
Reply-to: deshantm@xxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx


On Tue, Jun 10, 2008 at 5:58 PM, John Hannfield <hal9020@xxxxxxxxx> wrote:
Hi Todd,

Thanks for the ideas.

> did you try xm destroy <guest VM that crashed> ?

Yes, I did that, but wasn't sure it was destroyed, as  'xm list' - it
just hangs.
But I assumed the domain was destroyed.

> If that doesn't work you may be able to use xm block-detach
> or if that doesn't work, you could try to remove the entry from xenstore
> manually.

Do you know how to remove the entry from xenstore?
I had a look in /var/run/xenstored/   but couldn't really make
sense of anything there. Is there a guide to xenstore somewhere,
or any other tips on learning about it?

xenstore uses a backend tree database (tdb).

There are xenstore-* commands used to access it (see below).

This is a pretty good reference:
http://wiki.xensource.com/xenwiki/XenStoreReference

here are the commands that are available:

xenstore-chmod    xenstore-exists   xenstore-read    
xenstore-control  xenstore-list     xenstore-rm      
xenstored         xenstore-ls       xenstore-write

I suspect that it should be something like find the domain ID and getting rid of the vbd entry.

xm list hanging is not a good sign though.

Let us know if you run into problems in your efforts.

Cheers,
Todd
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users