From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:32922) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QZ1Rs-0005bI-HW for qemu-devel@nongnu.org; Tue, 21 Jun 2011 09:57:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QZ1Rq-0006rV-MV for qemu-devel@nongnu.org; Tue, 21 Jun 2011 09:57:00 -0400 Received: from mx1.redhat.com ([209.132.183.28]:61543) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QZ1Rq-0006rJ-7n for qemu-devel@nongnu.org; Tue, 21 Jun 2011 09:56:58 -0400 Message-ID: <4E00A322.2030006@redhat.com> Date: Tue, 21 Jun 2011 16:56:50 +0300 From: Avi Kivity MIME-Version: 1.0 References: <4E008060.5020900@redhat.com> <4E00A1B3.9030508@codemonkey.ws> In-Reply-To: <4E00A1B3.9030508@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] KVM call agenda for June 21 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Lucas Meneghel Rodrigues , "Justin M. Forbes" , qemu-devel@nongnu.org, KVM devel mailing list , quintela@redhat.com On 06/21/2011 04:50 PM, Anthony Liguori wrote: > On 06/21/2011 06:28 AM, Avi Kivity wrote: >> On 06/20/2011 10:42 AM, Juan Quintela wrote: >>> Please send in any agenda items you are interested in covering. >>> >> >> >> https://bugzilla.redhat.com/show_bug.cgi?id=689672 - Guests do not start >> after upgrading qemu to 0.13 >> >> Seems like our backward compatibility plan isn't working. How do we >> address it? How do we test it? > > f13 is ancient, no? Yes, a year old. Furthermore, Justin tells me it carries a lot downstream patches. > > I'm not sure what this particular issue is, but is this doing -M pc-0.12? > It has its own machine type. So this report may not indicate any problem with upstream. Still, I feel we have a potential problem here. We identify guest-visible attributes just by review; we're sure to miss something here and there. Unlike ordinary bugs, compatibility problems only show up later and are much harder to fix. Second, we don't do any tests in this area that I'm aware of. Lucas, what would it take (thanks, you're most kind) to test multiple qemus in a single run? We can have a script that runs lspci -vvvvvvvvvvvvvvvvvvv, x86info, and other interesting stuff and compare the results, and also system tests that boot a guest on multiple qemus (with the same -M and different -M) and see if things work. We can probably continue on email, I don't see a real need for a call for this topic. -- error compiling committee.c: too many arguments to function