From: Avi Kivity <avi@redhat.com>
To: Martin Wawro <wawro@digitalmedics.de>
Cc: kvm@vger.kernel.org, "libvir-list@redhat.com" <libvir-list@redhat.com>
Subject: Re: [User question] Huge buffer size on KVM host
Date: Thu, 16 Aug 2012 17:57:39 +0300 [thread overview]
Message-ID: <502D0A63.1070608@redhat.com> (raw)
In-Reply-To: <D26D13FF-4600-4428-9EFE-F9B322E0B8C1@digitalmedics.de>
On 08/16/2012 05:54 PM, Martin Wawro wrote:
>
> On Aug 15, 2012, at 2:57 PM, Avi Kivity wrote:
>
>>>
>>> We are using logical volumes and the cache is set to 'none'.
>>
>> Strange, that should work without any buffering.
>>
>> What the contents of
>>
>> /sys/block/sda/queue/hw_sector_size
>>
>> and
>>
>> /sys/block/sda/queue/logical_block_size
>>
>> ?
>>
>
> Hi Avi,
>
> It seems that the kernel on that particular machine is too old, those entries are
> not featured. We checked on a comparable setup with a newer kernel and both entries
> were set to 512.
>
> We also did have a third more thorough look on the caching. It turns out that the
> virt-manager does not seem to honor the caching adjusted in the GUI correctly.
> We disabled caching on all virtual devices for this particular VM and checking
> with "ps -fxal" revealed, that only one of those devices (and a rather small one too)
> had this set. We corrected this in the XML file directly and the buffer size
> currently resides at around 1.8 GB after rebooting the VM (the only virtio device
> not having the cache=none option set is now the (non-mounted) cdrom).
>
cc += libvirt-list
Is there a reason that cdroms don't get cache=none?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-08-16 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 8:06 [User question] Huge buffer size on KVM host Martin Wawro
2012-08-15 11:30 ` Avi Kivity
2012-08-15 12:05 ` Martin Wawro
2012-08-15 12:57 ` Avi Kivity
2012-08-16 14:54 ` Martin Wawro
2012-08-16 14:57 ` Avi Kivity [this message]
2012-09-10 9:22 ` Martin Wawro
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=502D0A63.1070608@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@redhat.com \
--cc=wawro@digitalmedics.de \
/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).