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)
46 For user emulation, x86, PowerPC, ARM, and SPARC CPUs are supported.
52 If you want to compile QEMU, please read the @file{README} which gives
53 the related information. Otherwise just download the binary
54 distribution (@file{qemu-XXX-i386.tar.gz}) and untar it as root in
60 tar zxvf /tmp/qemu-XXX-i386.tar.gz
66 @item Install the current versions of MSYS and MinGW from
67 @url{http://www.mingw.org/}. You can find detailed installation
68 instructions in the download section and the FAQ.
71 the MinGW development library of SDL 1.2.x
72 (@file{SDL-devel-1.2.x-mingw32.tar.gz}) from
73 @url{http://www.libsdl.org}. Unpack it in a temporary place, and
74 unpack the archive @file{i386-mingw32msvc.tar.gz} in the MinGW tool
75 directory. Edit the @file{sdl-config} script so that it gives the
76 correct SDL directory when invoked.
78 @item Extract the current version of QEMU.
80 @item Start the MSYS shell (file @file{msys.bat}).
82 @item Change to the QEMU directory. Launch @file{./configure} and
83 @file{make}. If you have problems using SDL, verify that
84 @file{sdl-config} can be launched from the MSYS command line.
86 @item You can install QEMU in @file{Program Files/Qemu} by typing
87 @file{make install}. Don't forget to copy @file{SDL.dll} in
88 @file{Program Files/Qemu}.
92 @section Cross compilation for Windows with Linux
96 Install the MinGW cross compilation tools available at
97 @url{http://www.mingw.org/}.
100 Install the Win32 version of SDL (@url{http://www.libsdl.org}) by
101 unpacking @file{i386-mingw32msvc.tar.gz}. Set up the PATH environment
102 variable so that @file{i386-mingw32msvc-sdl-config} can be launched by
103 the QEMU configuration script.
106 Configure QEMU for Windows cross compilation:
108 ./configure --enable-mingw32
110 If necessary, you can change the cross-prefix according to the prefix
111 choosen for the MinGW tools with --cross-prefix. You can also use
112 --prefix to set the Win32 install path.
114 @item You can install QEMU in the installation directory by typing
115 @file{make install}. Don't forget to copy @file{SDL.dll} in the
116 installation directory.
120 Note: Currently, Wine does not seem able to launch
125 Mac OS X is currently not supported.
127 @chapter QEMU PC System emulator invocation
129 @section Introduction
131 @c man begin DESCRIPTION
133 The QEMU System emulator simulates a complete PC.
135 In order to meet specific user needs, two versions of QEMU are
141 @code{qemu-fast} uses the host Memory Management Unit (MMU) to simulate
142 the x86 MMU. It is @emph{fast} but has limitations because the whole 4 GB
143 address space cannot be used and some memory mapped peripherials
144 cannot be emulated accurately yet. Therefore, a specific Linux kernel
145 must be used (@xref{linux_compile}).
148 @code{qemu} uses a software MMU. It is about @emph{two times
149 slower} but gives a more accurate emulation.
153 QEMU emulates the following PC peripherials:
157 VGA (hardware level, including all non standard modes)
159 PS/2 mouse and keyboard
161 2 IDE interfaces with hard disk and CD-ROM support
165 up to 6 NE2000 network adapters
176 Download and uncompress the linux image (@file{linux.img}) and type:
182 Linux should boot and give you a prompt.
187 @c man begin SYNOPSIS
188 usage: qemu [options] [disk_image]
193 @var{disk_image} is a raw hard disk image for IDE hard disk 0.
199 Use @var{file} as floppy disk 0/1 image (@xref{disk_images}). You can
200 use the host floppy by using @file{/dev/fd0} as filename.
206 Use @var{file} as hard disk 0, 1, 2 or 3 image (@xref{disk_images}).
209 Use @var{file} as CD-ROM image (you cannot use @option{-hdc} and and
210 @option{-cdrom} at the same time). You can use the host CD-ROM by
211 using @file{/dev/cdrom} as filename.
214 Boot on floppy (a), hard disk (c) or CD-ROM (d). Hard disk boot is
218 Write to temporary files instead of disk image files. In this case,
219 the raw disk image you use is not written back. You can however force
220 the write back by pressing @key{C-a s} (@xref{disk_images}).
223 Set virtual RAM size to @var{megs} megabytes.
226 Use @var{file} as initial ram disk.
230 Normally, QEMU uses SDL to display the VGA output. With this option,
231 you can totally disable graphical output so that QEMU is a simple
232 command line application. The emulated serial port is redirected on
233 the console. Therefore, you can still use QEMU to debug a Linux kernel
234 with a serial console.
238 The SB16 emulation is disabled by default as it may give problems with
239 Windows. You can enable it manually with this option.
248 Set TUN/TAP network init script [default=/etc/qemu-ifup]. This script
249 is launched to configure the host network interface (usually tun0)
250 corresponding to the virtual NE2000 card.
254 Set the mac address of the first interface (the format is
255 aa:bb:cc:dd:ee:ff in hexa). The mac address is incremented for each
256 new network interface.
259 Assumes @var{fd} talks to a tap/tun host network interface and use
260 it. Read @url{http://bellard.org/qemu/tetrinet.html} to have an
264 (Experimental) Use the user mode network stack. This is the default if
265 no tun/tap network init script is found.
268 Use the dummy network stack: no packet will be received on the network
273 Linux boot specific. When using this options, you can use a given
274 Linux kernel without installing it in the disk image. It can be useful
275 for easier testing of various kernels.
279 @item -kernel bzImage
280 Use @var{bzImage} as kernel image.
282 @item -append cmdline
283 Use @var{cmdline} as kernel command line
286 Use @var{file} as initial ram disk.
293 Wait gdb connection to port 1234 (@xref{gdb_usage}).
295 Change gdb connection port.
297 Do not start CPU at startup (you must type 'c' in the monitor).
299 Output log in /tmp/qemu.log
302 During the graphical emulation, you can use the following keys:
305 Toggle mouse and keyboard grab.
310 During emulation, if you are using the serial console, use @key{C-a h}
311 to get terminal commands:
319 Save disk data back to file (if -snapshot)
321 Send break (magic sysrq in Linux)
323 Switch between console and monitor
332 @settitle QEMU System Emulator
335 The HTML documentation of QEMU for more precise information and Linux
336 user mode emulator invocation.
348 @section QEMU Monitor
350 The QEMU monitor is used to give complex commands to the QEMU
351 emulator. You can use it to:
356 Remove or insert removable medias images
357 (such as CD-ROM or floppies)
360 Freeze/unfreeze the Virtual Machine (VM) and save or restore its state
363 @item Inspect the VM state without an external debugger.
369 The following commands are available:
373 @item help or ? [cmd]
374 Show the help for all commands or just for command @var{cmd}.
377 Commit changes to the disk images (if -snapshot is used)
379 @item info subcommand
380 show various information about the system state
384 show the network state
386 show the block devices
388 show the cpu registers
390 show the command line history
396 @item eject [-f] device
397 Eject a removable media (use -f to force it).
399 @item change device filename
400 Change a removable media.
402 @item screendump filename
403 Save screen into PPM image @var{filename}.
405 @item log item1[,...]
406 Activate logging of the specified items to @file{/tmp/qemu.log}.
408 @item savevm filename
409 Save the whole virtual machine state to @var{filename}.
411 @item loadvm filename
412 Restore the whole virtual machine state from @var{filename}.
420 @item gdbserver [port]
421 Start gdbserver session (default port=1234)
424 Virtual memory dump starting at @var{addr}.
427 Physical memory dump starting at @var{addr}.
429 @var{fmt} is a format which tells the command how to format the
430 data. Its syntax is: @option{/@{count@}@{format@}@{size@}}
434 is the number of items to be dumped.
437 can be x (hexa), d (signed decimal), u (unsigned decimal), o (octal),
438 c (char) or i (asm instruction).
441 can be b (8 bits), h (16 bits), w (32 bits) or g (64 bits). On x86,
442 @code{h} or @code{w} can be specified with the @code{i} format to
443 respectively select 16 or 32 bit code instruction size.
450 Dump 10 instructions at the current instruction pointer:
455 0x90107065: lea 0x0(%esi,1),%esi
456 0x90107069: lea 0x0(%edi,1),%edi
458 0x90107071: jmp 0x90107080
466 Dump 80 16 bit values at the start of the video memory.
468 (qemu) xp/80hx 0xb8000
469 0x000b8000: 0x0b50 0x0b6c 0x0b65 0x0b78 0x0b38 0x0b36 0x0b2f 0x0b42
470 0x000b8010: 0x0b6f 0x0b63 0x0b68 0x0b73 0x0b20 0x0b56 0x0b47 0x0b41
471 0x000b8020: 0x0b42 0x0b69 0x0b6f 0x0b73 0x0b20 0x0b63 0x0b75 0x0b72
472 0x000b8030: 0x0b72 0x0b65 0x0b6e 0x0b74 0x0b2d 0x0b63 0x0b76 0x0b73
473 0x000b8040: 0x0b20 0x0b30 0x0b35 0x0b20 0x0b4e 0x0b6f 0x0b76 0x0b20
474 0x000b8050: 0x0b32 0x0b30 0x0b30 0x0b33 0x0720 0x0720 0x0720 0x0720
475 0x000b8060: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
476 0x000b8070: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
477 0x000b8080: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
478 0x000b8090: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720
482 @item p or print/fmt expr
484 Print expression value. Only the @var{format} part of @var{fmt} is
489 Send @var{keys} to the emulator. Use @code{-} to press several keys
490 simultaneously. Example:
495 This command is useful to send keys that your graphical user interface
496 intercepts at low level, such as @code{ctrl-alt-f1} in X Window.
500 @subsection Integer expressions
502 The monitor understands integers expressions for every integer
503 argument. You can use register names to get the value of specifics
504 CPU registers by prefixing them with @emph{$}.
509 @subsection Raw disk images
511 The disk images can simply be raw images of the hard disk. You can
512 create them with the command:
514 dd of=myimage bs=1024 seek=mysize count=0
516 where @var{myimage} is the image filename and @var{mysize} is its size
519 @subsection Snapshot mode
521 If you use the option @option{-snapshot}, all disk images are
522 considered as read only. When sectors in written, they are written in
523 a temporary file created in @file{/tmp}. You can however force the
524 write back to the raw disk images by pressing @key{C-a s}.
526 NOTE: The snapshot mode only works with raw disk images.
528 @subsection Copy On Write disk images
530 QEMU also supports user mode Linux
531 (@url{http://user-mode-linux.sourceforge.net/}) Copy On Write (COW)
532 disk images. The COW disk images are much smaller than normal images
533 as they store only modified sectors. They also permit the use of the
534 same disk image template for many users.
536 To create a COW disk images, use the command:
539 qemu-mkcow -f myrawimage.bin mycowimage.cow
542 @file{myrawimage.bin} is a raw image you want to use as original disk
543 image. It will never be written to.
545 @file{mycowimage.cow} is the COW disk image which is created by
546 @code{qemu-mkcow}. You can use it directly with the @option{-hdx}
547 options. You must not modify the original raw disk image if you use
548 COW images, as COW images only store the modified sectors from the raw
549 disk image. QEMU stores the original raw disk image name and its
550 modified time in the COW disk image so that chances of mistakes are
553 If the raw disk image is not read-only, by pressing @key{C-a s} you
554 can flush the COW disk image back into the raw disk image, as in
557 COW disk images can also be created without a corresponding raw disk
558 image. It is useful to have a big initial virtual disk image without
559 using much disk space. Use:
562 qemu-mkcow mycowimage.cow 1024
565 to create a 1 gigabyte empty COW disk image.
570 COW disk images must be created on file systems supporting
571 @emph{holes} such as ext2 or ext3.
573 Since holes are used, the displayed size of the COW disk image is not
574 the real one. To know it, use the @code{ls -ls} command.
577 @section Network emulation
579 QEMU simulates up to 6 networks cards (NE2000 boards). Each card can
580 be connected to a specific host network interface.
582 @subsection Using tun/tap network interface
584 This is the standard way to emulate network. QEMU adds a virtual
585 network device on your host (called @code{tun0}), and you can then
586 configure it as if it was a real ethernet card.
588 As an example, you can download the @file{linux-test-xxx.tar.gz}
589 archive and copy the script @file{qemu-ifup} in @file{/etc} and
590 configure properly @code{sudo} so that the command @code{ifconfig}
591 contained in @file{qemu-ifup} can be executed as root. You must verify
592 that your host kernel supports the TUN/TAP network interfaces: the
593 device @file{/dev/net/tun} must be present.
595 See @ref{direct_linux_boot} to have an example of network use with a
598 @subsection Using the user mode network stack
600 This is @emph{experimental} (version 0.5.4). You must configure qemu
601 with @code{--enable-slirp}. Then by using the option
602 @option{-user-net} or if you have no tun/tap init script, QEMU uses a
603 completely user mode network stack (you don't need root priviledge to
604 use the virtual network). The virtual network configuration is the
609 QEMU Virtual Machine <------> Firewall/DHCP server <-----> Internet
610 (10.0.2.x) | (10.0.2.2)
616 The QEMU VM behaves as if it was behind a firewall which blocks all
617 incoming connections. You can use a DHCP client to automatically
618 configure the network in the QEMU VM.
620 In order to check that the user mode network is working, you can ping
621 the address 10.0.2.2 and verify that you got an address in the range
622 10.0.2.x from the QEMU virtual DHCP server.
624 Note that @code{ping} is not supported reliably to the internet as it
625 would require root priviledges. It means you can only ping the local
628 @node direct_linux_boot
629 @section Direct Linux Boot
631 This section explains how to launch a Linux kernel inside QEMU without
632 having to make a full bootable image. It is very useful for fast Linux
633 kernel testing. The QEMU network configuration is also explained.
637 Download the archive @file{linux-test-xxx.tar.gz} containing a Linux
638 kernel and a disk image.
640 @item Optional: If you want network support (for example to launch X11 examples), you
641 must copy the script @file{qemu-ifup} in @file{/etc} and configure
642 properly @code{sudo} so that the command @code{ifconfig} contained in
643 @file{qemu-ifup} can be executed as root. You must verify that your host
644 kernel supports the TUN/TAP network interfaces: the device
645 @file{/dev/net/tun} must be present.
647 When network is enabled, there is a virtual network connection between
648 the host kernel and the emulated kernel. The emulated kernel is seen
649 from the host kernel at IP address 172.20.0.2 and the host kernel is
650 seen from the emulated kernel at IP address 172.20.0.1.
652 @item Launch @code{qemu.sh}. You should have the following output:
656 Connected to host network interface: tun0
657 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
658 BIOS-provided physical RAM map:
659 BIOS-e801: 0000000000000000 - 000000000009f000 (usable)
660 BIOS-e801: 0000000000100000 - 0000000002000000 (usable)
661 32MB LOWMEM available.
662 On node 0 totalpages: 8192
666 Kernel command line: root=/dev/hda sb=0x220,5,1,5 ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe console=ttyS0
667 ide_setup: ide2=noprobe
668 ide_setup: ide3=noprobe
669 ide_setup: ide4=noprobe
670 ide_setup: ide5=noprobe
672 Detected 2399.621 MHz processor.
673 Console: colour EGA 80x25
674 Calibrating delay loop... 4744.80 BogoMIPS
675 Memory: 28872k/32768k available (1210k kernel code, 3508k reserved, 266k data, 64k init, 0k highmem)
676 Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
677 Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
678 Mount cache hash table entries: 512 (order: 0, 4096 bytes)
679 Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
680 Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
681 CPU: Intel Pentium Pro stepping 03
682 Checking 'hlt' instruction... OK.
683 POSIX conformance testing by UNIFIX
684 Linux NET4.0 for Linux 2.4
685 Based upon Swansea University Computer Society NET3.039
686 Initializing RT netlink socket
689 Journalled Block Device driver loaded
690 Detected PS/2 Mouse Port.
691 pty: 256 Unix98 ptys configured
692 Serial driver version 5.05c (2001-07-08) with no serial options enabled
693 ttyS00 at 0x03f8 (irq = 4) is a 16450
694 ne.c:v1.10 9/23/94 Donald Becker (becker@scyld.com)
695 Last modified Nov 1, 2000 by Paul Gortmaker
696 NE*000 ethercard probe at 0x300: 52 54 00 12 34 56
697 eth0: NE2000 found at 0x300, using IRQ 9.
698 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
699 Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
700 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
701 hda: QEMU HARDDISK, ATA DISK drive
702 ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
703 hda: attached ide-disk driver.
704 hda: 20480 sectors (10 MB) w/256KiB Cache, CHS=20/16/63
707 Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996
708 NET4: Linux TCP/IP 1.0 for NET4.0
709 IP Protocols: ICMP, UDP, TCP, IGMP
710 IP: routing cache hash table of 512 buckets, 4Kbytes
711 TCP: Hash tables configured (established 2048 bind 4096)
712 NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
713 EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
714 VFS: Mounted root (ext2 filesystem).
715 Freeing unused kernel memory: 64k freed
717 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
719 QEMU Linux test distribution (based on Redhat 9)
721 Type 'exit' to halt the system
727 Then you can play with the kernel inside the virtual serial console. You
728 can launch @code{ls} for example. Type @key{Ctrl-a h} to have an help
729 about the keys you can type inside the virtual serial console. In
730 particular, use @key{Ctrl-a x} to exit QEMU and use @key{Ctrl-a b} as
734 If the network is enabled, launch the script @file{/etc/linuxrc} in the
735 emulator (don't forget the leading dot):
740 Then enable X11 connections on your PC from the emulated Linux:
745 You can now launch @file{xterm} or @file{xlogo} and verify that you have
746 a real Virtual Linux system !
753 A 2.5.74 kernel is also included in the archive. Just
754 replace the bzImage in qemu.sh to try it.
757 qemu-fast creates a temporary file in @var{$QEMU_TMPDIR} (@file{/tmp} is the
758 default) containing all the simulated PC memory. If possible, try to use
759 a temporary directory using the tmpfs filesystem to avoid too many
760 unnecessary disk accesses.
763 In order to exit cleanly from qemu, you can do a @emph{shutdown} inside
764 qemu. qemu will automatically exit when the Linux shutdown is done.
767 You can boot slightly faster by disabling the probe of non present IDE
768 interfaces. To do so, add the following options on the kernel command
771 ide1=noprobe ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe
775 The example disk image is a modified version of the one made by Kevin
776 Lawton for the plex86 Project (@url{www.plex86.org}).
781 @section Linux Kernel Compilation
783 You can use any linux kernel with QEMU. However, if you want to use
784 @code{qemu-fast} to get maximum performances, you must use a modified
785 guest kernel. If you are using a 2.6 guest kernel, you can use
786 directly the patch @file{linux-2.6-qemu-fast.patch} made by Rusty
787 Russel available in the QEMU source archive. Otherwise, you can make the
788 following changes @emph{by hand} to the Linux kernel:
792 The kernel must be mapped at 0x90000000 (the default is
793 0xc0000000). You must modify only two lines in the kernel source:
795 In @file{include/asm/page.h}, replace
797 #define __PAGE_OFFSET (0xc0000000)
801 #define __PAGE_OFFSET (0x90000000)
804 And in @file{arch/i386/vmlinux.lds}, replace
806 . = 0xc0000000 + 0x100000;
810 . = 0x90000000 + 0x100000;
814 If you want to enable SMP (Symmetric Multi-Processing) support, you
815 must make the following change in @file{include/asm/fixmap.h}. Replace
817 #define FIXADDR_TOP (0xffffX000UL)
821 #define FIXADDR_TOP (0xa7ffX000UL)
823 (X is 'e' or 'f' depending on the kernel version). Although you can
824 use an SMP kernel with QEMU, it only supports one CPU.
827 If you are not using a 2.6 kernel as host kernel but if you use a target
828 2.6 kernel, you must also ensure that the 'HZ' define is set to 100
829 (1000 is the default) as QEMU cannot currently emulate timers at
830 frequencies greater than 100 Hz on host Linux systems < 2.6. In
831 @file{include/asm/param.h}, replace:
834 # define HZ 1000 /* Internal kernel timer frequency */
838 # define HZ 100 /* Internal kernel timer frequency */
843 The file config-2.x.x gives the configuration of the example kernels.
850 As you would do to make a real kernel. Then you can use with QEMU
851 exactly the same kernel as you would boot on your PC (in
852 @file{arch/i386/boot/bzImage}).
857 QEMU has a primitive support to work with gdb, so that you can do
858 'Ctrl-C' while the virtual machine is running and inspect its state.
860 In order to use gdb, launch qemu with the '-s' option. It will wait for a
863 > qemu -s -kernel arch/i386/boot/bzImage -hda root-2.4.20.img -append "root=/dev/hda"
864 Connected to host network interface: tun0
865 Waiting gdb connection on port 1234
868 Then launch gdb on the 'vmlinux' executable:
873 In gdb, connect to QEMU:
875 (gdb) target remote localhost:1234
878 Then you can use gdb normally. For example, type 'c' to launch the kernel:
883 Here are some useful tips in order to use gdb on system code:
887 Use @code{info reg} to display all the CPU registers.
889 Use @code{x/10i $eip} to display the code at the PC position.
891 Use @code{set architecture i8086} to dump 16 bit code. Then use
892 @code{x/10i $cs*16+*eip} to dump the code at the PC position.
895 @section Target OS specific information
899 To have access to SVGA graphic modes under X11, use the @code{vesa}
900 X11 driver. For optimal performances, use the same depth as your
905 If you have a slow host, using Windows 95 is better as it gives the
906 best speed. Windows 2000 is also a good choice.
908 SVGA graphic modes support: QEMU currently supports the Bochs VESA VBE
909 extensions. It supports color depths of 8, 15, 16 and 32 bits per
910 pixel in 640x480, 800x600 and 1024x768. For optimal performances, use
911 the same depth as your native display.
915 @item Windows XP: it should be automatically detected.
917 @item Windows NT4 or 2000: use the driver
918 @url{http://www.volny.cz/xnavara/qemuvid_bin.zip} by Filip Navara.
920 @item Windows 95/98/Me: no clean solution yet (but it will change
921 soon). You can however use the shareware driver from SciTech. Here are
922 the steps recommended by Christophe Bothamy on the Bochs mailing list:
925 @item install win95 with the VGA driver.
926 @item download sdd 7 beta from @url{http://www.majorgeeks.com/download382.html}
927 @item download pmhelp.vxd from @url{http://unununium.org/viewcvs/snap/redist/release/pmhelp.vxd}
928 @item copy pmhelp.vxd to the win95 system directory
933 @chapter QEMU PREP PowerPC System emulator invocation
935 Use the executable @file{qemu-system-ppc} to simulate a complete PREP
938 QEMU emulates the following PREP peripherials:
942 2 IDE interfaces with hard disk and CD-ROM support
946 up to 6 NE2000 network adapters
950 PREP Non Volatile RAM
953 You can read the qemu PC system emulation chapter to have more
954 informations about QEMU usage.
956 More information is available at
957 @url{http://jocelyn.mayer.free.fr/qemu-ppc/}.
959 @chapter QEMU User space emulator invocation
963 In order to launch a Linux process, QEMU needs the process executable
964 itself and all the target (x86) dynamic libraries used by it.
968 @item On x86, you can just try to launch any process by using the native
972 qemu-i386 -L / /bin/ls
975 @code{-L /} tells that the x86 dynamic linker must be searched with a
978 @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):
981 qemu-i386 -L / qemu-i386 -L / /bin/ls
984 @item On non x86 CPUs, you need first to download at least an x86 glibc
985 (@file{qemu-runtime-i386-XXX-.tar.gz} on the QEMU web page). Ensure that
986 @code{LD_LIBRARY_PATH} is not set:
989 unset LD_LIBRARY_PATH
992 Then you can launch the precompiled @file{ls} x86 executable:
995 qemu-i386 tests/i386/ls
997 You can look at @file{qemu-binfmt-conf.sh} so that
998 QEMU is automatically launched by the Linux kernel when you try to
999 launch x86 executables. It requires the @code{binfmt_misc} module in the
1002 @item The x86 version of QEMU is also included. You can try weird things such as:
1004 qemu-i386 /usr/local/qemu-i386/bin/qemu-i386 /usr/local/qemu-i386/bin/ls-i386
1009 @section Wine launch
1013 @item Ensure that you have a working QEMU with the x86 glibc
1014 distribution (see previous section). In order to verify it, you must be
1018 qemu-i386 /usr/local/qemu-i386/bin/ls-i386
1021 @item Download the binary x86 Wine install
1022 (@file{qemu-XXX-i386-wine.tar.gz} on the QEMU web page).
1024 @item Configure Wine on your account. Look at the provided script
1025 @file{/usr/local/qemu-i386/bin/wine-conf.sh}. Your previous
1026 @code{$@{HOME@}/.wine} directory is saved to @code{$@{HOME@}/.wine.org}.
1028 @item Then you can try the example @file{putty.exe}:
1031 qemu-i386 /usr/local/qemu-i386/wine/bin/wine /usr/local/qemu-i386/wine/c/Program\ Files/putty.exe
1036 @section Command line options
1039 usage: qemu-i386 [-h] [-d] [-L path] [-s size] program [arguments...]
1046 Set the x86 elf interpreter prefix (default=/usr/local/qemu-i386)
1048 Set the x86 stack size in bytes (default=524288)
1055 Activate log (logfile=/tmp/qemu.log)
1057 Act as if the host page size was 'pagesize' bytes