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] [PATCH] Fix "xm list --long" listing for removed devices

To: Dan Smith <danms@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Fix "xm list --long" listing for removed devices
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Thu, 1 Dec 2005 18:36:54 +0000
Cc: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 01 Dec 2005 18:36:44 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <87sltdhlso.fsf@xxxxxxxxxxxxxxxxxxxxxxxx>
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: <87sltdhlso.fsf@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Wed, Nov 30, 2005 at 01:23:51PM -0800, Dan Smith wrote:

> This patch makes xend clean up information about devices at removal so
> that the long xm listing is consistent with reality.
> 
> This will close bug #416.
> 
> Signed-off-by: Dan Smith <danms@xxxxxxxxxx>

Dan, sorry, but this patch breaks 02_network_attach_detach.  Vifs don't have
a 'dev' entry in their config, so the attempt to read that returns None,
which you end up passing to blkdev_name_to_number.

In any case, I would rather have the device-specific complexity in the
DevController subclasses.  If you look at xen/xend/server/blkif.py, it already
has to find a device ID from a device name (which in this case it does by
looking through the store rather than XendDomainInfo's config, but the effect
is the same).  I'd want to keep these things together.  I'm not sure how this
would all plumb through to XendDomainInfo -- it might be nice to have a
mapping from device ID to config so that it wasn't necessary to iterate over
info['device'] and go grubbing around in the configs there.

If you want to re-work this, feel free, otherwise I'll be taking your basic
idea and rejigging it so that the network-detach is not broken, and so that we
get that bug fixed in the next day or so.

Ewan.

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

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