From: Avi Kivity <avi@redhat.com>
To: Andrew Holway <a.holway@syseleven.de>
Cc: kvm@vger.kernel.org
Subject: Re: NFSoRDMA not working with KVM when cache disabled
Date: Mon, 03 Sep 2012 15:08:09 +0300 [thread overview]
Message-ID: <50449DA9.3010108@redhat.com> (raw)
In-Reply-To: <A5BE949C-2926-459E-A789-60DA369C7152@syseleven.de>
On 09/03/2012 02:57 PM, Andrew Holway wrote:
>>
>> and report which (if any) of the output files (x1, x2, y1, y2) are
>> corrupted, by comparing them against the original. This will tell us
>> whether O_DIRECT is broken, or 512 byte block size, or neither.
>>
>
>
> Looks like you were directly on the money there. 512, 1K and 2K O_DIRECT looks broken.
It was hardly unexpected. Please report the problem to the nfs/rdma
list (and keep kvm@ copied, nfs/rdma is fairly relevant to kvm).
You can work around it by exposing a 4k logical block size to the guest
(logical_block_size=4k). Note not all guests support this.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-09-03 12:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-2699@BrightComputing>
2012-08-31 17:05 ` NFSoRDMA not working with KVM when cache disabled Andrew Holway
2012-08-31 17:32 ` Andrew Holway
[not found] ` <rt-3.8.7-5952-1346432760-1448.2699-4-0@BrightComputing>
[not found] ` <CALiqupEThihQAj1mf43f2pNztXaFoxojYkTcrMbFkc1G=+vEAA@mail.gmail.com>
2012-08-31 21:20 ` [Bright Cluster Manager Support #2699] " Martijn de Vries
[not found] ` <056E76E7-5AAB-4622-A245-62725340D504@syseleven.de>
2012-09-01 11:51 ` Andrew Holway
[not found] ` <rt-3.8.7-5947-1346500280-1759.2699-16-0@BrightComputing>
[not found] ` <CALiqupEgJ2=2Mbg1trvQVEbgUProJj87dPzJOOG6XR2GwWZf5Q@mail.gmail.com>
2012-09-02 20:46 ` Martijn de Vries
[not found] ` <rt-3.8.7-19587-1346618782-561.2699-6-0@BrightComputing>
2012-09-03 13:21 ` Pawan Jaitly
2012-09-03 9:12 ` Stefan Hajnoczi
2012-09-03 9:58 ` Avi Kivity
2012-09-03 11:57 ` Andrew Holway
2012-09-03 12:08 ` Avi Kivity [this message]
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=50449DA9.3010108@redhat.com \
--to=avi@redhat.com \
--cc=a.holway@syseleven.de \
--cc=kvm@vger.kernel.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.