From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NDQEr-0002Pw-Gf for qemu-devel@nongnu.org; Wed, 25 Nov 2009 17:21:29 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NDQEm-0002MZ-AM for qemu-devel@nongnu.org; Wed, 25 Nov 2009 17:21:28 -0500 Received: from [199.232.76.173] (port=40538 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NDQEm-0002MF-3I for qemu-devel@nongnu.org; Wed, 25 Nov 2009 17:21:24 -0500 Received: from mx1.redhat.com ([209.132.183.28]:39924) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NDQEl-0007wM-MQ for qemu-devel@nongnu.org; Wed, 25 Nov 2009 17:21:23 -0500 Message-ID: <4B0DADDE.1080703@redhat.com> Date: Wed, 25 Nov 2009 23:21:18 +0100 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] debugcon: support for debugging consoles (e.g. Bochs port 0xe9) References: <1258752795-15434-1-git-send-email-hpa@linux.intel.com> <4B0A6973.4010303@redhat.com> <4B0AEC8A.1020905@zytor.com> <4B0C66B0.5090805@zytor.com> <4B0D2713.60001@redhat.com> <4B0D70DC.8020605@linux.intel.com> In-Reply-To: <4B0D70DC.8020605@linux.intel.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "H. Peter Anvin" Cc: qemu-devel@nongnu.org, "H. Peter Anvin" On 11/25/09 19:01, H. Peter Anvin wrote: > Gerd Hoffmann wrote: >> >> You can stick it into a config file[1] like this: >> >> [chardev "debuglog"] >> backend = "file" >> path = "/path/to/debug.log" >> >> [device] >> driver = "isa-debugcon" >> chardev = "debuglog" >> >> Then use "qemu -readconfig $file". >> > > Great... at least in my opinion, one of the things that makes Qemu so > much easier to use than Bochs is that one has a comprehensive (and > comprehensable) command line and don't have to set up a configuration > file for every trivial little thing. It's a good thing for long-living > virtualization instances, but I would be sad if the command line will > end up being neglected. You can happily mixup things as you like. Use pure command line. Use pure config file (well, at least is that the plan, it doesn't fully work yet). Mix cmd line switches and config file. Reading multiple config files works just fine too, so you can split your vm config into multiple parts and enable/disable parts by reading/not reading the file in question ... cheers, Gerd