All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Alexander Graf <agraf@suse.de>, Chris Wright <chrisw@redhat.com>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: KVM call agenda for Jan 26
Date: Tue, 26 Jan 2010 08:42:30 -0600	[thread overview]
Message-ID: <4B5EFF56.8080207@codemonkey.ws> (raw)
In-Reply-To: <4B5EFE13.1070300@redhat.com>

On 01/26/2010 08:37 AM, Avi Kivity wrote:
> People who use discovery tools are probably setting up a migration 
> cluster.  They aren't going to use -cpu host.

BTW, it might be neat to introduce a qemu command line that runs a 
monitor command and exits without creating a VM.  We could then 
introduce a info cpucap command that dumped all of the supported CPU 
features.

Someone setting up a migration cluster would then run qemu -monitor 
command="info cpucap", collect the results, compute an intersection, and 
then use that to generate a -cpu flag.  In fact, providing a tool that 
parsed a bunch of those outputs and generated a -cpu flag would be a 
pretty nice addition.

>>
>> Oh, I was under the impression that the tool was meant to be software 
>> agnostic.  IOW, here are all the virt features your hardware supports.
>
> That's /proc/cpuinfo, we should just extend it, maybe that's what Alex 
> meant, but I'd like to see something more capable.

I definitely think extending /proc/cpuinfo or introducing a 
/proc/virtinfo would be a good idea regardless of any tool we introduce.

Regards,

Anthony Liguori


WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>, Alexander Graf <agraf@suse.de>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: KVM call agenda for Jan 26
Date: Tue, 26 Jan 2010 08:42:30 -0600	[thread overview]
Message-ID: <4B5EFF56.8080207@codemonkey.ws> (raw)
In-Reply-To: <4B5EFE13.1070300@redhat.com>

On 01/26/2010 08:37 AM, Avi Kivity wrote:
> People who use discovery tools are probably setting up a migration 
> cluster.  They aren't going to use -cpu host.

BTW, it might be neat to introduce a qemu command line that runs a 
monitor command and exits without creating a VM.  We could then 
introduce a info cpucap command that dumped all of the supported CPU 
features.

Someone setting up a migration cluster would then run qemu -monitor 
command="info cpucap", collect the results, compute an intersection, and 
then use that to generate a -cpu flag.  In fact, providing a tool that 
parsed a bunch of those outputs and generated a -cpu flag would be a 
pretty nice addition.

>>
>> Oh, I was under the impression that the tool was meant to be software 
>> agnostic.  IOW, here are all the virt features your hardware supports.
>
> That's /proc/cpuinfo, we should just extend it, maybe that's what Alex 
> meant, but I'd like to see something more capable.

I definitely think extending /proc/cpuinfo or introducing a 
/proc/virtinfo would be a good idea regardless of any tool we introduce.

Regards,

Anthony Liguori

  parent reply	other threads:[~2010-01-26 14:42 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-26  6:49 KVM call agenda for Jan 26 Chris Wright
2010-01-26  6:49 ` [Qemu-devel] " Chris Wright
2010-01-26  9:09 ` Alexander Graf
2010-01-26  9:09   ` [Qemu-devel] " Alexander Graf
2010-01-26 13:11   ` Anthony Liguori
2010-01-26 13:11     ` [Qemu-devel] " Anthony Liguori
2010-01-26 13:17     ` Avi Kivity
2010-01-26 13:17       ` [Qemu-devel] " Avi Kivity
2010-01-26 13:18     ` Alexander Graf
2010-01-26 13:18       ` [Qemu-devel] " Alexander Graf
2010-01-26 13:24       ` Avi Kivity
2010-01-26 13:24         ` [Qemu-devel] " Avi Kivity
2010-01-26 13:33         ` Daniel P. Berrange
2010-01-26 13:33           ` [Qemu-devel] " Daniel P. Berrange
2010-01-26 13:37           ` Alexander Graf
2010-01-26 13:37             ` [Qemu-devel] " Alexander Graf
2010-01-26 13:45           ` Avi Kivity
2010-01-26 13:45             ` [Qemu-devel] " Avi Kivity
2010-01-26 14:13         ` Anthony Liguori
2010-01-26 14:13           ` [Qemu-devel] " Anthony Liguori
2010-01-26 14:15           ` Avi Kivity
2010-01-26 14:15             ` [Qemu-devel] " Avi Kivity
2010-01-26 14:22             ` Anthony Liguori
2010-01-26 14:22               ` [Qemu-devel] " Anthony Liguori
2010-01-26 14:26               ` Avi Kivity
2010-01-26 14:26                 ` [Qemu-devel] " Avi Kivity
2010-01-26 14:32                 ` Anthony Liguori
2010-01-26 14:32                   ` [Qemu-devel] " Anthony Liguori
2010-01-26 14:37                   ` Avi Kivity
2010-01-26 14:37                     ` [Qemu-devel] " Avi Kivity
2010-01-26 14:42                     ` Alexander Graf
2010-01-26 14:42                       ` [Qemu-devel] " Alexander Graf
2010-01-26 14:47                       ` Avi Kivity
2010-01-26 14:47                         ` [Qemu-devel] " Avi Kivity
2010-01-26 14:50                         ` Alexander Graf
2010-01-26 14:50                           ` [Qemu-devel] " Alexander Graf
2010-01-26 14:59                           ` Anthony Liguori
2010-01-26 14:59                             ` [Qemu-devel] " Anthony Liguori
2010-01-26 14:42                     ` Anthony Liguori [this message]
2010-01-26 14:42                       ` Anthony Liguori
2010-01-26 14:44                       ` Avi Kivity
2010-01-26 14:44                         ` [Qemu-devel] " Avi Kivity

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=4B5EFF56.8080207@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    /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.