From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Stabellini Subject: Re: RE: [Xen-changelog] [xen-unstable] blktap2: a completely rewritten blktap implementation Date: Wed, 27 May 2009 18:30:28 +0100 Message-ID: <4A1D78B4.4090000@eu.citrix.com> References: <0b764004-9d02-4b07-87de-abb74f4c4b09@default> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <0b764004-9d02-4b07-87de-abb74f4c4b09@default> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Magenheimer Cc: "dmeyer@cs.ubc.ca" , "xen-devel@lists.xensource.com" , Wires Jake List-Id: xen-devel@lists.xenproject.org Dan Magenheimer wrote: > Just wondering... has this been tested with multiple domains > sharing the same blktap device? (e.g. specifying > tap:aio:/pathto/file.img,hda,w! from two different domains > in a cluster) This feature is really important at least for stubdoms and windows pv drivers. However in this particular case the stubdom and the pv drivers in the guest will never open the disk at the same time because when the pv drivers start they ask qemu to close the disk. So far I have been doing some testing with stubdoms, blktap2 and vhd and they seem to work well together.