I have implemented .qvm as a test in Q.
Here is a sample configuration.plist and some additions to my initial
proposal:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd";>
<plist version="1.0">
<dict>
<key>About</key>
<dict>
<key>Author</key>
<string>Q</string>
<key>Copyright</key>
<string>none</string>
<key>Date</key>
<date>2005-08-07T19:25:41Z</date>
<key>Description</key>
<string>Converted guest PC from cocoaqemu.plist</string>
</dict>
<key>Arguments</key>
<dict>
<key>-boot</key>
<string>c</string>
<key>-cdrom</key>
<string>/dev/cdrom</string>
<key>-hda</key>
<string>harddisk_1.img</string>
<key>-localtime</key>
<true/>
<key>-m</key>
<integer>16</integer>
<key>-user-net</key>
<true/>
</dict>
<key>PC Data</key>
<dict>
<key>architecture</key>
<string>x86</string>
<key>name</key>
<string>Freedos</string>
<key>state</key>
<string>shutdown</string>
</dict>
<key>Temporary</key>
<dict>
<key>-cocoapath</key>
<string>/Users/mike/Documents/QEMU/Freedos.qvm</string>
</dict>
<key>Version</key>
<string>0.1.0.Q</string>
</dict>
</plist>
Changes:
- the type <integer> for integer values:
<key>-m</key>
<integer>16</integer>
- diskimages can have a relative path (to the .qvm root) or a
absolute path, to an image outside the package:
<key>-hda</key>
<string>harddisk_1.img</string>
- the key "architecture" for the used CPU
<key>architecture</key>
<string>x86</string>
- the key "state" can take the following values:
<key>state</key>
<string>shutdown</string>
<string>running</string>
<string>saved</string>
On OS X, if you have Q installed, .qvm packages show as a single file
and you can start QEMU by doubleclicking a .qvm package.
See the info.plist in Q.app/Contents for the Document definition.
Greetings
Mike
_______________________________________________
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
