From: Dustin Kirkland <kirkland@canonical.com>
To: Avi Kivity <avi@redhat.com>, Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [ANNOUNCE] qemu-kvm-0.12.0-rc2 released
Date: Mon, 14 Dec 2009 15:58:23 -0600 [thread overview]
Message-ID: <d9c105ea0912141358n33a937car68dc17bc3fa4b985@mail.gmail.com> (raw)
In-Reply-To: <4B2684EC.2040504@redhat.com>
On Mon, Dec 14, 2009 at 12:33 PM, Avi Kivity <avi@redhat.com> wrote:
> qemu-kvm-0.12.0-rc2 is now available. This release is is based on the
> upstream qemu 0.12.0-rc2, plus kvm-specific enhancements. Please see the
> original qemu 0.12.0-rc2 release announcement for details.
>
> This release can be used with the kvm kernel modules provided by your
> distribution kernel, or by the modules in the kvm-kmod package, such as
> kvm-kmod-2.6.32.
>
> Please give test this release out so we can enjoy a stable 0.12.0 final
> release.
Hi Avi/Anthony-
I'm working on the packaging updates for Ubuntu Lucid, and I'm having
trouble with the BIOS bits of qemu-kvm.
It seems that a fair amount of the BIOS submodules are missing.
The roms/ tree is basically empty.
I see some of the necessary bits in pc-bios/ and in kvm/vgabios/, but
not enough here to build a usable qemu-kvm-0.12.0~rc2 package yet.
:-Dustin
next parent reply other threads:[~2009-12-14 21:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B2684EC.2040504@redhat.com>
2009-12-14 21:58 ` Dustin Kirkland [this message]
2009-12-15 9:10 ` [Qemu-devel] Re: [ANNOUNCE] qemu-kvm-0.12.0-rc2 released Avi Kivity
2009-12-15 14:23 ` Lennart Sorensen
2009-12-15 14:29 ` Anthony Liguori
2009-12-15 15:21 ` Dustin Kirkland
2009-12-18 4:51 ` Dustin Kirkland
2009-12-20 16:25 ` Avi Kivity
2009-12-21 3:39 ` Dustin Kirkland
2009-12-21 9:30 ` Avi Kivity
[not found] ` <4B2748B6.9080305@eseco.de>
2009-12-15 9:07 ` Avi Kivity
2009-12-15 14:31 ` Anthony Liguori
2009-12-15 14:41 ` Gerd Hoffmann
2009-12-15 18:22 ` Luiz Capitulino
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=d9c105ea0912141358n33a937car68dc17bc3fa4b985@mail.gmail.com \
--to=kirkland@canonical.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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).