From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Boris Derzhavets <bderzhavets@yahoo.com>
Cc: e <paul@subsignal.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Keir Fraser" <keir.fraser@eu.citrix.com>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Subject: Re: Re: Failure to start xend with 2.6.32.15 (c2cb3df04eb3ff68d0de102b2acacc9b8616e659) under Xen 4.0
Date: Wed, 09 Jun 2010 11:50:39 -0700 [thread overview]
Message-ID: <4C0FE27F.2000908@goop.org> (raw)
In-Reply-To: <159970.98783.qm@web56107.mail.re3.yahoo.com>
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@goop.org>/* wrote:
>
>
> From: Jeremy Fitzhardinge <jeremy@goop.org>
> Subject: Re: [Xen-devel] Re: Failure to start xend with 2.6.32.15
> (c2cb3df04eb3ff68d0de102b2acacc9b8616e659) under Xen 4.0
> To: "Keir Fraser" <keir.fraser@eu.citrix.com>
> Cc: "Boris Derzhavets" <bderzhavets@yahoo.com>, "Paul Kölle"
> <paul@subsignal.org>, "xen-devel@lists.xensource.com"
> <xen-devel@lists.xensource.com>, "Konrad Rzeszutek Wilk"
> <konrad.wilk@oracle.com>
> 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@yahoo.com
> </mc/compose?to=bderzhavets@yahoo.com>> 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
>
>
next prev parent reply other threads:[~2010-06-09 18:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 18:29 Re: Failure to start xend with 2.6.32.15 (c2cb3df04eb3ff68d0de102b2acacc9b8616e659) under Xen 4.0 Boris Derzhavets
2010-06-08 18:50 ` Jeremy Fitzhardinge
2010-06-08 18:59 ` Boris Derzhavets
2010-06-08 19:13 ` Boris Derzhavets
2010-06-08 19:15 ` Jeremy Fitzhardinge
2010-06-08 19:27 ` Boris Derzhavets
2010-06-08 20:02 ` Re: Failure to start xend with 2.6.32.15 (c2cb3df04eb3ff68d0de102b2acacc9b8616e659) under Xen 4.0 (F13) Boris Derzhavets
2010-06-09 7:55 ` Paul Kölle
2010-06-09 10:34 ` Re: Failure to start xend with 2.6.32.15 (c2cb3df04eb3ff68d0de102b2acacc9b8616e659) under Xen 4.0 Keir Fraser
2010-06-09 11:15 ` Boris Derzhavets
2010-06-09 12:02 ` Keir Fraser
2010-06-09 18:16 ` Jeremy Fitzhardinge
2010-06-09 18:37 ` Boris Derzhavets
2010-06-09 18:50 ` Jeremy Fitzhardinge [this message]
2010-06-09 20:01 ` Boris Derzhavets
2010-06-09 20:15 ` Pasi Kärkkäinen
2010-06-10 13:16 ` Boris Derzhavets
2010-06-09 12:12 ` Boris Derzhavets
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C0FE27F.2000908@goop.org \
--to=jeremy@goop.org \
--cc=bderzhavets@yahoo.com \
--cc=keir.fraser@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=paul@subsignal.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.