qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] debugcon: support for debugging consoles (e.g.


From: H. Peter Anvin
Subject: Re: [Qemu-devel] [PATCH] debugcon: support for debugging consoles (e.g. Bochs port 0xe9)
Date: Wed, 25 Nov 2009 14:26:21 -0800
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4pre) Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Thunderbird/3.0b4

On 11/25/2009 02:21 PM, Gerd Hoffmann wrote:
> 
> 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 ...
> 

Right, of course; I didn't mean to imply that your config file would
make the command line be unavailable, nor did I mean to imply that it
isn't useful (quite on the contrary.)

What I meant was that the presence of config file does not avoid the
user-hostility of options like "-chardev stdio,id=debug -device
isa-debugcon,chardev=debug" ... for a command line user, the situation
is still the same, and when using Qemu for debugging and testing, this
is one case when you would be likely to run into the command line.

As such, I think there is still a place for the simple command line
options like "-hda", "-serial" and my proposed "-debugcon", in addition
to the full-featured connect-anything options and configuration files.
That's all.

        -hpa




reply via email to

[Prev in Thread] Current Thread [Next in Thread]