Stefan, We can run a tool to see if there is any active I/O or not. Does the image size shrink back if an I/O activity stops? What we found here is that the image size kept growing. If this problem persists, it could eat up the entire disk space.
-----Original Message----- From: Stefan Hajnoczi [mailto:stefa...@gmail.com] Sent: Monday, May 21, 2012 4:44 PM To: Charles.Tsai-蔡清海-研究發展部 Cc: qemu-devel@nongnu.org; Jonah.Wu-吳君勉-研究發展部 Subject: Re: [Qemu-devel] The image size of instance VM keeps growing On Mon, May 21, 2012 at 8:47 AM, Charles.Tsai-蔡清海-研究發展部 <charles.t...@cloudena.com> wrote: > Ideally, the image size of instance VM is supposed to remain in a > smaller size than the based-image. Why does it keep growing in size > which is even bigger than that of based-image? Our VM, in fact, did > nothing during the idle state. The guest is probably issuing I/O. Are there Windows tools you can use to see which process or kernel component is issuing I/O? You can try running qemu-img check <image-file> to ensure that the qcow2 file is consistent. Error messages will be printed if there are leaks or corruptions in the qcow2 file. Stefan
