All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "H. Peter Anvin" <hpa@linux.intel.com>
Cc: qemu-devel@nongnu.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [Qemu-devel] [PATCH] debugcon: support for debugging consoles (e.g.	Bochs port 0xe9)
Date: Wed, 25 Nov 2009 23:21:18 +0100	[thread overview]
Message-ID: <4B0DADDE.1080703@redhat.com> (raw)
In-Reply-To: <4B0D70DC.8020605@linux.intel.com>

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

  reply	other threads:[~2009-11-25 22:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-20 21:33 [Qemu-devel] [PATCH] debugcon: support for debugging consoles (e.g. Bochs port 0xe9) H. Peter Anvin
2009-11-22 17:16 ` [Qemu-devel] Re: [PATCH] debugcon: support for debugging consoles (e.g.Bochs " Sebastian Herbszt
2009-11-23  3:13   ` H. Peter Anvin
2009-11-23 10:52 ` [Qemu-devel] [PATCH] debugcon: support for debugging consoles (e.g. Bochs " Gerd Hoffmann
2009-11-23 20:11   ` H. Peter Anvin
2009-11-24 23:05     ` H. Peter Anvin
2009-11-25  7:33       ` Alexander Graf
2009-11-25 12:46       ` Gerd Hoffmann
2009-11-25 18:01         ` H. Peter Anvin
2009-11-25 22:21           ` Gerd Hoffmann [this message]
2009-11-25 22:26             ` H. Peter Anvin
2009-11-25 22:31               ` H. Peter Anvin
2009-11-25 22:54                 ` Gerd Hoffmann
2009-11-26  9:56                   ` Markus Armbruster
2009-11-26 13:18                   ` [Qemu-devel] " Paolo Bonzini
2009-11-25 22:53 ` [Qemu-devel] " H. Peter Anvin
2009-11-26  7:43   ` [Qemu-devel] " Jan Kiszka
  -- strict thread matches above, loose matches on Subject: below --
2009-12-03  3:11 [Qemu-devel] " H. Peter Anvin
2009-12-03  4:02 ` malc
2009-12-03  5:04 H. Peter Anvin
     [not found] <1262123496-12007-1-git-send-email-hpa@linux.intel.com>
     [not found] ` <20091230164946.GA9858@morn.localdomain>
2010-01-02  3:01   ` H. Peter Anvin
2010-01-02  3:02   ` H. Peter Anvin
2010-01-02 17:53     ` Kevin O'Connor
2010-01-02 18:56       ` H. Peter Anvin
2010-01-03  2:13         ` François Revol
2010-01-08 16:36 ` Anthony Liguori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B0DADDE.1080703@redhat.com \
    --to=kraxel@redhat.com \
    --cc=hpa@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.