eXeC001er
2010-Jul-11 13:18 UTC
[Xen-devel] [PATCH] blktap2: blktap2 and pygrub (xen-unstable)
1. Bug fix for error: "Error: Device /dev/xvdp (51952, tap2) is already
connected."
2. Bug fix for error: "Error: Device 51952 not connected"
process of booting DomU with ''mounted-blktap2'' (VHD for
example) and
''pygrub'' as bootloader:
1. Connect boot-device to Dom0 as ''/dev/xpvd''
2. Pygrub get info for load DomU
3. Disconnect boot-device from Dom0
4. Boot DomU
During step 3 created device disconnecting from Dom0, but xenstore
does not scrape
away after device disconnected from Dom0 => result:
"Error: Device /dev/xvdp (51952, tap2) is already connected."
During step 3 created device disconnecting from Dom0, but
''destroyDevice''
method is passed ''tap'' always => result:
"Error: Device 51952 not connected"
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Boris Derzhavets
2010-Jul-11 13:57 UTC
Re: [Xen-devel] [PATCH] blktap2: blktap2 and pygrub (xen-unstable)
Yes , patches
-rw-r--r-- 1 root root 1617 2010-07-11 17:28 blkpat2_pygrub.patch1
-rw-r--r-- 1 root root 567 2010-07-11 17:44 blktap_incorrect_parse.patch1
resolve the problem.
Thanks.
Boris.
--- On Sun, 7/11/10, eXeC001er <execooler@gmail.com> wrote:
From: eXeC001er <execooler@gmail.com>
Subject: [Xen-devel] [PATCH] blktap2: blktap2 and pygrub (xen-unstable)
To: "Xen-devel" <xen-devel@lists.xensource.com>
Date: Sunday, July 11, 2010, 9:18 AM
1. Bug fix for error: "Error: Device /dev/xvdp (51952, tap2) is already
connected."2. Bug fix for error: "Error: Device 51952 not
connected"
process of booting DomU with ''mounted-blktap2'' (VHD for
example) and ''pygrub'' as bootloader:
1. Connect boot-device to Dom0 as ''/dev/xpvd''2. Pygrub get
info for load DomU3. Disconnect boot-device from Dom04. Boot DomU
During step 3 created device disconnecting from Dom0, but xenstore does
not scrape away after device disconnected from Dom0 => result:
"Error: Device /dev/xvdp (51952, tap2) is already connected."
During step 3 created device disconnecting from Dom0, but
''destroyDevice'' method is
passed ''tap'' always => result: "Error: Device 51952
not connected"
-----Inline Attachment Follows-----
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel