From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Mallozzi Subject: xm block-attach with optional backend parameter Date: Sat, 04 Jul 2009 14:13:34 -0700 Message-ID: <4A4FC5FE.9080307@oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Typo - the command that I actually ran was xm block-attach 0 file:/root/mydisk.img /dev/xvda w 1 --------------------------------------------- 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