From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Gc4UE-0001LW-0H for qemu-devel@nongnu.org; Mon, 23 Oct 2006 14:25:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Gc4U9-0001FO-Aq for qemu-devel@nongnu.org; Mon, 23 Oct 2006 14:25:21 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gc4U9-0001FJ-94 for qemu-devel@nongnu.org; Mon, 23 Oct 2006 14:25:17 -0400 Received: from [68.230.240.33] (helo=eastrmmtao06.cox.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Gc4U9-00063h-5b for qemu-devel@nongnu.org; Mon, 23 Oct 2006 14:25:17 -0400 Message-ID: <2626863.1161627912347.JavaMail.root@eastrmwml08.mgt.cox.net> Date: Mon, 23 Oct 2006 14:25:12 -0400 From: Ben Taylor Subject: Re: [Qemu-devel] config file support MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Reply-To: sol10x86@cox.net, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ---- "K. Richard Pixley" wrote: > Rob Landley wrote: > > On Wednesday 18 October 2006 2:42 pm, Chuck Brazie wrote: > > > >> Is there any work going on now to add config file support? > >> > >> Chuck Brazie > >> brazie@us.ibm.com > >> > > As a random end-user, I really like being able to run qemu without a config > > file, configuring it entirely on the command line. I'd be highly > > disappointed if qemu turned into another Wine. > Except that I never do. Instead, I write a trivial shell script since I > can never remember the command line options, much less type them in > consistently. > > What's the difference between a shell script to cover qemu and a > #!/bin/qemu config file? Seems to me they both address roughly the same > issues with roughly the same considerations. Am I missing any > significant functionality differences? There are probably no functional differences. A shell script with a config file (which is how I wrote one 18 months ago) should be able to handle almost any kind of config, without adding to code bloat to qemu. The script I wrote is probably horribly out of date, and has some holes (and probably some logic flaws yet unfound), but for the most part replicated most of the things I wanted to do (networking, tun/tap or redirs, samba etc ) without having to type command lines in excess of 200 characters. Given that I had probably 8-10 qemu guest systems, it was a huge time saver when it came to starting up a brand new guest. Ben