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

[Pasi Kärkkäinen <pasik@xxxxxx>]

On Wed, Jun 09, 2010 at 01:01:51PM -0700, Boris Derzhavets wrote:
>    >Does doing "git revert -m 1 528ea798f02ccb03023e72cbda665ed5c3eec6b1"
>    >and rebuilding help?
> 
>    Yes, it helps.
> 
>    The first time virt-install F13 PV DomU is running in VNC mode at Xen
>    4.0.1 (2.6.32.15)
>    Dom0 on top of Ubuntu 10.04 Server. Virt-install passed through phase of
>    data fetching
>    from Apache Mirror at Dom0 like it happened before (.14)
> 

Good to hear that. Problem found..

-- Pasi

>    Boris
> 
>    --- On Wed, 6/9/10, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
> 
>      From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
>      Subject: Re: [Xen-devel] Re: Failure to start xend with 2.6.32.15
>      (c2cb3df04eb3ff68d0de102b2acacc9b8616e659) under Xen 4.0
>      To: "Boris Derzhavets" <bderzhavets@xxxxxxxxx>
>      Cc: =?ISO-8859-1?Q?Paul_K=F6ll?=@xxxxxxxxx, "e" <paul@xxxxxxxxxxxxx>,
>      "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Keir
>      Fraser" <keir.fraser@xxxxxxxxxxxxx>, "Konrad Rzeszutek Wilk"
>      <konrad.wilk@xxxxxxxxxx>
>      Date: Wednesday, June 9, 2010, 2:50 PM
> 
>      On 06/09/2010 11:37 AM, Boris Derzhavets wrote:
>      > >Things are pretty bad in the meantime, if they use a pvops kernel.
>      > > Maybe I should create a specific xen 4.0.0 branch?
>      >
>      > I've created 4.0.1-rc2-pre -  xen-4.0.1.fc13.src.rpm for F13
>      > and rebuild & reinstalled xen's rpms. Hot Hypervisor upgrade up to
>      > 4.0.1-rc2-pre
>      > Kernel 2.6.32.15.
>      >
>      > Pasi and myself noticed problems with VNC. Virt-installs run only text
>      > mode,
>      > otherwise hang on top Ubuntu 10.04 Server. It DOESN'T happen on top of
>      F13
>      > However,  at runtime on F13 :-
>      > VNC console hangs for Lucid PV Guest at Xen 4.0.1 Dom0 (.15 kernel) on
>      > top F13
>      > VNC console works for  F13 PV   Guest at Xen 4.0.1 Dom0 (.15 kernel)
>      > on top F13
>      >
> 
>      That's more likely related to the network problems than the
>      evtchn/gntdev device problems.
> 
>      Does doing "git revert -m 1 528ea798f02ccb03023e72cbda665ed5c3eec6b1"
>      and rebuilding help?
> 
>          J
> 
>      >
>      > It worked fine say for .12 or .13 kernels.
>      >
>      > > Any chance of a hotfix for just this particular issue?
>      >
>      > Looks like network communication problem with VNC.
>      > It's testing environment. But any customer watching  so unstable
>      > picture, won't be happy.
>      >
>      > Boris.
>      >
>      > --- On *Wed, 6/9/10, Jeremy Fitzhardinge /<[1]jeremy@xxxxxxxx>/*
>      wrote:
>      >
>      >
>      >     From: Jeremy Fitzhardinge <[2]jeremy@xxxxxxxx>
>      >     Subject: Re: [Xen-devel] Re: Failure to start xend with 2.6.32.15
>      >     (c2cb3df04eb3ff68d0de102b2acacc9b8616e659) under Xen 4.0
>      >     To: "Keir Fraser" <[3]keir.fraser@xxxxxxxxxxxxx>
>      >     Cc: "Boris Derzhavets" <[4]bderzhavets@xxxxxxxxx>, "Paul Kölle"
>      >     <[5]paul@xxxxxxxxxxxxx>, "[6]xen-devel@xxxxxxxxxxxxxxxxxxx"
>      >     <[7]xen-devel@xxxxxxxxxxxxxxxxxxx>, "Konrad Rzeszutek Wilk"
>      >     <[8]konrad.wilk@xxxxxxxxxx>
>      >     Date: Wednesday, June 9, 2010, 2:16 PM
>      >
>      >     On 06/09/2010 05:02 AM, Keir Fraser wrote:
>      >     > On 09/06/2010 12:15, "Boris Derzhavets"
>      <[9]bderzhavets@xxxxxxxxx
>      >     </mc/compose?to=[10]bderzhavets@xxxxxxxxx>> wrote:
>      >     >
>      >     >
>      >     >> Via my experience in meantime Xen 4.0 official release doesn't
>      >     have either
>      >     >> origin/xen/stable or origin/xen/stable-2.6.32.x branch
>      >     generating kernel
>      >     >> supporting it's Dom0.
>      >     >>
>      >     > We'll get a 4.0.1 release out by end of the month. The next 3.4
>      >     release is
>      >     > further out, but I don't think many users of that branch are
>      >     going to be
>      >     > flirting with pv_ops dom0. If they are, they can always upgrade
>      >     to 4.0
>      >     > branch.
>      >     >
>      >
>      >     Things are pretty bad in the meantime, if they use a pvops kernel.
>      >     Maybe I should create a specific xen 4.0.0 branch?
>      >
>      >     Any chance of a hotfix for just this particular issue?
>      >
>      >         J
>      >
>      >
> 
>      _______________________________________________
>      Xen-devel mailing list
>      [11]Xen-devel@xxxxxxxxxxxxxxxxxxx
>      [12]http://lists.xensource.com/xen-devel
> 
> References
> 
>    Visible links
>    1. file:///mc/compose?to=jeremy@xxxxxxxx
>    2. file:///mc/compose?to=jeremy@xxxxxxxx
>    3. file:///mc/compose?to=keir.fraser@xxxxxxxxxxxxx
>    4. file:///mc/compose?to=bderzhavets@xxxxxxxxx
>    5. file:///mc/compose?to=paul@xxxxxxxxxxxxx
>    6. file:///mc/compose?to=xen-devel@xxxxxxxxxxxxxxxxxxx
>    7. file:///mc/compose?to=xen-devel@xxxxxxxxxxxxxxxxxxx
>    8. file:///mc/compose?to=konrad.wilk@xxxxxxxxxx
>    9. file:///mc/compose?to=bderzhavets@xxxxxxxxx
>   10. file:///mc/compose?to=bderzhavets@xxxxxxxxx
>   11. file:///mc/compose?to=Xen-devel@xxxxxxxxxxxxxxxxxxx
>   12. http://lists.xensource.com/xen-devel

> _______________________________________________
> 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