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.
212 Set TUN/TAP network init script [default=/etc/qemu-ifup]. This script
213 is launched to configure the host network interface (usually tun0)
214 corresponding to the virtual NE2000 card.
218 Set the mac address of the first interface (the format is
219 aa:bb:cc:dd:ee:ff in hexa). The mac address is incremented for each
220 new network interface.
223 Assumes @var{fd} talks to a tap/tun host network interface and use
224 it. Read @url{http://bellard.org/qemu/tetrinet.html} to have an
228 Use the user mode network stack. This is the default if no tun/tap
229 network init script is found.
232 When using the user mode network stack, activate a built-in TFTP
233 server. All filenames beginning with @var{prefix} can be downloaded
234 from the host to the guest using a TFTP client. The TFTP client on the
235 guest must be configured in binary mode (use the command @code{bin} of
236 the Unix TFTP client). The host IP address on the guest is as usual
240 When using the user mode network stack, activate a built-in SMB
241 server so that Windows OSes can access to the host files in @file{dir}
244 In the guest Windows OS, the line:
248 must be added in the file @file{C:\WINDOWS\LMHOSTS} (for windows 9x/Me)
249 or @file{C:\WINNT\SYSTEM32\DRIVERS\ETC\LMHOSTS} (Windows NT/2000).
251 Then @file{dir} can be accessed in @file{\\smbserver\qemu}.
253 Note that a SAMBA server must be installed on the host OS in
254 @file{/usr/sbin/smbd}. QEMU was tested succesfully with smbd version
255 2.2.7a from the Red Hat 9.
257 @item -redir [tcp|udp]:host-port:[guest-host]:guest-port
259 When using the user mode network stack, redirect incoming TCP or UDP
260 connections to the host port @var{host-port} to the guest
261 @var{guest-host} on guest port @var{guest-port}. If @var{guest-host}
262 is not specified, its value is 10.0.2.15 (default address given by the
263 built-in DHCP server).
265 For example, to redirect host X11 connection from screen 1 to guest
266 screen 0, use the following:
270 qemu -redir tcp:6001::6000 [...]
271 # this host xterm should open in the guest X11 server
275 To redirect telnet connections from host port 5555 to telnet port on
276 the guest, use the following:
280 qemu -redir tcp:5555::23 [...]
281 telnet localhost 5555
284 Then when you use on the host @code{telnet localhost 5555}, you
285 connect to the guest telnet server.
288 Use the dummy network stack: no packet will be received by the network
293 Linux boot specific. When using this options, you can use a given
294 Linux kernel without installing it in the disk image. It can be useful
295 for easier testing of various kernels.
299 @item -kernel bzImage
300 Use @var{bzImage} as kernel image.
302 @item -append cmdline
303 Use @var{cmdline} as kernel command line
306 Use @var{file} as initial ram disk.
310 Debug/Expert options:
314 Redirect the virtual serial port to host device @var{dev}. Available
320 [Linux only] Pseudo TTY (a new PTY is automatically allocated)
324 [Unix only] standard input/output
326 The default device is @code{vc} in graphical mode and @code{stdio} in
329 This option can be used several times to simulate up to 4 serials
333 Redirect the monitor to host device @var{dev} (same devices as the
335 The default device is @code{vc} in graphical mode and @code{stdio} in
339 Wait gdb connection to port 1234 (@xref{gdb_usage}).
341 Change gdb connection port.
343 Do not start CPU at startup (you must type 'c' in the monitor).
345 Output log in /tmp/qemu.log
346 @item -hdachs c,h,s,[,t]
347 Force hard disk 0 physical geometry (1 <= @var{c} <= 16383, 1 <=
348 @var{h} <= 16, 1 <= @var{s} <= 63) and optionally force the BIOS
349 translation mode (@var{t}=none, lba or auto). Usually QEMU can guess
350 all thoses parameters. This option is useful for old MS-DOS disk
353 Simulate an ISA-only system (default is PCI system).
355 Simulate a standard VGA card with Bochs VBE extensions (default is
356 Cirrus Logic GD5446 PCI VGA)
358 Start right away with a saved state (@code{loadvm} in monitor)
367 During the graphical emulation, you can use the following keys:
373 Switch to virtual console 'n'. Standard console mappings are:
376 Target system display
384 Toggle mouse and keyboard grab.
387 In the virtual consoles, you can use @key{Ctrl-Up}, @key{Ctrl-Down},
388 @key{Ctrl-PageUp} and @key{Ctrl-PageDown} to move in the back log.
390 During emulation, if you are using the @option{-nographic} option, use
391 @key{Ctrl-a h} to get terminal commands:
399 Save disk data back to file (if -snapshot)
401 Send break (magic sysrq in Linux)
403 Switch between console and monitor
412 @settitle QEMU System Emulator
415 The HTML documentation of QEMU for more precise information and Linux
416 user mode emulator invocation.
428 @section QEMU Monitor
430 The QEMU monitor is used to give complex commands to the QEMU
431 emulator. You can use it to:
436 Remove or insert removable medias images
437 (such as CD-ROM or floppies)
440 Freeze/unfreeze the Virtual Machine (VM) and save or restore its state
443 @item Inspect the VM state without an external debugger.
449 The following commands are available:
453 @item help or ? [cmd]
454 Show the help for all commands or just for command @var{cmd}.
457 Commit changes to the disk images (if -snapshot is used)
459 @item info subcommand
460 show various information about the system state
464 show the network state
466 show the block devices
468 show the cpu registers
470 show the command line history
476 @item eject [-f] device
477 Eject a removable media (use -f to force it).
479 @item change device filename
480 Change a removable media.
482 @item screendump filename
483 Save screen into PPM image @var{filename}.
485 @item log item1[,...]
486 Activate logging of the specified items to @file{/tmp/qemu.log}.
488 @item savevm filename
489 Save the whole virtual machine state to @var{filename}.
491 @item loadvm filename
492 Restore the whole virtual machine state from @var{filename}.
500 @item gdbserver [port]
501 Start gdbserver session (default port=1234)
504 Virtual memory dump starting at @var{addr}.
507 Physical memory dump starting at @var{addr}.
509 @var{fmt} is a format which tells the command how to format the
510 data. Its syntax is: @option{/@{count@}@{format@}@{size@}}
514 is the number of items to be dumped.
517 can be x (hexa), d (signed decimal), u (unsigned decimal), o (octal),
518 c (char) or i (asm instruction).
521 can be b (8 bits), h (16 bits), w (32 bits) or g (64 bits). On x86,
522 @code{h} or @code{w} can be specified with the @code{i} format to
523 respectively select 16 or 32 bit code instruction size.
530 Dump 10 instructions at the current instruction pointer:
535 0x90107065: lea 0x0(%esi,1),%esi
536 0x90107069: lea 0x0(%edi,1),%edi
538 0x90107071: jmp 0x90107080
546 Dump 80 16 bit values at the start of the video memory.
548 (qemu) xp/80hx 0xb8000
549 0x000b8000: 0x0b50 0x0b6c 0x0b65 0x0b78 0x0b38 0x0b36 0x0b2f 0x0b42
550 0x000b8010: 0x0b6f 0x0b63 0x0b68 0x0b73 0x0b20 0x0b56 0x0b47 0x0b41
551 0x000b8020: 0x0b42 0x0b69 0x0b6f 0x0b73 0x0b20 0x0b63 0x0b75 0x0b72
552 0x000b8030: 0x0b72 0x0b65 0x0b6e 0x0b74 0x0b2d 0x0b63 0x0b76 0x0b73
553 0x000b8040: 0x0b20 0x0b30 0x0b35 0x0b20 0x0b4e 0x0b6f 0x0b76 0x0b20
554 0x000b8050: 0x0b32 0x0b30 0x0b30 0x0b33 0x0720 0x0720 0x0720 0x0720
555 0x000b8060: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
556 0x000b8070: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
557 0x000b8080: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
558 0x000b8090: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
562 @item p or print/fmt expr
564 Print expression value. Only the @var{format} part of @var{fmt} is
569 Send @var{keys} to the emulator. Use @code{-} to press several keys
570 simultaneously. Example:
575 This command is useful to send keys that your graphical user interface
576 intercepts at low level, such as @code{ctrl-alt-f1} in X Window.
584 @subsection Integer expressions
586 The monitor understands integers expressions for every integer
587 argument. You can use register names to get the value of specifics
588 CPU registers by prefixing them with @emph{$}.
593 Since version 0.6.1, QEMU supports many disk image formats, including
594 growable disk images (their size increase as non empty sectors are
595 written), compressed and encrypted disk images.
597 @subsection Quick start for disk image creation
599 You can create a disk image with the command:
601 qemu-img create myimage.img mysize
603 where @var{myimage.img} is the disk image filename and @var{mysize} is its
604 size in kilobytes. You can add an @code{M} suffix to give the size in
605 megabytes and a @code{G} suffix for gigabytes.
607 @xref{qemu_img_invocation} for more information.
609 @subsection Snapshot mode
611 If you use the option @option{-snapshot}, all disk images are
612 considered as read only. When sectors in written, they are written in
613 a temporary file created in @file{/tmp}. You can however force the
614 write back to the raw disk images by using the @code{commit} monitor
615 command (or @key{C-a s} in the serial console).
617 @node qemu_img_invocation
618 @subsection @code{qemu-img} Invocation
620 @include qemu-img.texi
622 @section Network emulation
624 QEMU simulates up to 6 networks cards (NE2000 boards). Each card can
625 be connected to a specific host network interface.
627 @subsection Using tun/tap network interface
629 This is the standard way to emulate network. QEMU adds a virtual
630 network device on your host (called @code{tun0}), and you can then
631 configure it as if it was a real ethernet card.
633 As an example, you can download the @file{linux-test-xxx.tar.gz}
634 archive and copy the script @file{qemu-ifup} in @file{/etc} and
635 configure properly @code{sudo} so that the command @code{ifconfig}
636 contained in @file{qemu-ifup} can be executed as root. You must verify
637 that your host kernel supports the TUN/TAP network interfaces: the
638 device @file{/dev/net/tun} must be present.
640 See @ref{direct_linux_boot} to have an example of network use with a
643 @subsection Using the user mode network stack
645 By using the option @option{-user-net} or if you have no tun/tap init
646 script, QEMU uses a completely user mode network stack (you don't need
647 root priviledge to use the virtual network). The virtual network
648 configuration is the following:
652 QEMU Virtual Machine <------> Firewall/DHCP server <-----> Internet
653 (10.0.2.x) | (10.0.2.2)
655 ----> DNS server (10.0.2.3)
657 ----> SMB server (10.0.2.4)
660 The QEMU VM behaves as if it was behind a firewall which blocks all
661 incoming connections. You can use a DHCP client to automatically
662 configure the network in the QEMU VM.
664 In order to check that the user mode network is working, you can ping
665 the address 10.0.2.2 and verify that you got an address in the range
666 10.0.2.x from the QEMU virtual DHCP server.
668 Note that @code{ping} is not supported reliably to the internet as it
669 would require root priviledges. It means you can only ping the local
672 When using the built-in TFTP server, the router is also the TFTP
675 When using the @option{-redir} option, TCP or UDP connections can be
676 redirected from the host to the guest. It allows for example to
677 redirect X11, telnet or SSH connections.
679 @node direct_linux_boot
680 @section Direct Linux Boot
682 This section explains how to launch a Linux kernel inside QEMU without
683 having to make a full bootable image. It is very useful for fast Linux
684 kernel testing. The QEMU network configuration is also explained.
688 Download the archive @file{linux-test-xxx.tar.gz} containing a Linux
689 kernel and a disk image.
691 @item Optional: If you want network support (for example to launch X11 examples), you
692 must copy the script @file{qemu-ifup} in @file{/etc} and configure
693 properly @code{sudo} so that the command @code{ifconfig} contained in
694 @file{qemu-ifup} can be executed as root. You must verify that your host
695 kernel supports the TUN/TAP network interfaces: the device
696 @file{/dev/net/tun} must be present.
698 When network is enabled, there is a virtual network connection between
699 the host kernel and the emulated kernel. The emulated kernel is seen
700 from the host kernel at IP address 172.20.0.2 and the host kernel is
701 seen from the emulated kernel at IP address 172.20.0.1.
703 @item Launch @code{qemu.sh}. You should have the following output:
707 Connected to host network interface: tun0
708 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
709 BIOS-provided physical RAM map:
710 BIOS-e801: 0000000000000000 - 000000000009f000 (usable)
711 BIOS-e801: 0000000000100000 - 0000000002000000 (usable)
712 32MB LOWMEM available.
713 On node 0 totalpages: 8192
717 Kernel command line: root=/dev/hda sb=0x220,5,1,5 ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe console=ttyS0
718 ide_setup: ide2=noprobe
719 ide_setup: ide3=noprobe
720 ide_setup: ide4=noprobe
721 ide_setup: ide5=noprobe
723 Detected 2399.621 MHz processor.
724 Console: colour EGA 80x25
725 Calibrating delay loop... 4744.80 BogoMIPS
726 Memory: 28872k/32768k available (1210k kernel code, 3508k reserved, 266k data, 64k init, 0k highmem)
727 Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
728 Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
729 Mount cache hash table entries: 512 (order: 0, 4096 bytes)
730 Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
731 Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
732 CPU: Intel Pentium Pro stepping 03
733 Checking 'hlt' instruction... OK.
734 POSIX conformance testing by UNIFIX
735 Linux NET4.0 for Linux 2.4
736 Based upon Swansea University Computer Society NET3.039
737 Initializing RT netlink socket
740 Journalled Block Device driver loaded
741 Detected PS/2 Mouse Port.
742 pty: 256 Unix98 ptys configured
743 Serial driver version 5.05c (2001-07-08) with no serial options enabled
744 ttyS00 at 0x03f8 (irq = 4) is a 16450
745 ne.c:v1.10 9/23/94 Donald Becker (becker@scyld.com)
746 Last modified Nov 1, 2000 by Paul Gortmaker
747 NE*000 ethercard probe at 0x300: 52 54 00 12 34 56
748 eth0: NE2000 found at 0x300, using IRQ 9.
749 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
750 Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
751 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
752 hda: QEMU HARDDISK, ATA DISK drive
753 ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
754 hda: attached ide-disk driver.
755 hda: 20480 sectors (10 MB) w/256KiB Cache, CHS=20/16/63
758 Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
759 NET4: Linux TCP/IP 1.0 for NET4.0
760 IP Protocols: ICMP, UDP, TCP, IGMP
761 IP: routing cache hash table of 512 buckets, 4Kbytes
762 TCP: Hash tables configured (established 2048 bind 4096)
763 NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
764 EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
765 VFS: Mounted root (ext2 filesystem).
766 Freeing unused kernel memory: 64k freed
768 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
770 QEMU Linux test distribution (based on Redhat 9)
772 Type 'exit' to halt the system
778 Then you can play with the kernel inside the virtual serial console. You
779 can launch @code{ls} for example. Type @key{Ctrl-a h} to have an help
780 about the keys you can type inside the virtual serial console. In
781 particular, use @key{Ctrl-a x} to exit QEMU and use @key{Ctrl-a b} as
785 If the network is enabled, launch the script @file{/etc/linuxrc} in the
786 emulator (don't forget the leading dot):
791 Then enable X11 connections on your PC from the emulated Linux:
796 You can now launch @file{xterm} or @file{xlogo} and verify that you have
797 a real Virtual Linux system !
804 A 2.5.74 kernel is also included in the archive. Just
805 replace the bzImage in qemu.sh to try it.
808 qemu-fast creates a temporary file in @var{$QEMU_TMPDIR} (@file{/tmp} is the
809 default) containing all the simulated PC memory. If possible, try to use
810 a temporary directory using the tmpfs filesystem to avoid too many
811 unnecessary disk accesses.
814 In order to exit cleanly from qemu, you can do a @emph{shutdown} inside
815 qemu. qemu will automatically exit when the Linux shutdown is done.
818 You can boot slightly faster by disabling the probe of non present IDE
819 interfaces. To do so, add the following options on the kernel command
822 ide1=noprobe ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe
826 The example disk image is a modified version of the one made by Kevin
827 Lawton for the plex86 Project (@url{www.plex86.org}).
832 @section Linux Kernel Compilation
834 You can use any linux kernel with QEMU. However, if you want to use
835 @code{qemu-fast} to get maximum performances, you must use a modified
836 guest kernel. If you are using a 2.6 guest kernel, you can use
837 directly the patch @file{linux-2.6-qemu-fast.patch} made by Rusty
838 Russel available in the QEMU source archive. Otherwise, you can make the
839 following changes @emph{by hand} to the Linux kernel:
843 The kernel must be mapped at 0x90000000 (the default is
844 0xc0000000). You must modify only two lines in the kernel source:
846 In @file{include/asm/page.h}, replace
848 #define __PAGE_OFFSET (0xc0000000)
852 #define __PAGE_OFFSET (0x90000000)
855 And in @file{arch/i386/vmlinux.lds}, replace
857 . = 0xc0000000 + 0x100000;
861 . = 0x90000000 + 0x100000;
865 If you want to enable SMP (Symmetric Multi-Processing) support, you
866 must make the following change in @file{include/asm/fixmap.h}. Replace
868 #define FIXADDR_TOP (0xffffX000UL)
872 #define FIXADDR_TOP (0xa7ffX000UL)
874 (X is 'e' or 'f' depending on the kernel version). Although you can
875 use an SMP kernel with QEMU, it only supports one CPU.
878 If you are not using a 2.6 kernel as host kernel but if you use a target
879 2.6 kernel, you must also ensure that the 'HZ' define is set to 100
880 (1000 is the default) as QEMU cannot currently emulate timers at
881 frequencies greater than 100 Hz on host Linux systems < 2.6. In
882 @file{include/asm/param.h}, replace:
885 # define HZ 1000 /* Internal kernel timer frequency */
889 # define HZ 100 /* Internal kernel timer frequency */
894 The file config-2.x.x gives the configuration of the example kernels.
901 As you would do to make a real kernel. Then you can use with QEMU
902 exactly the same kernel as you would boot on your PC (in
903 @file{arch/i386/boot/bzImage}).
908 QEMU has a primitive support to work with gdb, so that you can do
909 'Ctrl-C' while the virtual machine is running and inspect its state.
911 In order to use gdb, launch qemu with the '-s' option. It will wait for a
914 > qemu -s -kernel arch/i386/boot/bzImage -hda root-2.4.20.img -append "root=/dev/hda"
915 Connected to host network interface: tun0
916 Waiting gdb connection on port 1234
919 Then launch gdb on the 'vmlinux' executable:
924 In gdb, connect to QEMU:
926 (gdb) target remote localhost:1234
929 Then you can use gdb normally. For example, type 'c' to launch the kernel:
934 Here are some useful tips in order to use gdb on system code:
938 Use @code{info reg} to display all the CPU registers.
940 Use @code{x/10i $eip} to display the code at the PC position.
942 Use @code{set architecture i8086} to dump 16 bit code. Then use
943 @code{x/10i $cs*16+*eip} to dump the code at the PC position.
946 @section Target OS specific information
950 To have access to SVGA graphic modes under X11, use the @code{vesa} or
951 the @code{cirrus} X11 driver. For optimal performances, use 16 bit
952 color depth in the guest and the host OS.
954 When using a 2.6 guest Linux kernel, you should add the option
955 @code{clock=pit} on the kernel command line because the 2.6 Linux
956 kernels make very strict real time clock checks by default that QEMU
957 cannot simulate exactly.
961 If you have a slow host, using Windows 95 is better as it gives the
962 best speed. Windows 2000 is also a good choice.
964 @subsubsection SVGA graphic modes support
966 QEMU emulates a Cirrus Logic GD5446 Video
967 card. All Windows versions starting from Windows 95 should recognize
968 and use this graphic card. For optimal performances, use 16 bit color
969 depth in the guest and the host OS.
971 @subsubsection CPU usage reduction
973 Windows 9x does not correctly use the CPU HLT
974 instruction. The result is that it takes host CPU cycles even when
975 idle. You can install the utility from
976 @url{http://www.user.cityline.ru/~maxamn/amnhltm.zip} to solve this
977 problem. Note that no such tool is needed for NT, 2000 or XP.
979 @subsubsection Windows 2000 disk full problems
981 Currently (release 0.6.0) QEMU has a bug which gives a @code{disk
982 full} error during installation of some releases of Windows 2000. The
983 workaround is to stop QEMU as soon as you notice that your disk image
984 size is growing too fast (monitor it with @code{ls -ls}). Then
985 relaunch QEMU to continue the installation. If you still experience
986 the problem, relaunch QEMU again.
988 Future QEMU releases are likely to correct this bug.
990 @subsubsection Windows XP security problems
992 Some releases of Windows XP install correctly but give a security
995 A problem is preventing Windows from accurately checking the
996 license for this computer. Error code: 0x800703e6.
998 The only known workaround is to boot in Safe mode
999 without networking support.
1001 Future QEMU releases are likely to correct this bug.
1003 @subsection MS-DOS and FreeDOS
1005 @subsubsection CPU usage reduction
1007 DOS does not correctly use the CPU HLT instruction. The result is that
1008 it takes host CPU cycles even when idle. You can install the utility
1009 from @url{http://www.vmware.com/software/dosidle210.zip} to solve this
1012 @chapter QEMU PowerPC System emulator invocation
1014 Use the executable @file{qemu-system-ppc} to simulate a complete PREP
1015 or PowerMac PowerPC system.
1017 QEMU emulates the following PowerMac peripherials:
1023 PCI VGA compatible card with VESA Bochs Extensions
1025 2 PMAC IDE interfaces with hard disk and CD-ROM support
1031 VIA-CUDA with ADB keyboard and mouse.
1034 QEMU emulates the following PREP peripherials:
1040 PCI VGA compatible card with VESA Bochs Extensions
1042 2 IDE interfaces with hard disk and CD-ROM support
1046 NE2000 network adapters
1050 PREP Non Volatile RAM
1052 PC compatible keyboard and mouse.
1055 QEMU uses the Open Hack'Ware Open Firmware Compatible BIOS available at
1056 @url{http://site.voila.fr/jmayer/OpenHackWare/index.htm}.
1058 You can read the qemu PC system emulation chapter to have more
1059 informations about QEMU usage.
1061 @c man begin OPTIONS
1063 The following options are specific to the PowerPC emulation:
1068 Simulate a PREP system (default is PowerMAC)
1070 @item -g WxH[xDEPTH]
1072 Set the initial VGA graphic mode. The default is 800x600x15.
1079 More information is available at
1080 @url{http://jocelyn.mayer.free.fr/qemu-ppc/}.
1082 @chapter QEMU User space emulator invocation
1084 @section Quick Start
1086 In order to launch a Linux process, QEMU needs the process executable
1087 itself and all the target (x86) dynamic libraries used by it.
1091 @item On x86, you can just try to launch any process by using the native
1095 qemu-i386 -L / /bin/ls
1098 @code{-L /} tells that the x86 dynamic linker must be searched with a
1101 @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):
1104 qemu-i386 -L / qemu-i386 -L / /bin/ls
1107 @item On non x86 CPUs, you need first to download at least an x86 glibc
1108 (@file{qemu-runtime-i386-XXX-.tar.gz} on the QEMU web page). Ensure that
1109 @code{LD_LIBRARY_PATH} is not set:
1112 unset LD_LIBRARY_PATH
1115 Then you can launch the precompiled @file{ls} x86 executable:
1118 qemu-i386 tests/i386/ls
1120 You can look at @file{qemu-binfmt-conf.sh} so that
1121 QEMU is automatically launched by the Linux kernel when you try to
1122 launch x86 executables. It requires the @code{binfmt_misc} module in the
1125 @item The x86 version of QEMU is also included. You can try weird things such as:
1127 qemu-i386 /usr/local/qemu-i386/bin/qemu-i386 /usr/local/qemu-i386/bin/ls-i386
1132 @section Wine launch
1136 @item Ensure that you have a working QEMU with the x86 glibc
1137 distribution (see previous section). In order to verify it, you must be
1141 qemu-i386 /usr/local/qemu-i386/bin/ls-i386
1144 @item Download the binary x86 Wine install
1145 (@file{qemu-XXX-i386-wine.tar.gz} on the QEMU web page).
1147 @item Configure Wine on your account. Look at the provided script
1148 @file{/usr/local/qemu-i386/bin/wine-conf.sh}. Your previous
1149 @code{$@{HOME@}/.wine} directory is saved to @code{$@{HOME@}/.wine.org}.
1151 @item Then you can try the example @file{putty.exe}:
1154 qemu-i386 /usr/local/qemu-i386/wine/bin/wine /usr/local/qemu-i386/wine/c/Program\ Files/putty.exe
1159 @section Command line options
1162 usage: qemu-i386 [-h] [-d] [-L path] [-s size] program [arguments...]
1169 Set the x86 elf interpreter prefix (default=/usr/local/qemu-i386)
1171 Set the x86 stack size in bytes (default=524288)
1178 Activate log (logfile=/tmp/qemu.log)
1180 Act as if the host page size was 'pagesize' bytes
1184 @chapter Compilation from the sources
1188 Read the @file{README} which gives the related information.
1193 @item Install the current versions of MSYS and MinGW from
1194 @url{http://www.mingw.org/}. You can find detailed installation
1195 instructions in the download section and the FAQ.
1198 the MinGW development library of SDL 1.2.x
1199 (@file{SDL-devel-1.2.x-mingw32.tar.gz}) from
1200 @url{http://www.libsdl.org}. Unpack it in a temporary place, and
1201 unpack the archive @file{i386-mingw32msvc.tar.gz} in the MinGW tool
1202 directory. Edit the @file{sdl-config} script so that it gives the
1203 correct SDL directory when invoked.
1205 @item Extract the current version of QEMU.
1207 @item Start the MSYS shell (file @file{msys.bat}).
1209 @item Change to the QEMU directory. Launch @file{./configure} and
1210 @file{make}. If you have problems using SDL, verify that
1211 @file{sdl-config} can be launched from the MSYS command line.
1213 @item You can install QEMU in @file{Program Files/Qemu} by typing
1214 @file{make install}. Don't forget to copy @file{SDL.dll} in
1215 @file{Program Files/Qemu}.
1219 @section Cross compilation for Windows with Linux
1223 Install the MinGW cross compilation tools available at
1224 @url{http://www.mingw.org/}.
1227 Install the Win32 version of SDL (@url{http://www.libsdl.org}) by
1228 unpacking @file{i386-mingw32msvc.tar.gz}. Set up the PATH environment
1229 variable so that @file{i386-mingw32msvc-sdl-config} can be launched by
1230 the QEMU configuration script.
1233 Configure QEMU for Windows cross compilation:
1235 ./configure --enable-mingw32
1237 If necessary, you can change the cross-prefix according to the prefix
1238 choosen for the MinGW tools with --cross-prefix. You can also use
1239 --prefix to set the Win32 install path.
1241 @item You can install QEMU in the installation directory by typing
1242 @file{make install}. Don't forget to copy @file{SDL.dll} in the
1243 installation directory.
1247 Note: Currently, Wine does not seem able to launch
1252 The Mac OS X patches are not fully merged in QEMU, so you should look
1253 at the QEMU mailing list archive to have all the necessary