All of lore.kernel.org
 help / color / mirror / Atom feed
* ANNOUNCE: Xen 3.1.1 Second Release Candidate
@ 2007-09-27 16:38 Keir Fraser
  2007-09-27 16:56 ` Daniel P. Berrange
  0 siblings, 1 reply; 3+ messages in thread
From: Keir Fraser @ 2007-09-27 16:38 UTC (permalink / raw)
  To: xen-devel

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!

 -- Keir

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: ANNOUNCE: Xen 3.1.1 Second Release Candidate
  2007-09-27 16:38 ANNOUNCE: Xen 3.1.1 Second Release Candidate Keir Fraser
@ 2007-09-27 16:56 ` Daniel P. Berrange
  2007-09-27 17:05   ` Keir Fraser
  0 siblings, 1 reply; 3+ messages in thread
From: Daniel P. Berrange @ 2007-09-27 16:56 UTC (permalink / raw)
  To: Keir Fraser; +Cc: xen-devel

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: ANNOUNCE: Xen 3.1.1 Second Release Candidate
  2007-09-27 16:56 ` Daniel P. Berrange
@ 2007-09-27 17:05   ` Keir Fraser
  0 siblings, 0 replies; 3+ messages in thread
From: Keir Fraser @ 2007-09-27 17:05 UTC (permalink / raw)
  To: Daniel P. Berrange; +Cc: xen-devel

On 27/9/07 17:56, "Daniel P. Berrange" <berrange@redhat.com> wrote:

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

I can happily tell you that the tools ABI is stable for minor point
releases. At least, that is our intention (we don't automatically test it).

By the way, I guess I'll push your xend patches into -rc3 if they seem well
behaved in -unstable after a few days.

 -- Keir

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-09-27 17:05 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-09-27 16:38 ANNOUNCE: Xen 3.1.1 Second Release Candidate Keir Fraser
2007-09-27 16:56 ` Daniel P. Berrange
2007-09-27 17:05   ` Keir Fraser

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.