All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	KVM devel mailing list <kvm@vger.kernel.org>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: KVM call agenda for 2012-11-12
Date: Tue, 13 Nov 2012 15:48:55 +0100	[thread overview]
Message-ID: <87a9uld0dk.fsf@trasno.org> (raw)
In-Reply-To: <87wqxptwih.fsf@codemonkey.ws> (Anthony Liguori's message of "Tue, 13 Nov 2012 08:20:22 -0600")

Anthony Liguori <anthony@codemonkey.ws> wrote:
> Marcelo Tosatti <mtosatti@redhat.com> writes:
>
>> On Mon, Nov 12, 2012 at 01:58:38PM +0100, Juan Quintela wrote:
>>> 
>>> Hi
>>> 
>>> Please send in any agenda topics you are interested in.
>>> 
>>> Later, Juan.
>>
>> It would be good to have a status report on qemu-kvm compatibility
>> (the remaining TODO items are with Anthony). They are:
>>
>> - qemu-kvm 1.2 machine type.
>> - default accelerator being KVM.
>>
>> Note migration will remain broken due to 
>>
>> https://patchwork.kernel.org/patch/1674521/
>>
>> BTW, this can be via email, if preferred (i cannot attend the call).
>
> Let's cancel the call and I'll spend the hour writing up the patches and
> sending them out.

Same for Eduardo requsets?

Later, Juan.

  reply	other threads:[~2012-11-13 14:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12 12:58 KVM call agenda for 2012-11-12 Juan Quintela
2012-11-12 22:31 ` Marcelo Tosatti
2012-11-13 14:20   ` Anthony Liguori
2012-11-13 14:48     ` Juan Quintela [this message]
2012-11-13 15:05       ` [Qemu-devel] " Eduardo Habkost
2012-11-13 12:29 ` Eduardo Habkost
2012-11-13 14:29   ` Andreas Färber
2012-11-13 15:17     ` Eduardo Habkost
2012-11-13 12:43 ` Zhi Yong Wu

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=87a9uld0dk.fsf@trasno.org \
    --to=quintela@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@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 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.