Emaculation.com

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
ppc-osx-on-qemu-for-windows [2020/05/23 03:45] – [Networking] cat_7ppc-osx-on-qemu-for-windows [2024/02/05 12:54] (current) – [Networking] cat_7
Line 1: Line 1:
-===== Installing Qemu for Windows =====+===== Running Qemu-system-ppc with Mac OS/OSX guests in Windows =====
  
-(Guide Updated February 182017)+(Guide updated July 7th2023)
  
 ===== Introduction ===== ===== Introduction =====
  
-[[Qemu]] can run PPC Mac OS 9.0, 9.1, 9.2 and PPC OSX 10.0, 10.110.2, 10.3, 10.4 and 10.5+Qemu-system-ppc can run the PowerPC versions of Mac OS 9.0 to 9.2 and OSX 10.0 to 10.5. Qemu can also run some OSX release previews. 
 + 
 +The status of various guests based on the latest builds available from the forum: 
 +^ Guest ^ Default build ^ Sound-enabled build ^ Argument(s) ^ Remarks ^ 
 +| Mac OS 9.0         | OK            | OK          | -M mac99 | Requires rom version 5.2.1 or abovemouse wiggle to boot | 
 +| Mac OS 9.1         | OK            | OK          | -M mac99,via=pmu | 
 +| Mac OS 9.2         | OK            | OK                     | -M mac99,via=pmu         | 
 +| Mac OSX 10.0       | OK            | Cracklechannel issue                     | -M mac99 |  
 +| Mac OSX 10.1       | OK            | Channel issue                     | -M mac99 |  
 +| Mac OSX 10.2       | OK            | OKbut channels reversed         | -M mac99 -device pci-ohci,id=usb1 -device usb-mouse,bus=usb1.0 -device usb-kbd,bus=usb-bus.0        |  | 
 +| Mac OSX 10.3       | OK            | OK         | -M mac99,via=pmu          | Sound has speed drift | 
 +| Mac OSX 10.4       | OK            | OK         | -M mac99,via=pmu         | 
 +| Mac OSX 10.5       | OK            | OK        | -M mac99,via=pmu |
 ===== Requirements ===== ===== Requirements =====
   * Qemu program \\   * Qemu program \\
Line 15: Line 27:
  
 Installations of other versions of Mac OS or OSX (roughly) follow the same path. \\ Installations of other versions of Mac OS or OSX (roughly) follow the same path. \\
-===== Qemu installation =====+See the table above for information about specific qemu parameters required to run Mac OS/OSX versions. 
 +===== Qemu-system-ppc installation =====
  
   * Go to http://www.emaculation.com/forum/viewtopic.php?f=34&t=9028 and download our latest build from the **official** Qemu source.   * Go to http://www.emaculation.com/forum/viewtopic.php?f=34&t=9028 and download our latest build from the **official** Qemu source.
Line 26: Line 39:
   * Open your favorite text editor and create a file called qemu.bat in your qemu folder. (If one is contained in the download, edit that one).   * Open your favorite text editor and create a file called qemu.bat in your qemu folder. (If one is contained in the download, edit that one).
   * Paste the code below into the file:   * Paste the code below into the file:
- 
      
-  qemu-system-ppc.exe -L pc-bios -boot d -M mac99,via=pmu -m 512 ^ +qemu-system-ppc.exe ^\\ 
-  -prom-env "auto-boot?=true" -prom-env "boot-args=-v" -prom-env "vga-ndrv?=true" +-L pc-bios ^\\ 
-  -drive file=MacOS9.2.iso,format=raw,media=cdrom ^ +-M mac99,via=pmu ^\\ 
-  -drive file=MacOS9.2.img,format=raw,media=disk +-m 512 ^\\ 
-  -sdl ^ +-display sdl ^\\ 
-  -netdev user,id=network01 -device sungem,netdev=network01 ^ +-boot ^\\ 
-  -device VGA,edid=on +-drive file=MacOS9.2.iso,format=raw,media=cdrom ^\\ 
 +-drive file=MacOS9.2.img,format=raw,media=disk 
  
   * Save qemu.bat    * Save qemu.bat 
Line 40: Line 53:
 Short explanation of the content of the file:\\ Short explanation of the content of the file:\\
  
