[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: eXeC001er <execooler@xxxxxxxxx>
  • Date: Sun, 27 Jun 2010 16:08:16 +0400
  • Delivery-date: Sun, 27 Jun 2010 05:09:12 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=JQIl5H1h2nKdTeoVrAKUNhBPyncLNCVeQCBQbxDU8chazsS3GYDMetQZ5GOTeXcPpJ NKMSM0i4d/RvCYticXWlWCQOL4ukDiOFYzkezv+4WxiVxzDbJgS2cNgbIxhcn+L4nSw/ z8CFKQS2QXl1YQOlW/HquX8yWr8t9pclgczj4=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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>

Attachment: blktap2_ctrl_func.patch
Description: Text Data

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.