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

[Åukasz OleÅ <lukaszoles@xxxxxxxxx>]

On Monday 16 August 2010 18:35:10 Stefano Stabellini wrote:
> On Sun, 1 Aug 2010, Boris Derzhavets wrote:
> > 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"
> 
> applied, thanks

Could you merge it also to Xen 4.0? Without this patch I can not use vhd + 
pygrub. In  Xen-unstable it was added in commit cd5b4135fe03.

Regards,

Åukasz OleÅ

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