From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: "Charles.Tsai-蔡清海-研究發展部" <charles.tsai@cloudena.com>
Cc: "Jonah.Wu-吳君勉-研究發展部" <jonah.wu@cloudena.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] The image size of instance VM keeps growing
Date: Wed, 23 May 2012 09:17:37 -0500 [thread overview]
Message-ID: <20120523141737.GA5615@illuin> (raw)
In-Reply-To: <B98D01AC6D58544886DC44AD0A4A1F6504B83804@MBX02.systex.tw>
On Mon, May 21, 2012 at 07:47:49AM +0000, Charles.Tsai-蔡清海-研究發展部 wrote:
>
>
> We created a qcow2 based-image for a VM whose size is big 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. We doubted this issue is caused by the Windows swap file(virtual memory) that Windows OS pages the memory contents to it during the run-time. We did disable the swap file setting from Windows but the image size of the instance VM still kept growing.
>
>
>
> 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.
>
Do you have automatic indexing turned on in the guest? Not sure of the
specifics WRT to NTFS, but indexing might be causing metadata updates
(particularly last access time) that might be causing a COW on a lot of
blocks in a relatively short amount of time.
prev parent reply other threads:[~2012-05-23 14:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 7:47 [Qemu-devel] The image size of instance VM keeps growing Charles.Tsai-蔡清海-研究發展部
2012-05-21 8:44 ` Stefan Hajnoczi
2012-05-21 9:08 ` Charles.Tsai-蔡清海-研究發展部
2012-05-21 13:24 ` Stefan Hajnoczi
2012-05-22 0:58 ` Charles.Tsai-蔡清海-研究發展部
2012-05-23 10:47 ` Charles.Tsai-蔡清海-研究發展部
2012-05-23 10:58 ` nicolas prochazka
2012-05-23 12:57 ` Stefan Hajnoczi
2012-05-23 13:11 ` Michael Tokarev
2012-05-24 2:35 ` Charles.Tsai-蔡清海-研究發展部
2012-05-25 11:28 ` Stefan Hajnoczi
2012-05-24 2:33 ` Charles.Tsai-蔡清海-研究發展部
2012-05-24 10:40 ` Charles.Tsai-蔡清海-研究發展部
2012-05-25 11:36 ` Stefan Hajnoczi
2012-05-25 9:20 ` Charles.Tsai-蔡清海-研究發展部
2012-05-25 11:45 ` Stefan Hajnoczi
2012-05-25 2:42 ` [Qemu-devel] Tracing message for mu Charles.Tsai-蔡清海-研究發展部
2012-05-25 8:13 ` Stefan Hajnoczi
2012-05-26 6:50 ` Charles.Tsai-蔡清海-研究發展部
2012-05-28 12:30 ` Stefan Hajnoczi
2012-05-23 14:17 ` Michael Roth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120523141737.GA5615@illuin \
--to=mdroth@linux.vnet.ibm.com \
--cc=charles.tsai@cloudena.com \
--cc=jonah.wu@cloudena.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).