public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Avi Kivity <avi@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: Setting disk parameters in a VM
Date: Sun, 15 Mar 2009 16:42:50 -0400	[thread overview]
Message-ID: <49BD684A.2000202@tmr.com> (raw)
In-Reply-To: <49BCDB2C.60407@redhat.com>

Avi Kivity wrote:
> Bill Davidsen wrote:
>> Based on a discussion in another list on ioschedulers, I added a few 
>> lines to my rc.local to set the scheduler to "noop" for disks with 
>> model QEMU*, to the scheduling in the VM will not be computing with 
>> the scheduling in the host.
>>
>> I wonder if the same thinking applies to the "rotational" feature 
>> added to /sys/block in 2.6.29, intended for SSD but probably 
>> appropriate for virtual and nbd devices as well.
>
> A virtual disk backed by a rotational physical disk probably should be 
> marked rotational, at least with cache=off.
>
The question was more regarding virtual drives backed by files, but even 
so I would think the bad case would be to let the host decide what 
methods should be used, rather than the VM, which is more likely to do 
things wrong based on incomplete information.

Feel free to clarify if you think there's a case where the VM and the 
host should both be doing caching and scheduling. The only one I can 
imagine is if a USB port is passed to the VM and it has a storage device 
attached. That's not really a common configuration, I would guess.

-- 
Bill Davidsen <davidsen@tmr.com>
  "Woe unto the statesman who makes war without a reason that will still
  be valid when the war is over..." Otto von Bismark 



      reply	other threads:[~2009-03-15 20:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-13 16:58 Setting disk parameters in a VM Bill Davidsen
2009-03-15 10:40 ` Avi Kivity
2009-03-15 20:42   ` Bill Davidsen [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=49BD684A.2000202@tmr.com \
    --to=davidsen@tmr.com \
    --cc=avi@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox