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.
185 Use @var{file} as initial ram disk.
189 Normally, QEMU uses SDL to display the VGA output. With this option,
190 you can totally disable graphical output so that QEMU is a simple
191 command line application. The emulated serial port is redirected on
192 the console. Therefore, you can still use QEMU to debug a Linux kernel
193 with a serial console.
197 The SB16 emulation is disabled by default as it may give problems with
198 Windows. You can enable it manually with this option.
201 Set the real time clock to local time (the default is to UTC
202 time). This option is needed to have correct date in MS-DOS or
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 Use the dummy network stack: no packet will be received by the network
237 Linux boot specific. When using this options, you can use a given
238 Linux kernel without installing it in the disk image. It can be useful
239 for easier testing of various kernels.
243 @item -kernel bzImage
244 Use @var{bzImage} as kernel image.
246 @item -append cmdline
247 Use @var{cmdline} as kernel command line
250 Use @var{file} as initial ram disk.
254 Debug/Expert options:
258 Redirect the virtual serial port to host device @var{dev}. Available
264 [Linux only] Pseudo TTY (a new PTY is automatically allocated)
268 [Unix only] standard input/output
270 The default device is @code{vc} in graphical mode and @code{stdio} in
274 Redirect the monitor to host device @var{dev} (same devices as the
276 The default device is @code{vc} in graphical mode and @code{stdio} in
280 Wait gdb connection to port 1234 (@xref{gdb_usage}).
282 Change gdb connection port.
284 Do not start CPU at startup (you must type 'c' in the monitor).
286 Output log in /tmp/qemu.log
288 Simulate an ISA-only system (default is PCI system).
290 Simulate a standard VGA card with Bochs VBE extensions (default is
291 Cirrus Logic GD5446 PCI VGA)
301 During the graphical emulation, you can use the following keys:
307 Switch to virtual console 'n'. Standard console mappings are:
310 Target system display
318 Toggle mouse and keyboard grab.
321 In the virtual consoles, you can use @key{Ctrl-Up}, @key{Ctrl-Down},
322 @key{Ctrl-PageUp} and @key{Ctrl-PageDown} to move in the back log.
324 During emulation, if you are using the @option{-nographic} option, use
325 @key{Ctrl-a h} to get terminal commands:
333 Save disk data back to file (if -snapshot)
335 Send break (magic sysrq in Linux)
337 Switch between console and monitor
346 @settitle QEMU System Emulator
349 The HTML documentation of QEMU for more precise information and Linux
350 user mode emulator invocation.
362 @section QEMU Monitor
364 The QEMU monitor is used to give complex commands to the QEMU
365 emulator. You can use it to:
370 Remove or insert removable medias images
371 (such as CD-ROM or floppies)
374 Freeze/unfreeze the Virtual Machine (VM) and save or restore its state
377 @item Inspect the VM state without an external debugger.
383 The following commands are available:
387 @item help or ? [cmd]
388 Show the help for all commands or just for command @var{cmd}.
391 Commit changes to the disk images (if -snapshot is used)
393 @item info subcommand
394 show various information about the system state
398 show the network state
400 show the block devices
402 show the cpu registers
404 show the command line history
410 @item eject [-f] device
411 Eject a removable media (use -f to force it).
413 @item change device filename
414 Change a removable media.
416 @item screendump filename
417 Save screen into PPM image @var{filename}.
419 @item log item1[,...]
420 Activate logging of the specified items to @file{/tmp/qemu.log}.
422 @item savevm filename
423 Save the whole virtual machine state to @var{filename}.
425 @item loadvm filename
426 Restore the whole virtual machine state from @var{filename}.
434 @item gdbserver [port]
435 Start gdbserver session (default port=1234)
438 Virtual memory dump starting at @var{addr}.
441 Physical memory dump starting at @var{addr}.
443 @var{fmt} is a format which tells the command how to format the
444 data. Its syntax is: @option{/@{count@}@{format@}@{size@}}
448 is the number of items to be dumped.
451 can be x (hexa), d (signed decimal), u (unsigned decimal), o (octal),
452 c (char) or i (asm instruction).
455 can be b (8 bits), h (16 bits), w (32 bits) or g (64 bits). On x86,
456 @code{h} or @code{w} can be specified with the @code{i} format to
457 respectively select 16 or 32 bit code instruction size.
464 Dump 10 instructions at the current instruction pointer:
469 0x90107065: lea 0x0(%esi,1),%esi
470 0x90107069: lea 0x0(%edi,1),%edi
472 0x90107071: jmp 0x90107080
480 Dump 80 16 bit values at the start of the video memory.
482 (qemu) xp/80hx 0xb8000
483 0x000b8000: 0x0b50 0x0b6c 0x0b65 0x0b78 0x0b38 0x0b36 0x0b2f 0x0b42
484 0x000b8010: 0x0b6f 0x0b63 0x0b68 0x0b73 0x0b20 0x0b56 0x0b47 0x0b41
485 0x000b8020: 0x0b42 0x0b69 0x0b6f 0x0b73 0x0b20 0x0b63 0x0b75 0x0b72
486 0x000b8030: 0x0b72 0x0b65 0x0b6e 0x0b74 0x0b2d 0x0b63 0x0b76 0x0b73
487 0x000b8040: 0x0b20 0x0b30 0x0b35 0x0b20 0x0b4e 0x0b6f 0x0b76 0x0b20
488 0x000b8050: 0x0b32 0x0b30 0x0b30 0x0b33 0x0720 0x0720 0x0720 0x0720
489 0x000b8060: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
490 0x000b8070: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
491 0x000b8080: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
492 0x000b8090: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
496 @item p or print/fmt expr
498 Print expression value. Only the @var{format} part of @var{fmt} is
503 Send @var{keys} to the emulator. Use @code{-} to press several keys
504 simultaneously. Example:
509 This command is useful to send keys that your graphical user interface
510 intercepts at low level, such as @code{ctrl-alt-f1} in X Window.
518 @subsection Integer expressions
520 The monitor understands integers expressions for every integer
521 argument. You can use register names to get the value of specifics
522 CPU registers by prefixing them with @emph{$}.
527 @subsection Raw disk images
529 The disk images can simply be raw images of the hard disk. You can
530 create them with the command:
532 dd of=myimage bs=1024 seek=mysize count=0
534 where @var{myimage} is the image filename and @var{mysize} is its size
537 @subsection Snapshot mode
539 If you use the option @option{-snapshot}, all disk images are
540 considered as read only. When sectors in written, they are written in
541 a temporary file created in @file{/tmp}. You can however force the
542 write back to the raw disk images by pressing @key{C-a s}.
544 NOTE: The snapshot mode only works with raw disk images.
546 @subsection Copy On Write disk images
548 QEMU also supports user mode Linux
549 (@url{http://user-mode-linux.sourceforge.net/}) Copy On Write (COW)
550 disk images. The COW disk images are much smaller than normal images
551 as they store only modified sectors. They also permit the use of the
552 same disk image template for many users.
554 To create a COW disk images, use the command:
557 qemu-mkcow -f myrawimage.bin mycowimage.cow
560 @file{myrawimage.bin} is a raw image you want to use as original disk
561 image. It will never be written to.
563 @file{mycowimage.cow} is the COW disk image which is created by
564 @code{qemu-mkcow}. You can use it directly with the @option{-hdx}
565 options. You must not modify the original raw disk image if you use
566 COW images, as COW images only store the modified sectors from the raw
567 disk image. QEMU stores the original raw disk image name and its
568 modified time in the COW disk image so that chances of mistakes are
571 If the raw disk image is not read-only, by pressing @key{C-a s} you
572 can flush the COW disk image back into the raw disk image, as in
575 COW disk images can also be created without a corresponding raw disk
576 image. It is useful to have a big initial virtual disk image without
577 using much disk space. Use:
580 qemu-mkcow mycowimage.cow 1024
583 to create a 1 gigabyte empty COW disk image.
588 COW disk images must be created on file systems supporting
589 @emph{holes} such as ext2 or ext3.
591 Since holes are used, the displayed size of the COW disk image is not
592 the real one. To know it, use the @code{ls -ls} command.
595 @subsection Convert VMware disk images to raw disk images
597 You can use the tool @file{vmdk2raw} to convert VMware disk images to
598 raw disk images directly usable by QEMU. The syntax is:
600 vmdk2raw vmware_image output_image
603 @section Network emulation
605 QEMU simulates up to 6 networks cards (NE2000 boards). Each card can
606 be connected to a specific host network interface.
608 @subsection Using tun/tap network interface
610 This is the standard way to emulate network. QEMU adds a virtual
611 network device on your host (called @code{tun0}), and you can then
612 configure it as if it was a real ethernet card.
614 As an example, you can download the @file{linux-test-xxx.tar.gz}
615 archive and copy the script @file{qemu-ifup} in @file{/etc} and
616 configure properly @code{sudo} so that the command @code{ifconfig}
617 contained in @file{qemu-ifup} can be executed as root. You must verify
618 that your host kernel supports the TUN/TAP network interfaces: the
619 device @file{/dev/net/tun} must be present.
621 See @ref{direct_linux_boot} to have an example of network use with a
624 @subsection Using the user mode network stack
626 By using the option @option{-user-net} or if you have no tun/tap init
627 script, QEMU uses a completely user mode network stack (you don't need
628 root priviledge to use the virtual network). The virtual network
629 configuration is the following:
633 QEMU Virtual Machine <------> Firewall/DHCP server <-----> Internet
634 (10.0.2.x) | (10.0.2.2)
640 The QEMU VM behaves as if it was behind a firewall which blocks all
641 incoming connections. You can use a DHCP client to automatically
642 configure the network in the QEMU VM.
644 In order to check that the user mode network is working, you can ping
645 the address 10.0.2.2 and verify that you got an address in the range
646 10.0.2.x from the QEMU virtual DHCP server.
648 Note that @code{ping} is not supported reliably to the internet as it
649 would require root priviledges. It means you can only ping the local
652 The user mode network is currently only supported on a Unix host.
654 @node direct_linux_boot
655 @section Direct Linux Boot
657 This section explains how to launch a Linux kernel inside QEMU without
658 having to make a full bootable image. It is very useful for fast Linux
659 kernel testing. The QEMU network configuration is also explained.
663 Download the archive @file{linux-test-xxx.tar.gz} containing a Linux
664 kernel and a disk image.
666 @item Optional: If you want network support (for example to launch X11 examples), you
667 must copy the script @file{qemu-ifup} in @file{/etc} and configure
668 properly @code{sudo} so that the command @code{ifconfig} contained in
669 @file{qemu-ifup} can be executed as root. You must verify that your host
670 kernel supports the TUN/TAP network interfaces: the device
671 @file{/dev/net/tun} must be present.
673 When network is enabled, there is a virtual network connection between
674 the host kernel and the emulated kernel. The emulated kernel is seen
675 from the host kernel at IP address 172.20.0.2 and the host kernel is
676 seen from the emulated kernel at IP address 172.20.0.1.
678 @item Launch @code{qemu.sh}. You should have the following output:
682 Connected to host network interface: tun0
683 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
684 BIOS-provided physical RAM map:
685 BIOS-e801: 0000000000000000 - 000000000009f000 (usable)
686 BIOS-e801: 0000000000100000 - 0000000002000000 (usable)
687 32MB LOWMEM available.
688 On node 0 totalpages: 8192
692 Kernel command line: root=/dev/hda sb=0x220,5,1,5 ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe console=ttyS0
693 ide_setup: ide2=noprobe
694 ide_setup: ide3=noprobe
695 ide_setup: ide4=noprobe
696 ide_setup: ide5=noprobe
698 Detected 2399.621 MHz processor.
699 Console: colour EGA 80x25
700 Calibrating delay loop... 4744.80 BogoMIPS
701 Memory: 28872k/32768k available (1210k kernel code, 3508k reserved, 266k data, 64k init, 0k highmem)
702 Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
703 Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
704 Mount cache hash table entries: 512 (order: 0, 4096 bytes)
705 Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
706 Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
707 CPU: Intel Pentium Pro stepping 03
708 Checking 'hlt' instruction... OK.
709 POSIX conformance testing by UNIFIX
710 Linux NET4.0 for Linux 2.4
711 Based upon Swansea University Computer Society NET3.039
712 Initializing RT netlink socket
715 Journalled Block Device driver loaded
716 Detected PS/2 Mouse Port.
717 pty: 256 Unix98 ptys configured
718 Serial driver version 5.05c (2001-07-08) with no serial options enabled
719 ttyS00 at 0x03f8 (irq = 4) is a 16450
720 ne.c:v1.10 9/23/94 Donald Becker (becker@scyld.com)
721 Last modified Nov 1, 2000 by Paul Gortmaker
722 NE*000 ethercard probe at 0x300: 52 54 00 12 34 56
723 eth0: NE2000 found at 0x300, using IRQ 9.
724 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
725 Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
726 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
727 hda: QEMU HARDDISK, ATA DISK drive
728 ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
729 hda: attached ide-disk driver.
730 hda: 20480 sectors (10 MB) w/256KiB Cache, CHS=20/16/63
733 Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
734 NET4: Linux TCP/IP 1.0 for NET4.0
735 IP Protocols: ICMP, UDP, TCP, IGMP
736 IP: routing cache hash table of 512 buckets, 4Kbytes
737 TCP: Hash tables configured (established 2048 bind 4096)
738 NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
739 EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
740 VFS: Mounted root (ext2 filesystem).
741 Freeing unused kernel memory: 64k freed
743 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
745 QEMU Linux test distribution (based on Redhat 9)
747 Type 'exit' to halt the system
753 Then you can play with the kernel inside the virtual serial console. You
754 can launch @code{ls} for example. Type @key{Ctrl-a h} to have an help
755 about the keys you can type inside the virtual serial console. In
756 particular, use @key{Ctrl-a x} to exit QEMU and use @key{Ctrl-a b} as
760 If the network is enabled, launch the script @file{/etc/linuxrc} in the
761 emulator (don't forget the leading dot):
766 Then enable X11 connections on your PC from the emulated Linux:
771 You can now launch @file{xterm} or @file{xlogo} and verify that you have
772 a real Virtual Linux system !
779 A 2.5.74 kernel is also included in the archive. Just
780 replace the bzImage in qemu.sh to try it.
783 qemu-fast creates a temporary file in @var{$QEMU_TMPDIR} (@file{/tmp} is the
784 default) containing all the simulated PC memory. If possible, try to use
785 a temporary directory using the tmpfs filesystem to avoid too many
786 unnecessary disk accesses.
789 In order to exit cleanly from qemu, you can do a @emph{shutdown} inside
790 qemu. qemu will automatically exit when the Linux shutdown is done.
793 You can boot slightly faster by disabling the probe of non present IDE
794 interfaces. To do so, add the following options on the kernel command
797 ide1=noprobe ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe
801 The example disk image is a modified version of the one made by Kevin
802 Lawton for the plex86 Project (@url{www.plex86.org}).
807 @section Linux Kernel Compilation
809 You can use any linux kernel with QEMU. However, if you want to use
810 @code{qemu-fast} to get maximum performances, you must use a modified
811 guest kernel. If you are using a 2.6 guest kernel, you can use
812 directly the patch @file{linux-2.6-qemu-fast.patch} made by Rusty
813 Russel available in the QEMU source archive. Otherwise, you can make the
814 following changes @emph{by hand} to the Linux kernel:
818 The kernel must be mapped at 0x90000000 (the default is
819 0xc0000000). You must modify only two lines in the kernel source:
821 In @file{include/asm/page.h}, replace
823 #define __PAGE_OFFSET (0xc0000000)
827 #define __PAGE_OFFSET (0x90000000)
830 And in @file{arch/i386/vmlinux.lds}, replace
832 . = 0xc0000000 + 0x100000;
836 . = 0x90000000 + 0x100000;
840 If you want to enable SMP (Symmetric Multi-Processing) support, you
841 must make the following change in @file{include/asm/fixmap.h}. Replace
843 #define FIXADDR_TOP (0xffffX000UL)
847 #define FIXADDR_TOP (0xa7ffX000UL)
849 (X is 'e' or 'f' depending on the kernel version). Although you can
850 use an SMP kernel with QEMU, it only supports one CPU.
853 If you are not using a 2.6 kernel as host kernel but if you use a target
854 2.6 kernel, you must also ensure that the 'HZ' define is set to 100
855 (1000 is the default) as QEMU cannot currently emulate timers at
856 frequencies greater than 100 Hz on host Linux systems < 2.6. In
857 @file{include/asm/param.h}, replace:
860 # define HZ 1000 /* Internal kernel timer frequency */
864 # define HZ 100 /* Internal kernel timer frequency */
869 The file config-2.x.x gives the configuration of the example kernels.
876 As you would do to make a real kernel. Then you can use with QEMU
877 exactly the same kernel as you would boot on your PC (in
878 @file{arch/i386/boot/bzImage}).
883 QEMU has a primitive support to work with gdb, so that you can do
884 'Ctrl-C' while the virtual machine is running and inspect its state.
886 In order to use gdb, launch qemu with the '-s' option. It will wait for a
889 > qemu -s -kernel arch/i386/boot/bzImage -hda root-2.4.20.img -append "root=/dev/hda"
890 Connected to host network interface: tun0
891 Waiting gdb connection on port 1234
894 Then launch gdb on the 'vmlinux' executable:
899 In gdb, connect to QEMU:
901 (gdb) target remote localhost:1234
904 Then you can use gdb normally. For example, type 'c' to launch the kernel:
909 Here are some useful tips in order to use gdb on system code:
913 Use @code{info reg} to display all the CPU registers.
915 Use @code{x/10i $eip} to display the code at the PC position.
917 Use @code{set architecture i8086} to dump 16 bit code. Then use
918 @code{x/10i $cs*16+*eip} to dump the code at the PC position.
921 @section Target OS specific information
925 To have access to SVGA graphic modes under X11, use the @code{vesa} or
926 the @code{cirrus} X11 driver. For optimal performances, use 16 bit
927 color depth in the guest and the host OS.
929 When using a 2.6 guest Linux kernel, you should add the option
930 @code{clock=pit} on the kernel command line because the 2.6 Linux
931 kernels make very strict real time clock checks by default that QEMU
932 cannot simulate exactly.
936 If you have a slow host, using Windows 95 is better as it gives the
937 best speed. Windows 2000 is also a good choice.
939 @subsubsection SVGA graphic modes support
941 QEMU emulates a Cirrus Logic GD5446 Video
942 card. All Windows versions starting from Windows 95 should recognize
943 and use this graphic card. For optimal performances, use 16 bit color
944 depth in the guest and the host OS.
946 @subsubsection CPU usage reduction
948 Windows 9x does not correctly use the CPU HLT
949 instruction. The result is that it takes host CPU cycles even when
950 idle. You can install the utility from
951 @url{http://www.user.cityline.ru/~maxamn/amnhltm.zip} to solve this
952 problem. Note that no such tool is needed for NT, 2000 or XP.
954 @subsubsection Windows 2000 disk full problems
956 Currently (release 0.6.0) QEMU has a bug which gives a @code{disk
957 full} error during installation of some releases of Windows 2000. The
958 workaround is to stop QEMU as soon as you notice that your disk image
959 size is growing too fast (monitor it with @code{ls -ls}). Then
960 relaunch QEMU to continue the installation. If you still experience
961 the problem, relaunch QEMU again.
963 Future QEMU releases are likely to correct this bug.
965 @subsubsection Windows XP security problems
967 Some releases of Windows XP install correctly but give a security
970 A problem is preventing Windows from accurately checking the
971 license for this computer. Error code: 0x800703e6.
973 The only known workaround is to boot in Safe mode
974 without networking support.
976 Future QEMU releases are likely to correct this bug.
978 @subsection MS-DOS and FreeDOS
980 @subsubsection CPU usage reduction
982 DOS does not correctly use the CPU HLT instruction. The result is that
983 it takes host CPU cycles even when idle. You can install the utility
984 from @url{http://www.vmware.com/software/dosidle210.zip} to solve this
987 @chapter QEMU PowerPC System emulator invocation
989 Use the executable @file{qemu-system-ppc} to simulate a complete PREP
990 or PowerMac PowerPC system.
992 QEMU emulates the following PowerMac peripherials:
998 PCI VGA compatible card with VESA Bochs Extensions
1000 2 PMAC IDE interfaces with hard disk and CD-ROM support
1006 VIA-CUDA with ADB keyboard and mouse.
1009 QEMU emulates the following PREP peripherials:
1015 PCI VGA compatible card with VESA Bochs Extensions
1017 2 IDE interfaces with hard disk and CD-ROM support
1021 NE2000 network adapters
1025 PREP Non Volatile RAM
1027 PC compatible keyboard and mouse.
1030 QEMU uses the Open Hack'Ware Open Firmware Compatible BIOS available at
1031 @url{http://site.voila.fr/jmayer/OpenHackWare/index.htm}.
1033 You can read the qemu PC system emulation chapter to have more
1034 informations about QEMU usage.
1036 @c man begin OPTIONS
1038 The following options are specific to the PowerPC emulation:
1043 Simulate a PREP system (default is PowerMAC)
1045 @item -g WxH[xDEPTH]
1047 Set the initial VGA graphic mode. The default is 800x600x15.
1054 More information is available at
1055 @url{http://jocelyn.mayer.free.fr/qemu-ppc/}.
1057 @chapter QEMU User space emulator invocation
1059 @section Quick Start
1061 In order to launch a Linux process, QEMU needs the process executable
1062 itself and all the target (x86) dynamic libraries used by it.
1066 @item On x86, you can just try to launch any process by using the native
1070 qemu-i386 -L / /bin/ls
1073 @code{-L /} tells that the x86 dynamic linker must be searched with a
1076 @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):
1079 qemu-i386 -L / qemu-i386 -L / /bin/ls
1082 @item On non x86 CPUs, you need first to download at least an x86 glibc
1083 (@file{qemu-runtime-i386-XXX-.tar.gz} on the QEMU web page). Ensure that
1084 @code{LD_LIBRARY_PATH} is not set:
1087 unset LD_LIBRARY_PATH
1090 Then you can launch the precompiled @file{ls} x86 executable:
1093 qemu-i386 tests/i386/ls
1095 You can look at @file{qemu-binfmt-conf.sh} so that
1096 QEMU is automatically launched by the Linux kernel when you try to
1097 launch x86 executables. It requires the @code{binfmt_misc} module in the
1100 @item The x86 version of QEMU is also included. You can try weird things such as:
1102 qemu-i386 /usr/local/qemu-i386/bin/qemu-i386 /usr/local/qemu-i386/bin/ls-i386
1107 @section Wine launch
1111 @item Ensure that you have a working QEMU with the x86 glibc
1112 distribution (see previous section). In order to verify it, you must be
1116 qemu-i386 /usr/local/qemu-i386/bin/ls-i386
1119 @item Download the binary x86 Wine install
1120 (@file{qemu-XXX-i386-wine.tar.gz} on the QEMU web page).
1122 @item Configure Wine on your account. Look at the provided script
1123 @file{/usr/local/qemu-i386/bin/wine-conf.sh}. Your previous
1124 @code{$@{HOME@}/.wine} directory is saved to @code{$@{HOME@}/.wine.org}.
1126 @item Then you can try the example @file{putty.exe}:
1129 qemu-i386 /usr/local/qemu-i386/wine/bin/wine /usr/local/qemu-i386/wine/c/Program\ Files/putty.exe
1134 @section Command line options
1137 usage: qemu-i386 [-h] [-d] [-L path] [-s size] program [arguments...]
1144 Set the x86 elf interpreter prefix (default=/usr/local/qemu-i386)
1146 Set the x86 stack size in bytes (default=524288)
1153 Activate log (logfile=/tmp/qemu.log)
1155 Act as if the host page size was 'pagesize' bytes
1159 @chapter Compilation from the sources
1163 Read the @file{README} which gives the related information.
1168 @item Install the current versions of MSYS and MinGW from
1169 @url{http://www.mingw.org/}. You can find detailed installation
1170 instructions in the download section and the FAQ.
1173 the MinGW development library of SDL 1.2.x
1174 (@file{SDL-devel-1.2.x-mingw32.tar.gz}) from
1175 @url{http://www.libsdl.org}. Unpack it in a temporary place, and
1176 unpack the archive @file{i386-mingw32msvc.tar.gz} in the MinGW tool
1177 directory. Edit the @file{sdl-config} script so that it gives the
1178 correct SDL directory when invoked.
1180 @item Extract the current version of QEMU.
1182 @item Start the MSYS shell (file @file{msys.bat}).
1184 @item Change to the QEMU directory. Launch @file{./configure} and
1185 @file{make}. If you have problems using SDL, verify that
1186 @file{sdl-config} can be launched from the MSYS command line.
1188 @item You can install QEMU in @file{Program Files/Qemu} by typing
1189 @file{make install}. Don't forget to copy @file{SDL.dll} in
1190 @file{Program Files/Qemu}.
1194 @section Cross compilation for Windows with Linux
1198 Install the MinGW cross compilation tools available at
1199 @url{http://www.mingw.org/}.
1202 Install the Win32 version of SDL (@url{http://www.libsdl.org}) by
1203 unpacking @file{i386-mingw32msvc.tar.gz}. Set up the PATH environment
1204 variable so that @file{i386-mingw32msvc-sdl-config} can be launched by
1205 the QEMU configuration script.
1208 Configure QEMU for Windows cross compilation:
1210 ./configure --enable-mingw32
1212 If necessary, you can change the cross-prefix according to the prefix
1213 choosen for the MinGW tools with --cross-prefix. You can also use
1214 --prefix to set the Win32 install path.
1216 @item You can install QEMU in the installation directory by typing
1217 @file{make install}. Don't forget to copy @file{SDL.dll} in the
1218 installation directory.
1222 Note: Currently, Wine does not seem able to launch
1227 The Mac OS X patches are not fully merged in QEMU, so you should look
1228 at the QEMU mailing list archive to have all the necessary