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 /<
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: "Keir Fraser" <
keir.fraser@xxxxxxxxxxxxx>
> Cc: "Boris Derzhavets" <
bderzhavets@xxxxxxxxx>, "Paul Kölle"
> <
paul@xxxxxxxxxxxxx>, "
xen-devel@xxxxxxxxxxxxxxxxxxx"
> <
xen-devel@xxxxxxxxxxxxxxxxxxx>, "Konrad Rzeszutek
Wilk"
> <
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" <
bderzhavets@xxxxxxxxx> </mc/compose?to=
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
Xen-devel@xxxxxxxxxxxxxxxxxxxhttp://lists.xensource.com/xen-devel
