From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1E10qw-0000Vq-Tx for qemu-devel@nongnu.org; Fri, 05 Aug 2005 07:59:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1E10qs-0000Tl-Nq for qemu-devel@nongnu.org; Fri, 05 Aug 2005 07:59:03 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E10qs-0000JW-4V for qemu-devel@nongnu.org; Fri, 05 Aug 2005 07:59:02 -0400 Received: from [195.129.94.187] (helo=srv94-187.ip-tech.ch) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1E10qw-00008v-Kh for qemu-devel@nongnu.org; Fri, 05 Aug 2005 07:59:07 -0400 Message-ID: <42F3515E.8070201@kberg.ch> Date: Fri, 05 Aug 2005 13:45:34 +0200 From: Mike Kronenberg MIME-Version: 1.0 Subject: Re: [Qemu-devel] news on the OS X cocoa port References: <42DF6E93.3010705@kberg.ch> <41e41e7a0507210312259ae3d5@mail.gmail.com> <42DF9604.2090503@kberg.ch> <42F1C589.40608@kberg.ch> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Reply-To: 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 Natalia Portillo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Better to have a architecture/machine pair. > > Architecture: x86-64 > Machine: PC > > Architecture: PowerPC > Machine: Core99 > > To be coincident with the -M flag and having the possibility of > changing the qemu executable name (that should be in the GUI > configuration) I do see the logical connection of the two. But -M is a commandline Parameter that should remain with the other commandline arguments. Maybe "PC Data" is not the correct name for what I had in mind: "PC Data" stores information, that is neccessary for a launcher app, to choose the correct binary and setup the right state, then apply the "Arguments" to this binary to start qemu. Since binarynames could change in the future, I agree that we should use generic names for the Architectures. I'll list them now (please correct me, if I'm mistaken): x86 x86-64 (x86_64 has more hits in google, but all the tech pages use x86-64) PowerPC (maybe PPC will make it easyer to grep?) SPARC MIPS G Mike > > El 04/08/2005, a las 8:36, Mike Kronenberg escribió: > >> Mike Kronenberg wrote: >> >> >>> I'm thinking of a new way to store the images and saved VMs, too. >>> Maybe we could make something like vpc: A package with the config, >>> disk-images and saved VMs, located in ~/Documents/QEMU PCs/ >>> >> >> QEMU guest PC Format, a Proposal >> >> This should serve as a base for the discussion on a Structure/ Format >> to save preconfigured/saved guest PCs. >> >> >> Structure: >> all the Files needed by the VM are stored in a folder. The folder >> has an ending of .qvm (QEMU Virtual Machine). >> >> Mandatory Files: >> - Harddiskimages >> Configuration File (configuration.plist) >> >> Other Files: >> FDImages >> CDImages >> Thumbnail (thumbnail.png) >> VM State File (saved.vm) >> >> Host dependent Files: >> PkgInfo (OS X) >> info.plist (OS X) >> >> >> Format: >> As a general format, I propose XML. To be more exact: PropertyLists. >> You find the definition for PropertyLists at: http:// >> www.apple.com/DTDs/PropertyList-1.0.dtd >> >> Why XML? >> We live in a small world, the QEMU community started out from France >> and has now it's followers all over the world. The developers and >> (hard)core users may stick to ASCII characters. But this is not the >> case for a broader community. Localized Operating Systems and less >> interested/educated users will fast break compatibility of simple >> text/ini files. (There might even arise difficulties with >> ASCII/MacRoman) So XML is the choice in the long run. >> >> Why PropertyList? >> Because they are easy to handle. Datatypes/Values and Variable Names >> are stored as pairs: >> >> author >> Mike Kronenberg >> date >> 2005-07-27T22:00:00Z >> >> >> What should be covered by “configuration.plist”? >> Version >> About >> Arguments >> PC Data >> Temporary >> >> There is no particular Order, Data is accessed by key. >> >> >> 1.Version >> Simple String to define the version of this configurations.plist >> file. Format: 1.0.0 >> >> 2.About >> Author name, Date, Copyright/left. Place for further Descriptions. >> >> 3.Arguments >> To have the highest compatibility, we should stick to a simple >> option/value Scheme here, with boolean YES/NO for arguments with no >> value, like -enable-audio. There should be no host dependent >> switches here. >> >> 4.PC Data >> PC Name, PC Description, PC Status, emulated CPU and other guest PC >> related “Meta” Information. >> >> 5.Temporary >> “Nice to have” data, host dependent switches – shortly everything >> that is NOT needed to guarantee the operation of QEMU. >> >> Sample configuration.plist: >> >> >> > "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> >> >> >> About >> >> author >> Mike Kronenberg >> copyright >> © 2005, Mike Kronenberg >> date >> 2005-07-27T22:00:00Z >> description >> This is a sample PC configuration. >> >> Arguments >> >> -boot >> c >> -cdrom >> /dev/cdrom >> -hda >> Harddisk1.raw >> >> PC Data >> >> name >> My new PC >> state >> saved >> system >> qemu-system-x86_64 >> >> Temporary >> >> Version >> 0.1.0 >> >> >> >> >> >> >> Waiting for Your Suggestions... >> >> Mike >> >> >> _______________________________________________ >> Qemu-devel mailing list >> Qemu-devel@nongnu.org >> http://lists.nongnu.org/mailman/listinfo/qemu-devel >> >> > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (Darwin) > > iD8DBQFC8mDXSOHwOb87puQRApVgAJ432rq0FSwpBjRaxzmgVRcr3h/cpACg2+Cd > O8Amp84ZCvMwvkEGJieWYkE= > =npr3 > -----END PGP SIGNATURE----- > > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel