From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Xen-devel <xen-devel@lists.xensource.com>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Zachary Amsden <zach@vmware.com>, Andi Kleen <ak@suse.de>
Subject: Xen/paravirt_ops kernel available for testing
Date: Thu, 26 Apr 2007 13:23:52 -0700 [thread overview]
Message-ID: <46310A58.4090207@goop.org> (raw)
Hi all,
I'm pleased to announce a Xen paravirt_ops kernel available for testing
at http://xenbits.xensource.com/ext/paravirt_ops/.
These kernels are based on this morning's 2.6.21, along with all the
paravirt_ops + Xen patches. The pre-built i386 kernel RPM is based on
the FC6 configuration, and it has both Xen and VMI paravirt_ops support
enabled. Unfortunately the RPM is a bit rough, and you'll need to
generate an initrd and update your boot-loader to make it bootable. To
boot under Xen, use /boot/vmlinux-.gz as the kernel image.
This is definitely a testing snapshot release, but it has had a bit of
testing. I've been using it running native on my main work machine, and
it behaves exactly like a non-paravirt kernel. It has also been tested
under Xen on XenRT, XenSource's automated testing infrastructure, where
it passes almost everything.
There are a couple of expected BUG messages which appear on boot: one in
init_sched_clock, and one in xen_apic_read. Both are harmless warning
messages, and will be removed shortly. (However, if you see more than
one xen_apic_read warning, please send me the details along with your
kernel config.)
Please see the RELEASE*.txt for release notes.
J
reply other threads:[~2007-04-26 20:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46310A58.4090207@goop.org \
--to=jeremy@goop.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.com \
--cc=zach@vmware.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).