From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DxlBT-0004YE-39 for qemu-devel@nongnu.org; Wed, 27 Jul 2005 08:38:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DxlBI-0004T3-6N for qemu-devel@nongnu.org; Wed, 27 Jul 2005 08:38:40 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DxlBG-0004Pp-Qv for qemu-devel@nongnu.org; Wed, 27 Jul 2005 08:38:38 -0400 Received: from [64.233.184.205] (helo=wproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DxlH3-0004fF-1S for qemu-devel@nongnu.org; Wed, 27 Jul 2005 08:44:37 -0400 Received: by wproxy.gmail.com with SMTP id i20so154566wra for ; Wed, 27 Jul 2005 05:33:15 -0700 (PDT) Message-ID: <23bcb87005072705335a4df4f2@mail.gmail.com> Date: Wed, 27 Jul 2005 08:33:15 -0400 From: Doctor Bill Subject: Re: [Qemu-devel] Problem installing WIndows In-Reply-To: <42E77673.2030006@wayforth.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <42E62AA2.5090702@wayforth.co.uk> <41e41e7a05072606263863044a@mail.gmail.com> <42E63D5B.80504@wayforth.co.uk> <42E75A9B.3060503@wayforth.co.uk> <46d6db6605072704031b63cef7@mail.gmail.com> <42E77673.2030006@wayforth.co.uk> Reply-To: Doctor Bill , 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 In your original message, you mentioned setup had finished. One thing I can recommend trying on your second attempt is to make sure you create more than one user account when prompted. XP Pro seems to behave differently depending on if there is one or more than one accounts. I actually had the exact same problem on a real PC. I did not have time to try and resolve thi problem, so I ended up installing XP Home edition on that particular computer. Bill On 7/27/05, Antony Gelberg wrote: > Christian MICHON wrote: > > 1) have you tried using qemu-img instead of dd ? > > (I usually use the qcow format for windows guests. 2G should be ok. > > "qemu-img create -f qcow hd.img 2G" ) >=20 > I'm trying that now. >=20 > > 2) you do not mention bios path, memory of vm and boot sequence. > > I suggest you add at least the "-boot d". By default, 128M will be us= ed > > for the vm (sufficient for XP). Make sure your debian box has plenty = of > > RAM (512M is good). >=20 > I mentioned the command line in my original post to the thread. >=20 > qemu -boot c -cdrom /dev/cdrom -hda hd.img >=20 > So it's using 128MB, and my box does indeed have 512MB. >=20 > > 3) is your qemu optimized? and which version of gcc is used? >=20 > I have had a look in the Debian config. The only non-standard configure > option is --enable-slirp. Debian compiles qemu with -Wall -O2 -g > -fno-strict-aliasing. Not sure what gcc was used, but probably 3.3. >=20 > Antony >=20 >=20 > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel >