[SOLVED] qemu, virtio, difference between viostor and vioscsi
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
qemu, virtio, difference between viostor and vioscsi
Hi,
I'm struggling to find out what is the difference between viostor and vioscsi.
I know that viostor allows me to pass file to be seen as SCSI disk in the guest, but I have no clue what the vioscsi is for.
There are two virtio block devices available. viostor is the driver for virtio_blk, a very basic block device that only supports a small number of scsi commands, but also has a small overhead and very fast. For a simple VM disk it is all you will ever require. the other device is virtio_scsi, with the driver vioscsi, it supports the complete scsi protocol, so you do do things like windows clusters over such devices.
for your particular use case, run both, check which performs best under your specific workloads and choose.
Thanks for the reply, basically that's everything I needed to know.
Does it make sense to try vioscsi (now I'm using viostor), if I have just a simple qemu machine with no "clusters", etc.?
Since viostor is simpler (I guess there's less abstraction, e.g. function calls), I guess this should be my choice.
Or is it only possible to know by trying them both?
There are some additional differences in the way these two devices are implemented, some workloads might turn out to be faster on virtio_scsi than on virtio_blk, so the answer is - try it and choose for yourself
Thanks for the hints. As of now I'm gonna skip the tests.
Basically I'm running Windows 7 to work with some Windows-only applications, but all the files are hosted on the Linux host through Samba, so there shouldn't be any significant I/O when it comes to the virtualized disk.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.