From: Piavlo <piavka@cs.bgu.ac.il>
To: kvm@vger.kernel.org
Subject: What io scheduler to use inside guest VM?
Date: Sat, 21 Mar 2009 22:53:33 +0200 [thread overview]
Message-ID: <49C553CD.1070800@cs.bgu.ac.il> (raw)
Hi,
I use LVM volumes as guest VM disk.
I'm wondering if setting setting the io scheduler inside linux gest has
any effect (with virtio disk driver and with emulated scsi or ide driver)
And if it has affect what's better choice ? My thoughts is that if
changing the scheduler inside guest has affect - then it's probably
best to use noop scheduler inside the guest
and let the hypervisor linux decide according to it's scheduler.
So what I don't understand is if there are two levels of io scheduling ,
one inside the guest (the redundant one and setting it to noop will
minimize it's affect) and other inside the hypervisor linux?(or just one
level in the hypervisor)
Probably with virtio driver tthere is no io scheduling inside the guest,
but is it so with emulated drivers too?
And also is there any difference in io scheduling if I use image file
instead of LVM?
Thanks a lot
Alex
next reply other threads:[~2009-03-21 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 20:53 Piavlo [this message]
2009-03-22 0:52 ` What io scheduler to use inside guest VM? Bill Davidsen
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=49C553CD.1070800@cs.bgu.ac.il \
--to=piavka@cs.bgu.ac.il \
--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