From: "Daniel P. Berrange" <berrange@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: ANNOUNCE: Xen 3.1.1 Second Release Candidate
Date: Thu, 27 Sep 2007 17:56:55 +0100 [thread overview]
Message-ID: <20070927165655.GL17433@redhat.com> (raw)
In-Reply-To: <C3219B01.16163%Keir.Fraser@cl.cam.ac.uk>
On Thu, Sep 27, 2007 at 05:38:09PM +0100, Keir Fraser wrote:
> Folks,
>
> The second release candidate for 3.1.1 is now tagged and available from
> http://xenbits.xensource.com/xen-3.1-testing.hg. Hopefully we can call the
> final release next week, so please test!
Is the 3.1.1 release intended to be hypervisor ABI compatible with the
3.1.0 release ? ie can I expect the 3.1.1 userspace bits to work reliably
on a 3.1.0 hypervisor, or vica-verca.
A quick test shows I can start XenD & launch guests with a 3.1.1 XenD
on a 3.1.0 hypervisor. I'm wondering if this is just luck that will soon
fail me, or a intended result ?
If hypervisor ABI compatability for minor point releases is intended this
would make me very happy because it removes a huge upgrade headache. We
have traditionally not been able to push out the Xen minor point releases
as update errata to Fedora distros because of the need to lock-step upgrade
the hypervisor at the same time as the userspace.
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2007-09-27 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 16:38 ANNOUNCE: Xen 3.1.1 Second Release Candidate Keir Fraser
2007-09-27 16:56 ` Daniel P. Berrange [this message]
2007-09-27 17:05 ` Keir Fraser
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=20070927165655.GL17433@redhat.com \
--to=berrange@redhat.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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.