From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU/pc and scsi disks
Date: Sun, 04 Mar 2007 11:06:49 -0600	[thread overview]
Message-ID: <45EAFCA9.805@codemonkey.ws> (raw)
In-Reply-To: <45EA9122.6000207@qumranet.com>
Avi Kivity wrote:
> Anthony Liguori wrote:
>>>
>>> 1.  Any option should be settable either in the config file or 
>>> command line.  In other words, the user should not be forced to use 
>>> a config file.  This is useful for management programs who keep all 
>>> options in an internal database, and for users who can experiment 
>>> via a ^P edit edit edit <enter>.
>>
>> I think we should still provide the ability to set the most common 
>> options via the command line.  I'm also fine with specifying single 
>> options on the command line.  I suspect though that being able to do 
>> -config - is more useful for management tools than building large 
>> strings of command line options.
>
> Out of curiosity, why?  If the options are store in some database, as 
> is likely, surely it is easier to generate a longish command line than 
> to generate a unique name for a file, remove it if it already exists, 
> write out the data, launch qemu, and clean up the file later?  And for 
> migration, you have to regenerate it, since some options may have 
> changed (cdrom media).
Sorry, I should have been more specific.  I mean '-config -' where '-' 
would indicate reading from stdin.
Regards,
Anthony Liguori
> Of course the config file is very useful for a user maintaining a few 
> virtual machines on their own, but when qemu is part of a longer food 
> chain, I think it's just a complication.
>
next prev parent reply	other threads:[~2007-03-04 17:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 17:26 [Qemu-devel] QEMU/pc and scsi disks Laurent Vivier
2007-03-01 17:36 ` Paul Brook
2007-03-02  8:36   ` Laurent Vivier
2007-03-02 11:02     ` Thiemo Seufer
2007-03-02 15:42       ` Paul Brook
2007-03-02 16:24         ` Anthony Liguori
2007-03-02 16:45           ` Joe Batt
2007-03-25 17:05             ` Anthony Liguori
2007-03-25 20:38               ` Thiemo Seufer
2007-03-03 19:01           ` Avi Kivity
2007-03-03 23:38             ` Anthony Liguori
2007-03-04  9:28               ` Avi Kivity
2007-03-04 11:43                 ` Paul Brook
2007-03-04 11:48                   ` Avi Kivity
2007-03-04 12:05                     ` Paul Brook
2007-03-04 13:44                 ` Chris Wilson
2007-03-04 17:50                   ` Avi Kivity
2007-03-04 17:06                 ` Anthony Liguori [this message]
2007-03-06 17:59             ` Joseph Miller
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=45EAFCA9.805@codemonkey.ws \
    --to=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).