Hi, This may be completely unrelated to AUFS but I thought I'd mention it. If I create a new qcow2 image based of a read-only master then for some reason midway through a WinXP boot the master image triggers AUFS to do a copyup. I would have expected that the large read-only image is never written to and hence would never trigger a copyup. The following command creates a new COW image using the "master" as a read-only source:
qemu-img create -b /var/lib/libvirt/images/winxp-master.qcow2 -f qcow2 /var/lib/libvirt/images/winxp.qcow2 I would like to avoid having to copyup the 5Gig winxp-master.qcow2 file if it is never getting written to. Like I said AUFS may be doing the right thing and it is Qemu that makes a write call to the master image. Regards, Daire ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
