Re: [Xen-devel] [PATCH] blktap/blktap2: Fix for incorrect parse disk configuration (xen-unstable)

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

After patching xen-unstable (changeset:   21769:a672af698bc3)
Rebuilt and reinstalled xen&tools.
Changed  "tap2:tapdisk:vhd" to "tap:vhd"

root@ServerLSX:~/NexentaStor-Community-3.0.2# xm create -c  nexentastor-3.0.2-xen.cfg
Using config file "./nexentastor-3.0.2-xen.cfg".
root@ServerLSX:~/NexentaStor-Community-3.0.2# Error: Device 51952 not connected

root@ServerLSX:/usr/local/NexentaStor-Community-3.0.2# xm create -c  nexentastor-3.0.2-xen.cfg
Using config file "./nexentastor-3.0.2-xen.cfg".
Error: Device /dev/xvdp (51952, tap2) is already connected.

Boris.

--- On Sun, 7/11/10, eXeC001er <execooler@xxxxxxxxx> wrote:

From: eXeC001er <execooler@xxxxxxxxx>
Subject: [Xen-devel] [PATCH] blktap/blktap2: Fix for incorrect parse disk configuration (xen-unstable)
To: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Date: Sunday, July 11, 2010, 4:16 AM

Current source-code work if use following configuration:

config example:    disk=['tap:vhd:/path/../disk.img,xvda,w']

but not work if use:

config example:    disk=['tap:tapdisk:vhd:/path/../disk.img,xvda,w']

Error during start DomU:    File 'vhd:/path/.../disk.img' doesn't exist.

this patch fix this bug.

Signed-off-by: eXeC001er <execooler@xxxxxxxxx>

Thanks.

-----Inline Attachment Follows-----

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

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