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). _______________________________________________ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
