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] [PATCH] Fix for xm block-detach, blktap devices

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH] Fix for xm block-detach, blktap devices
From: Andres Lagar Cavilla <andreslc@xxxxxxxxxxxxxx>
Date: Tue, 5 Sep 2006 15:18:03 -0400 (EDT)
Cc: Andrew Warfield <andrew.warfield@xxxxxxxxxxxx>, Ewan Mellor <ewan@xxxxxxxxxxxxx>
Delivery-date: Tue, 05 Sep 2006 12:18:32 -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
a new take on a solution for the problem described in the subject line.

The idea is to have destroyDevice in XendDomainInfo scan the
frontend devices for the domain to see which one matches the provided
devid string. Because 'tap' and 'vbd' block devices are all under the same
'vbd' hierarchy in the frontend, this works when xm
block-detach calls this function with deviceClass='vbd'.

Signed-off-by: Andres Lagar-Cavilla <andreslc@xxxxxxxxxxxxxx>

Attachment: fix-block-detach-for-blktap.patch
Description: Text document

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH] Fix for xm block-detach, blktap devices, Andres Lagar Cavilla <=