From: Keir Fraser <keir.fraser@eu.citrix.com>
To: M A Young <m.a.young@durham.ac.uk>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Sixth (and final?) release candidate for Xen 3.4.3
Date: Thu, 6 May 2010 17:34:22 +0100 [thread overview]
Message-ID: <C808AE1E.136D1%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <alpine.GSO.2.00.1005061710560.2292@algedi.dur.ac.uk>
On 06/05/2010 17:13, "M A Young" <m.a.young@durham.ac.uk> wrote:
>> Do you have this issue with 3.4.2?
>
> No, it boots with 3.4.2 which I actually a bit surprised about as I didn't
> think 3.4.2 was compatible with that kernel though this might explain why
> the network doesn't work for 3.4.2.
Hm, there were changes to 3.4.3 to make it work better with pv_ops dom0
kernels. I'm thinking things like xen-3.4-testing:19862 and 19863. I suggest
you post more details and you should get help from pv_ops people (I cc'ed a
couple of them :-). They may be able to tell you straight off whether your
pv_ops kernel is too old/new/weird/whatever, for example.
-- Keir
next prev parent reply other threads:[~2010-05-06 16:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 12:00 Sixth (and final?) release candidate for Xen 3.4.3 Keir Fraser
2010-05-05 9:50 ` M A Young
2010-05-06 14:13 ` M A Young
2010-05-06 14:26 ` Keir Fraser
2010-05-06 16:13 ` M A Young
2010-05-06 16:34 ` Keir Fraser [this message]
2010-05-07 2:03 ` Zhang, Xiantao
2010-05-07 7:10 ` Keir Fraser
2010-05-07 23:11 ` Jeremy Fitzhardinge
2010-05-08 8:05 ` Keir Fraser
2010-05-08 11:00 ` Boris Derzhavets
2010-05-08 15:14 ` Errors when loading 2.6.32.12 under Xen 4.0 on ASUS P5Q-E Boris Derzhavets
2010-05-12 17:50 ` Sixth (and final?) release candidate for Xen 3.4.3 Langsdorf, Mark
2010-05-12 19:21 ` Keir Fraser
2010-05-12 19:42 ` Langsdorf, Mark
2010-05-06 18:50 ` Jeremy Fitzhardinge
2010-05-06 19:13 ` M A Young
2010-05-06 20:17 ` Jeremy Fitzhardinge
2010-05-07 18:33 ` M A Young
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=C808AE1E.136D1%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=m.a.young@durham.ac.uk \
--cc=xen-devel@lists.xensource.com \
--cc=xiantao.zhang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).