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] determining if a backend device is not working

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] determining if a backend device is not working
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 10 Mar 2009 10:00:59 +0000
Cc:
Delivery-date: Tue, 10 Mar 2009 03:01:25 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D0162CB79@trantor>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcmhIgybbc5MxlDyS1KuqiEOxhybGAAN3qkJAAHVfyAAAY/WYg==
Thread-topic: [Xen-devel] determining if a backend device is not working
User-agent: Microsoft-Entourage/12.15.0.081119
On 10/03/2009 09:21, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

>> I think we expect backends to always be responsive. So we have no
> model
>> for
>> what to do if that assumption breaks. Your particular example above
> sounds
>> like a weird backend bug?
>> 
> 
> A block device definition of ',hdc:cdrom,r' appears to be valid on the
> qemu side of things. You just 'xm block-configure' it when you want to
> 'insert' a cdrom image into it.
> 
> Blkback appears to not handle such things though, so it would have been
> nice to quickly detect that blkback wasn't doing anything useful and
> just move on...

So blkback currently just clams up in this case and won't let you connect at
all? I wonder if perhaps blkback isn't even configured in this case... Hmmm.

 -- Keir



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

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