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


[Xen-devel] RFC: Migration and VBD/SR/VDI creation

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] RFC: Migration and VBD/SR/VDI creation
From: Pascal Bouchareine <pascal@xxxxxxxxx>
Date: Fri, 18 May 2007 16:10:46 +0200
Delivery-date: Fri, 18 May 2007 07:09:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.11

When migrating a domain, the VDI definition is not recreated
building the VBD, hence loosing API access to the VBD location & al
({'VDI' : ''}).

The attached patch is an attempt to recreate the VDI in XendConfig.device_add
(in the 'Local' SR, eventually some other) when using an sxp_obj (I guess
the SR/VDI is always defined when using a xenapi_cfg).

Is this an acceptable idea ?

I missed a lot of things reading the code, so someone might want to
check this is not too horrible and doesn't break anything.


\o/   Pascal Bouchareine - Gandi 
 g    0170393757           15, place de la Nation - 75011 Paris      

Attachment: XendConfig_create_vdi.diff
Description: Text document

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] RFC: Migration and VBD/SR/VDI creation, Pascal Bouchareine <=