Re: [Xen-devel] [PATCH] blktap2 control function (version 2)

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

FYI this remains unacked afaik.

 K.

On 27/06/2010 14:19, "eXeC001er" <execooler@xxxxxxxxx> wrote:

> blktap2_ctrl_func.patch - for xen-4.x-testing only (because in xen-unstable i
> see previous version of patch)
> 
> ====================
> attach in current e-mail:
> blktap2-fix-regression.patch -  for xen-unstable
> 
> 1. Fix 
> regression http://xenbits.xensource.com/xen-4.0-testing.hg?rev/3544bdd56c32
> 2. Fix README for blktap2
> 
> Signed-off-by: eXeC001er <execooler@xxxxxxxxx>
> 
> 2010/6/27 Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
>> Is this for xen-unstable, or xen-4.0, or both? Either way, it goes via Ian
>> Jackson and Stefano now, just fyi. I've cc'ed them.
>> 
>>  -- Keir
>> 
>> On 27/06/2010 13:08, "eXeC001er" <execooler@xxxxxxxxx> wrote:
>> 
>>> Patch description:
>>> 1. Bug fix for error: "Error: Device /dev/xvdp (51952, tap2) is already
>>> connected." (xenstore does not clean after DomU stopped)
>>> 2. Bug fix for error: "File 'vhd:/path/.../disk.img' doesn't exist." (not
>>> correct parsing)
>>> 3. Bug fix for error: "Error: Device 51952 not connected" (in config file
>>> for
>>> DomU we should be use prefix "tap2:tapdisk:xxx" (tap2:xxx) for devices from
>>> (aio, ram, qcow, vhd, remus) or "tap:tapdisk:xxx" (tap:xxx) for devices from
>>> (sync, vmdk, qcow2, ioemu))
>>> 4. Bug fix for error: "Disk is not accessible" (if use 'tap2'-device type,
>>> then '/dev/xpvd' may not be accessible immediately after its creation)
>>> 5. fix regression related to the previous version of this
>>> patch.: http://xenbits.xensource.com/xen-4.0-testing.hg?rev/3544bdd56c32
>>> 
>>> Signed-off-by: eXeC001er <execooler@xxxxxxxxx>
>>> 
>> 
>> 
> 
> 



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