From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KfySt-0008Sl-Hn for qemu-devel@nongnu.org; Wed, 17 Sep 2008 10:57:11 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KfySq-0008QO-UN for qemu-devel@nongnu.org; Wed, 17 Sep 2008 10:57:10 -0400 Received: from [199.232.76.173] (port=45507 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KfySq-0008Py-NJ for qemu-devel@nongnu.org; Wed, 17 Sep 2008 10:57:08 -0400 Received: from mail2.shareable.org ([80.68.89.115]:35384) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KfySq-0007zj-Ae for qemu-devel@nongnu.org; Wed, 17 Sep 2008 10:57:08 -0400 Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from ) id 1KfySm-0006nY-KC for qemu-devel@nongnu.org; Wed, 17 Sep 2008 15:57:04 +0100 Date: Wed, 17 Sep 2008 15:57:04 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] Problem with `change' monitor command Message-ID: <20080917145704.GC22613@shareable.org> References: <48D0EE05.574440C9@bttr-software.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48D0EE05.574440C9@bttr-software.de> 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 Robert Riebisch wrote: > I'm using QEMU 0.9.1 and SVN on Win32 to emulate an x86 PC environment. > > With `change floppy0 foo.img' I'm able to use another floppy image on > the fly, but this will only work, if the new floppy image is of the same > size as the old one. Switching from, e.g., 1.44M to 2.88M is not > recognized by the guest OS. Even rebooting the VM doesn't help, because > CMOS value 0x10 ("Floppy Drive Type") won't be adjusted. > (http://www.brl.ntt.co.jp/people/takehiko/interrupt/CMOS.LST.txt) I agree that CMOS should be adjusted, but only on the next reboot. Changing floppy _drive_ type is not possible until the next reboot, and it might confuse the OS to try it: you can't replace a floppy drive on a real PC while the OS is running either. It might be possible to force the drive type to 2.88M at boot time even with a 1.44 image, though. I think those drives can read smaller capacity disks, and the OS should be fine with that. -- Jamie