All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Lucas Meneghel Rodrigues <lmr@redhat.com>,
	"Justin M. Forbes" <jforbes@redhat.com>,
	qemu-devel@nongnu.org,
	KVM devel mailing list <kvm@vger.kernel.org>,
	quintela@redhat.com
Subject: Re: [Qemu-devel] KVM call agenda for June 21
Date: Tue, 21 Jun 2011 11:07:33 -0500	[thread overview]
Message-ID: <4E00C1C5.2080909@codemonkey.ws> (raw)
In-Reply-To: <4E00A322.2030006@redhat.com>

On 06/21/2011 08:56 AM, Avi Kivity wrote:
> On 06/21/2011 04:50 PM, Anthony Liguori wrote:
> 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.

I think a simple tool that dumped as much info as possible in a 
diff'able format would be useful not only within guests but also in bare 
metal.

Regards,

Anthony Liguori

>
> We can probably continue on email, I don't see a real need for a call
> for this topic.
>


WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Lucas Meneghel Rodrigues <lmr@redhat.com>,
	quintela@redhat.com, qemu-devel@nongnu.org,
	"Justin M. Forbes" <jforbes@redhat.com>,
	KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM call agenda for June 21
Date: Tue, 21 Jun 2011 11:07:33 -0500	[thread overview]
Message-ID: <4E00C1C5.2080909@codemonkey.ws> (raw)
In-Reply-To: <4E00A322.2030006@redhat.com>

On 06/21/2011 08:56 AM, Avi Kivity wrote:
> On 06/21/2011 04:50 PM, Anthony Liguori wrote:
> 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.

I think a simple tool that dumped as much info as possible in a 
diff'able format would be useful not only within guests but also in bare 
metal.

Regards,

Anthony Liguori

>
> We can probably continue on email, I don't see a real need for a call
> for this topic.
>

  parent reply	other threads:[~2011-06-21 16:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20  7:42 KVM call agenda for June 21 Juan Quintela
2011-06-20  7:42 ` [Qemu-devel] " Juan Quintela
2011-06-21 11:28 ` Avi Kivity
2011-06-21 11:28   ` [Qemu-devel] " Avi Kivity
2011-06-21 13:50   ` Anthony Liguori
2011-06-21 13:50     ` Anthony Liguori
2011-06-21 13:56     ` Avi Kivity
2011-06-21 13:56       ` Avi Kivity
2011-06-21 14:27       ` Markus Armbruster
2011-06-21 14:27         ` Markus Armbruster
2011-06-21 14:28         ` Avi Kivity
2011-06-21 14:28           ` Avi Kivity
2011-06-21 15:08       ` Frédéric Grelot
2011-06-21 16:07       ` Anthony Liguori [this message]
2011-06-21 16:07         ` Anthony Liguori
2011-06-21 16:58       ` Lucas Meneghel Rodrigues
2011-06-21 16:58         ` Lucas Meneghel Rodrigues
2011-06-21 13:51 ` Anthony Liguori
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=4E00C1C5.2080909@codemonkey.ws \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.