[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] KVM call agenda for June 21
From: |
Markus Armbruster |
Subject: |
Re: [Qemu-devel] KVM call agenda for June 21 |
Date: |
Tue, 21 Jun 2011 16:27:01 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) |
Avi Kivity <address@hidden> writes:
> 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.
Suggest to compare info qtree as well.
> We can probably continue on email, I don't see a real need for a call
> for this topic.
Re: [Qemu-devel] KVM call agenda for June 21, Anthony Liguori, 2011/06/21