From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CGgE6-0001mu-7L for qemu-devel@nongnu.org; Sun, 10 Oct 2004 12:07:14 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CGgE5-0001mG-Mb for qemu-devel@nongnu.org; Sun, 10 Oct 2004 12:07:13 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CGgE5-0001m5-HU for qemu-devel@nongnu.org; Sun, 10 Oct 2004 12:07:13 -0400 Received: from [80.91.229.2] (helo=main.gmane.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CGg6e-0004IQ-9q for qemu-devel@nongnu.org; Sun, 10 Oct 2004 11:59:32 -0400 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CGg6d-0003oS-00 for ; Sun, 10 Oct 2004 17:59:31 +0200 Received: from 203.7.227.188 ([203.7.227.188]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 10 Oct 2004 17:59:31 +0200 Received: from wildfire by 203.7.227.188 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 10 Oct 2004 17:59:31 +0200 From: Anand Kumria Date: Mon, 11 Oct 2004 02:05:46 +1000 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: news Subject: [Qemu-devel] Re: change boot device in monitor 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 On Sun, 10 Oct 2004 16:26:43 +0200, Johannes Schindelin wrote: > Hi, > > On Sun, 10 Oct 2004, Anand Kumria wrote: > >> Attached is a patch which allows you to change the boot device in the >> monitor. The change won't take affect until the next 'system_reset' but >> I've found it useful as I can specify a floppy, hard disk and cdrom and >> switch between booting them without exiting. > > I like this feature! (Also your "info version"). Thanks - I hope Fabrice does also. >> As I'm now going to be working on a way to modify the memory amount within >> the monitor. The struct_vm would basically be the what is used for >> savevm/loadvm. Thoughts? > > Well, I prefer to specify the memory on the command line. Of course, if > you loadvm with a different size, this does not work AFAIK, but IMHO it > does not make sense to support virtual hot-plugging of memory ;-) The reason I want to be able to do this is to support testing installer disks and operating systems with varying amounts of memory. Since qemu can be forked and have the monitor available to another process as stdin/stdout it means I can setup regressions test for memory points. Cheers, Anand