From: "Andreas Färber" <afaerber@suse.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: KVM devel mailing list <kvm@vger.kernel.org>,
quintela@redhat.com, Michael Roth <mdroth@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] KVM call agenda for May, Tuesday 8th
Date: Tue, 08 May 2012 16:10:55 +0200 [thread overview]
Message-ID: <4FA9296F.4060903@suse.de> (raw)
In-Reply-To: <4FA7C60E.8030802@codemonkey.ws>
Am 07.05.2012 14:54, schrieb Anthony Liguori:
> On 05/07/2012 06:47 AM, Juan Quintela wrote:
>>
>> Please send in any agenda items you are interested in covering.
>
> - Status of the 1.1 release
Since it looked like the call is not going to take place lacking
feedback from Anthony, I will provocatively go ahead and say the status
of 1.1 is pretty bad, currently. ;)
rc0 is available, but patches submitted for 1.1 shortly before rc0
neither got review nor were applied. Neither did pulls or patches
applied by Anthony get such a notice fwiw so that it's hard to
distinguish what's missing for anyone but the patch author.
With rc0 not being provided as tarball, it would be nice to document the
official, reproducible way of packaging a QEMU tarball on the Wiki. I
have collected some steps from the Rob Landley mips thread, but the
submodules complicate things a bit.
rc1 should've been released yesterday, but it's not available yet, no
info and same issue with patches not being applied.
In the current state of master, rc1 will not build on ppc due to an
#error introduced since rc0 by malc - with its history, Darwin/ppc
should not be a release blocker here and *some* fix to restore the build
should please be applied soon.
And worse, there's more and more colliding patch series on the list -
fixed-width visitors, realize, QBus, VMState, AREG0, CPU - for which we
need a strategy to coordinate our ongoing development and post-1.1
merging. Someone needs to rebase on someone else, question is whom.
Some downstream feedback: I've so far been unable to do a static build
of v1.1-rc0 in the openSUSE build system due to a -lpcre coming from
gthread-2.0.pc Libs.private - an issue we don't see for v1.0.1. If
another distro has encountered that issue I'd be grateful for feedback.
Might be our own issue.
In course of investigating though, I've noticed that lots of our
configure checks are not limited to non-static/softmmu builds and will
contribute cflags/libs to a static linux-user build even if unused.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-05-08 14:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 11:47 [Qemu-devel] KVM call agenda for May, Tuesday 8th Juan Quintela
2012-05-07 12:54 ` Anthony Liguori
2012-05-08 14:10 ` Andreas Färber [this message]
2012-05-08 14:24 ` Anthony Liguori
2012-05-08 14:53 ` Andreas Färber
2012-05-08 15:13 ` Andreas Färber
2012-05-08 15:32 ` Anthony Liguori
2012-05-07 12:59 ` Anthony Liguori
2012-05-07 13:22 ` 陳韋任
2012-05-08 12:14 ` Anthony Liguori
2012-05-08 12:22 ` Alexander Graf
2012-05-08 13:39 ` Luiz Capitulino
2012-05-08 13:53 ` Juan Quintela
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=4FA9296F.4060903@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).