From: =?ISO-8859-1?Q?Andreas_F=E4rber?= Subject: Re: [Qemu-devel] KVM call agenda for May, Tuesday 8th Date: Tue, 08 May 2012 16:10:55 +0200 Message-ID: <4FA9296F.4060903@suse.de> References: <87pqag9psa.fsf@elfo.elfo> <4FA7C60E.8030802@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: quintela@redhat.com, qemu-devel@nongnu.org, KVM devel mailing list , malc , Paolo Bonzini , Michael Roth , Blue Swirl To: Anthony Liguori Return-path: Received: from cantor2.suse.de ([195.135.220.15]:50551 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754582Ab2EHOK4 (ORCPT ); Tue, 8 May 2012 10:10:56 -0400 In-Reply-To: <4FA7C60E.8030802@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: 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. >=20 > - 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 th= e 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 buil= d 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 --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrn= berg