qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] QemuOpts: config file support.
Date: Fri, 16 Oct 2009 12:16:30 +0200	[thread overview]
Message-ID: <4AD847FE.1000306@redhat.com> (raw)
In-Reply-To: <4AD62006.4080008@codemonkey.ws>

> What I really want to do, which I don't think is possibly in right now, is:
>
> [net "default"]
> type=tap
> script=/etc/qemu-ifup-bridge
>
> In /etc/qemurc to globally change from slirp default to tap default. Of
> course, why stop there, we should install an /etc/qemurc by default with:
>
> [net "default"]
> type=user
> host=10.0.1.2
> net=10.0.1.0/24
> dhcpstart=10.0.1.10
> dns=10.0.1.2
>
> And completely get rid of any baked in defaults.

Yes.  Kill all these automagic devices from qemu, move them into config 
files.  So long-term we'll have something like:

/usr/share/qemu/boards/pc.dtc
         -> your virtual mainboard, i.e. all piix3/4 and core stuff
            like pic, apic, ...

/usr/share/qemu/defaults/pc.conf
         -> useful default configuration for pc, i.e. cirrus vga,
            e1000 nic, serial port, parallel port, cdrom drive, ...

/etc/qemu/host.conf
         -> host-wide config, i.e. slirp networking, maybe chardevs
            for serial0+parallel0, ...

$HOME/.qemu.conf (maybe)
         -> user-wide config

qemu would (by default) read all these files in the specified order, 
additionally a virtual-machine config file specified on the command 
line.  Asking qemu to NOT read defaults/pc.conf would zap all default 
devices from your configuration.

Maybe it is useful to have some kind of profiles, i.e.
/etc/qemu/default.conf, /etc/qemu/nographic.conf, ...

cheers,
   Gerd

      reply	other threads:[~2009-10-16 10:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14  8:39 [Qemu-devel] [PATCH 0/4] QemuOpts: config file support Gerd Hoffmann
2009-10-14  8:39 ` [Qemu-devel] [PATCH 1/4] QemuOpts: add find_list() Gerd Hoffmann
2009-10-14  8:39 ` [Qemu-devel] [PATCH 2/4] QemuOpts: dump config Gerd Hoffmann
2009-10-14 18:56   ` Anthony Liguori
2009-10-14  8:39 ` [Qemu-devel] [PATCH 3/4] QemuOpts: parse config from file Gerd Hoffmann
2009-10-14 18:55   ` Anthony Liguori
2009-10-14  8:39 ` [Qemu-devel] [PATCH 4/4] QemuOpts: command line switches for the config file Gerd Hoffmann
2009-10-16 18:39   ` Nathan Baum
2009-10-16 19:29     ` Gerd Hoffmann
2009-10-16 18:48   ` Nathan Baum
2009-10-16 19:33     ` Gerd Hoffmann
2009-10-14 18:53 ` [Qemu-devel] [PATCH 0/4] QemuOpts: config file support Anthony Liguori
2009-10-14 19:01 ` Anthony Liguori
2009-10-16 10:16   ` Gerd Hoffmann [this message]

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=4AD847FE.1000306@redhat.com \
    --to=kraxel@redhat.com \
    --cc=anthony@codemonkey.ws \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).