public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
	quintela@redhat.com, qemu-devel@nongnu.org,
	KVM devel mailing list <kvm@vger.kernel.org>,
	"Justin M. Forbes" <jforbes@redhat.com>,
	Lucas Meneghel Rodrigues <lmr@redhat.com>
Subject: Re: [Qemu-devel] KVM call agenda for June 21
Date: Tue, 21 Jun 2011 16:27:01 +0200	[thread overview]
Message-ID: <m3hb7jclai.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <4E00A322.2030006@redhat.com> (Avi Kivity's message of "Tue, 21 Jun 2011 16:56:50 +0300")

Avi Kivity <avi@redhat.com> 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.

  reply	other threads:[~2011-06-21 14:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20  7:42 KVM call agenda for June 21 Juan Quintela
2011-06-21 11:28 ` Avi Kivity
2011-06-21 13:50   ` [Qemu-devel] " Anthony Liguori
2011-06-21 13:56     ` Avi Kivity
2011-06-21 14:27       ` Markus Armbruster [this message]
2011-06-21 14:28         ` Avi Kivity
2011-06-21 15:08       ` Frédéric Grelot
2011-06-21 16:07       ` Anthony Liguori
2011-06-21 16:58       ` Lucas Meneghel Rodrigues
2011-06-21 13:51 ` Anthony Liguori

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=m3hb7jclai.fsf@blackfin.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=jforbes@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lmr@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