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 peripherals. 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 QEMU can run without an host kernel driver and yet gives acceptable
40 For system emulation, the following hardware targets are supported:
42 @item PC (x86 or x86_64 processor)
43 @item PREP (PowerPC processor)
44 @item G3 BW PowerMac (PowerPC processor)
45 @item Mac99 PowerMac (PowerPC processor, in progress)
46 @item Sun4m (32-bit Sparc processor)
47 @item Sun4u (64-bit Sparc processor, in progress)
48 @item Malta board (32-bit MIPS processor, in progress)
51 For user emulation, x86, PowerPC, ARM, and Sparc32/64 CPUs are supported.
55 If you want to compile QEMU yourself, see @ref{compilation}.
59 If a precompiled package is available for your distribution - you just
60 have to install it. Otherwise, see @ref{compilation}.
64 Download the experimental binary installer at
65 @url{http://www.freeoszoo.org/download.php}.
69 Download the experimental binary installer at
70 @url{http://www.freeoszoo.org/download.php}.
72 @chapter QEMU PC System emulator invocation
76 @c man begin DESCRIPTION
78 The QEMU System emulator simulates the
79 following PC peripherals:
83 i440FX host PCI bridge and PIIX3 PCI to ISA bridge
85 Cirrus CLGD 5446 PCI VGA card or dummy VGA card with Bochs VESA
86 extensions (hardware level, including all non standard modes).
88 PS/2 mouse and keyboard
90 2 PCI IDE interfaces with hard disk and CD-ROM support
94 NE2000 PCI network adapters
101 QEMU uses the PC BIOS from the Bochs project and the Plex86/Bochs LGPL
108 Download and uncompress the linux image (@file{linux.img}) and type:
114 Linux should boot and give you a prompt.
119 @c man begin SYNOPSIS
120 usage: qemu [options] [disk_image]
125 @var{disk_image} is a raw hard disk image for IDE hard disk 0.
131 Use @var{file} as floppy disk 0/1 image (@xref{disk_images}). You can
132 use the host floppy by using @file{/dev/fd0} as filename.
138 Use @var{file} as hard disk 0, 1, 2 or 3 image (@xref{disk_images}).
141 Use @var{file} as CD-ROM image (you cannot use @option{-hdc} and and
142 @option{-cdrom} at the same time). You can use the host CD-ROM by
143 using @file{/dev/cdrom} as filename.
146 Boot on floppy (a), hard disk (c) or CD-ROM (d). Hard disk boot is
150 Write to temporary files instead of disk image files. In this case,
151 the raw disk image you use is not written back. You can however force
152 the write back by pressing @key{C-a s} (@xref{disk_images}).
155 Set virtual RAM size to @var{megs} megabytes. Default is 128 MB.
159 Normally, QEMU uses SDL to display the VGA output. With this option,
160 you can totally disable graphical output so that QEMU is a simple
161 command line application. The emulated serial port is redirected on
162 the console. Therefore, you can still use QEMU to debug a Linux kernel
163 with a serial console.
167 Use keyboard layout @var{language} (for example @code{fr} for
168 French). This option is only needed where it is not easy to get raw PC
169 keycodes (e.g. on Macs or with some X11 servers). You don't need to
170 use it on PC/Linux or PC/Windows hosts.
172 The available layouts are:
174 ar de-ch es fo fr-ca hu ja mk no pt-br sv
175 da en-gb et fr fr-ch is lt nl pl ru th
176 de en-us fi fr-be hr it lv nl-be pt sl tr
179 The default is @code{en-us}.
183 The SB16 emulation is disabled by default as it may give problems with
184 Windows. You can enable it manually with this option.
187 Set the real time clock to local time (the default is to UTC
188 time). This option is needed to have correct date in MS-DOS or
192 Start in full screen.
195 Store the QEMU process PID in @var{file}. It is useful if you launch QEMU
199 Use it when installing Windows 2000 to avoid a disk full bug. After
200 Windows 2000 is installed, you no longer need this option (this option
201 slows down the IDE transfers).
210 Set TUN/TAP network init script [default=/etc/qemu-ifup]. This script
211 is launched to configure the host network interface (usually tun0)
212 corresponding to the virtual NE2000 card.
216 Simulate @var{n} network cards (the default is 1).
220 Set the mac address of the first interface (the format is
221 aa:bb:cc:dd:ee:ff in hexa). The mac address is incremented for each
222 new network interface.
225 Assumes @var{fd} talks to a tap/tun host network interface and use
226 it. Read @url{http://bellard.org/qemu/tetrinet.html} to have an
230 Use the user mode network stack. This is the default if no tun/tap
231 network init script is found.
234 When using the user mode network stack, activate a built-in TFTP
235 server. All filenames beginning with @var{prefix} can be downloaded
236 from the host to the guest using a TFTP client. The TFTP client on the
237 guest must be configured in binary mode (use the command @code{bin} of
238 the Unix TFTP client). The host IP address on the guest is as usual
242 When using the user mode network stack, activate a built-in SMB
243 server so that Windows OSes can access to the host files in @file{dir}
246 In the guest Windows OS, the line:
250 must be added in the file @file{C:\WINDOWS\LMHOSTS} (for windows 9x/Me)
251 or @file{C:\WINNT\SYSTEM32\DRIVERS\ETC\LMHOSTS} (Windows NT/2000).
253 Then @file{dir} can be accessed in @file{\\smbserver\qemu}.
255 Note that a SAMBA server must be installed on the host OS in
256 @file{/usr/sbin/smbd}. QEMU was tested succesfully with smbd version
257 2.2.7a from the Red Hat 9.
259 @item -redir [tcp|udp]:host-port:[guest-host]:guest-port
261 When using the user mode network stack, redirect incoming TCP or UDP
262 connections to the host port @var{host-port} to the guest
263 @var{guest-host} on guest port @var{guest-port}. If @var{guest-host}
264 is not specified, its value is 10.0.2.15 (default address given by the
265 built-in DHCP server).
267 For example, to redirect host X11 connection from screen 1 to guest
268 screen 0, use the following:
272 qemu -redir tcp:6001::6000 [...]
273 # this host xterm should open in the guest X11 server
277 To redirect telnet connections from host port 5555 to telnet port on
278 the guest, use the following:
282 qemu -redir tcp:5555::23 [...]
283 telnet localhost 5555
286 Then when you use on the host @code{telnet localhost 5555}, you
287 connect to the guest telnet server.
290 Use the dummy network stack: no packet will be received by the network
295 Linux boot specific. When using this options, you can use a given
296 Linux kernel without installing it in the disk image. It can be useful
297 for easier testing of various kernels.
301 @item -kernel bzImage
302 Use @var{bzImage} as kernel image.
304 @item -append cmdline
305 Use @var{cmdline} as kernel command line
308 Use @var{file} as initial ram disk.
312 Debug/Expert options:
316 Redirect the virtual serial port to host device @var{dev}. Available
322 [Linux only] Pseudo TTY (a new PTY is automatically allocated)
326 [Unix only] standard input/output
328 The default device is @code{vc} in graphical mode and @code{stdio} in
331 This option can be used several times to simulate up to 4 serials
335 Redirect the monitor to host device @var{dev} (same devices as the
337 The default device is @code{vc} in graphical mode and @code{stdio} in
341 Wait gdb connection to port 1234 (@xref{gdb_usage}).
343 Change gdb connection port.
345 Do not start CPU at startup (you must type 'c' in the monitor).
347 Output log in /tmp/qemu.log
348 @item -hdachs c,h,s,[,t]
349 Force hard disk 0 physical geometry (1 <= @var{c} <= 16383, 1 <=
350 @var{h} <= 16, 1 <= @var{s} <= 63) and optionally force the BIOS
351 translation mode (@var{t}=none, lba or auto). Usually QEMU can guess
352 all thoses parameters. This option is useful for old MS-DOS disk
356 Simulate an ISA-only system (default is PCI system).
358 Simulate a standard VGA card with Bochs VBE extensions (default is
359 Cirrus Logic GD5446 PCI VGA)
361 Start right away with a saved state (@code{loadvm} in monitor)
370 During the graphical emulation, you can use the following keys:
376 Switch to virtual console 'n'. Standard console mappings are:
379 Target system display
387 Toggle mouse and keyboard grab.
390 In the virtual consoles, you can use @key{Ctrl-Up}, @key{Ctrl-Down},
391 @key{Ctrl-PageUp} and @key{Ctrl-PageDown} to move in the back log.
393 During emulation, if you are using the @option{-nographic} option, use
394 @key{Ctrl-a h} to get terminal commands:
402 Save disk data back to file (if -snapshot)
404 Send break (magic sysrq in Linux)
406 Switch between console and monitor
415 @settitle QEMU System Emulator
418 The HTML documentation of QEMU for more precise information and Linux
419 user mode emulator invocation.
430 @section QEMU Monitor
432 The QEMU monitor is used to give complex commands to the QEMU
433 emulator. You can use it to:
438 Remove or insert removable medias images
439 (such as CD-ROM or floppies)
442 Freeze/unfreeze the Virtual Machine (VM) and save or restore its state
445 @item Inspect the VM state without an external debugger.
451 The following commands are available:
455 @item help or ? [cmd]
456 Show the help for all commands or just for command @var{cmd}.
459 Commit changes to the disk images (if -snapshot is used)
461 @item info subcommand
462 show various information about the system state
466 show the network state
468 show the block devices
470 show the cpu registers
472 show the command line history
478 @item eject [-f] device
479 Eject a removable media (use -f to force it).
481 @item change device filename
482 Change a removable media.
484 @item screendump filename
485 Save screen into PPM image @var{filename}.
487 @item log item1[,...]
488 Activate logging of the specified items to @file{/tmp/qemu.log}.
490 @item savevm filename
491 Save the whole virtual machine state to @var{filename}.
493 @item loadvm filename
494 Restore the whole virtual machine state from @var{filename}.
502 @item gdbserver [port]
503 Start gdbserver session (default port=1234)
506 Virtual memory dump starting at @var{addr}.
509 Physical memory dump starting at @var{addr}.
511 @var{fmt} is a format which tells the command how to format the
512 data. Its syntax is: @option{/@{count@}@{format@}@{size@}}
516 is the number of items to be dumped.
519 can be x (hexa), d (signed decimal), u (unsigned decimal), o (octal),
520 c (char) or i (asm instruction).
523 can be b (8 bits), h (16 bits), w (32 bits) or g (64 bits). On x86,
524 @code{h} or @code{w} can be specified with the @code{i} format to
525 respectively select 16 or 32 bit code instruction size.
532 Dump 10 instructions at the current instruction pointer:
537 0x90107065: lea 0x0(%esi,1),%esi
538 0x90107069: lea 0x0(%edi,1),%edi
540 0x90107071: jmp 0x90107080
548 Dump 80 16 bit values at the start of the video memory.
550 (qemu) xp/80hx 0xb8000
551 0x000b8000: 0x0b50 0x0b6c 0x0b65 0x0b78 0x0b38 0x0b36 0x0b2f 0x0b42
552 0x000b8010: 0x0b6f 0x0b63 0x0b68 0x0b73 0x0b20 0x0b56 0x0b47 0x0b41
553 0x000b8020: 0x0b42 0x0b69 0x0b6f 0x0b73 0x0b20 0x0b63 0x0b75 0x0b72
554 0x000b8030: 0x0b72 0x0b65 0x0b6e 0x0b74 0x0b2d 0x0b63 0x0b76 0x0b73
555 0x000b8040: 0x0b20 0x0b30 0x0b35 0x0b20 0x0b4e 0x0b6f 0x0b76 0x0b20
556 0x000b8050: 0x0b32 0x0b30 0x0b30 0x0b33 0x0720 0x0720 0x0720 0x0720
557 0x000b8060: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
558 0x000b8070: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
559 0x000b8080: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
560 0x000b8090: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
564 @item p or print/fmt expr
566 Print expression value. Only the @var{format} part of @var{fmt} is
571 Send @var{keys} to the emulator. Use @code{-} to press several keys
572 simultaneously. Example:
577 This command is useful to send keys that your graphical user interface
578 intercepts at low level, such as @code{ctrl-alt-f1} in X Window.
586 @subsection Integer expressions
588 The monitor understands integers expressions for every integer
589 argument. You can use register names to get the value of specifics
590 CPU registers by prefixing them with @emph{$}.
595 Since version 0.6.1, QEMU supports many disk image formats, including
596 growable disk images (their size increase as non empty sectors are
597 written), compressed and encrypted disk images.
599 @subsection Quick start for disk image creation
601 You can create a disk image with the command:
603 qemu-img create myimage.img mysize
605 where @var{myimage.img} is the disk image filename and @var{mysize} is its
606 size in kilobytes. You can add an @code{M} suffix to give the size in
607 megabytes and a @code{G} suffix for gigabytes.
609 @xref{qemu_img_invocation} for more information.
611 @subsection Snapshot mode
613 If you use the option @option{-snapshot}, all disk images are
614 considered as read only. When sectors in written, they are written in
615 a temporary file created in @file{/tmp}. You can however force the
616 write back to the raw disk images by using the @code{commit} monitor
617 command (or @key{C-a s} in the serial console).
619 @node qemu_img_invocation
620 @subsection @code{qemu-img} Invocation
622 @include qemu-img.texi
624 @section Network emulation
626 QEMU simulates up to 6 networks cards (NE2000 boards). Each card can
627 be connected to a specific host network interface.
629 @subsection Using tun/tap network interface
631 This is the standard way to emulate network. QEMU adds a virtual
632 network device on your host (called @code{tun0}), and you can then
633 configure it as if it was a real ethernet card.
635 As an example, you can download the @file{linux-test-xxx.tar.gz}
636 archive and copy the script @file{qemu-ifup} in @file{/etc} and
637 configure properly @code{sudo} so that the command @code{ifconfig}
638 contained in @file{qemu-ifup} can be executed as root. You must verify
639 that your host kernel supports the TUN/TAP network interfaces: the
640 device @file{/dev/net/tun} must be present.
642 See @ref{direct_linux_boot} to have an example of network use with a
645 @subsection Using the user mode network stack
647 By using the option @option{-user-net} or if you have no tun/tap init
648 script, QEMU uses a completely user mode network stack (you don't need
649 root priviledge to use the virtual network). The virtual network
650 configuration is the following:
654 QEMU Virtual Machine <------> Firewall/DHCP server <-----> Internet
655 (10.0.2.x) | (10.0.2.2)
657 ----> DNS server (10.0.2.3)
659 ----> SMB server (10.0.2.4)
662 The QEMU VM behaves as if it was behind a firewall which blocks all
663 incoming connections. You can use a DHCP client to automatically
664 configure the network in the QEMU VM.
666 In order to check that the user mode network is working, you can ping
667 the address 10.0.2.2 and verify that you got an address in the range
668 10.0.2.x from the QEMU virtual DHCP server.
670 Note that @code{ping} is not supported reliably to the internet as it
671 would require root priviledges. It means you can only ping the local
674 When using the built-in TFTP server, the router is also the TFTP
677 When using the @option{-redir} option, TCP or UDP connections can be
678 redirected from the host to the guest. It allows for example to
679 redirect X11, telnet or SSH connections.
681 @node direct_linux_boot
682 @section Direct Linux Boot
684 This section explains how to launch a Linux kernel inside QEMU without
685 having to make a full bootable image. It is very useful for fast Linux
686 kernel testing. The QEMU network configuration is also explained.
690 Download the archive @file{linux-test-xxx.tar.gz} containing a Linux
691 kernel and a disk image.
693 @item Optional: If you want network support (for example to launch X11 examples), you
694 must copy the script @file{qemu-ifup} in @file{/etc} and configure
695 properly @code{sudo} so that the command @code{ifconfig} contained in
696 @file{qemu-ifup} can be executed as root. You must verify that your host
697 kernel supports the TUN/TAP network interfaces: the device
698 @file{/dev/net/tun} must be present.
700 When network is enabled, there is a virtual network connection between
701 the host kernel and the emulated kernel. The emulated kernel is seen
702 from the host kernel at IP address 172.20.0.2 and the host kernel is
703 seen from the emulated kernel at IP address 172.20.0.1.
705 @item Launch @code{qemu.sh}. You should have the following output:
709 Connected to host network interface: tun0
710 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
711 BIOS-provided physical RAM map:
712 BIOS-e801: 0000000000000000 - 000000000009f000 (usable)
713 BIOS-e801: 0000000000100000 - 0000000002000000 (usable)
714 32MB LOWMEM available.
715 On node 0 totalpages: 8192
719 Kernel command line: root=/dev/hda sb=0x220,5,1,5 ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe console=ttyS0
720 ide_setup: ide2=noprobe
721 ide_setup: ide3=noprobe
722 ide_setup: ide4=noprobe
723 ide_setup: ide5=noprobe
725 Detected 2399.621 MHz processor.
726 Console: colour EGA 80x25
727 Calibrating delay loop... 4744.80 BogoMIPS
728 Memory: 28872k/32768k available (1210k kernel code, 3508k reserved, 266k data, 64k init, 0k highmem)
729 Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
730 Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
731 Mount cache hash table entries: 512 (order: 0, 4096 bytes)
732 Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
733 Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
734 CPU: Intel Pentium Pro stepping 03
735 Checking 'hlt' instruction... OK.
736 POSIX conformance testing by UNIFIX
737 Linux NET4.0 for Linux 2.4
738 Based upon Swansea University Computer Society NET3.039
739 Initializing RT netlink socket
742 Journalled Block Device driver loaded
743 Detected PS/2 Mouse Port.
744 pty: 256 Unix98 ptys configured
745 Serial driver version 5.05c (2001-07-08) with no serial options enabled
746 ttyS00 at 0x03f8 (irq = 4) is a 16450
747 ne.c:v1.10 9/23/94 Donald Becker (becker@scyld.com)
748 Last modified Nov 1, 2000 by Paul Gortmaker
749 NE*000 ethercard probe at 0x300: 52 54 00 12 34 56
750 eth0: NE2000 found at 0x300, using IRQ 9.
751 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
752 Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
753 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
754 hda: QEMU HARDDISK, ATA DISK drive
755 ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
756 hda: attached ide-disk driver.
757 hda: 20480 sectors (10 MB) w/256KiB Cache, CHS=20/16/63
760 Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
761 NET4: Linux TCP/IP 1.0 for NET4.0
762 IP Protocols: ICMP, UDP, TCP, IGMP
763 IP: routing cache hash table of 512 buckets, 4Kbytes
764 TCP: Hash tables configured (established 2048 bind 4096)
765 NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
766 EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
767 VFS: Mounted root (ext2 filesystem).
768 Freeing unused kernel memory: 64k freed
770 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
772 QEMU Linux test distribution (based on Redhat 9)
774 Type 'exit' to halt the system
780 Then you can play with the kernel inside the virtual serial console. You
781 can launch @code{ls} for example. Type @key{Ctrl-a h} to have an help
782 about the keys you can type inside the virtual serial console. In
783 particular, use @key{Ctrl-a x} to exit QEMU and use @key{Ctrl-a b} as
787 If the network is enabled, launch the script @file{/etc/linuxrc} in the
788 emulator (don't forget the leading dot):
793 Then enable X11 connections on your PC from the emulated Linux:
798 You can now launch @file{xterm} or @file{xlogo} and verify that you have
799 a real Virtual Linux system !
806 A 2.5.74 kernel is also included in the archive. Just
807 replace the bzImage in qemu.sh to try it.
810 In order to exit cleanly from qemu, you can do a @emph{shutdown} inside
811 qemu. qemu will automatically exit when the Linux shutdown is done.
814 You can boot slightly faster by disabling the probe of non present IDE
815 interfaces. To do so, add the following options on the kernel command
818 ide1=noprobe ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe
822 The example disk image is a modified version of the one made by Kevin
823 Lawton for the plex86 Project (@url{www.plex86.org}).
830 QEMU has a primitive support to work with gdb, so that you can do
831 'Ctrl-C' while the virtual machine is running and inspect its state.
833 In order to use gdb, launch qemu with the '-s' option. It will wait for a
836 > qemu -s -kernel arch/i386/boot/bzImage -hda root-2.4.20.img -append "root=/dev/hda"
837 Connected to host network interface: tun0
838 Waiting gdb connection on port 1234
841 Then launch gdb on the 'vmlinux' executable:
846 In gdb, connect to QEMU:
848 (gdb) target remote localhost:1234
851 Then you can use gdb normally. For example, type 'c' to launch the kernel:
856 Here are some useful tips in order to use gdb on system code:
860 Use @code{info reg} to display all the CPU registers.
862 Use @code{x/10i $eip} to display the code at the PC position.
864 Use @code{set architecture i8086} to dump 16 bit code. Then use
865 @code{x/10i $cs*16+*eip} to dump the code at the PC position.
868 @section Target OS specific information
872 To have access to SVGA graphic modes under X11, use the @code{vesa} or
873 the @code{cirrus} X11 driver. For optimal performances, use 16 bit
874 color depth in the guest and the host OS.
876 When using a 2.6 guest Linux kernel, you should add the option
877 @code{clock=pit} on the kernel command line because the 2.6 Linux
878 kernels make very strict real time clock checks by default that QEMU
879 cannot simulate exactly.
881 When using a 2.6 guest Linux kernel, verify that the 4G/4G patch is
882 not activated because QEMU is slower with this patch. The QEMU
883 Accelerator Module is also much slower in this case. Earlier Fedora
884 Core 3 Linux kernel (< 2.6.9-1.724_FC3) were known to incorporte this
885 patch by default. Newer kernels don't have it.
889 If you have a slow host, using Windows 95 is better as it gives the
890 best speed. Windows 2000 is also a good choice.
892 @subsubsection SVGA graphic modes support
894 QEMU emulates a Cirrus Logic GD5446 Video
895 card. All Windows versions starting from Windows 95 should recognize
896 and use this graphic card. For optimal performances, use 16 bit color
897 depth in the guest and the host OS.
899 @subsubsection CPU usage reduction
901 Windows 9x does not correctly use the CPU HLT
902 instruction. The result is that it takes host CPU cycles even when
903 idle. You can install the utility from
904 @url{http://www.user.cityline.ru/~maxamn/amnhltm.zip} to solve this
905 problem. Note that no such tool is needed for NT, 2000 or XP.
907 @subsubsection Windows 2000 disk full problem
909 Windows 2000 has a bug which gives a disk full problem during its
910 installation. When installing it, use the @option{-win2k-hack} QEMU
911 option to enable a specific workaround. After Windows 2000 is
912 installed, you no longer need this option (this option slows down the
915 @subsubsection Windows XP security problems
917 Some releases of Windows XP install correctly but give a security
920 A problem is preventing Windows from accurately checking the
921 license for this computer. Error code: 0x800703e6.
923 The only known workaround is to boot in Safe mode
924 without networking support.
926 Future QEMU releases are likely to correct this bug.
928 @subsection MS-DOS and FreeDOS
930 @subsubsection CPU usage reduction
932 DOS does not correctly use the CPU HLT instruction. The result is that
933 it takes host CPU cycles even when idle. You can install the utility
934 from @url{http://www.vmware.com/software/dosidle210.zip} to solve this
937 @chapter QEMU PowerPC System emulator invocation
939 Use the executable @file{qemu-system-ppc} to simulate a complete PREP
940 or PowerMac PowerPC system.
942 QEMU emulates the following PowerMac peripherals:
948 PCI VGA compatible card with VESA Bochs Extensions
950 2 PMAC IDE interfaces with hard disk and CD-ROM support
956 VIA-CUDA with ADB keyboard and mouse.
959 QEMU emulates the following PREP peripherals:
965 PCI VGA compatible card with VESA Bochs Extensions
967 2 IDE interfaces with hard disk and CD-ROM support
971 NE2000 network adapters
975 PREP Non Volatile RAM
977 PC compatible keyboard and mouse.
980 QEMU uses the Open Hack'Ware Open Firmware Compatible BIOS available at
981 @url{http://site.voila.fr/jmayer/OpenHackWare/index.htm}.
983 You can read the qemu PC system emulation chapter to have more
984 informations about QEMU usage.
988 The following options are specific to the PowerPC emulation:
993 Simulate a PREP system (default is PowerMAC)
997 Set the initial VGA graphic mode. The default is 800x600x15.
1004 More information is available at
1005 @url{http://jocelyn.mayer.free.fr/qemu-ppc/}.
1007 @chapter Sparc32 System emulator invocation
1009 Use the executable @file{qemu-system-sparc} to simulate a JavaStation
1010 (sun4m architecture). The emulation is somewhat complete.
1012 QEMU emulates the following sun4m peripherals:
1020 Lance (Am7990) Ethernet
1022 Non Volatile RAM M48T08
1024 Slave I/O: timers, interrupt controllers, Zilog serial ports, keyboard
1025 and power/reset logic
1027 ESP SCSI controller with hard disk and CD-ROM support
1032 The number of peripherals is fixed in the architecture.
1034 QEMU uses the Proll, a PROM replacement available at
1035 @url{http://people.redhat.com/zaitcev/linux/}. The required
1036 QEMU-specific patches are included with the sources.
1038 A sample Linux 2.6 series kernel and ram disk image are available on
1039 the QEMU web site. Please note that currently neither Linux 2.4
1040 series, NetBSD, nor OpenBSD kernels work.
1042 @c man begin OPTIONS
1044 The following options are specific to the Sparc emulation:
1050 Set the initial TCX graphic mode. The default is 1024x768.
1056 @chapter Sparc64 System emulator invocation
1058 Use the executable @file{qemu-system-sparc64} to simulate a Sun4u machine.
1059 The emulator is not usable for anything yet.
1061 QEMU emulates the following sun4u peripherals:
1065 UltraSparc IIi APB PCI Bridge
1067 PCI VGA compatible card with VESA Bochs Extensions
1069 Non Volatile RAM M48T59
1071 PC-compatible serial ports
1074 @chapter MIPS System emulator invocation
1076 Use the executable @file{qemu-system-mips} to simulate a MIPS machine.
1077 The emulator begins to launch a Linux kernel.
1079 @chapter QEMU User space emulator invocation
1081 @section Quick Start
1083 In order to launch a Linux process, QEMU needs the process executable
1084 itself and all the target (x86) dynamic libraries used by it.
1088 @item On x86, you can just try to launch any process by using the native
1092 qemu-i386 -L / /bin/ls
1095 @code{-L /} tells that the x86 dynamic linker must be searched with a
1098 @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):
1101 qemu-i386 -L / qemu-i386 -L / /bin/ls
1104 @item On non x86 CPUs, you need first to download at least an x86 glibc
1105 (@file{qemu-runtime-i386-XXX-.tar.gz} on the QEMU web page). Ensure that
1106 @code{LD_LIBRARY_PATH} is not set:
1109 unset LD_LIBRARY_PATH
1112 Then you can launch the precompiled @file{ls} x86 executable:
1115 qemu-i386 tests/i386/ls
1117 You can look at @file{qemu-binfmt-conf.sh} so that
1118 QEMU is automatically launched by the Linux kernel when you try to
1119 launch x86 executables. It requires the @code{binfmt_misc} module in the
1122 @item The x86 version of QEMU is also included. You can try weird things such as:
1124 qemu-i386 /usr/local/qemu-i386/bin/qemu-i386 /usr/local/qemu-i386/bin/ls-i386
1129 @section Wine launch
1133 @item Ensure that you have a working QEMU with the x86 glibc
1134 distribution (see previous section). In order to verify it, you must be
1138 qemu-i386 /usr/local/qemu-i386/bin/ls-i386
1141 @item Download the binary x86 Wine install
1142 (@file{qemu-XXX-i386-wine.tar.gz} on the QEMU web page).
1144 @item Configure Wine on your account. Look at the provided script
1145 @file{/usr/local/qemu-i386/bin/wine-conf.sh}. Your previous
1146 @code{$@{HOME@}/.wine} directory is saved to @code{$@{HOME@}/.wine.org}.
1148 @item Then you can try the example @file{putty.exe}:
1151 qemu-i386 /usr/local/qemu-i386/wine/bin/wine /usr/local/qemu-i386/wine/c/Program\ Files/putty.exe
1156 @section Command line options
1159 usage: qemu-i386 [-h] [-d] [-L path] [-s size] program [arguments...]
1166 Set the x86 elf interpreter prefix (default=/usr/local/qemu-i386)
1168 Set the x86 stack size in bytes (default=524288)
1175 Activate log (logfile=/tmp/qemu.log)
1177 Act as if the host page size was 'pagesize' bytes
1181 @chapter Compilation from the sources
1185 @subsection Compilation
1187 First you must decompress the sources:
1190 tar zxvf qemu-x.y.z.tar.gz
1194 Then you configure QEMU and build it (usually no options are needed):
1200 Then type as root user:
1204 to install QEMU in @file{/usr/local}.
1206 @subsection Tested tool versions
1208 In order to compile QEMU succesfully, it is very important that you
1209 have the right tools. The most important one is gcc. I cannot guaranty
1210 that QEMU works if you do not use a tested gcc version. Look at
1211 'configure' and 'Makefile' if you want to make a different gcc
1215 host gcc binutils glibc linux distribution
1216 ----------------------------------------------------------------------
1217 x86 3.2 2.13.2 2.1.3 2.4.18
1218 2.96 2.11.93.0.2 2.2.5 2.4.18 Red Hat 7.3
1219 3.2.2 2.13.90.0.18 2.3.2 2.4.20 Red Hat 9
1221 PowerPC 3.3 [4] 2.13.90.0.18 2.3.1 2.4.20briq
1224 Alpha 3.3 [1] 2.14.90.0.4 2.2.5 2.2.20 [2] Debian 3.0
1226 Sparc32 2.95.4 2.12.90.0.1 2.2.5 2.4.18 Debian 3.0
1228 ARM 2.95.4 2.12.90.0.1 2.2.5 2.4.9 [3] Debian 3.0
1230 [1] On Alpha, QEMU needs the gcc 'visibility' attribute only available
1231 for gcc version >= 3.3.
1232 [2] Linux >= 2.4.20 is necessary for precise exception support
1234 [3] 2.4.9-ac10-rmk2-np1-cerf2
1236 [4] gcc 2.95.x generates invalid code when using too many register
1237 variables. You must use gcc 3.x on PowerPC.
1243 @item Install the current versions of MSYS and MinGW from
1244 @url{http://www.mingw.org/}. You can find detailed installation
1245 instructions in the download section and the FAQ.
1248 the MinGW development library of SDL 1.2.x
1249 (@file{SDL-devel-1.2.x-mingw32.tar.gz}) from
1250 @url{http://www.libsdl.org}. Unpack it in a temporary place, and
1251 unpack the archive @file{i386-mingw32msvc.tar.gz} in the MinGW tool
1252 directory. Edit the @file{sdl-config} script so that it gives the
1253 correct SDL directory when invoked.
1255 @item Extract the current version of QEMU.
1257 @item Start the MSYS shell (file @file{msys.bat}).
1259 @item Change to the QEMU directory. Launch @file{./configure} and
1260 @file{make}. If you have problems using SDL, verify that
1261 @file{sdl-config} can be launched from the MSYS command line.
1263 @item You can install QEMU in @file{Program Files/Qemu} by typing
1264 @file{make install}. Don't forget to copy @file{SDL.dll} in
1265 @file{Program Files/Qemu}.
1269 @section Cross compilation for Windows with Linux
1273 Install the MinGW cross compilation tools available at
1274 @url{http://www.mingw.org/}.
1277 Install the Win32 version of SDL (@url{http://www.libsdl.org}) by
1278 unpacking @file{i386-mingw32msvc.tar.gz}. Set up the PATH environment
1279 variable so that @file{i386-mingw32msvc-sdl-config} can be launched by
1280 the QEMU configuration script.
1283 Configure QEMU for Windows cross compilation:
1285 ./configure --enable-mingw32
1287 If necessary, you can change the cross-prefix according to the prefix
1288 choosen for the MinGW tools with --cross-prefix. You can also use
1289 --prefix to set the Win32 install path.
1291 @item You can install QEMU in the installation directory by typing
1292 @file{make install}. Don't forget to copy @file{SDL.dll} in the
1293 installation directory.
1297 Note: Currently, Wine does not seem able to launch
1302 The Mac OS X patches are not fully merged in QEMU, so you should look
1303 at the QEMU mailing list archive to have all the necessary