qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: Manish Regmi <regmi.manish@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu per vm config file support
Date: Tue, 13 Apr 2010 11:50:20 +0530	[thread overview]
Message-ID: <20100413062020.GA15703@amit-x200.redhat.com> (raw)
In-Reply-To: <l2o652016d31004121906qebfa0f85kf34ae08b1ca86a75@mail.gmail.com>

On (Mon) Apr 12 2010 [21:06:29], Manish Regmi wrote:
> Hi,
>   These days i am playing with qemu and kvm. The command line parameters can
> become very long. Is there any technical reason why config file is not
> implemented in qemu yet.

See -readconfig and -writeconfig. There's partial support for config
files; not all devices can be initialised via configs yet.

		Amit

      reply	other threads:[~2010-04-13  6:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13  2:06 [Qemu-devel] qemu per vm config file support Manish Regmi
2010-04-13  6:20 ` Amit Shah [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=20100413062020.GA15703@amit-x200.redhat.com \
    --to=amit.shah@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=regmi.manish@gmail.com \
    /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).