Re: [Xen-devel] Re: Failure to start xend with 2.6.32.15 (c2cb3df04eb3ff68d0de102b2acacc9b8616e659) under Xen 4.0

[Boris Derzhavets <bderzhavets@xxxxxxxxx>]

If it's possible a separate patch for official xen 4.0 tarball  should be created.
To provide an option of loading 2.6.32.15 under Xen 4.0 Release.
Otherwise,  it  appears to be useless. Specially on F13

Boris

--- On Wed, 6/9/10, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:

From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: Failure to start xend with 2.6.32.15 (c2cb3df04eb3ff68d0de102b2acacc9b8616e659) under Xen 4.0
To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>, "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
Date: Wednesday, June 9, 2010, 6:34 AM

On 08/06/2010 19:50, "Jeremy Fitzhardinge" <jeremy@xxxxxxxx> wrote:

>> Seems like  i have  evtchn device missing, regardless in .config :-
>>
>
> You should be able to see if its present in the kernel by looking at
> /proc/misc, but something still needs to create the /dev nodes.  Usually
> this is udev, but libxc goes to special lengths to get this wrong, and
> will end up deleting the perfectly good nodes unless you update it.
>
> Keir, have the libxc changes been backported to all the release trees?

Backported to 4.0. Wasn't sure about putting it into 3.4 yet? I'm not too
fussed either way. It's working okay for me and it is basically the right
thing to do. :-)

-- Keir



_______________________________________________
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