Re: [Xen-devel] Xen 4.3 development update CODE FREEZE HAS_BEGUN

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Tue, Apr 16, 2013 at 05:24:05PM +0100, George Dunlap wrote:
> On 16/04/13 17:11, Wei Liu wrote:
> > On Tue, Apr 16, 2013 at 04:20:09PM +0100, George Dunlap wrote:
> >> On Tue, Apr 16, 2013 at 4:02 PM, Wei Liu <wei.liu2@xxxxxxxxxx> wrote:
> >>> On Tue, Apr 16, 2013 at 01:50:26PM +0100, George Dunlap wrote:
> >>>> On Tue, Apr 16, 2013 at 1:22 PM, George Dunlap
> >>>> <George.Dunlap@xxxxxxxxxxxxx> wrote:
> >>>>
> >>>>> == Bugs ==
> >>>>>
> >>>>> * xl, compat mode, and older kernels
> >>>>>    owner: ?
> >>>>>    Many older 32-bit PV kernels that can run on a 64-bit hypervisor with
> >>>>>    xend do not work when started with xl.  The following work-around 
> >>>>> seems to
> >>>>>    work:
> >>>>>      xl create -p lightning.cfg
> >>>>>      xenstore-write /local/domain/$(xl domid
> >>>>> lightning)/device/vbd/51713/protocol x86_32-abi
> >>>>>      xl unpause lightning
> >>>>>    This node is normally written by the guest kernel, but for older 
> >>>>> kernels
> >>>>>    seems not to be.  xend must have a work-around; port this 
> >>>>> work-around to xl.
> >>> I played with Xend several years ago, I can try to have a look at this.
> >>>
> > Quick question, anyone has kernel image that's needs this workaround?
> 
> The original thread that started this is here:
> 
> http://www.gossamer-threads.com/lists/xen/devel/258488?do=post_view_threaded
> 
> It mentioned using Debian etch's built-in 2.6.16.33-xen kernel.

Now I've identified the problem, should I write a patch for it or should
I wait till 4.4 window is open?


Wei.

> 
>   -George

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel