Hi,
On Sun, 8 Jan 2006, Giuseppe Della Bianca wrote:
> > Giuseppe Della Bianca wrote:
> > > Please, who is that decides if to insert patch or modifications in qemu
> > > code?
> >
> > Fabrice
That is not completely true. QEmu is Open Source, and the license permits
to have your own version ("fo
> Giuseppe Della Bianca wrote:
> > Please, who is that decides if to insert patch or modifications in qemu
> > code?
>
> Fabrice
Thanks for the confirmation.
Therefore the alternatives are:
- create several script that they use the command line of qemu
- modify and maintain one personalized ver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giuseppe Della Bianca wrote:
> Please, who is that decides if to insert patch or modifications in qemu code?
Fabrice
- --
Flavio Visentin
| \|||/
|@/0.0\@
| \ - /
+--oOOo---
Hi.
Please, who is that decides if to insert patch or modifications in qemu code?
Gdb
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
]zac[
> I'd prefer to have 5 config files and just specify one of them on the
> command-line, than having 5 scripts, which run qemu with the parameters I
> want.
I would prefer to go also beyond, one unique configuration file for every
image of S.O., and use the command line for overwrite the set
]zac[
> What do you want (specifically)?
Please, read this:
Re: [Qemu-devel] qemu and configuration file?
(Giuseppe Della Bianca, Tue Jan 3 22:49:41 2006)
]zac[
> about config files, I fail to see the necessity of config files, let alone
> XML config files.
]zac[
Ok.
]zac[
> > Please, you can make an detailed example?
]zac[
> uuid.action = "create"
> usb.autoConnect.device0 = ""
]zac[
Thanks.
Gdb
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
]zac[
> Unless you mean like a GUI config file editor? But that would likely be
> a separate program anyways (and not a script).
I thing that would be useful to insert in the configuration file the options
for set up the mac address, for assing at one key the combinations of keys
for execute cha
On Thu, Jan 05, 2006 at 12:42:27AM +0100, Jernej Simon?i? wrote:
> On Wednesday, January 4, 2006, 22:39:23, Giuseppe Della Bianca wrote:
>
> > Also modifying qemu, the command line of qemu allow to use the logic
> > that everyone prefers.
>
> I'd prefer to have 5 config files and just specify o
On Thursday, January 5, 2006, 1:28:36, Mike Kronenberg wrote:
> qemu "/Users/Jernej Simončič/Simončič_image_2.img" -m 128
> can be correctly declarated and stored in a XML file while its
> generating problems with normal 8bit text files.
You do realize, that Qemu could easily declare that it's
simple example:
qemu "/Users/Jernej Simončič/Simončič_image_2.img" -m 128
can be correctly declarated and stored in a XML file while its
generating problems with normal 8bit text files. Not necessarily on
the creators system, but maybe on another users system, if you share
the config file
On Thursday, January 5, 2006, 0:52:07, Mike Kronenberg wrote:
> As I mentioned in a earlier thread about config files, one of the big
> advantages of XML is it's language independence.
And flat files are language dependant how?
> There are french, spanish, japanese, chinese people using qemu,
As I mentioned in a earlier thread about config files, one of the big
advantages of XML is it's language independence.
There are french, spanish, japanese, chinese people using qemu,
resulting in imagenames / paths in the corresponding language.
ASCII/UTF-8 is not everything.
Mike
On 05.01.
On Wednesday, January 4, 2006, 22:39:23, Giuseppe Della Bianca wrote:
> Also modifying qemu, the command line of qemu allow to use the logic
> that everyone prefers.
I'd prefer to have 5 config files and just specify one of them on the
command-line, than having 5 scripts, which run qemu with th
On Wednesday, January 4, 2006, 22:22:09, Giuseppe Della Bianca wrote:
> The xml configuration file are too much hard to consult and to modify
> directly from a human.
It's not hard to edit XML (when it's nicely structured, and not clumped all
in a single line), but from my experience it just do
I'd like to see some more things in it (besides that windows clients
can't handle (ba)sh scripts:
- State of the machine (saved/running/snapshot)
- what cpu/machine
- further information (Author, Copyright...)
- paths that can be handled by every plattform
...
so you can g(zip) up a vm and sen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giuseppe Della Bianca wrote:
>>I like VMWare style. Maybe it should be possible to share the same
>>config file between qemu and VMWare, also to favour user migration.
>
> Please, you can make an detailed example?
This is one config I use with VMPl
Hi,
On Wed, 4 Jan 2006, Giuseppe Della Bianca wrote:
> > Yah. I like this the best. It is the most flexible. It even allows
> > you to put logic into your qemu startup.
> ]zac[
>
> The script not are the solution that I would want.
What do you want (specifically)?
> To make a good job wit
On Wed, Jan 04, 2006 at 10:39:23PM +0100, Giuseppe Della Bianca wrote:
> > Yah. I like this the best. It is the most flexible. It even allows
> > you to put logic into your qemu startup.
> ]zac[
>
> The script not are the solution that I would want.
>
> To make a good job with the script is
Hi,
On Wed, 4 Jan 2006, Giuseppe Della Bianca wrote:
> ]zac[
> > I like VMWare style. Maybe it should be possible to share the same
> > config file between qemu and VMWare, also to favour user migration.
>
> Please, you can make an detailed example?
I can give you a perfectly simple example of
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.
>
]zac[
> I'd go for the shell script. If enough people like it I'm sure it could be
> included with qemu.
Ok.
> Config file support without a decent GUI seem rather pointless.
]zac[
I understand and I agree yours (and of the others that prefer the scripts)
motivations.
To modify qemu allows t
> Yah. I like this the best. It is the most flexible. It even allows
> you to put logic into your qemu startup.
]zac[
The script not are the solution that I would want.
To make a good job with the script is much laborious, and demands to use one
collection of additional programs (that I thi
]zac[
> I like VMWare style. Maybe it should be possible to share the same
> config file between qemu and VMWare, also to favour user migration.
Please, you can make an detailed example?
Gdb
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://l
]zac[
> sry :) , you probably understood anyway what i meant ...
]zac[
Yes, :) .
Gdb
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
]zac[
> > xml style or rc style, please no hack in betweeen :)
>
> INI? *SCNR* :)
and kde, samba and other?
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
]zac[
> 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...).
]zac[
The xml configuration file are too much hard to consult and to modify
directly from a human.
The idea to use additional library and the
I made a proposal some month ago based on xml:
http://lists.gnu.org/archive/html/qemu-devel/2005-08/msg00034.html
I use this style of xml property lists for the configuration of the
vm of Q (slightly alter by now).
Q is a OS X port of QEMU http://www.kberg.ch/q
I ran recently into some troubl
On Wednesday, January 4, 2006, 6:50:28, martin wrote:
> xml style or rc style, please no hack in betweeen :)
INI? *SCNR* :)
--
< Jernej Simončič ><><><><>< http://deepthought.ena.si/ >
The deficiency will never show itself during the dry runs.
-- Boyle's Third Law
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
martin wrote:
> xml style or rc style, please no hack in betweeen :)
I like VMWare style. Maybe it should be possible to share the same
config file between qemu and VMWare, also to favour user migration.
- --
Flavio Visentin
| \|
I shouldn't write posts at 7-8am
should be
s/Certainly better every/Certainly better than every/
s/broken and compatible/broken and incompatible/
sry :) , you probably understood anyway what i meant ...
martin
martin wrote:
If we'd go for a config file at all with such a complicated struct
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
On 1/3/06, Johannes Schindelin <[EMAIL PROTECTED]> wrote:
> > If I find 1 free hour tomorrow I'll post a POC.
>
> POC=Piece Of Crap??? ;-)
I can only hope he meant Proof Of Concept :)
--
"I decry the current tendency to seek patents on algorithms. There are
better ways to earn a living than to p
Hi,
On Tue, 3 Jan 2006, Flavio Visentin wrote:
> 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.
It is simpler to write the bash script right away, especially if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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 automati
> 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 b
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]
[/
Hi.
The options of qemu are so many, that would be the case to use configuration
file.
You are interested to this?
If the answer is, I could also think to insert in qemu the code of management
of the configuration file of my program gesconf
( http://savannah.nongnu.org/projects/gesconf ).
38 matches
Mail list logo
