Running QEMU 0.11.00 Under eComStation
Article Info | |
---|---|
Author | |
Date | |
OS Version | eComStation 2.1 |
Companion File | N/A |
Source | Archived Site (German) |
Note: This English version is translated from German with Google Translate.
It is not necessary to install QEMU. Just download and unpack the archive with the latest QEMU version. That's all. Different QEMU versions can also be run simultaneously. In the command prompt, change to the created directory and start qemu.exe.
Host [C:\] qemu -version SYS1804: The system cannot find the file LIBC063.
If this error message appears, download the LIBC063 library from the URL ftp://ftp.netlabs.org/pub/gcc/libc-0_6_3-csd3.wpi and install it with a double click.
Host [C:\] qemu -version SYS1804: The system cannot find the file KSDL12.
This error message appears if the KSDL12.dll library is missing from the system. To do this, search for the corresponding archive on Hobbes: http://hobbes.nmsu.edu/h-search.php?button=Search&key=SDL-1.2.14-os2-gcc44-20091106. After downloading, unpack the KSDL12.dll file from the archive and copy it to the dll path. After successful installation, qemu -version shows the version and qemu -help shows the QEMU options.
Host [C:\] qemu -version QEMU PC emulator version 0.11.0, Copyright (c) 2003-2008 Fabrice Bellard Host [C:\] qemu -help
Quickstart
To set up a virtual machine, at least one image file and an operating system as a guest system are required. The virtual machine is configured using the QEMU options. When installing the guest systems, you only need to ensure that the hardware emulated by QEMU is supported.
For this example, the operating system ReactOS (http://www.reactos.org/de/) was selected as the guest system. The reasons for this are as follows:
- The installation is the same as for Microsoft Windows systems and is therefore generally known.
- ReactOS is open source and can be used freely.
- The image of the installation CD is quickly downloaded.
To install the operating system, a virtual hard disk is created. This is done using the qemu-img tool included in the QEMU package and its create parameter (see also http://qemu-buch.de/d/Speichermedien/_Images_anlegen). The name and size of the virtual hard disk must be specified. The format is specified with the -f option (see http://qemu-buch.de/d/Speichermedien/_Image-Formate).
Host [C:\] qemu-img create -f qcow2 ReactOS.img 1G
The image of the installation CD must be downloaded from the ReactOS website and unpacked.
Host [C:\] unzip ReactOS*-iso.zip
QEMU is called with the qemu command. The virtual machine is configured using options on the command line. To install the guest system, the virtual machine is started with the image of the installation CD. Its name is entered after the -cdrom option. The name of the created virtual hard disk is entered after the -hda option (see also http://qemu-buch.de/d/Speichermedien/_Zugriff_auf_Speichermedien) Archived Link) . The -boot d option is used to ensure that the virtual computer boots from the virtual CD. The -L option refers to the directory with the BIOS files. For QEMU under OS/2 and eComstation, the -priority option must also be used (see below).
Host [C:\] qemu -L pc-bios -hda ReactOS.img -cdrom ReactOS.iso -boot d -priority idle
The virtual PC starts in a window. The installation of ReactOS is started by clicking in the window and pressing any key. First, the German keyboard is selected. Then the virtual hard disk is partitioned and formatted. The target directory for installing the ReactOS files does not need to be changed. The bootloader is then installed, whereby the default option Install bootloader on the harddisk (mbr) applies. The virtual machine must then be restarted. The installation continues graphically. To boot from the hard disk, enter the -boot c option. The QEMU window is exited with [Ctrl]+[Alt].
Host [C:\] qemu -L pc-bios -hda ReactOS.img -cdrom ReactOS.iso -boot c -priority idle
To boot without a CD image, use the following command.
Host [C:\] qemu -L pc-bios -hda ReactOS.img -localtime -priority idle
After installation and configuration, it is recommended to shut down the virtual machine and create one or more overlay files to protect the base image from changes (see http://qemu-buch.de/d/Speichermedien/_Images_anlegen#Overlay-Images_anlegen). In this example, two overlay files are created.
Host [C:\] qemu-img create -b ReactOS.img -f qcow2 ReactOS-01.ovl Host [C:\] qemu-img create -b ReactOS.img -f qcow2 ReactOS-02.ovl
It is now possible to start two QEMU instances, each with an overlay file. The base image with the basic installation remains unchanged.
Host [C:\] qemu -L pc-bios -hda ReactOS-01.ovl -localtime -priority idle Host [C:\] qemu -L pc-bios -hda ReactOS-02.ovl -localtime -priority idle
To test ReactOS under the 64-bit processor architecture, use qemu-system-x86_64.
Host [C:\] qemu-system-x86_64 -L pc-bios -hda ReactOS-01.ovl -localtime -priority idle
So that you don't always have to type in the entire command line to start a virtual machine, the command line can be written in a file with the extension .cmd. If you click on this file, the virtual machine starts. The QEMU monitor is used to manipulate the running virtual machine (see http://qemu-buch.de/d/Der_QEMU-Monitor). The key combination [Ctrl]+[Alt]+[2] takes you to the QEMU monitor, and [Ctrl]+[Alt]+[1] takes you back. Creating virtual machines with different guest systems is described at the URL http://qemu-buch.de/d/Gast-Systeme. Some useful tools for working with QEMU are explained in the appendix (see http://qemu-buch.de/d/Anhang/_Nützliche_Tools). This short overview also serves to help you find your way around less well-known guest systems.
Additional options of the QEMU OS/2 port
In addition to the numerous QEMU options (see http://qemu-buch.de/d/Anhang/_Startoptionen_von_QEMU_und_KVM), the QEMU version for OS/2 Warp 4 and eComstation has the -priority option. For convenient GUI operation, the -priority idle option is recommended.
-priority nochange
No change/use of the current priority (default).
-priority idle
Idle (PRTYC_IDLETIME).
-priority normal
Normal/Regular (PRTYC_REGULAR)
-priority high
High (PRTYC_FORGROUNDSERVER)