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
95 Moreover there is no separation between the host and target address
96 spaces, so it offers no security (the target OS can modify the
97 @code{qemu-fast} code by writing at the right addresses).
100 @code{qemu} uses a software MMU. It is about @emph{two times slower}
101 but gives a more accurate emulation and a complete separation between
102 the host and target address spaces.
106 QEMU emulates the following PC peripherials:
110 i440FX host PCI bridge and PIIX3 PCI to ISA bridge
112 Cirrus CLGD 5446 PCI VGA card or dummy VGA card with Bochs VESA
113 extensions (hardware level, including all non standard modes).
115 PS/2 mouse and keyboard
117 2 PCI IDE interfaces with hard disk and CD-ROM support
121 NE2000 PCI network adapters
128 QEMU uses the PC BIOS from the Bochs project and the Plex86/Bochs LGPL
135 Download and uncompress the linux image (@file{linux.img}) and type:
141 Linux should boot and give you a prompt.
146 @c man begin SYNOPSIS
147 usage: qemu [options] [disk_image]
152 @var{disk_image} is a raw hard disk image for IDE hard disk 0.
158 Use @var{file} as floppy disk 0/1 image (@xref{disk_images}). You can
159 use the host floppy by using @file{/dev/fd0} as filename.
165 Use @var{file} as hard disk 0, 1, 2 or 3 image (@xref{disk_images}).
168 Use @var{file} as CD-ROM image (you cannot use @option{-hdc} and and
169 @option{-cdrom} at the same time). You can use the host CD-ROM by
170 using @file{/dev/cdrom} as filename.
173 Boot on floppy (a), hard disk (c) or CD-ROM (d). Hard disk boot is
177 Write to temporary files instead of disk image files. In this case,
178 the raw disk image you use is not written back. You can however force
179 the write back by pressing @key{C-a s} (@xref{disk_images}).
182 Set virtual RAM size to @var{megs} megabytes. Default is 128 MB.
186 Normally, QEMU uses SDL to display the VGA output. With this option,
187 you can totally disable graphical output so that QEMU is a simple
188 command line application. The emulated serial port is redirected on
189 the console. Therefore, you can still use QEMU to debug a Linux kernel
190 with a serial console.
194 The SB16 emulation is disabled by default as it may give problems with
195 Windows. You can enable it manually with this option.
198 Set the real time clock to local time (the default is to UTC
199 time). This option is needed to have correct date in MS-DOS or
203 Start in full screen.
206 Store the QEMU process PID in @var{file}. It is useful if you launch QEMU
216 Set TUN/TAP network init script [default=/etc/qemu-ifup]. This script
217 is launched to configure the host network interface (usually tun0)
218 corresponding to the virtual NE2000 card.
222 Set the mac address of the first interface (the format is
223 aa:bb:cc:dd:ee:ff in hexa). The mac address is incremented for each
224 new network interface.
227 Assumes @var{fd} talks to a tap/tun host network interface and use
228 it. Read @url{http://bellard.org/qemu/tetrinet.html} to have an
232 Use the user mode network stack. This is the default if no tun/tap
233 network init script is found.
236 When using the user mode network stack, activate a built-in TFTP
237 server. All filenames beginning with @var{prefix} can be downloaded
238 from the host to the guest using a TFTP client. The TFTP client on the
239 guest must be configured in binary mode (use the command @code{bin} of
240 the Unix TFTP client). The host IP address on the guest is as usual
244 When using the user mode network stack, activate a built-in SMB
245 server so that Windows OSes can access to the host files in @file{dir}
248 In the guest Windows OS, the line:
252 must be added in the file @file{C:\WINDOWS\LMHOSTS} (for windows 9x/Me)
253 or @file{C:\WINNT\SYSTEM32\DRIVERS\ETC\LMHOSTS} (Windows NT/2000).
255 Then @file{dir} can be accessed in @file{\\smbserver\qemu}.
257 Note that a SAMBA server must be installed on the host OS in
258 @file{/usr/sbin/smbd}. QEMU was tested succesfully with smbd version
259 2.2.7a from the Red Hat 9.
261 @item -redir [tcp|udp]:host-port:[guest-host]:guest-port
263 When using the user mode network stack, redirect incoming TCP or UDP
264 connections to the host port @var{host-port} to the guest
265 @var{guest-host} on guest port @var{guest-port}. If @var{guest-host}
266 is not specified, its value is 10.0.2.15 (default address given by the
267 built-in DHCP server).
269 For example, to redirect host X11 connection from screen 1 to guest
270 screen 0, use the following:
274 qemu -redir tcp:6001::6000 [...]
275 # this host xterm should open in the guest X11 server
279 To redirect telnet connections from host port 5555 to telnet port on
280 the guest, use the following:
284 qemu -redir tcp:5555::23 [...]
285 telnet localhost 5555
288 Then when you use on the host @code{telnet localhost 5555}, you
289 connect to the guest telnet server.
292 Use the dummy network stack: no packet will be received by the network
297 Linux boot specific. When using this options, you can use a given
298 Linux kernel without installing it in the disk image. It can be useful
299 for easier testing of various kernels.
303 @item -kernel bzImage
304 Use @var{bzImage} as kernel image.
306 @item -append cmdline
307 Use @var{cmdline} as kernel command line
310 Use @var{file} as initial ram disk.
314 Debug/Expert options:
318 Redirect the virtual serial port to host device @var{dev}. Available
324 [Linux only] Pseudo TTY (a new PTY is automatically allocated)
328 [Unix only] standard input/output
330 The default device is @code{vc} in graphical mode and @code{stdio} in
333 This option can be used several times to simulate up to 4 serials
337 Redirect the monitor to host device @var{dev} (same devices as the
339 The default device is @code{vc} in graphical mode and @code{stdio} in
343 Wait gdb connection to port 1234 (@xref{gdb_usage}).
345 Change gdb connection port.
347 Do not start CPU at startup (you must type 'c' in the monitor).
349 Output log in /tmp/qemu.log
350 @item -hdachs c,h,s,[,t]
351 Force hard disk 0 physical geometry (1 <= @var{c} <= 16383, 1 <=
352 @var{h} <= 16, 1 <= @var{s} <= 63) and optionally force the BIOS
353 translation mode (@var{t}=none, lba or auto). Usually QEMU can guess
354 all thoses parameters. This option is useful for old MS-DOS disk
357 Simulate an ISA-only system (default is PCI system).
359 Simulate a standard VGA card with Bochs VBE extensions (default is
360 Cirrus Logic GD5446 PCI VGA)
362 Start right away with a saved state (@code{loadvm} in monitor)
371 During the graphical emulation, you can use the following keys:
377 Switch to virtual console 'n'. Standard console mappings are:
380 Target system display
388 Toggle mouse and keyboard grab.
391 In the virtual consoles, you can use @key{Ctrl-Up}, @key{Ctrl-Down},
392 @key{Ctrl-PageUp} and @key{Ctrl-PageDown} to move in the back log.
394 During emulation, if you are using the @option{-nographic} option, use
395 @key{Ctrl-a h} to get terminal commands:
403 Save disk data back to file (if -snapshot)
405 Send break (magic sysrq in Linux)
407 Switch between console and monitor
416 @settitle QEMU System Emulator
419 The HTML documentation of QEMU for more precise information and Linux
420 user mode emulator invocation.
432 @section QEMU Monitor
434 The QEMU monitor is used to give complex commands to the QEMU
435 emulator. You can use it to:
440 Remove or insert removable medias images
441 (such as CD-ROM or floppies)
444 Freeze/unfreeze the Virtual Machine (VM) and save or restore its state
447 @item Inspect the VM state without an external debugger.
453 The following commands are available:
457 @item help or ? [cmd]
458 Show the help for all commands or just for command @var{cmd}.
461 Commit changes to the disk images (if -snapshot is used)
463 @item info subcommand
464 show various information about the system state
468 show the network state
470 show the block devices
472 show the cpu registers
474 show the command line history
480 @item eject [-f] device
481 Eject a removable media (use -f to force it).
483 @item change device filename
484 Change a removable media.
486 @item screendump filename
487 Save screen into PPM image @var{filename}.
489 @item log item1[,...]
490 Activate logging of the specified items to @file{/tmp/qemu.log}.
492 @item savevm filename
493 Save the whole virtual machine state to @var{filename}.
495 @item loadvm filename
496 Restore the whole virtual machine state from @var{filename}.
504 @item gdbserver [port]
505 Start gdbserver session (default port=1234)
508 Virtual memory dump starting at @var{addr}.
511 Physical memory dump starting at @var{addr}.
513 @var{fmt} is a format which tells the command how to format the
514 data. Its syntax is: @option{/@{count@}@{format@}@{size@}}
518 is the number of items to be dumped.
521 can be x (hexa), d (signed decimal), u (unsigned decimal), o (octal),
522 c (char) or i (asm instruction).
525 can be b (8 bits), h (16 bits), w (32 bits) or g (64 bits). On x86,
526 @code{h} or @code{w} can be specified with the @code{i} format to
527 respectively select 16 or 32 bit code instruction size.
534 Dump 10 instructions at the current instruction pointer:
539 0x90107065: lea 0x0(%esi,1),%esi
540 0x90107069: lea 0x0(%edi,1),%edi
542 0x90107071: jmp 0x90107080
550 Dump 80 16 bit values at the start of the video memory.
552 (qemu) xp/80hx 0xb8000
553 0x000b8000: 0x0b50 0x0b6c 0x0b65 0x0b78 0x0b38 0x0b36 0x0b2f 0x0b42
554 0x000b8010: 0x0b6f 0x0b63 0x0b68 0x0b73 0x0b20 0x0b56 0x0b47 0x0b41
555 0x000b8020: 0x0b42 0x0b69 0x0b6f 0x0b73 0x0b20 0x0b63 0x0b75 0x0b72
556 0x000b8030: 0x0b72 0x0b65 0x0b6e 0x0b74 0x0b2d 0x0b63 0x0b76 0x0b73
557 0x000b8040: 0x0b20 0x0b30 0x0b35 0x0b20 0x0b4e 0x0b6f 0x0b76 0x0b20
558 0x000b8050: 0x0b32 0x0b30 0x0b30 0x0b33 0x0720 0x0720 0x0720 0x0720
559 0x000b8060: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
560 0x000b8070: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
561 0x000b8080: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
562 0x000b8090: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
566 @item p or print/fmt expr
568 Print expression value. Only the @var{format} part of @var{fmt} is
573 Send @var{keys} to the emulator. Use @code{-} to press several keys
574 simultaneously. Example:
579 This command is useful to send keys that your graphical user interface
580 intercepts at low level, such as @code{ctrl-alt-f1} in X Window.
588 @subsection Integer expressions
590 The monitor understands integers expressions for every integer
591 argument. You can use register names to get the value of specifics
592 CPU registers by prefixing them with @emph{$}.
597 Since version 0.6.1, QEMU supports many disk image formats, including
598 growable disk images (their size increase as non empty sectors are
599 written), compressed and encrypted disk images.
601 @subsection Quick start for disk image creation
603 You can create a disk image with the command:
605 qemu-img create myimage.img mysize
607 where @var{myimage.img} is the disk image filename and @var{mysize} is its
608 size in kilobytes. You can add an @code{M} suffix to give the size in
609 megabytes and a @code{G} suffix for gigabytes.
611 @xref{qemu_img_invocation} for more information.
613 @subsection Snapshot mode
615 If you use the option @option{-snapshot}, all disk images are
616 considered as read only. When sectors in written, they are written in
617 a temporary file created in @file{/tmp}. You can however force the
618 write back to the raw disk images by using the @code{commit} monitor
619 command (or @key{C-a s} in the serial console).
621 @node qemu_img_invocation
622 @subsection @code{qemu-img} Invocation
624 @include qemu-img.texi
626 @section Network emulation
628 QEMU simulates up to 6 networks cards (NE2000 boards). Each card can
629 be connected to a specific host network interface.
631 @subsection Using tun/tap network interface
633 This is the standard way to emulate network. QEMU adds a virtual
634 network device on your host (called @code{tun0}), and you can then
635 configure it as if it was a real ethernet card.
637 As an example, you can download the @file{linux-test-xxx.tar.gz}
638 archive and copy the script @file{qemu-ifup} in @file{/etc} and
639 configure properly @code{sudo} so that the command @code{ifconfig}
640 contained in @file{qemu-ifup} can be executed as root. You must verify
641 that your host kernel supports the TUN/TAP network interfaces: the
642 device @file{/dev/net/tun} must be present.
644 See @ref{direct_linux_boot} to have an example of network use with a
647 @subsection Using the user mode network stack
649 By using the option @option{-user-net} or if you have no tun/tap init
650 script, QEMU uses a completely user mode network stack (you don't need
651 root priviledge to use the virtual network). The virtual network
652 configuration is the following:
656 QEMU Virtual Machine <------> Firewall/DHCP server <-----> Internet
657 (10.0.2.x) | (10.0.2.2)
659 ----> DNS server (10.0.2.3)
661 ----> SMB server (10.0.2.4)
664 The QEMU VM behaves as if it was behind a firewall which blocks all
665 incoming connections. You can use a DHCP client to automatically
666 configure the network in the QEMU VM.
668 In order to check that the user mode network is working, you can ping
669 the address 10.0.2.2 and verify that you got an address in the range
670 10.0.2.x from the QEMU virtual DHCP server.
672 Note that @code{ping} is not supported reliably to the internet as it
673 would require root priviledges. It means you can only ping the local
676 When using the built-in TFTP server, the router is also the TFTP
679 When using the @option{-redir} option, TCP or UDP connections can be
680 redirected from the host to the guest. It allows for example to
681 redirect X11, telnet or SSH connections.
683 @node direct_linux_boot
684 @section Direct Linux Boot
686 This section explains how to launch a Linux kernel inside QEMU without
687 having to make a full bootable image. It is very useful for fast Linux
688 kernel testing. The QEMU network configuration is also explained.
692 Download the archive @file{linux-test-xxx.tar.gz} containing a Linux
693 kernel and a disk image.
695 @item Optional: If you want network support (for example to launch X11 examples), you
696 must copy the script @file{qemu-ifup} in @file{/etc} and configure
697 properly @code{sudo} so that the command @code{ifconfig} contained in
698 @file{qemu-ifup} can be executed as root. You must verify that your host
699 kernel supports the TUN/TAP network interfaces: the device
700 @file{/dev/net/tun} must be present.
702 When network is enabled, there is a virtual network connection between
703 the host kernel and the emulated kernel. The emulated kernel is seen
704 from the host kernel at IP address 172.20.0.2 and the host kernel is
705 seen from the emulated kernel at IP address 172.20.0.1.
707 @item Launch @code{qemu.sh}. You should have the following output:
711 Connected to host network interface: tun0
712 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
713 BIOS-provided physical RAM map:
714 BIOS-e801: 0000000000000000 - 000000000009f000 (usable)
715 BIOS-e801: 0000000000100000 - 0000000002000000 (usable)
716 32MB LOWMEM available.
717 On node 0 totalpages: 8192
721 Kernel command line: root=/dev/hda sb=0x220,5,1,5 ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe console=ttyS0
722 ide_setup: ide2=noprobe
723 ide_setup: ide3=noprobe
724 ide_setup: ide4=noprobe
725 ide_setup: ide5=noprobe
727 Detected 2399.621 MHz processor.
728 Console: colour EGA 80x25
729 Calibrating delay loop... 4744.80 BogoMIPS
730 Memory: 28872k/32768k available (1210k kernel code, 3508k reserved, 266k data, 64k init, 0k highmem)
731 Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
732 Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
733 Mount cache hash table entries: 512 (order: 0, 4096 bytes)
734 Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
735 Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
736 CPU: Intel Pentium Pro stepping 03
737 Checking 'hlt' instruction... OK.
738 POSIX conformance testing by UNIFIX
739 Linux NET4.0 for Linux 2.4
740 Based upon Swansea University Computer Society NET3.039
741 Initializing RT netlink socket
744 Journalled Block Device driver loaded
745 Detected PS/2 Mouse Port.
746 pty: 256 Unix98 ptys configured
747 Serial driver version 5.05c (2001-07-08) with no serial options enabled
748 ttyS00 at 0x03f8 (irq = 4) is a 16450
749 ne.c:v1.10 9/23/94 Donald Becker (becker@scyld.com)
750 Last modified Nov 1, 2000 by Paul Gortmaker
751 NE*000 ethercard probe at 0x300: 52 54 00 12 34 56
752 eth0: NE2000 found at 0x300, using IRQ 9.
753 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
754 Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
755 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
756 hda: QEMU HARDDISK, ATA DISK drive
757 ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
758 hda: attached ide-disk driver.
759 hda: 20480 sectors (10 MB) w/256KiB Cache, CHS=20/16/63
762 Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
763 NET4: Linux TCP/IP 1.0 for NET4.0
764 IP Protocols: ICMP, UDP, TCP, IGMP
765 IP: routing cache hash table of 512 buckets, 4Kbytes
766 TCP: Hash tables configured (established 2048 bind 4096)
767 NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
768 EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
769 VFS: Mounted root (ext2 filesystem).
770 Freeing unused kernel memory: 64k freed
772 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
774 QEMU Linux test distribution (based on Redhat 9)
776 Type 'exit' to halt the system
782 Then you can play with the kernel inside the virtual serial console. You
783 can launch @code{ls} for example. Type @key{Ctrl-a h} to have an help
784 about the keys you can type inside the virtual serial console. In
785 particular, use @key{Ctrl-a x} to exit QEMU and use @key{Ctrl-a b} as
789 If the network is enabled, launch the script @file{/etc/linuxrc} in the
790 emulator (don't forget the leading dot):
795 Then enable X11 connections on your PC from the emulated Linux:
800 You can now launch @file{xterm} or @file{xlogo} and verify that you have
801 a real Virtual Linux system !
808 A 2.5.74 kernel is also included in the archive. Just
809 replace the bzImage in qemu.sh to try it.
812 qemu-fast creates a temporary file in @var{$QEMU_TMPDIR} (@file{/tmp} is the
813 default) containing all the simulated PC memory. If possible, try to use
814 a temporary directory using the tmpfs filesystem to avoid too many
815 unnecessary disk accesses.
818 In order to exit cleanly from qemu, you can do a @emph{shutdown} inside
819 qemu. qemu will automatically exit when the Linux shutdown is done.
822 You can boot slightly faster by disabling the probe of non present IDE
823 interfaces. To do so, add the following options on the kernel command
826 ide1=noprobe ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe
830 The example disk image is a modified version of the one made by Kevin
831 Lawton for the plex86 Project (@url{www.plex86.org}).
836 @section Linux Kernel Compilation
838 You can use any linux kernel with QEMU. However, if you want to use
839 @code{qemu-fast} to get maximum performances, you must use a modified
840 guest kernel. If you are using a 2.6 guest kernel, you can use
841 directly the patch @file{linux-2.6-qemu-fast.patch} made by Rusty
842 Russel available in the QEMU source archive. Otherwise, you can make the
843 following changes @emph{by hand} to the Linux kernel:
847 The kernel must be mapped at 0x90000000 (the default is
848 0xc0000000). You must modify only two lines in the kernel source:
850 In @file{include/asm/page.h}, replace
852 #define __PAGE_OFFSET (0xc0000000)
856 #define __PAGE_OFFSET (0x90000000)
859 And in @file{arch/i386/vmlinux.lds}, replace
861 . = 0xc0000000 + 0x100000;
865 . = 0x90000000 + 0x100000;
869 If you want to enable SMP (Symmetric Multi-Processing) support, you
870 must make the following change in @file{include/asm/fixmap.h}. Replace
872 #define FIXADDR_TOP (0xffffX000UL)
876 #define FIXADDR_TOP (0xa7ffX000UL)
878 (X is 'e' or 'f' depending on the kernel version). Although you can
879 use an SMP kernel with QEMU, it only supports one CPU.
882 If you are not using a 2.6 kernel as host kernel but if you use a target
883 2.6 kernel, you must also ensure that the 'HZ' define is set to 100
884 (1000 is the default) as QEMU cannot currently emulate timers at
885 frequencies greater than 100 Hz on host Linux systems < 2.6. In
886 @file{include/asm/param.h}, replace:
889 # define HZ 1000 /* Internal kernel timer frequency */
893 # define HZ 100 /* Internal kernel timer frequency */
898 The file config-2.x.x gives the configuration of the example kernels.
905 As you would do to make a real kernel. Then you can use with QEMU
906 exactly the same kernel as you would boot on your PC (in
907 @file{arch/i386/boot/bzImage}).
912 QEMU has a primitive support to work with gdb, so that you can do
913 'Ctrl-C' while the virtual machine is running and inspect its state.
915 In order to use gdb, launch qemu with the '-s' option. It will wait for a
918 > qemu -s -kernel arch/i386/boot/bzImage -hda root-2.4.20.img -append "root=/dev/hda"
919 Connected to host network interface: tun0
920 Waiting gdb connection on port 1234
923 Then launch gdb on the 'vmlinux' executable:
928 In gdb, connect to QEMU:
930 (gdb) target remote localhost:1234
933 Then you can use gdb normally. For example, type 'c' to launch the kernel:
938 Here are some useful tips in order to use gdb on system code:
942 Use @code{info reg} to display all the CPU registers.
944 Use @code{x/10i $eip} to display the code at the PC position.
946 Use @code{set architecture i8086} to dump 16 bit code. Then use
947 @code{x/10i $cs*16+*eip} to dump the code at the PC position.
950 @section Target OS specific information
954 To have access to SVGA graphic modes under X11, use the @code{vesa} or
955 the @code{cirrus} X11 driver. For optimal performances, use 16 bit
956 color depth in the guest and the host OS.
958 When using a 2.6 guest Linux kernel, you should add the option
959 @code{clock=pit} on the kernel command line because the 2.6 Linux
960 kernels make very strict real time clock checks by default that QEMU
961 cannot simulate exactly.
965 If you have a slow host, using Windows 95 is better as it gives the
966 best speed. Windows 2000 is also a good choice.
968 @subsubsection SVGA graphic modes support
970 QEMU emulates a Cirrus Logic GD5446 Video
971 card. All Windows versions starting from Windows 95 should recognize
972 and use this graphic card. For optimal performances, use 16 bit color
973 depth in the guest and the host OS.
975 @subsubsection CPU usage reduction
977 Windows 9x does not correctly use the CPU HLT
978 instruction. The result is that it takes host CPU cycles even when
979 idle. You can install the utility from
980 @url{http://www.user.cityline.ru/~maxamn/amnhltm.zip} to solve this
981 problem. Note that no such tool is needed for NT, 2000 or XP.
983 @subsubsection Windows 2000 disk full problems
985 Currently (release 0.6.0) QEMU has a bug which gives a @code{disk
986 full} error during installation of some releases of Windows 2000. The
987 workaround is to stop QEMU as soon as you notice that your disk image
988 size is growing too fast (monitor it with @code{ls -ls}). Then
989 relaunch QEMU to continue the installation. If you still experience
990 the problem, relaunch QEMU again.
992 Future QEMU releases are likely to correct this bug.
994 @subsubsection Windows XP security problems
996 Some releases of Windows XP install correctly but give a security
999 A problem is preventing Windows from accurately checking the
1000 license for this computer. Error code: 0x800703e6.
1002 The only known workaround is to boot in Safe mode
1003 without networking support.
1005 Future QEMU releases are likely to correct this bug.
1007 @subsection MS-DOS and FreeDOS
1009 @subsubsection CPU usage reduction
1011 DOS does not correctly use the CPU HLT instruction. The result is that
1012 it takes host CPU cycles even when idle. You can install the utility
1013 from @url{http://www.vmware.com/software/dosidle210.zip} to solve this
1016 @chapter QEMU PowerPC System emulator invocation
1018 Use the executable @file{qemu-system-ppc} to simulate a complete PREP
1019 or PowerMac PowerPC system.
1021 QEMU emulates the following PowerMac peripherials:
1027 PCI VGA compatible card with VESA Bochs Extensions
1029 2 PMAC IDE interfaces with hard disk and CD-ROM support
1035 VIA-CUDA with ADB keyboard and mouse.
1038 QEMU emulates the following PREP peripherials:
1044 PCI VGA compatible card with VESA Bochs Extensions
1046 2 IDE interfaces with hard disk and CD-ROM support
1050 NE2000 network adapters
1054 PREP Non Volatile RAM
1056 PC compatible keyboard and mouse.
1059 QEMU uses the Open Hack'Ware Open Firmware Compatible BIOS available at
1060 @url{http://site.voila.fr/jmayer/OpenHackWare/index.htm}.
1062 You can read the qemu PC system emulation chapter to have more
1063 informations about QEMU usage.
1065 @c man begin OPTIONS
1067 The following options are specific to the PowerPC emulation:
1072 Simulate a PREP system (default is PowerMAC)
1074 @item -g WxH[xDEPTH]
1076 Set the initial VGA graphic mode. The default is 800x600x15.
1083 More information is available at
1084 @url{http://jocelyn.mayer.free.fr/qemu-ppc/}.
1086 @chapter QEMU User space emulator invocation
1088 @section Quick Start
1090 In order to launch a Linux process, QEMU needs the process executable
1091 itself and all the target (x86) dynamic libraries used by it.
1095 @item On x86, you can just try to launch any process by using the native
1099 qemu-i386 -L / /bin/ls
1102 @code{-L /} tells that the x86 dynamic linker must be searched with a
1105 @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):
1108 qemu-i386 -L / qemu-i386 -L / /bin/ls
1111 @item On non x86 CPUs, you need first to download at least an x86 glibc
1112 (@file{qemu-runtime-i386-XXX-.tar.gz} on the QEMU web page). Ensure that
1113 @code{LD_LIBRARY_PATH} is not set:
1116 unset LD_LIBRARY_PATH
1119 Then you can launch the precompiled @file{ls} x86 executable:
1122 qemu-i386 tests/i386/ls
1124 You can look at @file{qemu-binfmt-conf.sh} so that
1125 QEMU is automatically launched by the Linux kernel when you try to
1126 launch x86 executables. It requires the @code{binfmt_misc} module in the
1129 @item The x86 version of QEMU is also included. You can try weird things such as:
1131 qemu-i386 /usr/local/qemu-i386/bin/qemu-i386 /usr/local/qemu-i386/bin/ls-i386
1136 @section Wine launch
1140 @item Ensure that you have a working QEMU with the x86 glibc
1141 distribution (see previous section). In order to verify it, you must be
1145 qemu-i386 /usr/local/qemu-i386/bin/ls-i386
1148 @item Download the binary x86 Wine install
1149 (@file{qemu-XXX-i386-wine.tar.gz} on the QEMU web page).
1151 @item Configure Wine on your account. Look at the provided script
1152 @file{/usr/local/qemu-i386/bin/wine-conf.sh}. Your previous
1153 @code{$@{HOME@}/.wine} directory is saved to @code{$@{HOME@}/.wine.org}.
1155 @item Then you can try the example @file{putty.exe}:
1158 qemu-i386 /usr/local/qemu-i386/wine/bin/wine /usr/local/qemu-i386/wine/c/Program\ Files/putty.exe
1163 @section Command line options
1166 usage: qemu-i386 [-h] [-d] [-L path] [-s size] program [arguments...]
1173 Set the x86 elf interpreter prefix (default=/usr/local/qemu-i386)
1175 Set the x86 stack size in bytes (default=524288)
1182 Activate log (logfile=/tmp/qemu.log)
1184 Act as if the host page size was 'pagesize' bytes
1188 @chapter Compilation from the sources
1192 Read the @file{README} which gives the related information.
1197 @item Install the current versions of MSYS and MinGW from
1198 @url{http://www.mingw.org/}. You can find detailed installation
1199 instructions in the download section and the FAQ.
1202 the MinGW development library of SDL 1.2.x
1203 (@file{SDL-devel-1.2.x-mingw32.tar.gz}) from
1204 @url{http://www.libsdl.org}. Unpack it in a temporary place, and
1205 unpack the archive @file{i386-mingw32msvc.tar.gz} in the MinGW tool
1206 directory. Edit the @file{sdl-config} script so that it gives the
1207 correct SDL directory when invoked.
1209 @item Extract the current version of QEMU.
1211 @item Start the MSYS shell (file @file{msys.bat}).
1213 @item Change to the QEMU directory. Launch @file{./configure} and
1214 @file{make}. If you have problems using SDL, verify that
1215 @file{sdl-config} can be launched from the MSYS command line.
1217 @item You can install QEMU in @file{Program Files/Qemu} by typing
1218 @file{make install}. Don't forget to copy @file{SDL.dll} in
1219 @file{Program Files/Qemu}.
1223 @section Cross compilation for Windows with Linux
1227 Install the MinGW cross compilation tools available at
1228 @url{http://www.mingw.org/}.
1231 Install the Win32 version of SDL (@url{http://www.libsdl.org}) by
1232 unpacking @file{i386-mingw32msvc.tar.gz}. Set up the PATH environment
1233 variable so that @file{i386-mingw32msvc-sdl-config} can be launched by
1234 the QEMU configuration script.
1237 Configure QEMU for Windows cross compilation:
1239 ./configure --enable-mingw32
1241 If necessary, you can change the cross-prefix according to the prefix
1242 choosen for the MinGW tools with --cross-prefix. You can also use
1243 --prefix to set the Win32 install path.
1245 @item You can install QEMU in the installation directory by typing
1246 @file{make install}. Don't forget to copy @file{SDL.dll} in the
1247 installation directory.
1251 Note: Currently, Wine does not seem able to launch
1256 The Mac OS X patches are not fully merged in QEMU, so you should look
1257 at the QEMU mailing list archive to have all the necessary