Qemu can work with vmdk but some features of vmdk aren’t used. So I can understand vmdk is slow. Best practice: 1.
Use LVM is you can (harder to transfer/copy images) 2.
Alternative raw-file for speed (but you lose functionalities) 3.
Qcow for functionality in a file image (snapshots, compression,…) I think other formats are supported for compatibility reasons in testing and migration scenarios, not for production environments. Van: libvirt-users-bounces@xxxxxxxxxx [mailto:libvirt-users-bounces@xxxxxxxxxx]
Namens John Obaterspok 2016-02-18 15:15 GMT+01:00 Martin Kletzander <mkletzan@xxxxxxxxxx>: On Thu, Feb 18, 2016 at 12:59:52PM +0100, John Obaterspok wrote: 2016-02-18 11:25 GMT+01:00 Martin Kletzander <mkletzan@xxxxxxxxxx>: On Thu, Feb 18, 2016 at 10:41:42AM +0100, John Obaterspok wrote: 2016-02-18 10:13 GMT+01:00 Martin Kletzander <mkletzan@xxxxxxxxxx>:
Not on the host AFAIK. The io is 100% in windows task manager performing less than 1MB/s other processes and devices doing? {,a,h}top should do for the initial runs, just to see if the block layer atop seems to indicate that sdd is busy? And it doesn't do that in any other process on the host? It looks like Hi, I changed from vmdk to raw and the Write performance went from 1.6 MB/s to ~100 MB/s Is vmdk write performance so bad? Result: -- john |
_______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users