From: "Aarian P. Aleahmad" <arian.spidey@gmail.com>
To: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] virtio ssd caching
Date: Tue, 6 Sep 2016 12:44:39 +0430 [thread overview]
Message-ID: <CAEbcHeouzS-GAX3AwVZoTSmkuoEorT93xBM0Fo2-ekVSs-AJeA@mail.gmail.com> (raw)
Hi there
I am looking for a solution to cache a VM on a SSD without the guest
knowing about it. We can do it by caching the disk on which the VM's disk
is lcoated with a SSD or we can do it through the hypervisor (i.e. Qemu,
KVM, etc.).
I was thinking about passing an ssd device to the hypervisor as a cache
disk (e.g. passing /dev/sdb to the hypervisor) or making a new virtual disk
image and storing it on a SSD and passing the SSD located vDisk to the
hypervisor as a cache.
Thus, I would like to know whether is it possible or not, and if not, if I
wish to implement such a thing, what should I do and whether is there any
reusable code to do so or not?
Thanks
next reply other threads:[~2016-09-06 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 8:14 Aarian P. Aleahmad [this message]
2016-09-07 19:36 ` [Qemu-devel] virtio ssd caching Stefan Hajnoczi
2016-09-07 19:47 ` Richard W.M. Jones
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=CAEbcHeouzS-GAX3AwVZoTSmkuoEorT93xBM0Fo2-ekVSs-AJeA@mail.gmail.com \
--to=arian.spidey@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).