All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: Flavio Visentin <THe_ZiPMaN@zipman.it>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu and configuration file?
Date: Wed, 4 Jan 2006 16:48:43 -0500	[thread overview]
Message-ID: <20060104214842.GA22633@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <43BAFA68.9060100@zipman.it>

On Tue, Jan 03, 2006 at 11:27:52PM +0100, Flavio Visentin wrote:
> Paul Brook wrote:
> > Config file support without a decent GUI seem rather pointless.
> > The big advantage of doing it as a shell script is it's dead easy to hack to 
> > include whatever custom magical features people want.
> 
> It would be useful for automatic startup of the VMs by init scripts.
> OTOH it's very simple to create a config file parser with
> perl/python/bash who can wrap around qemu options.
> 
> If I find 1 free hour tomorrow I'll post a POC.
> 
> - --
> Flavio Visentin

I wrote one a long time ago called vqemu. It's a simple bash script that
gives support for a really primitive style of config file (basically a file
full of "qemu parameter"="on/off" or "parameter"="value". All I have to do is
type 'vqemu' in the right directory (or call 'vqemu -config file') and I get
a VM running with no troubles.

If people think this is a good idea I can easily update this to qemu 0.8.0's
options.

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

  parent reply	other threads:[~2006-01-04 21:50 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-31 20:20 [Qemu-devel] qemu and configuration file? Giuseppe Della Bianca
2006-01-03 21:49 ` Giuseppe Della Bianca
2006-01-03 22:02   ` Paul Brook
2006-01-03 22:27     ` Flavio Visentin
2006-01-03 23:31       ` Johannes Schindelin
2006-01-04  2:34         ` André Braga
2006-01-04 21:48       ` Jim C. Brown [this message]
2006-01-04 21:39     ` Giuseppe Della Bianca
2006-01-04  5:50   ` martin
2006-01-04  6:44     ` martin
2006-01-04 21:20       ` Giuseppe Della Bianca
2006-01-04  8:52     ` Flavio Visentin
2006-01-04 21:22       ` Giuseppe Della Bianca
2006-01-04 21:50         ` Johannes Schindelin
2006-01-04 22:58           ` Mike Kronenberg
2006-01-04 22:54         ` Flavio Visentin
2006-01-05 20:24           ` Giuseppe Della Bianca
2006-01-04  9:40     ` Jernej Simončič
2006-01-04 21:21       ` Giuseppe Della Bianca
2006-01-04 18:44     ` Mike Kronenberg
2006-01-04 21:22     ` Giuseppe Della Bianca
2006-01-04 23:41       ` Jernej Simončič
2006-01-04 23:52         ` Mike Kronenberg
2006-01-05  0:04           ` Jernej Simončič
2006-01-05  0:28             ` Mike Kronenberg
2006-01-05 10:49               ` Jernej Simončič
     [not found]   ` <1136325437.27117.3.camel@fred.ofc.soliddesign.net>
2006-01-04 21:39     ` Giuseppe Della Bianca
2006-01-04 21:50       ` Jim C. Brown
2006-01-05 20:18         ` Giuseppe Della Bianca
2006-01-04 22:07       ` Johannes Schindelin
2006-01-05 20:23         ` Giuseppe Della Bianca
2006-01-04 23:42       ` Jernej Simončič
2006-01-05 15:47         ` Jim C. Brown
2006-01-05 20:35         ` Giuseppe Della Bianca
2006-01-07 13:34 ` Giuseppe Della Bianca
2006-01-07 16:00   ` Flavio Visentin
2006-01-08 13:29     ` Giuseppe Della Bianca
2006-01-08 14:59       ` Johannes Schindelin

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=20060104214842.GA22633@jbrown.mylinuxbox.org \
    --to=jma5@umd.edu \
    --cc=THe_ZiPMaN@zipman.it \
    --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.