1 \input texinfo @c -*- texinfo -*-
4 @settitle QEMU CPU Emulator User Documentation
7 @center @titlefont{QEMU CPU Emulator User Documentation}
16 QEMU is a FAST! processor emulator using dynamic translation to
17 achieve good emulation speed.
19 QEMU has two operating modes:
24 Full system emulation. In this mode, QEMU emulates a full system (for
25 example a PC), including a processor and various peripherials. It can
26 be used to launch different Operating Systems without rebooting the
27 PC or to debug system code.
30 User mode emulation (Linux host only). In this mode, QEMU can launch
31 Linux processes compiled for one CPU on another CPU. It can be used to
32 launch the Wine Windows API emulator (@url{http://www.winehq.org}) or
33 to ease cross-compilation and cross-debugging.
37 As QEMU requires no host kernel driver to run, it is very safe and
40 For system emulation, the following hardware targets are supported:
42 @item PC (x86 processor)
43 @item PREP (PowerPC processor)
44 @item PowerMac (PowerPC processor, in progress)
47 For user emulation, x86, PowerPC, ARM, and SPARC CPUs are supported.
51 If you want to compile QEMU yourself, see @ref{compilation}.
55 Download the binary distribution (@file{qemu-XXX-i386.tar.gz}) and
56 untar it as root in @file{/}:
61 tar zxvf /tmp/qemu-XXX-i386.tar.gz
66 Download the experimental binary installer at
67 @url{http://www.freeoszoo.org/download.php}.
71 Download the experimental binary installer at
72 @url{http://www.freeoszoo.org/download.php}.
74 @chapter QEMU PC System emulator invocation
78 @c man begin DESCRIPTION
80 The QEMU System emulator simulates a complete PC.
82 In order to meet specific user needs, two versions of QEMU are
88 @code{qemu-fast} uses the host Memory Management Unit (MMU) to
89 simulate the x86 MMU. It is @emph{fast} but has limitations because
90 the whole 4 GB address space cannot be used and some memory mapped
91 peripherials cannot be emulated accurately yet. Therefore, a specific
92 guest Linux kernel can be used (@xref{linux_compile}) as guest OS.
95 @code{qemu} uses a software MMU. It is about @emph{two times
96 slower} but gives a more accurate emulation.
100 QEMU emulates the following PC peripherials:
104 i440FX host PCI bridge and PIIX3 PCI to ISA bridge
106 Cirrus CLGD 5446 PCI VGA card or dummy VGA card with Bochs VESA
107 extensions (hardware level, including all non standard modes).
109 PS/2 mouse and keyboard
111 2 PCI IDE interfaces with hard disk and CD-ROM support
115 NE2000 PCI network adapters
122 QEMU uses the PC BIOS from the Bochs project and the Plex86/Bochs LGPL
129 Download and uncompress the linux image (@file{linux.img}) and type:
135 Linux should boot and give you a prompt.
140 @c man begin SYNOPSIS
141 usage: qemu [options] [disk_image]
146 @var{disk_image} is a raw hard disk image for IDE hard disk 0.
152 Use @var{file} as floppy disk 0/1 image (@xref{disk_images}). You can
153 use the host floppy by using @file{/dev/fd0} as filename.
159 Use @var{file} as hard disk 0, 1, 2 or 3 image (@xref{disk_images}).
162 Use @var{file} as CD-ROM image (you cannot use @option{-hdc} and and
163 @option{-cdrom} at the same time). You can use the host CD-ROM by
164 using @file{/dev/cdrom} as filename.
167 Boot on floppy (a), hard disk (c) or CD-ROM (d). Hard disk boot is
171 Write to temporary files instead of disk image files. In this case,
172 the raw disk image you use is not written back. You can however force
173 the write back by pressing @key{C-a s} (@xref{disk_images}).
176 Set virtual RAM size to @var{megs} megabytes. Default is 128 MB.
179 Use @var{file} as initial ram disk.
183 Normally, QEMU uses SDL to display the VGA output. With this option,
184 you can totally disable graphical output so that QEMU is a simple
185 command line application. The emulated serial port is redirected on
186 the console. Therefore, you can still use QEMU to debug a Linux kernel
187 with a serial console.
191 The SB16 emulation is disabled by default as it may give problems with
192 Windows. You can enable it manually with this option.
195 Set the real time clock to local time (the default is to UTC
196 time). This option is needed to have correct date in MS-DOS or
206 Set TUN/TAP network init script [default=/etc/qemu-ifup]. This script
207 is launched to configure the host network interface (usually tun0)
208 corresponding to the virtual NE2000 card.
212 Set the mac address of the first interface (the format is
213 aa:bb:cc:dd:ee:ff in hexa). The mac address is incremented for each
214 new network interface.
217 Assumes @var{fd} talks to a tap/tun host network interface and use
218 it. Read @url{http://bellard.org/qemu/tetrinet.html} to have an
222 Use the user mode network stack. This is the default if no tun/tap
223 network init script is found.
226 Use the dummy network stack: no packet will be received by the network
231 Linux boot specific. When using this options, you can use a given
232 Linux kernel without installing it in the disk image. It can be useful
233 for easier testing of various kernels.
237 @item -kernel bzImage
238 Use @var{bzImage} as kernel image.
240 @item -append cmdline
241 Use @var{cmdline} as kernel command line
244 Use @var{file} as initial ram disk.
248 Debug/Expert options:
252 Redirect the virtual serial port to host device @var{dev}. Available
258 [Linux only] Pseudo TTY (a new PTY is automatically allocated)
262 [Unix only] standard input/output
264 The default device is @code{vc} in graphical mode and @code{stdio} in
268 Redirect the monitor to host device @var{dev} (same devices as the
270 The default device is @code{vc} in graphical mode and @code{stdio} in
274 Wait gdb connection to port 1234 (@xref{gdb_usage}).
276 Change gdb connection port.
278 Do not start CPU at startup (you must type 'c' in the monitor).
280 Output log in /tmp/qemu.log
282 Simulate an ISA-only system (default is PCI system).
284 Simulate a standard VGA card with Bochs VBE extensions (default is
285 Cirrus Logic GD5446 PCI VGA)
289 During the graphical emulation, you can use the following keys:
295 Switch to virtual console 'n'. Standard console mappings are:
298 Target system display
306 Toggle mouse and keyboard grab.
309 During emulation, if you are using the @option{-nographic} option, use
310 @key{Ctrl-a h} to get terminal commands:
318 Save disk data back to file (if -snapshot)
320 Send break (magic sysrq in Linux)
322 Switch between console and monitor
331 @settitle QEMU System Emulator
334 The HTML documentation of QEMU for more precise information and Linux
335 user mode emulator invocation.
347 @section QEMU Monitor
349 The QEMU monitor is used to give complex commands to the QEMU
350 emulator. You can use it to:
355 Remove or insert removable medias images
356 (such as CD-ROM or floppies)
359 Freeze/unfreeze the Virtual Machine (VM) and save or restore its state
362 @item Inspect the VM state without an external debugger.
368 The following commands are available:
372 @item help or ? [cmd]
373 Show the help for all commands or just for command @var{cmd}.
376 Commit changes to the disk images (if -snapshot is used)
378 @item info subcommand
379 show various information about the system state
383 show the network state
385 show the block devices
387 show the cpu registers
389 show the command line history
395 @item eject [-f] device
396 Eject a removable media (use -f to force it).
398 @item change device filename
399 Change a removable media.
401 @item screendump filename
402 Save screen into PPM image @var{filename}.
404 @item log item1[,...]
405 Activate logging of the specified items to @file{/tmp/qemu.log}.
407 @item savevm filename
408 Save the whole virtual machine state to @var{filename}.
410 @item loadvm filename
411 Restore the whole virtual machine state from @var{filename}.
419 @item gdbserver [port]
420 Start gdbserver session (default port=1234)
423 Virtual memory dump starting at @var{addr}.
426 Physical memory dump starting at @var{addr}.
428 @var{fmt} is a format which tells the command how to format the
429 data. Its syntax is: @option{/@{count@}@{format@}@{size@}}
433 is the number of items to be dumped.
436 can be x (hexa), d (signed decimal), u (unsigned decimal), o (octal),
437 c (char) or i (asm instruction).
440 can be b (8 bits), h (16 bits), w (32 bits) or g (64 bits). On x86,
441 @code{h} or @code{w} can be specified with the @code{i} format to
442 respectively select 16 or 32 bit code instruction size.
449 Dump 10 instructions at the current instruction pointer:
454 0x90107065: lea 0x0(%esi,1),%esi
455 0x90107069: lea 0x0(%edi,1),%edi
457 0x90107071: jmp 0x90107080
465 Dump 80 16 bit values at the start of the video memory.
467 (qemu) xp/80hx 0xb8000
468 0x000b8000: 0x0b50 0x0b6c 0x0b65 0x0b78 0x0b38 0x0b36 0x0b2f 0x0b42
469 0x000b8010: 0x0b6f 0x0b63 0x0b68 0x0b73 0x0b20 0x0b56 0x0b47 0x0b41
470 0x000b8020: 0x0b42 0x0b69 0x0b6f 0x0b73 0x0b20 0x0b63 0x0b75 0x0b72
471 0x000b8030: 0x0b72 0x0b65 0x0b6e 0x0b74 0x0b2d 0x0b63 0x0b76 0x0b73
472 0x000b8040: 0x0b20 0x0b30 0x0b35 0x0b20 0x0b4e 0x0b6f 0x0b76 0x0b20
473 0x000b8050: 0x0b32 0x0b30 0x0b30 0x0b33 0x0720 0x0720 0x0720 0x0720
474 0x000b8060: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
475 0x000b8070: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
476 0x000b8080: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
477 0x000b8090: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
481 @item p or print/fmt expr
483 Print expression value. Only the @var{format} part of @var{fmt} is
488 Send @var{keys} to the emulator. Use @code{-} to press several keys
489 simultaneously. Example:
494 This command is useful to send keys that your graphical user interface
495 intercepts at low level, such as @code{ctrl-alt-f1} in X Window.
503 @subsection Integer expressions
505 The monitor understands integers expressions for every integer
506 argument. You can use register names to get the value of specifics
507 CPU registers by prefixing them with @emph{$}.
512 @subsection Raw disk images
514 The disk images can simply be raw images of the hard disk. You can
515 create them with the command:
517 dd of=myimage bs=1024 seek=mysize count=0
519 where @var{myimage} is the image filename and @var{mysize} is its size
522 @subsection Snapshot mode
524 If you use the option @option{-snapshot}, all disk images are
525 considered as read only. When sectors in written, they are written in
526 a temporary file created in @file{/tmp}. You can however force the
527 write back to the raw disk images by pressing @key{C-a s}.
529 NOTE: The snapshot mode only works with raw disk images.
531 @subsection Copy On Write disk images
533 QEMU also supports user mode Linux
534 (@url{http://user-mode-linux.sourceforge.net/}) Copy On Write (COW)
535 disk images. The COW disk images are much smaller than normal images
536 as they store only modified sectors. They also permit the use of the
537 same disk image template for many users.
539 To create a COW disk images, use the command:
542 qemu-mkcow -f myrawimage.bin mycowimage.cow
545 @file{myrawimage.bin} is a raw image you want to use as original disk
546 image. It will never be written to.
548 @file{mycowimage.cow} is the COW disk image which is created by
549 @code{qemu-mkcow}. You can use it directly with the @option{-hdx}
550 options. You must not modify the original raw disk image if you use
551 COW images, as COW images only store the modified sectors from the raw
552 disk image. QEMU stores the original raw disk image name and its
553 modified time in the COW disk image so that chances of mistakes are
556 If the raw disk image is not read-only, by pressing @key{C-a s} you
557 can flush the COW disk image back into the raw disk image, as in
560 COW disk images can also be created without a corresponding raw disk
561 image. It is useful to have a big initial virtual disk image without
562 using much disk space. Use:
565 qemu-mkcow mycowimage.cow 1024
568 to create a 1 gigabyte empty COW disk image.
573 COW disk images must be created on file systems supporting
574 @emph{holes} such as ext2 or ext3.
576 Since holes are used, the displayed size of the COW disk image is not
577 the real one. To know it, use the @code{ls -ls} command.
580 @subsection Convert VMware disk images to raw disk images
582 You can use the tool @file{vmdk2raw} to convert VMware disk images to
583 raw disk images directly usable by QEMU. The syntax is:
585 vmdk2raw vmware_image output_image
588 @section Network emulation
590 QEMU simulates up to 6 networks cards (NE2000 boards). Each card can
591 be connected to a specific host network interface.
593 @subsection Using tun/tap network interface
595 This is the standard way to emulate network. QEMU adds a virtual
596 network device on your host (called @code{tun0}), and you can then
597 configure it as if it was a real ethernet card.
599 As an example, you can download the @file{linux-test-xxx.tar.gz}
600 archive and copy the script @file{qemu-ifup} in @file{/etc} and
601 configure properly @code{sudo} so that the command @code{ifconfig}
602 contained in @file{qemu-ifup} can be executed as root. You must verify
603 that your host kernel supports the TUN/TAP network interfaces: the
604 device @file{/dev/net/tun} must be present.
606 See @ref{direct_linux_boot} to have an example of network use with a
609 @subsection Using the user mode network stack
611 By using the option @option{-user-net} or if you have no tun/tap init
612 script, QEMU uses a completely user mode network stack (you don't need
613 root priviledge to use the virtual network). The virtual network
614 configuration is the following:
618 QEMU Virtual Machine <------> Firewall/DHCP server <-----> Internet
619 (10.0.2.x) | (10.0.2.2)
625 The QEMU VM behaves as if it was behind a firewall which blocks all
626 incoming connections. You can use a DHCP client to automatically
627 configure the network in the QEMU VM.
629 In order to check that the user mode network is working, you can ping
630 the address 10.0.2.2 and verify that you got an address in the range
631 10.0.2.x from the QEMU virtual DHCP server.
633 Note that @code{ping} is not supported reliably to the internet as it
634 would require root priviledges. It means you can only ping the local
637 The user mode network is currently only supported on a Unix host.
639 @node direct_linux_boot
640 @section Direct Linux Boot
642 This section explains how to launch a Linux kernel inside QEMU without
643 having to make a full bootable image. It is very useful for fast Linux
644 kernel testing. The QEMU network configuration is also explained.
648 Download the archive @file{linux-test-xxx.tar.gz} containing a Linux
649 kernel and a disk image.
651 @item Optional: If you want network support (for example to launch X11 examples), you
652 must copy the script @file{qemu-ifup} in @file{/etc} and configure
653 properly @code{sudo} so that the command @code{ifconfig} contained in
654 @file{qemu-ifup} can be executed as root. You must verify that your host
655 kernel supports the TUN/TAP network interfaces: the device
656 @file{/dev/net/tun} must be present.
658 When network is enabled, there is a virtual network connection between
659 the host kernel and the emulated kernel. The emulated kernel is seen
660 from the host kernel at IP address 172.20.0.2 and the host kernel is
661 seen from the emulated kernel at IP address 172.20.0.1.
663 @item Launch @code{qemu.sh}. You should have the following output:
667 Connected to host network interface: tun0
668 Linux version 2.4.21 (bellard@voyager.localdomain) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #5 Tue Nov 11 18:18:53 CET 2003
669 BIOS-provided physical RAM map:
670 BIOS-e801: 0000000000000000 - 000000000009f000 (usable)
671 BIOS-e801: 0000000000100000 - 0000000002000000 (usable)
672 32MB LOWMEM available.
673 On node 0 totalpages: 8192
677 Kernel command line: root=/dev/hda sb=0x220,5,1,5 ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe console=ttyS0
678 ide_setup: ide2=noprobe
679 ide_setup: ide3=noprobe
680 ide_setup: ide4=noprobe
681 ide_setup: ide5=noprobe
683 Detected 2399.621 MHz processor.
684 Console: colour EGA 80x25
685 Calibrating delay loop... 4744.80 BogoMIPS
686 Memory: 28872k/32768k available (1210k kernel code, 3508k reserved, 266k data, 64k init, 0k highmem)
687 Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
688 Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
689 Mount cache hash table entries: 512 (order: 0, 4096 bytes)
690 Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
691 Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
692 CPU: Intel Pentium Pro stepping 03
693 Checking 'hlt' instruction... OK.
694 POSIX conformance testing by UNIFIX
695 Linux NET4.0 for Linux 2.4
696 Based upon Swansea University Computer Society NET3.039
697 Initializing RT netlink socket
700 Journalled Block Device driver loaded
701 Detected PS/2 Mouse Port.
702 pty: 256 Unix98 ptys configured
703 Serial driver version 5.05c (2001-07-08) with no serial options enabled
704 ttyS00 at 0x03f8 (irq = 4) is a 16450
705 ne.c:v1.10 9/23/94 Donald Becker (becker@scyld.com)
706 Last modified Nov 1, 2000 by Paul Gortmaker
707 NE*000 ethercard probe at 0x300: 52 54 00 12 34 56
708 eth0: NE2000 found at 0x300, using IRQ 9.
709 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
710 Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
711 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
712 hda: QEMU HARDDISK, ATA DISK drive
713 ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
714 hda: attached ide-disk driver.
715 hda: 20480 sectors (10 MB) w/256KiB Cache, CHS=20/16/63
718 Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
719 NET4: Linux TCP/IP 1.0 for NET4.0
720 IP Protocols: ICMP, UDP, TCP, IGMP
721 IP: routing cache hash table of 512 buckets, 4Kbytes
722 TCP: Hash tables configured (established 2048 bind 4096)
723 NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
724 EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
725 VFS: Mounted root (ext2 filesystem).
726 Freeing unused kernel memory: 64k freed
728 Linux version 2.4.21 (bellard@voyager.localdomain) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #5 Tue Nov 11 18:18:53 CET 2003
730 QEMU Linux test distribution (based on Redhat 9)
732 Type 'exit' to halt the system
738 Then you can play with the kernel inside the virtual serial console. You
739 can launch @code{ls} for example. Type @key{Ctrl-a h} to have an help
740 about the keys you can type inside the virtual serial console. In
741 particular, use @key{Ctrl-a x} to exit QEMU and use @key{Ctrl-a b} as
745 If the network is enabled, launch the script @file{/etc/linuxrc} in the
746 emulator (don't forget the leading dot):
751 Then enable X11 connections on your PC from the emulated Linux:
756 You can now launch @file{xterm} or @file{xlogo} and verify that you have
757 a real Virtual Linux system !
764 A 2.5.74 kernel is also included in the archive. Just
765 replace the bzImage in qemu.sh to try it.
768 qemu-fast creates a temporary file in @var{$QEMU_TMPDIR} (@file{/tmp} is the
769 default) containing all the simulated PC memory. If possible, try to use
770 a temporary directory using the tmpfs filesystem to avoid too many
771 unnecessary disk accesses.
774 In order to exit cleanly from qemu, you can do a @emph{shutdown} inside
775 qemu. qemu will automatically exit when the Linux shutdown is done.
778 You can boot slightly faster by disabling the probe of non present IDE
779 interfaces. To do so, add the following options on the kernel command
782 ide1=noprobe ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe
786 The example disk image is a modified version of the one made by Kevin
787 Lawton for the plex86 Project (@url{www.plex86.org}).
792 @section Linux Kernel Compilation
794 You can use any linux kernel with QEMU. However, if you want to use
795 @code{qemu-fast} to get maximum performances, you must use a modified
796 guest kernel. If you are using a 2.6 guest kernel, you can use
797 directly the patch @file{linux-2.6-qemu-fast.patch} made by Rusty
798 Russel available in the QEMU source archive. Otherwise, you can make the
799 following changes @emph{by hand} to the Linux kernel:
803 The kernel must be mapped at 0x90000000 (the default is
804 0xc0000000). You must modify only two lines in the kernel source:
806 In @file{include/asm/page.h}, replace
808 #define __PAGE_OFFSET (0xc0000000)
812 #define __PAGE_OFFSET (0x90000000)
815 And in @file{arch/i386/vmlinux.lds}, replace
817 . = 0xc0000000 + 0x100000;
821 . = 0x90000000 + 0x100000;
825 If you want to enable SMP (Symmetric Multi-Processing) support, you
826 must make the following change in @file{include/asm/fixmap.h}. Replace
828 #define FIXADDR_TOP (0xffffX000UL)
832 #define FIXADDR_TOP (0xa7ffX000UL)
834 (X is 'e' or 'f' depending on the kernel version). Although you can
835 use an SMP kernel with QEMU, it only supports one CPU.
838 If you are not using a 2.6 kernel as host kernel but if you use a target
839 2.6 kernel, you must also ensure that the 'HZ' define is set to 100
840 (1000 is the default) as QEMU cannot currently emulate timers at
841 frequencies greater than 100 Hz on host Linux systems < 2.6. In
842 @file{include/asm/param.h}, replace:
845 # define HZ 1000 /* Internal kernel timer frequency */
849 # define HZ 100 /* Internal kernel timer frequency */
854 The file config-2.x.x gives the configuration of the example kernels.
861 As you would do to make a real kernel. Then you can use with QEMU
862 exactly the same kernel as you would boot on your PC (in
863 @file{arch/i386/boot/bzImage}).
868 QEMU has a primitive support to work with gdb, so that you can do
869 'Ctrl-C' while the virtual machine is running and inspect its state.
871 In order to use gdb, launch qemu with the '-s' option. It will wait for a
874 > qemu -s -kernel arch/i386/boot/bzImage -hda root-2.4.20.img -append "root=/dev/hda"
875 Connected to host network interface: tun0
876 Waiting gdb connection on port 1234
879 Then launch gdb on the 'vmlinux' executable:
884 In gdb, connect to QEMU:
886 (gdb) target remote localhost:1234
889 Then you can use gdb normally. For example, type 'c' to launch the kernel:
894 Here are some useful tips in order to use gdb on system code:
898 Use @code{info reg} to display all the CPU registers.
900 Use @code{x/10i $eip} to display the code at the PC position.
902 Use @code{set architecture i8086} to dump 16 bit code. Then use
903 @code{x/10i $cs*16+*eip} to dump the code at the PC position.
906 @section Target OS specific information
910 To have access to SVGA graphic modes under X11, use the @code{vesa} or
911 the @code{cirrus} X11 driver. For optimal performances, use 16 bit
912 color depth in the guest and the host OS.
914 When using a 2.6 guest Linux kernel, you should add the option
915 @code{clock=pit} on the kernel command line because the 2.6 Linux
916 kernels make very strict real time clock checks by default that QEMU
917 cannot simulate exactly.
921 If you have a slow host, using Windows 95 is better as it gives the
922 best speed. Windows 2000 is also a good choice.
924 @subsubsection SVGA graphic modes support
926 QEMU emulates a Cirrus Logic GD5446 Video
927 card. All Windows versions starting from Windows 95 should recognize
928 and use this graphic card. For optimal performances, use 16 bit color
929 depth in the guest and the host OS.
931 @subsubsection CPU usage reduction
933 Windows 9x does not correctly use the CPU HLT
934 instruction. The result is that it takes host CPU cycles even when
935 idle. You can install the utility from
936 @url{http://www.user.cityline.ru/~maxamn/amnhltm.zip} to solve this
937 problem. Note that no such tool is needed for NT, 2000 or XP.
939 @subsubsection Windows 2000 disk full problems
941 Currently (release 0.6.0) QEMU has a bug which gives a @code{disk
942 full} error during installation of some releases of Windows 2000. The
943 workaround is to stop QEMU as soon as you notice that your disk image
944 size is growing too fast (monitor it with @code{ls -ls}). Then
945 relaunch QEMU to continue the installation. If you still experience
946 the problem, relaunch QEMU again.
948 Future QEMU releases are likely to correct this bug.
950 @subsubsection Windows XP security problems
952 Some releases of Windows XP install correctly but give a security
955 A problem is preventing Windows from accurately checking the
956 license for this computer. Error code: 0x800703e6.
958 The only known workaround is to boot in Safe mode
959 without networking support.
961 Future QEMU releases are likely to correct this bug.
963 @subsection MS-DOS and FreeDOS
965 @subsubsection CPU usage reduction
967 DOS does not correctly use the CPU HLT instruction. The result is that
968 it takes host CPU cycles even when idle. You can install the utility
969 from @url{http://www.vmware.com/software/dosidle210.zip} to solve this
972 @chapter QEMU PowerPC System emulator invocation
974 Use the executable @file{qemu-system-ppc} to simulate a complete PREP
975 or PowerMac PowerPC system.
977 QEMU emulates the following PowerMac peripherials:
983 PCI VGA compatible card with VESA Bochs Extensions
985 2 PMAC IDE interfaces with hard disk and CD-ROM support
991 VIA-CUDA with ADB keyboard and mouse.
994 QEMU emulates the following PREP peripherials:
1000 PCI VGA compatible card with VESA Bochs Extensions
1002 2 IDE interfaces with hard disk and CD-ROM support
1006 NE2000 network adapters
1010 PREP Non Volatile RAM
1012 PC compatible keyboard and mouse.
1015 QEMU uses the Open Hack'Ware Open Firmware Compatible BIOS available at
1016 @url{http://site.voila.fr/jmayer/OpenHackWare/index.htm}.
1018 You can read the qemu PC system emulation chapter to have more
1019 informations about QEMU usage.
1021 @c man begin OPTIONS
1023 The following options are specific to the PowerPC emulation:
1028 Simulate a PREP system (default is PowerMAC)
1030 @item -g WxH[xDEPTH]
1032 Set the initial VGA graphic mode. The default is 800x600x15.
1039 More information is available at
1040 @url{http://jocelyn.mayer.free.fr/qemu-ppc/}.
1042 @chapter QEMU User space emulator invocation
1044 @section Quick Start
1046 In order to launch a Linux process, QEMU needs the process executable
1047 itself and all the target (x86) dynamic libraries used by it.
1051 @item On x86, you can just try to launch any process by using the native
1055 qemu-i386 -L / /bin/ls
1058 @code{-L /} tells that the x86 dynamic linker must be searched with a
1061 @item Since QEMU is also a linux process, you can launch qemu with qemu (NOTE: you can only do that if you compiled QEMU from the sources):
1064 qemu-i386 -L / qemu-i386 -L / /bin/ls
1067 @item On non x86 CPUs, you need first to download at least an x86 glibc
1068 (@file{qemu-runtime-i386-XXX-.tar.gz} on the QEMU web page). Ensure that
1069 @code{LD_LIBRARY_PATH} is not set:
1072 unset LD_LIBRARY_PATH
1075 Then you can launch the precompiled @file{ls} x86 executable:
1078 qemu-i386 tests/i386/ls
1080 You can look at @file{qemu-binfmt-conf.sh} so that
1081 QEMU is automatically launched by the Linux kernel when you try to
1082 launch x86 executables. It requires the @code{binfmt_misc} module in the
1085 @item The x86 version of QEMU is also included. You can try weird things such as:
1087 qemu-i386 /usr/local/qemu-i386/bin/qemu-i386 /usr/local/qemu-i386/bin/ls-i386
1092 @section Wine launch
1096 @item Ensure that you have a working QEMU with the x86 glibc
1097 distribution (see previous section). In order to verify it, you must be
1101 qemu-i386 /usr/local/qemu-i386/bin/ls-i386
1104 @item Download the binary x86 Wine install
1105 (@file{qemu-XXX-i386-wine.tar.gz} on the QEMU web page).
1107 @item Configure Wine on your account. Look at the provided script
1108 @file{/usr/local/qemu-i386/bin/wine-conf.sh}. Your previous
1109 @code{$@{HOME@}/.wine} directory is saved to @code{$@{HOME@}/.wine.org}.
1111 @item Then you can try the example @file{putty.exe}:
1114 qemu-i386 /usr/local/qemu-i386/wine/bin/wine /usr/local/qemu-i386/wine/c/Program\ Files/putty.exe
1119 @section Command line options
1122 usage: qemu-i386 [-h] [-d] [-L path] [-s size] program [arguments...]
1129 Set the x86 elf interpreter prefix (default=/usr/local/qemu-i386)
1131 Set the x86 stack size in bytes (default=524288)
1138 Activate log (logfile=/tmp/qemu.log)
1140 Act as if the host page size was 'pagesize' bytes
1144 @chapter Compilation from the sources
1148 Read the @file{README} which gives the related information.
1153 @item Install the current versions of MSYS and MinGW from
1154 @url{http://www.mingw.org/}. You can find detailed installation
1155 instructions in the download section and the FAQ.
1158 the MinGW development library of SDL 1.2.x
1159 (@file{SDL-devel-1.2.x-mingw32.tar.gz}) from
1160 @url{http://www.libsdl.org}. Unpack it in a temporary place, and
1161 unpack the archive @file{i386-mingw32msvc.tar.gz} in the MinGW tool
1162 directory. Edit the @file{sdl-config} script so that it gives the
1163 correct SDL directory when invoked.
1165 @item Extract the current version of QEMU.
1167 @item Start the MSYS shell (file @file{msys.bat}).
1169 @item Change to the QEMU directory. Launch @file{./configure} and
1170 @file{make}. If you have problems using SDL, verify that
1171 @file{sdl-config} can be launched from the MSYS command line.
1173 @item You can install QEMU in @file{Program Files/Qemu} by typing
1174 @file{make install}. Don't forget to copy @file{SDL.dll} in
1175 @file{Program Files/Qemu}.
1179 @section Cross compilation for Windows with Linux
1183 Install the MinGW cross compilation tools available at
1184 @url{http://www.mingw.org/}.
1187 Install the Win32 version of SDL (@url{http://www.libsdl.org}) by
1188 unpacking @file{i386-mingw32msvc.tar.gz}. Set up the PATH environment
1189 variable so that @file{i386-mingw32msvc-sdl-config} can be launched by
1190 the QEMU configuration script.
1193 Configure QEMU for Windows cross compilation:
1195 ./configure --enable-mingw32
1197 If necessary, you can change the cross-prefix according to the prefix
1198 choosen for the MinGW tools with --cross-prefix. You can also use
1199 --prefix to set the Win32 install path.
1201 @item You can install QEMU in the installation directory by typing
1202 @file{make install}. Don't forget to copy @file{SDL.dll} in the
1203 installation directory.
1207 Note: Currently, Wine does not seem able to launch
1212 The Mac OS X patches are not fully merged in QEMU, so you should look
1213 at the QEMU mailing list archive to have all the necessary