From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Czbqa-0006Mk-CF for qemu-devel@nongnu.org; Fri, 11 Feb 2005 09:32:40 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CzbqY-0006M4-Ig for qemu-devel@nongnu.org; Fri, 11 Feb 2005 09:32:39 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CzbqY-0006M1-FZ for qemu-devel@nongnu.org; Fri, 11 Feb 2005 09:32:38 -0500 Received: from [64.233.184.201] (helo=wproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CzbdH-0007Xa-Bd for qemu-devel@nongnu.org; Fri, 11 Feb 2005 09:18:55 -0500 Received: by wproxy.gmail.com with SMTP id 69so1043117wri for ; Fri, 11 Feb 2005 06:18:53 -0800 (PST) Message-ID: Date: Fri, 11 Feb 2005 09:18:53 -0500 From: Joe Bogner Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] image size - OS reports 720mb, but image file is 2.3 gig Reply-To: Joe Bogner , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hello, I'm trying to create an win2k image that is as small as possible. I'd like to be able to copy the image back and forth between machines so that I have a complete win2k development image. According to win2k, the size is about 720mb. Originally win2k was reporting the size to be about 1.2gig, but I was able to reduce it through NTFS compression. Here's the dilemna. The physical image file is 2.3gig. I've run a qemu-img convert -f qcow -O qcow , which took the original 4.5 gig image down to 2.3 gig. With qemu-img compression, I was able to get it down to 1.7gig. Why is there such a large discrepency between what win2k reports and the physical image file on disk? Is there anything else I can do to reduce it, aside from compressing the physical image file? 1.7 gig is still quite a bit to be shuffling around between machines. Thanks, Joe