From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: Chris Wright <chrisw@redhat.com>, kvm-devel <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: KVM call agenda for Jan 11
Date: Mon, 10 Jan 2011 14:32:40 +0100 [thread overview]
Message-ID: <m3lj2sevev.fsf@trasno.org> (raw)
In-Reply-To: <m3ipxxezqd.fsf@trasno.org> (Juan Quintela's message of "Mon, 10 Jan 2011 12:59:22 +0100")
Juan Quintela <quintela@redhat.com> wrote:
> Juan Quintela <quintela@redhat.com> wrote:
>
> Now sent it to the right kvm list. Sorry for the second sent.
>
>> Please send any agenda items you are interested in covering.
>>
>> - KVM Forum 2011 (Jes).
>>
>> thanks, Juan.
- migration and block devices: a mess.
* patches I sent last week: only work for root (for some definition of
work)
* qemu is used as non-root user.
* forcing to have cache=none solves the issue
* we use migrate not only for live migration, but also for
save/resume.
At this point only 4 ideas remaining:
* -incoming-this-is-a-live-migration
(or the opposite -incoming-this-is-a-restore-operation)
* just forche cache=none if you want to call migration code.
* let management app to do the right thing (it can check for cache=none)
* do nothing and pray?
Later, Juan.
next prev parent reply other threads:[~2011-01-10 13:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 10:17 [Qemu-devel] KVM call agenda for Jan 11 Juan Quintela
2011-01-10 11:59 ` [Qemu-devel] " Juan Quintela
2011-01-10 13:05 ` Jes Sorensen
2011-01-10 13:45 ` Stefan Hajnoczi
2011-01-10 16:46 ` Peter Maydell
2011-01-10 13:32 ` Juan Quintela [this message]
2011-01-11 11:13 ` Kevin Wolf
2011-01-11 13:41 ` Juan Quintela
2011-01-11 14:43 ` Anthony Liguori
2011-01-13 16:12 ` Avi Kivity
2011-01-10 16:02 ` [Qemu-devel] " 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=m3lj2sevev.fsf@trasno.org \
--to=quintela@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 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).