All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: quintela@redhat.com
Cc: qemu-devel@nongnu.org, Chris Wright <chrisw@redhat.com>,
	kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Re: KVM call agenda for Jan 11
Date: Tue, 11 Jan 2011 12:13:17 +0100	[thread overview]
Message-ID: <4D2C3B4D.2090709@redhat.com> (raw)
In-Reply-To: <m3lj2sevev.fsf@trasno.org>

Am 10.01.2011 14:32, schrieb Juan Quintela:
> 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

I need to have a look at the specific problem, but it's hard to imagine
that cache=none fixes anything reliably.

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: Kevin Wolf <kwolf@redhat.com>
To: quintela@redhat.com
Cc: Chris Wright <chrisw@redhat.com>,
	qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Re: KVM call agenda for Jan 11
Date: Tue, 11 Jan 2011 12:13:17 +0100	[thread overview]
Message-ID: <4D2C3B4D.2090709@redhat.com> (raw)
In-Reply-To: <m3lj2sevev.fsf@trasno.org>

Am 10.01.2011 14:32, schrieb Juan Quintela:
> 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

I need to have a look at the specific problem, but it's hard to imagine
that cache=none fixes anything reliably.

Kevin

  reply	other threads:[~2011-01-11 11:11 UTC|newest]

Thread overview: 19+ 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 ` Juan Quintela
2011-01-10 11:59   ` [Qemu-devel] " Juan Quintela
2011-01-10 13:05   ` Jes Sorensen
2011-01-10 13:05     ` Jes Sorensen
2011-01-10 13:45     ` Stefan Hajnoczi
2011-01-10 13:45       ` Stefan Hajnoczi
2011-01-10 16:46       ` Peter Maydell
2011-01-10 16:46         ` Peter Maydell
2011-01-10 13:32   ` Juan Quintela
2011-01-10 13:32     ` [Qemu-devel] " Juan Quintela
2011-01-11 11:13     ` Kevin Wolf [this message]
2011-01-11 11:13       ` Kevin Wolf
2011-01-11 13:41       ` Juan Quintela
2011-01-11 13:41         ` [Qemu-devel] " Juan Quintela
2011-01-11 14:43         ` Anthony Liguori
2011-01-13 16:12           ` Avi Kivity
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=4D2C3B4D.2090709@redhat.com \
    --to=kwolf@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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.