On Tue, Sep 27, 2011 at 04:41:33PM +0800, Emmanuel Noobadmin wrote: > On 9/27/11, Robin Lee Powell <rlpowell@xxxxxxxxxxxxxxxxxx> wrote: > > On Mon, Sep 26, 2011 at 04:15:37PM +0800, Emmanuel Noobadmin > > wrote: > >> It's unrelated to what you're actually using as the disks, > >> whether file or block devices like LVs. I think it just makes > >> KVM tell the host not to cache I/O done on the storage device. > > > > Wait, hold on, I think I had it backwards. > > > > It tells the *host* to not cache the device in question, or the > > *VMs* to not cache the device in question? > > I'm fairly certain it tells the qemu not to cache the device in > question. If you don't want the guest to cache their i/o, then the > guest OS should be configured if it allows that. Although I'm not > sure if it's possible to disable disk buffering/caching system > wide in Linux. OK, great, thanks. Now if I could just figure out how to stop the host from swapping out much of the VMs' qemu-kvm procs when it has almost a GiB of RAM left. -_- swappiness 0 doesn't seem to help there. -Robin -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
