From: martin <martin@vision.ee>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu and configuration file?
Date: Wed, 04 Jan 2006 07:50:28 +0200 [thread overview]
Message-ID: <43BB6224.9020507@vision.ee> (raw)
In-Reply-To: <200601032249.41640.bepi@adria.it>
If we'd go for a config file at all with such a complicated structure, i see no reasons why to
choose anything else than xml for it. We have tons of xml libs that can be used for gui's (think
perl, tk, python etc...). Certainly better every dude writing it's own XuPeRpArSeR that will be
broken and compatible after a major change in qemu ...
Another choice would be the pure rc (just 'item = value' lines) without any supersmart blocks.
xml style or rc style, please no hack in betweeen :)
martin
Giuseppe Della Bianca wrote:
> Hi.
>
> My idea is this:
> - qemu start
> - set up of the hardcode parameters
> - reading of the configuration file and set up of the parameters
> - set up of the parameters of command line
>
> Example of configuration file:
> [general]
> ....
> [vlan0]
> ip= x.y.x.w
> mac= l:m:n:o
> ....
> [/vlan0]
> [/general]
>
> [suse.img]
> ....
> [vlan3]
> mac= h:j:k:l
> ....
> [/vlan3]
> [/suse.img]
>
> [win.img]
> ....
> [vlan2]
> mac= z:x:c:v
> ....
> [/vlan2]
> [/win.img]
>
> Result:
> - full compatibility with every version of qemu
> - more flexibility
> - possibility to set up the hardcode parameters
> - possibility of parameters personalized for every image
>
> One similar thing, with smaller flexibility, is possible
> without modify qemu and using one series of bash script.
>
> Comments are welcomes (at least one "it does not interest to us").
>
> Regards.
> Gdb
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2006-01-04 6:20 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
2006-01-04 21:39 ` Giuseppe Della Bianca
2006-01-04 5:50 ` martin [this message]
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=43BB6224.9020507@vision.ee \
--to=martin@vision.ee \
--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).