From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BrfAM-0003wm-QY for qemu-devel@nongnu.org; Mon, 02 Aug 2004 11:55:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BrfAK-0003uN-NU for qemu-devel@nongnu.org; Mon, 02 Aug 2004 11:55:58 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BrfAK-0003tR-LP for qemu-devel@nongnu.org; Mon, 02 Aug 2004 11:55:56 -0400 Received: from [64.233.170.193] (helo=mproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Brf6i-0002M3-HM for qemu-devel@nongnu.org; Mon, 02 Aug 2004 11:52:12 -0400 Received: by mproxy.gmail.com with SMTP id 78so207737rnl for ; Mon, 02 Aug 2004 08:52:11 -0700 (PDT) Message-ID: <76bfb9d204080208521209003e@mail.gmail.com> Date: Mon, 2 Aug 2004 11:52:11 -0400 From: Garth Dahlstrom In-Reply-To: <3328529919214537182@unknownmsgid> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <3328529919214537182@unknownmsgid> Subject: [Qemu-devel] Re: Best way to get 6GB = 3 x 2GB + soft raid? Reply-To: 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 Let me explain how I became confused here... I read Readme-EN.txt bundled with QEMU-Windows-0.6 which says: "6. Notes A hard disk image file is up to 2GB." I took that to mean that QEMU was only capable of open HDD images of up to 2GB in size, so I was thinking that I could do 3x2GB disks and software JBOD/Raid0 them together under a linux guest. However it turns out, as Ronald pointed out, QEMU on Windows can read whatever size image the host OS can muster, meaning in my case (using NTFS) I can create a 6GB disk image file straight up using Cygwin and 'dd of=oe-hda.img bs=1M count=6000 seek=6000' (followed quickly by ctrl-break)... That limitation would appear to apply to FAT based host OS's such as Win9x. QEMU has no trouble with that size guest image file at all and it's easier then trying to build a softRAID on the guest.