qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel@nongnu.org, Cole Robinson <crobinso@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] define qemukvm-1.2 machine type
Date: Fri, 14 Dec 2012 07:29:27 -0600	[thread overview]
Message-ID: <87k3skhidk.fsf@codemonkey.ws> (raw)
In-Reply-To: <1379550897.23864274.1355471680686.JavaMail.root@redhat.com>

Paolo Bonzini <pbonzini@redhat.com> writes:

>> > > > I think distros that used to ship qemu-kvm should just change
>> > > > the default just like for the acpi_piix4.c change.
>> > >
>> > > Maybe we could provide a --with-qemu-kvm-compat configure flag to
>> > > them?
>
> I like this.
>
>> > I think that defeats the purpose of a single binary.
>> > 
>> > I think it would be better for the distros to have a qemu-kvm
>> > script that was:
>> > 
>> > /usr/libexec/qemu-kvm:
>> > 
>> > #!/bin/sh
>> > 
>> > qemu-system-x86_64 -enable-qemu-kvm-compat "$@"
>> 
>> That would be even better. I proposed a configure flag because I
>> understood (maybe incorrectly) that Paolo proposed a build-time
>> default change.
>
> Yes, that's what I was thinking.  The problem is that Fedora did ship a
> qemu-system-x86_64 binary that disabled the qemu-kvm options (including
> using TCG by default), but it still had a qemu-kvm-compatible migration
> format.

Can you be more specific?  What's different in the migration format?

Regards,

Anthony Liguori

>
> Paolo

  reply	other threads:[~2012-12-14 13:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-12 22:39 [Qemu-devel] [PATCH] define qemukvm-1.2 machine type Marcelo Tosatti
2012-12-13  8:35 ` Paolo Bonzini
2012-12-13 20:29   ` Marcelo Tosatti
2012-12-13 21:25   ` Eduardo Habkost
2012-12-13 21:35     ` Anthony Liguori
2012-12-13 21:41       ` Eduardo Habkost
2012-12-14  7:54         ` Paolo Bonzini
2012-12-14 13:29           ` Anthony Liguori [this message]
2012-12-14 13:46             ` Paolo Bonzini
2012-12-13 21:15 ` Anthony Liguori
2013-01-15  3:45 ` Cole Robinson
2013-01-15 16:29   ` Paolo Bonzini
2013-01-16 23:17     ` Cole Robinson
2013-01-18 12:12       ` Marcelo Tosatti
2013-01-18 17:04         ` Cole Robinson
2013-01-18 17:34           ` Paolo Bonzini
2013-01-18 20:09             ` Marcelo Tosatti
2013-01-19 14:17               ` Paolo Bonzini
2013-01-18 19:50           ` Marcelo Tosatti

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=87k3skhidk.fsf@codemonkey.ws \
    --to=aliguori@us.ibm.com \
    --cc=crobinso@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).