-qemu-system-ppc.exe starts qemu with all the following as parameters:\\ +qemu-system-ppc.exe starts qemu with all of the following as parameters:\\ 
--L pc-bios defines the location of bios files to be used.\\ +  -L pc-bios defines the location of bios files to be used.\\ 
--boot d defines to boot from a drive entry marked as a cdrom, “-boot c” would define to boot from a drive entry marked as disk.\\ +  -M mac99,via=pmu defines the mac model used(*).\\ 
--M mac99 defines the mac model used(*).\\ +  -m 512 defines the amount of memory (in Mb) for OS9/OSX.\\ 
--m 512 defines the amount of memory (in Mb) for OS9/OSX.\\ +  -display sdl instructs Qemu to use SDL for the graphical display\\ 
--prom-env "auto-boot?=true" -prom-env "boot-args=-v" define boot parameters for openbios and Mac OSX. The “-v” makes the boot process verbose\\ +  -boot d defines to boot from a drive entry marked as a cdrom, “-boot c” would define to boot from a drive entry marked as disk.\\ 
--prom-env "vga-ndrv?=true" loads the qemu-vga.ndrv file to provide on the fly resolution swithingSetting this to false ignores the driver\\ +  -drive file=MacOS9.2.iso,format=raw,media=cdrom defines the name, location, format, and type of image (cdrom) file to be used\\ 
--drive file=MacOS9.2.iso,format=raw,media=cdrom defines the name, location, format, and type of a cdrom (or dvdimage file to be used\\ +  -drive file=MacOS9.2.img,format=raw,media=disk defines the name, location, format, and type of image (diskfile to be used\\
--drive file=MacOS9.2.img,format=raw,media=disk defines the name, location, format, and type of a hard disk image file to be used\\ +
--sdl instructs Qemu to use SDL for the graphical display\\ +
--netdev user,id=network01 -device sungem,netdev=network01  tell qemu to use the sungem network device on a qemu-internal DHCP server\\ +
--device VGA,edid=on presents additional resolutions to choose from in the guest \\+
  
 (*)The mac model entry accepts 3 options for the via parameter: \\ (*)The mac model entry accepts 3 options for the via parameter: \\
Line 57: Line 66:
 mac99,via=pmu-adb (this allows some older Mac OS/Mac OS server builds to use a keyboard and mouse through the adb bus) \\ mac99,via=pmu-adb (this allows some older Mac OS/Mac OS server builds to use a keyboard and mouse through the adb bus) \\
 mac99,via=cuda (default, this allows use of the older adb (Apple Desktop Bus), now less supported cuda) \\ mac99,via=cuda (default, this allows use of the older adb (Apple Desktop Bus), now less supported cuda) \\
 +**Note:** to run Leopard, you have to use -M mac99,via=pmu \\
 +
  
   * Double-click qemu.bat. This starts Qemu and boots the MacOS9.2.iso installation CD image.   * Double-click qemu.bat. This starts Qemu and boots the MacOS9.2.iso installation CD image.
Line 62: Line 73:
 ===== Installation of Mac OS 9.2 ===== ===== Installation of Mac OS 9.2 =====
  
-To install Mac OS, you first need to partition the hard disk, so after you booted from the CD go into the "Utilities" folder and start the "Drive Setup" program. Select the entry "<not initialized>" and click "Initialize" and again in the next window. After initialization has finished and a disk icon has appeared on the desktop, quit the program. \\ +After you booted from the CD you first need to partition the hard disk:  
-You can then start the installation of Mac OS. Shut down Mac OS after the installation has finished. +  * Go into the "Utilities" folder and start the "Drive Setup" program.  
- +  * Select the entry "<not initialized>" and click "Initialize" and again in the next window.  
 + 
 +After initialization has finished and a disk icon has appeared on the desktop, quit the program. \\ 
 +You can then start the installation of Mac OS. Shut down Mac OS after the installation has finished.\\ 
 +Please note that the initialization step has to be repeated for any NEW disk added to Mac OS.
 ===== Booting the installed Mac OS ===== ===== Booting the installed Mac OS =====
-To boot the installed Mac OS, you need to edit the qemu.bat file: Change the "-boot dargument to "-boot cAlso reverse the order in which your disk and cd rom entry are listed in qemu.bat. When booting with "-boot c", make sure your hard disk image file is listed first. Save the file. Double-click qemu.bat and Mac OS will boot from the hard disk. \\+To boot the installed Mac OS, you need to edit the qemu.bat file:  
 +  * Change the -boot d argument to -boot c.  
 +  * Reverse the order in which your disk and cdrom entry are listed in qemu.bat.  
 + 
 +When booting with -boot c, make sure your hard disk image file is listed first. Save the file. Double-click qemu.bat and Mac OS will boot from the hard disk. \\
  
 Done. Done.
Line 72: Line 91:
 ===== Connecting other CDs or disk images ===== ===== Connecting other CDs or disk images =====
  
-If you want to install software, make an image of the CD-Rom and attach it to Qemu. Add a disk //after// the hard disk like below to qemu.bat:+If you want to install software, make an image of the CD-Rom and attach it to Qemu. Add a disk //after// the hard disk entry to qemu.bat:
  
   "-drive file=Name-of-CD-image.iso,format=raw,media=cdrom" (without the quotes!)   "-drive file=Name-of-CD-image.iso,format=raw,media=cdrom" (without the quotes!)
Line 80: Line 99:
   "-drive file=Name-of-hard-disk-image.img,format=raw,media=disk" (without the quotes!)   "-drive file=Name-of-hard-disk-image.img,format=raw,media=disk" (without the quotes!)
  
-And save the file. Start qemu.bat. The CD image (if readable by Mac OS) will appear on the desktop for you to use.+And save the file. Start qemu.bat. The CD image (if readable by Mac OS) will appear on the desktop for you to use.\\ 
 +A new hard disk needs to be partitioned as described above.
  
 ===== Changing the graphics settings ===== ===== Changing the graphics settings =====
Line 88: Line 108:
   "-g 1024x768x32"  (Without the quotes!)    "-g 1024x768x32"  (Without the quotes!) 
      
-Once in Mac OS, you can use the monitors control panel to set the desired screen size and colour depth. +Subsequent changes to the resolution can be made with default OS tools. (e.g., the Monitors control panel in MacOS or equivalent in OSX)
-===== Networking =====+
  
-The latest Qemu for Windows builds emulate network device that is supported out of the box for Mac OS 9.0 up to OSX 10.5 \\ + 
-However, you can also use the realtek 8139 device. This requires installation of the appropriate drivers. You can download them from the [[http://www.realtek.com.tw/Downloads/downloadsView.aspx?Langid=1&PNid=14&PFid=6&Level=5&Conn=4&DownTypeID=3&GetDown=false|Realtek site]]or all drivers in one iso from [[http://www.open.ou.nl/hsp/downloads3/MacOSRealtekDrivers.zip |here]] \\+===== Opening serial connection to the host ===== 
 + 
 +You can open a connection to a com port on the windows host by adding: 
 + 
 +  "-device usb-serial,chardev=com -chardev serial,path=com1,id=com" 
 + 
 +to your command line. chardev=""  and id="" have to matchbut you can open a different com port by changing the path= parameter.\\ 
 +When you start Qemu, a window will open in which you can set the serial communication parameters.\\
    
-There are several ways to get networking going in Windows: through slirp or tap networking+Inside your Mac OS 9.x guest a FTDI driver is needed fromhttps://www.ftdichip.com/Drivers/VCP.htm (download the 1.0f4 version) \\ 
 +Once installed you can open a modem connection through the "USBHighSpeedSerialConverter", or use a terminal emulator such as zterm. 
 +===== Sharing devices with the Guest--GUIDE IN PROGRESS =====
  
-=== Slirp-based networking ===+You can attempt to pass-through devices attached to the host to the guest. For USB devices in general this takes the form of:
  
-If not added alreadyadd the following to your command line:+  "-device usb-host,vendorid=0x0000,productid=0x0000" 
 +   
 +On a Windows host, you can find the required USB vendorid and productid by checking the USB device in the Device Manager. 
 +Mac OS up to 10.2.8 will only support USB 1.1. If your device uses USB 2, you can attach it to an USB 1.1 hub to force it into USB 1.1 mode.
  
-  * -netdev user,id=network01 -device sungem,netdev=network01  +To allow Qemu to take control of the device you might have to use a utility such as the USBDriverTool to load a different driver for the device.
  
-=== Bridging tap device ===+=== Mac OS 9.0 to 10.2 === 
 + 
 +Sharing an USB device with Mac OS 9.0 up to Mac OSX 10.2 is restricted to using USB 1.1 devices. 
 +A way to push a USB 2.0 device into USB 1.1 mode is to attach it to a strictly USB 1.1 hub (as found in older Apple keyboards or regular 1.1 hubs). 
 + 
 +    "-device usb-host,vendorid=0x058f,productid=0x6387" to the command line (replace product and vendor id with what you found) 
 + 
 +=== Mac OS 10.3 and above === 
 + 
 +Mac OS 10.3 and above support USB 2. To add an USB 2 device, first add a USB 2 controller and then attach you device to that controller: 
 + 
 +    "-device usb-ehci,id=ehci" 
 +    "-device usb-host,bus=ehci.0,vendorid=0x058f,productid=0x6387" to the command line (replace product and vendor id with what you found) 
 + 
 + 
 +===== Networking ===== 
 + 
 +The latest Qemu-system-ppc for Windows builds emulate network device that is supported out of the box for Mac OS 9.0 up to OSX 10.5 \\ 
 + 
 +  
 +There are several ways to get networking going in Windows: 
 + 
 +=== Slirp-based networking ===
  
-You need to install the OpenVPN tap driver, bridge it with your normal ethernet connection and use the following in the qemu command line:+**Note:** this is activated by default on Qemu-system-ppc, so doesn'need to be mentioned explicitly on the command line:
  
-  * -netdev tap,ifname=TapEthernet1,id=network01 -device sungem,netdev=network01 (and replace "TapEthernet1" with the name of the tap device network connection)+  * -device sungem,netdev=network01 -netdev user,id=network01   
  
-=== Running two qemu instances with networking===+== Running two Qemu-system-ppc instances with networking ==
  
-If you want to run two installations of Mac OS/OSX, Qemu needs to be able to tell the network devices apart. You can add a mac address to the networking device:+If you want to run two instances of Mac OS/OSX simultaneously, Qemu needs to be able to tell the network devices apart. You can add a mac address to the networking device:
  
-  * -netdev user,id=network01 -device sungem,netdev=network01,mac=52:54:00:12:34:56   (this is the default mac address)+  * -device sungem,netdev=network01,mac=52:54:00:12:34:56 -netdev user,id=network01    (this is the default mac address)
 and make sure you add a different mac address to the second instance: and make sure you add a different mac address to the second instance:
-  * -netdev user,id=network01 -device sungem,netdev=network01,mac=52:54:00:12:34:66+  * -device sungem,netdev=network01,mac=52:54:00:12:34:66 -netdev user,id=network01 
 Please note that adding a mac address other than the default to the network device leads to the discovery of a new network card in OSX. You need to configure that card through the network preferences.\\ Please note that adding a mac address other than the default to the network device leads to the discovery of a new network card in OSX. You need to configure that card through the network preferences.\\
  
-To allow two qemu instances to "see" each other on the network, you can e.g. install a second tap device and bridge both tap devices with the default network connection. You must then also use different mac addresses for each connection:+=== Tap-based: Bridging one or more tap device (enabling Appletalk networking) ===
  
-  * -netdev tap,ifname=TapEthernet1,id=network01 -device sungem,netdev=network01,mac=52:54:00:12:34:56 +Install an OpenVPN tap device and bridge it with your normal ethernet connection. Then use the following on the Qemu-system-ppc command line:
-  * -netdev tap,ifname=TapEthernet2,id=network01 -device sungem,netdev=network01,mac=52:54:00:12:34:66+
  
 +  * -device sungem,netdev=network01 -netdev tap,ifname=TapEthernet1,id=network01  (and replace "TapEthernet1" with the name of the tap device network connection)
 +
 +To allow two Qemu-system-ppc instances to "see" each other on the network and also have internet access, install a second tap device and bridge both tap devices with your default network connection. You must then also use different mac addresses for each connection. Note that the tap devices should have different names too.
 +
 +  * -device sungem,netdev=network01,mac=52:54:00:12:34:56 -netdev tap,ifname=TapEthernet1,id=network01 
 +  * -device sungem,netdev=network01,mac=52:54:00:12:34:66 -netdev tap,ifname=TapEthernet2,id=network01 
  
 === Peer to peer networking between two Qemu instances === === Peer to peer networking between two Qemu instances ===
  
-Qemu can use socket networking to connect two peers. Note the peers will have no internet access using the commands below, but can exchange data between each-other. Set one guest to be a listener for network traffic:+Qemu can use socket networking to connect two peers. The peers will have no internet access, but can exchange data between each other. \\ 
 +Set one guest to be a listener for network traffic:
  
-  * -device sungem,netdev=net1,mac=52:54:00:12:34:56 -netdev socket,id=net1,listen=:1234+  * -device sungem,netdev=network01,mac=52:54:00:12:34:56 -netdev socket,id=network01,listen=:1234
  
 Set the other guest to connect to the listener: Set the other guest to connect to the listener:
  
-  * -device sungem,netdev=net1,mac=52:54:00:12:34:66 -netdev socket,id=net1,connect=127.0.0.1:1234+  * -device sungem,netdev=network01,mac=52:54:00:12:34:66 -netdev socket,id=network01,connect=127.0.0.1:1234 
 + 
 +For both instances, set the TCP/IP settings manually to a free ip address in your IP range and set the subnetmask to 255.255.255.0. No other settings have to be made. 
 + 
 +=== Forwarding (multiple) ports to the host (only needed when using the slirp network option) === 
 + 
 +You can provide services running on the guest to the host by forwarding ports to the host.  
 + 
 +== Running a webserver == 
 + 
 +  * -device sungem,netdev=network01 -netdev user,id=network01,hostfwd=tcp::8080-:80 
 + 
 +The webserver running on the guest is then accessible through http://name-or-ip-adress-of-host:8080 from other machines running on your network. 
 + 
 +== Getting files in and out of the guest with FTP == 
 + 
 +  * -device sungem,netdev=network01 -netdev user,id=network01,hostfwd=tcp::2121-:21
  
 +Forwarding port 21 to the host allows running an ftp server (such as Netpresenz, available from the macintosh garden site) on an Mac OS 9.x guest and read/write access to the file system of the guest. Make sure to use an FTP client capable of active transfer mode on the host (such as Filezilla, we are dealing with an old guest system after all.) For access to a Mac OS X guest, enable the ftp service.\\
 +You can access the guest by connecting to ftp://name-or-ip-adress-of-host:2121 from other machines running on your network. 
  
 +-On the Mac OS side: Enable file sharing through the control panel: Enter a Owner name, password and computer name and click Start under File Sharing. Then, at the Users & Groups pane open your user. At Show, select Sharing and set allow user to connect and select see all disks.\\
 +Next, share your hard drive: select the drive icon, use File/Get info/Sharing to set Share this item and...\\
 +Start Netpresenz setup, configure the ftp service and user: At ftp setup, Owner need full access. Then check the Summary for any additional configuration hints, then start Netpresenz. \\
  
-=== Forwarding ports to the host ===+-On the Windows/Filezilla side:\\ 
 +Start Filezilla, open Settings.\\ 
 +At FTP set transfer mode to active.\\ 
 +At FTP active mode/Active mode IP set "Use the following IP address" to your host ip address.\\ 
 +On the same page disable Don't use external IP address.....\\
  
-You can provide services running on the guest to the host by forwarding ports to the hostTo provide access to e.g., a webserver running in the guest you can use:+In the connection bar, enter localhost and your Mac OS user name and port 2121, then click connectFilezilla will ask for your Mac OS password.\\
  
-  * -netdev user,id=network01,hostfwd=tcp::80-:80+==Multiple port forwarding == 
 +You can forward multiple ports:
  
-The webserver running on the guest is then accessible through e.g.http://localhost or http://name-or-ip-adress-of-machine from other machines running on your network.+  * -device sungem,netdev=network01 -netdev user,id=network01,hostfwd=tcp::2121-:21,hostfwd=tcp::8080-:80
  
 +You can also forward ports for appletalk over tcp/ip:
  
 +  * -device sungem,netdev=network01 -netdev user,id=network01,hostfwd=tcp::548-:548,hostfwd=tcp::387-:387
  
 === Accessing a Windows 10 share from Mac OS 9.2 running in Qemu, using Dave 6.2.1 === === Accessing a Windows 10 share from Mac OS 9.2 running in Qemu, using Dave 6.2.1 ===
Line 194: Line 281:
 In Mac OS: First drag any mounted CD from the desktop into the trash\\ In Mac OS: First drag any mounted CD from the desktop into the trash\\
  
-Open the Qemu Monitor by pressing Ctrl-Alt-2 \\ +  * Open the Qemu Monitor by pressing Ctrl-Alt-2 \\ 
-Type "info block" to find the name of the CD drive in Qemu (most likely: ide1-cd0) \\ +  Type "info block" to find the name of the CD drive in Qemu (most likely: ide1-cd0) \\ 
-Type "eject ide1-cd0" \\ +  Type "eject ide1-cd0" \\ 
-Type "change ide1-cd0 Driveletter:/path/name-of-cd-image.iso" (note the forward slashes!) \\ +  Type "change ide1-cd0 Driveletter:/path/name-of-cd-image.iso" (note the forward slashes!) \\ 
-Close the Qemu Monitor by pressing Ctrl-Alt-2 again (do **not** close the window by clicking the close button)\\+  Close the Qemu Monitor by pressing Ctrl-Alt-2 again (do **not** close the window by clicking the close button)\\
  
 Also see the qemu documentation here: https://www.linux-kvm.org/page/Change_cdrom \\ Also see the qemu documentation here: https://www.linux-kvm.org/page/Change_cdrom \\
  
 ==== Mounting a real cd ==== ==== Mounting a real cd ====
-NOTE: you cannot mount Mac formatted CD's, but other formats work \\+**NOTE**You cannot mount Mac formatted CD's, but other formats work \\
  
-Open the Qemu Monitor by pressing Ctrl-Alt-2 \\ +  * Open the Qemu Monitor by pressing Ctrl-Alt-2 \\ 
-Type "info block" to find the name of the CD drive in Qemu (most likely: ide1-cd0) \\ +  Type "info block" to find the name of the CD drive in Qemu (most likely: ide1-cd0) \\ 
-Type "change ide1-cd0 /dev/cdrom" (note the forward slashes!) \\ +  Type "change ide1-cd0 /dev/cdrom" (note the forward slashes!) \\ 
-Close the Qemu Monitor by pressing Ctrl-Alt-2 again (do **not** close the window by clicking the close button)\\ +  Close the Qemu Monitor by pressing Ctrl-Alt-2 again (do **not** close the window by clicking the close button)\\ 
-===== Experimental builds =====+ 
 +==== Using a virtual usb drive to exchange files with the host ==== 
 +**NOTE: This option is not error-free**   
 + 
 +Create an empty folder to be used to exchange files. In the example below, the folder c:\QemuVVFAT is used.\\ 
 +Add the following to your command line: \\ 
 +-device usb-storage,drive=fat32 -drive file=fat:rw:c:\QemuVVFAT,id=fat32,format=raw,if=none 
 + 
 +An USB drive called Qemu-VVFAT will appear on your desktop. You can use it to exchange files with the host. 
 +===== Experimental builds and features =====
  
 Qemu is being actively developed. This means that some new features can become available that are not yet incorporated into the official source code. Qemu is being actively developed. This means that some new features can become available that are not yet incorporated into the official source code.
 Currently there are several such developments, in various states of reliability: Currently there are several such developments, in various states of reliability:
  
--Sound support\\+-Sound support\\
  
 You can download some of these experimental builds for our forum under **Experimental builds** : http://www.emaculation.com/forum/viewtopic.php?f=34&t=9028 You can download some of these experimental builds for our forum under **Experimental builds** : http://www.emaculation.com/forum/viewtopic.php?f=34&t=9028
  
 +-File sharing with the host \\
 +-Mouse tablet driver
 +
 +You can download drivers enabling these features here: https://www.emaculation.com/forum/viewtopic.php?t=11973
 +
 +
 +===== Issues =====
 +
 +  * Restart doesn't work in Mac OS. Use Shut Down and restart Qemu.
 +  * Qemu will not boot Mac OS when memory is set to 64Mb or less.
 +  * Sound only works reasonably well in Mac OS 9 guests.
 +  * Sound will not work in, or crash Mac OS guests with memory set to 1024Mb or more. 
 +
 +===== Useful additional command line arguments =====
 +
 +  * -k en-us sets the keyboard language (see below for possible languages)
 +
 +The language codes available are:\\
 +ar  de-ch  es  fo     fr-ca  hu  ja  mk     no  pt-br  sv \\
 +da  en-gb  et  fr     fr-ch  is  lt  nl     pl  ru     th \\
 +de  en-us  fi  fr-be  hr     it  lv  nl-be  pt  sl     tr \\
 +
 +  * -rtc base=localtime sets the guest time to the local machine time
 +  * -full-screen sets the guest to run full screen
 +  * -prom-env "auto-boot?=false" stops boot at the openbios prompt  
 +  * -prom-env "boot-args=-v" shows verbose boot messages with OSX guests 
 +  * -prom-env "vga-ndrv?=false" disables loading the default VGA driver