From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DvrvB-0006vH-3x for qemu-devel@nongnu.org; Fri, 22 Jul 2005 03:26:13 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Dvrv7-0006tr-Bw for qemu-devel@nongnu.org; Fri, 22 Jul 2005 03:26:11 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dvrv4-0006nX-Nv for qemu-devel@nongnu.org; Fri, 22 Jul 2005 03:26:06 -0400 Received: from [207.226.20.171] (helo=arinda0.dvdencored.com) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1Dvrrt-0002Ms-Ar for qemu-devel@nongnu.org; Fri, 22 Jul 2005 03:22:49 -0400 From: TSUME Date: Fri, 22 Jul 2005 07:11:41 -0800 Message-Id: <1122045101.32759.2.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] QEMU disk geometry sizes Reply-To: tsume@tsumelabs.com, 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 everybody! I'm curious why qemu works fine on disk sizes of about 20G, but when I create 100G sized images it gives a wrong number in BIOS. When I create a 400G image, the boot screen says my size is.. -11423..MB When I get freebsd installed, it sees my drive as 400G at first, until I fsck at boot. Then it changes the drive geometry to 11 TB(I wish) Is this a bug or does qemu have limitation? Thank you in advance, TSUME