You're not answering right to this topic, then you keep answering but what for ? Why you're so angry ? Get back down to earth mate, you're not serving OMV.
You forgot we were not just the two of us ? By far, you're the last person my posts were trying to reach, I barely am answering to you. And thanks again for explaining everything so clearly to me." "the feel between passthru and image is not detectable (in most cases). There's a reason to describe why passing on a RAW partition is faster than mounting a virtual disk, it's called AR-GU-MENTS, it helps people easily understand what you argue for, just saying. I'm sorry to see you took something bad, I do work with "thousands" of VM also, for a french hosting company, do I have to play that game too ? In the real world, the feel between passthru and image is not detectable (in most cases).Īnd thanks again for explaining everything so clearly to me. I work with thousands of VMs all day long and have many at home.
To answer OP, passing a raw partition to a VM is better (performance wise) than having a "disk image" mounted, that is relative to what virtualisation technology you use, but I can assume a good 99% (xen kvm vb and esxi)Įdit : this sub forum is called "configuration" and he is asking on how to make a debian/kodi host and an OMV VM cohabitate, and if OMV how to pass / how OMV would see the disks or virtual drives to achieve Raid inside a VM I really love VirtualBox and VirtIO but there, in fact, is a "loss", that's why the default config (of VB's VMs) cheats a little on how to honor fsyncs (you can bench a VM and its' host, and have better perf on the VM) but then, enjoy the halving on perf if you do a lot of sequencial reads, it's a matter of compromise Passing an entire drive through to a VM in virtualbox is a pain in the ass and I really haven't seen performance gains from it. Most of those questions aren't OMV questions if OMV is not the host.
I was assuming OMV was the host and it doesn't work if OMV is the host.