Fw: [Xen-devel] [PATCH] blktap2: blktap2 and pygrub (xen-unstabl

To:	Patrick Schlicher <pa-schl@xxxxxx>
Subject:	Fw: [Xen-devel] [PATCH] blktap2: blktap2 and pygrub (xen-unstable)
From:	Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date:	Sun, 1 Aug 2010 12:12:19 -0700 (PDT)
Cc:	Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date:	Sun, 01 Aug 2010 12:13:14 -0700
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1280689939; bh=O4QrnnwjOu0JxH3u+UBsKtyt4E11Hyk0oyJOCc7y+RE=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=2kCSh42x6N/qac+8jWW6oP/Zpct8x3YSR9n79Ns7GvFZB7We0oPreLnwcP0Y+y/HPyXKAWzbZcI0Kd4IEzP2REBP0Zk61Bk8H92i26Yk5kRV21sxc3AoLdkuWHQfsGrRVu4+Ak+CzQR/2v3A5NrGuOH8NS1mNuRsUfQCMB72ZZ8=
Domainkey-signature:	a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=sDWh43mww9m68DrxXaG/+9tLIldg+aECE9sn7I9kAqMrgl9GnVK1XFRuzZTI4l072HVtE2DxWpDytC+IZUmwMQgAA1wFYLpWl43PLfMTTNR6qAwxlA3hD7iKMQMYUtqYpW16lIAg1feODkkZr2IZt0s8kESu2XiI4YV8yz9ItFk=;
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Forwarding to you original patch requested.
It works for me.

Boris

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

From: eXeC001er <execooler@xxxxxxxxx>
Subject: [Xen-devel] [PATCH] blktap2: blktap2 and pygrub (xen-unstable)
To: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
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 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"

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

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

blkpat2_pygrub.patch
Description: Text Data

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

WARNING - OLD ARCHIVES

xen-devel

Fw: [Xen-devel] [PATCH] blktap2: blktap2 and pygrub (xen-unstable)