[Spice-devel] Image size of the instance VM (qcow2 format)
charles.tsai at cloudena.com
Mon May 21 00:55:33 PDT 2012
No, our running VM does nothing and it simply just stays in idle. That is the reason we do not know why the image size of the instance VM keeps growing. I posted this issue to qemu-devel for helpful opinions.
From: Alon Levy [mailto:alevy at redhat.com]
Sent: Monday, May 21, 2012 5:32 PM
Cc: Yonit Halperin; spice-devel at freedesktop.org; Jonah.Wu-吳君勉-研究發展部
Subject: Re: Image size of the instance VM (qcow2 format)
On Mon, May 21, 2012 at 06:01:05AM +0000, Charles.Tsai-蔡清海-研究發展部 wrote:
> Hi Alon,
> Do you have any idea about this issue? We doubt this issue is caused by the Windows swap file(virtual memory) that Windows OS pages the memory contents to it during the run-time. However, we did disable the swap file setting from Windows. The image size of the instance VM still keeps growing. Can you tell us what area we need to study so as to attack this issue if you know it? Thanks.
I assume the image is getting bigger because the guest is doing writes
- try checking what is writing in the guest. You could also ask on
qemu-devel which is more appropriate for general qemu questions.
> -----Original Message-----
> From: Charles.Tsai-蔡清海-研究發展部
> Sent: Thursday, May 17, 2012 3:17 PM
> To: 'Alon Levy'; Yonit Halperin
> Cc: spice-devel at freedesktop.org; Jonah.Wu-吳君勉-研究發展部
> Subject: Image size of the instance VM (qcow2 format)
> Hi Alon,
> We created a qcow2 based-image for a VM whose size is bigger when it is created. When a VM is launched, it is a instance VM image which refers to the based-image. Initially, the image size of instance VM is smaller than that of the based-mage. But we found the image size of the instance VM kept growing, when a VM ran in idle state. The image size of instance VM is supposed to remain in a smaller size than the based-image. How come it keeps growing in size? Is it a normal issue?
More information about the Spice-devel