From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU/pc and scsi disks
Date: Sun, 4 Mar 2007 12:05:28 +0000 [thread overview]
Message-ID: <200703041205.29153.paul@codesourcery.com> (raw)
In-Reply-To: <45EAB217.8080708@qumranet.com>
On Sunday 04 March 2007 11:48, Avi Kivity wrote:
> Paul Brook wrote:
> >> 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).
> >
> > You're going to start hitting commandline length limits fairly rapidly
> > (Windows in particular has a fairly low limit).
>
> Well, at list on linux, the limit is sane (1024 or 10240?).
IIRC linux has a ~32k commandline limit. I wouldn't be surprised if configs
end up exceeding that. If you're running on linux then creating a temporary
file is also trivial[1].
Paul
[1] see mkstemp(3) and tmpfile(3).
next prev parent reply other threads:[~2007-03-04 12:05 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 [this message]
2007-03-04 13:44 ` Chris Wilson
2007-03-04 17:50 ` Avi Kivity
2007-03-04 17:06 ` Anthony Liguori
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=200703041205.29153.paul@codesourcery.com \
--to=paul@codesourcery.com \
--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).