public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Ben Budts <ben-laA516G/SH0TgVtkpCPgWQ@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: qcow2 image growing without reason ?
Date: Sun, 29 Jul 2007 11:09:37 +0300	[thread overview]
Message-ID: <46AC4B41.7050907@qumranet.com> (raw)
In-Reply-To: <20070726130252.GA1913-FwLs51Cl57fY4EFHVxF16w@public.gmane.org>

Ben Budts wrote:
> Hi,
>
> I've been running kvm21 for a long time (just upgraded to kvm-33 with 2.6.22.1)
>
> I have a 60GB qcow2 image, I noticed the image was growing without me installing software on the guest os...(WIN XP)
>
> When I select all my files and take properties (in win xp that is), it says 3.7GB, as expected...
>
> The image is allmost the double though (6.4GB) when i look at the qcow2 image, 
> when taking the properties of the HD in win xp it also indictates 6.4GB.
>
> I've been installing some software, after each install I did a restart, bakupped the image etc...
>
> Any idea's ?
>
>   

If Windows says the disk size is 6.4GB, then the qcow image certainly 
can't be smaller.

Maybe you have a large paging file, or perhaps you need to run chkdsk.


-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

  parent reply	other threads:[~2007-07-29  8:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26 13:02 qcow2 image growing without reason ? Ben Budts
     [not found] ` <20070726130252.GA1913-FwLs51Cl57fY4EFHVxF16w@public.gmane.org>
2007-07-29  8:09   ` Avi Kivity [this message]
2007-07-29 12:14   ` Luca

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=46AC4B41.7050907@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=ben-laA516G/SH0TgVtkpCPgWQ@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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