From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <keir@xensource.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Xen 3.1 released!
Date: Mon, 21 May 2007 12:10:21 +0200 [thread overview]
Message-ID: <46518C2D.76E4.0078.0@novell.com> (raw)
In-Reply-To: <C2738EB5.F2EB%keir@xensource.com>
Any chance of getting the -rc10 tag removed from xen/Makefile? Thanks, Jan
>>> Keir Fraser <keir@xensource.com> 18.05.07 18:11 >>>
Folks,
We're pleased to announce the official release of Xen 3.1!
This represents a major milestone in the Xen project containing performance
and stability enhancements, additional features for all architectures, and a
brand new management API. Highlights of this release include:
- XenAPI 1.0 support
- XML configuration files for virtual machines;
- VM life-cycle management operations; and
- Secure on- or off-box XML-RPC with bindings for many languages
- Preliminary save/restore/migrate support for HVM (e.g. Windows) VMs;
- Dynamic memory control for HVM guests;
- 32-on-64 PV guest support (run PAE PV VMs on a 64-bit Xen!); and
- Blktap copy-on-write disk support.
You can get the source using mercurial from:
http://xenbits.xensource.com/xen-3.1-testing.hg
Source and binary tarballs, and RPMs, are available from:
http://www.xensource.com/download/index_oss.html
Cheers,
Keir (on behalf of the whole Xen dev team)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2007-05-21 10:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 16:11 Xen 3.1 released! Keir Fraser
2007-05-21 1:26 ` Tony Breeds
2007-05-22 4:06 ` 答复: [Xen-users] Re: [Xen-devel] " Yuzhong Sun
2007-05-22 4:06 ` Yuzhong Sun
2007-05-21 10:10 ` Jan Beulich [this message]
2007-05-21 10:12 ` Keir Fraser
2007-05-29 10:41 ` Pasi Kärkkäinen
2007-05-29 10:56 ` 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=46518C2D.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=keir@xensource.com \
--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.