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

[Xen-devel] xm block-attach with optional backend parameter

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] xm block-attach with optional backend parameter
From: Matthew Mallozzi <matt.mallozzi@xxxxxxxxxx>
Date: Sat, 04 Jul 2009 11:46:51 -0700
Delivery-date: Sat, 04 Jul 2009 11:47:20 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
User-agent: Thunderbird 2.0.0.22 (X11/20090608)
Hey,
I am trying to attach a disk image file stored in a domU as a block device to dom0, using the command
         xm block-attach 0 file:/root/mydisk.img /dev/xvda 1
where 1 is the domain ID of the particular domU that I want to act as the backend/driver domain. I get an error about "Hotplug scripts not working", and I've already posted to the xen-users list for advice on simply getting this to work, but I was hoping that someone here might be able to walk me through the execution path of a block-attach command, so that I can dive into the code and insert print statements everywhere? I've been able to follow what functions are being called and all that through the xm Python code, but I get lost when it starts to communicate with xend. Any help would be much appreciated!

Thanks,
Matt

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

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