X-Git-Url: https://vcs.maemo.org/git/?a=blobdiff_plain;f=qemu-doc.texi;h=c3a529ba9c6874aa3b9d14f83c5df73cd66decbc;hb=be147d08790d4d80bfcf2c209031eede52b7dd62;hp=4b9c5f4cd428822ad0dd35f1c60b7409d99f34c5;hpb=f749998939e564d8b8363bd6148b7a067d6bc9e3;p=qemu diff --git a/qemu-doc.texi b/qemu-doc.texi index 4b9c5f4..c3a529b 100644 --- a/qemu-doc.texi +++ b/qemu-doc.texi @@ -25,7 +25,7 @@ * Installation:: * QEMU PC System emulator:: * QEMU System emulator for non PC targets:: -* QEMU Linux User space emulator:: +* QEMU User space emulator:: * compilation:: Compilation from the sources * Index:: @end menu @@ -50,22 +50,22 @@ QEMU has two operating modes: @itemize @minus -@item +@item Full system emulation. In this mode, QEMU emulates a full system (for example a PC), including one or several processors and various peripherals. It can be used to launch different Operating Systems without rebooting the PC or to debug system code. -@item -User mode emulation (Linux host only). In this mode, QEMU can launch -Linux processes compiled for one CPU on another CPU. It can be used to +@item +User mode emulation. In this mode, QEMU can launch +processes compiled for one CPU on another CPU. It can be used to launch the Wine Windows API emulator (@url{http://www.winehq.org}) or to ease cross-compilation and cross-debugging. @end itemize QEMU can run without an host kernel driver and yet gives acceptable -performance. +performance. For system emulation, the following hardware targets are supported: @itemize @@ -77,8 +77,12 @@ For system emulation, the following hardware targets are supported: @item Sun4m (32-bit Sparc processor) @item Sun4u (64-bit Sparc processor, in progress) @item Malta board (32-bit MIPS processor) -@item ARM Integrator/CP (ARM926E or 1026E processor) +@item ARM Integrator/CP (ARM926E, 1026E or 946E processor) @item ARM Versatile baseboard (ARM926E) +@item ARM RealView Emulation baseboard (ARM926EJ-S) +@item Spitz, Akita, Borzoi and Terrier PDAs (PXA270 processor) +@item Freescale MCF5208EVB (ColdFire V2). +@item Arnewsh MCF5206 evaluation board (ColdFire V2). @end itemize For user emulation, x86, PowerPC, ARM, MIPS, Sparc32/64 and ColdFire(m68k) CPUs are supported. @@ -125,6 +129,7 @@ Download the experimental binary installer at * pcsys_network:: Network emulation * direct_linux_boot:: Direct Linux Boot * pcsys_usb:: USB emulation +* vnc_security:: VNC security * gdb_usage:: GDB usage * pcsys_os_specific:: Target OS specific information @end menu @@ -138,19 +143,19 @@ The QEMU PC System emulator simulates the following peripherals: @itemize @minus -@item +@item i440FX host PCI bridge and PIIX3 PCI to ISA bridge @item Cirrus CLGD 5446 PCI VGA card or dummy VGA card with Bochs VESA extensions (hardware level, including all non standard modes). @item PS/2 mouse and keyboard -@item +@item 2 PCI IDE interfaces with hard disk and CD-ROM support @item Floppy disk -@item -NE2000 PCI network adapters +@item +PCI/ISA PCI network adapters @item Serial ports @item @@ -239,47 +244,6 @@ Set virtual RAM size to @var{megs} megabytes. Default is 128 MB. Simulate an SMP system with @var{n} CPUs. On the PC target, up to 255 CPUs are supported. -@item -nographic - -Normally, QEMU uses SDL to display the VGA output. With this option, -you can totally disable graphical output so that QEMU is a simple -command line application. The emulated serial port is redirected on -the console. Therefore, you can still use QEMU to debug a Linux kernel -with a serial console. - -@item -vnc display - -Normally, QEMU uses SDL to display the VGA output. With this option, -you can have QEMU listen on VNC display @var{display} and redirect the VGA -display over the VNC session. It is very useful to enable the usb -tablet device when using this option (option @option{-usbdevice -tablet}). When using the VNC display, you must use the @option{-k} -option to set the keyboard layout if you are not using en-us. - -@var{display} may be in the form @var{interface:d}, in which case connections -will only be allowed from @var{interface} on display @var{d}. Optionally, -@var{interface} can be omitted. @var{display} can also be in the form -@var{unix:path} where @var{path} is the location of a unix socket to listen for -connections on. - - -@item -k language - -Use keyboard layout @var{language} (for example @code{fr} for -French). This option is only needed where it is not easy to get raw PC -keycodes (e.g. on Macs, with some X11 servers or with a VNC -display). You don't normally need to use it on PC/Linux or PC/Windows -hosts. - -The available layouts are: -@example -ar de-ch es fo fr-ca hu ja mk no pt-br sv -da en-gb et fr fr-ch is lt nl pl ru th -de en-us fi fr-be hr it lv nl-be pt sl tr -@end example - -The default is @code{en-us}. - @item -audio-help Will show the audio subsystem help: list of drivers, tunable @@ -302,9 +266,6 @@ Set the real time clock to local time (the default is to UTC time). This option is needed to have correct date in MS-DOS or Windows. -@item -full-screen -Start in full screen. - @item -pidfile file Store the QEMU process PID in @var{file}. It is useful if you launch QEMU from a script. @@ -324,6 +285,121 @@ slows down the IDE transfers). Load the contents of file as an option ROM. This option is useful to load things like EtherBoot. +@item -name string +Sets the name of the guest. This name will be display in the SDL window +caption. The name will also be used for the VNC server. + +@end table + +Display options: +@table @option + +@item -nographic + +Normally, QEMU uses SDL to display the VGA output. With this option, +you can totally disable graphical output so that QEMU is a simple +command line application. The emulated serial port is redirected on +the console. Therefore, you can still use QEMU to debug a Linux kernel +with a serial console. + +@item -no-frame + +Do not use decorations for SDL windows and start them using the whole +available screen space. This makes the using QEMU in a dedicated desktop +workspace more convenient. + +@item -full-screen +Start in full screen. + +@item -vnc display[,option[,option[,...]]] + +Normally, QEMU uses SDL to display the VGA output. With this option, +you can have QEMU listen on VNC display @var{display} and redirect the VGA +display over the VNC session. It is very useful to enable the usb +tablet device when using this option (option @option{-usbdevice +tablet}). When using the VNC display, you must use the @option{-k} +parameter to set the keyboard layout if you are not using en-us. Valid +syntax for the @var{display} is + +@table @code + +@item @var{interface:d} + +TCP connections will only be allowed from @var{interface} on display @var{d}. +By convention the TCP port is 5900+@var{d}. Optionally, @var{interface} can +be omitted in which case the server will bind to all interfaces. + +@item @var{unix:path} + +Connections will be allowed over UNIX domain sockets where @var{path} is the +location of a unix socket to listen for connections on. + +@item @var{none} + +VNC is initialized by not started. The monitor @code{change} command can be used +to later start the VNC server. + +@end table + +Following the @var{display} value there may be one or more @var{option} flags +separated by commas. Valid options are + +@table @code + +@item @var{password} + +Require that password based authentication is used for client connections. +The password must be set separately using the @code{change} command in the +@ref{pcsys_monitor} + +@item @var{tls} + +Require that client use TLS when communicating with the VNC server. This +uses anonymous TLS credentials so is susceptible to a man-in-the-middle +attack. It is recommended that this option be combined with either the +@var{x509} or @var{x509verify} options. + +@item @var{x509=/path/to/certificate/dir} + +Valid if @var{tls} is specified. Require that x509 credentials are used +for negotiating the TLS session. The server will send its x509 certificate +to the client. It is recommended that a password be set on the VNC server +to provide authentication of the client when this is used. The path following +this option specifies where the x509 certificates are to be loaded from. +See the @ref{vnc_security} section for details on generating certificates. + +@item @var{x509verify=/path/to/certificate/dir} + +Valid if @var{tls} is specified. Require that x509 credentials are used +for negotiating the TLS session. The server will send its x509 certificate +to the client, and request that the client send its own x509 certificate. +The server will validate the client's certificate against the CA certificate, +and reject clients when validation fails. If the certificate authority is +trusted, this is a sufficient authentication mechanism. You may still wish +to set a password on the VNC server as a second authentication layer. The +path following this option specifies where the x509 certificates are to +be loaded from. See the @ref{vnc_security} section for details on generating +certificates. + +@end table + +@item -k language + +Use keyboard layout @var{language} (for example @code{fr} for +French). This option is only needed where it is not easy to get raw PC +keycodes (e.g. on Macs, with some X11 servers or with a VNC +display). You don't normally need to use it on PC/Linux or PC/Windows +hosts. + +The available layouts are: +@example +ar de-ch es fo fr-ca hu ja mk no pt-br sv +da en-gb et fr fr-ch is lt nl pl ru th +de en-us fi fr-be hr it lv nl-be pt sl tr +@end example + +The default is @code{en-us}. + @end table USB options: @@ -342,23 +418,27 @@ Network options: @item -net nic[,vlan=n][,macaddr=addr][,model=type] Create a new Network Interface Card and connect it to VLAN @var{n} (@var{n} -= 0 is the default). The NIC is currently an NE2000 on the PC += 0 is the default). The NIC is an ne2k_pci by default on the PC target. Optionally, the MAC address can be changed. If no @option{-net} option is specified, a single NIC is created. -Qemu can emulate several different models of network card. Valid values for -@var{type} are @code{ne2k_pci}, @code{ne2k_isa}, @code{rtl8139}, -@code{smc91c111} and @code{lance}. Not all devices are supported on all -targets. +Qemu can emulate several different models of network card. +Valid values for @var{type} are +@code{i82551}, @code{i82557b}, @code{i82559er}, +@code{ne2k_pci}, @code{ne2k_isa}, @code{pcnet}, @code{rtl8139}, +@code{smc91c111}, @code{lance} and @code{mcf_fec}. +Not all devices are supported on all targets. Use -net nic,model=? +for a list of available devices for your target. @item -net user[,vlan=n][,hostname=name] Use the user mode network stack which requires no administrator -priviledge to run. @option{hostname=name} can be used to specify the client +privilege to run. @option{hostname=name} can be used to specify the client hostname reported by the builtin DHCP server. @item -net tap[,vlan=n][,fd=h][,ifname=name][,script=file] Connect the host TAP network interface @var{name} to VLAN @var{n} and use the network script @var{file} to configure it. The default -network script is @file{/etc/qemu-ifup}. If @var{name} is not +network script is @file{/etc/qemu-ifup}. Use @option{script=no} to +disable script execution. If @var{name} is not provided, the OS automatically provides one. @option{fd=h} can be used to specify the handle of an already opened host TAP interface. Example: @@ -396,17 +476,18 @@ qemu linux.img -net nic,macaddr=52:54:00:12:34:57 \ @item -net socket[,vlan=n][,fd=h][,mcast=maddr:port] Create a VLAN @var{n} shared with another QEMU virtual -machines using a UDP multicast socket, effectively making a bus for +machines using a UDP multicast socket, effectively making a bus for every QEMU with same multicast address @var{maddr} and @var{port}. NOTES: @enumerate -@item -Several QEMU can be running on different hosts and share same bus (assuming +@item +Several QEMU can be running on different hosts and share same bus (assuming correct multicast setup for these hosts). @item mcast support is compatible with User Mode Linux (argument @option{eth@var{N}=mcast}), see @url{http://user-mode-linux.sf.net}. -@item Use @option{fd=h} to specify an already opened UDP multicast socket. +@item +Use @option{fd=h} to specify an already opened UDP multicast socket. @end enumerate Example: @@ -437,13 +518,22 @@ Indicate that no network devices should be configured. It is used to override the default configuration (@option{-net nic -net user}) which is activated if no @option{-net} options are provided. -@item -tftp prefix +@item -tftp dir When using the user mode network stack, activate a built-in TFTP -server. All filenames beginning with @var{prefix} can be downloaded -from the host to the guest using a TFTP client. The TFTP client on the -guest must be configured in binary mode (use the command @code{bin} of -the Unix TFTP client). The host IP address on the guest is as usual -10.0.2.2. +server. The files in @var{dir} will be exposed as the root of a TFTP server. +The TFTP client on the guest must be configured in binary mode (use the command +@code{bin} of the Unix TFTP client). The host IP address on the guest is as +usual 10.0.2.2. + +@item -bootp file +When using the user mode network stack, broadcast @var{file} as the BOOTP +filename. In conjunction with @option{-tftp}, this can be used to network boot +a guest from a local directory. + +Example (using pxelinux): +@example +qemu -hda linux.img -boot n -tftp /path/to/tftp/files -bootp /pxelinux.0 +@end example @item -smb dir When using the user mode network stack, activate a built-in SMB @@ -501,10 +591,10 @@ for easier testing of various kernels. @table @option -@item -kernel bzImage +@item -kernel bzImage Use @var{bzImage} as kernel image. -@item -append cmdline +@item -append cmdline Use @var{cmdline} as kernel command line @item -initrd file @@ -527,8 +617,15 @@ Use @code{-serial none} to disable all serial ports. Available character devices are: @table @code -@item vc -Virtual console +@item vc[:WxH] +Virtual console. Optionally, a width and height can be given in pixel with +@example +vc:800x600 +@end example +It is also possible to specify width or height in characters: +@example +vc:80Cx24C +@end example @item pty [Linux only] Pseudo TTY (a new PTY is automatically allocated) @item none @@ -540,7 +637,7 @@ void device parameters are set according to the emulated ones. @item /dev/parportN [Linux only, parallel port only] Use host parallel port -@var{N}. Currently only SPP parallel port features can be used. +@var{N}. Currently SPP and EPP parallel port features can be used. @item file:filename Write output to filename. No character can be read. @item stdio @@ -550,7 +647,7 @@ name pipe @var{filename} @item COMn [Windows only] Use host serial port @var{n} @item udp:[remote_host]:remote_port[@@[src_ip]:src_port] -This implements UDP Net Console. When @var{remote_host} or @var{src_ip} are not specified they default to @code{0.0.0.0}. When not using a specifed @var{src_port} a random port is automatically chosen. +This implements UDP Net Console. When @var{remote_host} or @var{src_ip} are not specified they default to @code{0.0.0.0}. When not using a specified @var{src_port} a random port is automatically chosen. If you just want a simple readonly console you can use @code{netcat} or @code{nc}, by starting qemu with: @code{-serial udp::4555} and nc as: @@ -583,7 +680,7 @@ the TCP Net Console is sent to @var{host} at the @var{port}. If you use the @var{server} option QEMU will wait for a client socket application to connect to the port before continuing, unless the @code{nowait} option was specified. The @code{nodelay} option disables the Nagle buffering -algoritm. If @var{host} is omitted, 0.0.0.0 is assumed. Only +algorithm. If @var{host} is omitted, 0.0.0.0 is assumed. Only one TCP connection at a time is accepted. You can use @code{telnet} to connect to the corresponding character device. @table @code @@ -609,6 +706,18 @@ A unix domain socket is used instead of a tcp socket. The option works the same as if you had specified @code{-serial tcp} except the unix domain socket @var{path} is used for connections. +@item mon:dev_string +This is a special option to allow the monitor to be multiplexed onto +another serial port. The monitor is accessed with key sequence of +@key{Control-a} and then pressing @key{c}. See monitor access +@ref{pcsys_keys} in the -nographic section for more keys. +@var{dev_string} should be any one of the serial devices specified +above. An example to multiplex the monitor onto a telnet server +listening on port 4444 would be: +@table @code +@item -serial mon:telnet::4444,server,nowait +@end table + @end table @item -parallel dev @@ -628,19 +737,33 @@ serial port). The default device is @code{vc} in graphical mode and @code{stdio} in non graphical mode. +@item -echr numeric_ascii_value +Change the escape character used for switching to the monitor when using +monitor and serial sharing. The default is @code{0x01} when using the +@code{-nographic} option. @code{0x01} is equal to pressing +@code{Control-a}. You can select a different character from the ascii +control keys where 1 through 26 map to Control-a through Control-z. For +instance you could use the either of the following to change the escape +character to Control-t. +@table @code +@item -echr 0x14 +@item -echr 20 +@end table + @item -s -Wait gdb connection to port 1234 (@pxref{gdb_usage}). +Wait gdb connection to port 1234 (@pxref{gdb_usage}). @item -p port -Change gdb connection port. +Change gdb connection port. @var{port} can be either a decimal number +to specify a TCP port, or a host device (same devices as the serial port). @item -S Do not start CPU at startup (you must type 'c' in the monitor). -@item -d +@item -d Output log in /tmp/qemu.log @item -hdachs c,h,s,[,t] Force hard disk 0 physical geometry (1 <= @var{c} <= 16383, 1 <= @var{h} <= 16, 1 <= @var{s} <= 63) and optionally force the BIOS translation mode (@var{t}=none, lba or auto). Usually QEMU can guess -all thoses parameters. This option is useful for old MS-DOS disk +all those parameters. This option is useful for old MS-DOS disk images. @item -L path @@ -664,7 +787,11 @@ Exit instead of rebooting. Start right away with a saved state (@code{loadvm} in monitor) @item -semihosting -Enable "Angel" semihosting interface (ARM target machines only). +Enable semihosting syscall emulation (ARM and M68K target machines only). + +On ARM this implements the "Angel" interface. +On M68K this implements the "ColdFire GDB" interface used by libgloss. + Note that this allows guest direct access to the host filesystem, so should only be used with trusted guest OS. @end table @@ -705,10 +832,12 @@ During emulation, if you are using the @option{-nographic} option, use @table @key @item Ctrl-a h Print this help -@item Ctrl-a x +@item Ctrl-a x Exit emulator -@item Ctrl-a s +@item Ctrl-a s Save disk data back to file (if -snapshot) +@item Ctrl-a t +toggle console timestamps @item Ctrl-a b Send break (magic sysrq in Linux) @item Ctrl-a c @@ -740,10 +869,10 @@ emulator. You can use it to: @itemize @minus @item -Remove or insert removable medias images +Remove or insert removable media images (such as CD-ROM or floppies) -@item +@item Freeze/unfreeze the Virtual Machine (VM) and save or restore its state from a disk file. @@ -760,10 +889,10 @@ The following commands are available: @item help or ? [cmd] Show the help for all commands or just for command @var{cmd}. -@item commit +@item commit Commit changes to the disk images (if -snapshot is used) -@item info subcommand +@item info subcommand show various information about the system state @table @option @@ -793,10 +922,40 @@ show which guest mouse is receiving events Quit the emulator. @item eject [-f] device -Eject a removable media (use -f to force it). +Eject a removable medium (use -f to force it). + +@item change device setting + +Change the configuration of a device + +@table @option +@item change @var{diskdevice} @var{filename} +Change the medium for a removable disk device to point to @var{filename}. eg + +@example +(qemu) change cdrom /path/to/some.iso +@end example + +@item change vnc @var{display,options} +Change the configuration of the VNC server. The valid syntax for @var{display} +and @var{options} are described at @ref{sec_invocation}. eg -@item change device filename -Change a removable media. +@example +(qemu) change vnc localhost:1 +@end example + +@item change vnc password + +Change the password associated with the VNC server. The monitor will prompt for +the new password to be entered. VNC passwords are only significant upto 8 letters. +eg. + +@example +(qemu) change vnc password +Password: ******** +@end example + +@end table @item screendump filename Save screen into PPM image @var{filename}. @@ -867,11 +1026,11 @@ Physical memory dump starting at @var{addr}. data. Its syntax is: @option{/@{count@}@{format@}@{size@}} @table @var -@item count +@item count is the number of items to be dumped. @item format -can be x (hexa), d (signed decimal), u (unsigned decimal), o (octal), +can be x (hex), d (signed decimal), u (unsigned decimal), o (octal), c (char) or i (asm instruction). @item size @@ -881,11 +1040,11 @@ respectively select 16 or 32 bit code instruction size. @end table -Examples: +Examples: @itemize @item Dump 10 instructions at the current instruction pointer: -@example +@example (qemu) x/10i $eip 0x90107063: ret 0x90107064: sti @@ -901,7 +1060,7 @@ Dump 10 instructions at the current instruction pointer: @item Dump 80 16 bit values at the start of the video memory. -@smallexample +@smallexample (qemu) xp/80hx 0xb8000 0x000b8000: 0x0b50 0x0b6c 0x0b65 0x0b78 0x0b38 0x0b36 0x0b2f 0x0b42 0x000b8010: 0x0b6f 0x0b63 0x0b68 0x0b73 0x0b20 0x0b56 0x0b47 0x0b41 @@ -1038,10 +1197,10 @@ but they are deleted as soon as you exit QEMU. VM snapshots currently have the following known limitations: @itemize -@item +@item They cannot cope with removable devices if they are removed or inserted after a snapshot is done. -@item +@item A few device drivers still have incomplete snapshot support so their state is not saved or restored properly (in particular USB). @end itemize @@ -1060,7 +1219,7 @@ devices. We describe here the usage for QEMU version >= 0.8.3. @subsubsection Linux On Linux, you can directly use the host device filename instead of a -disk image filename provided you have enough proviledge to access +disk image filename provided you have enough privileges to access it. For example, use @file{/dev/cdrom} to access to the CDROM or @file{/dev/fd0} for the floppy. @@ -1087,11 +1246,11 @@ line option or modify the device permissions accordingly). @table @code @item CD -The prefered syntax is the drive letter (e.g. @file{d:}). The +The preferred syntax is the drive letter (e.g. @file{d:}). The alternate syntax @file{\\.\d:} is supported. @file{/dev/cdrom} is supported as an alias to the first CDROM drive. -Currently there is no specific code to handle removable medias, so it +Currently there is no specific code to handle removable media, so it is better to use the @code{change} or @code{eject} monitor commands to change or eject media. @item Hard disks @@ -1107,9 +1266,9 @@ modifications are written in a temporary file). @subsubsection Mac OS X -@file{/dev/cdrom} is an alias to the first CDROM. +@file{/dev/cdrom} is an alias to the first CDROM. -Currently there is no specific code to handle removable medias, so it +Currently there is no specific code to handle removable media, so it is better to use the @code{change} or @code{eject} monitor commands to change or eject media. @@ -1119,7 +1278,7 @@ change or eject media. QEMU can automatically create a virtual FAT disk image from a directory tree. In order to use it, just type: -@example +@example qemu linux.img -hdb fat:/my_directory @end example @@ -1129,14 +1288,14 @@ them via SAMBA or NFS. The default access is @emph{read-only}. Floppies can be emulated with the @code{:floppy:} option: -@example +@example qemu linux.img -fda fat:floppy:/my_directory @end example A read/write support is available for testing (beta stage) with the @code{:rw:} option: -@example +@example qemu linux.img -fda fat:floppy:rw:/my_directory @end example @@ -1151,11 +1310,11 @@ What you should @emph{never} do: @node pcsys_network @section Network emulation -QEMU can simulate several networks cards (NE2000 boards on the PC +QEMU can simulate several network cards (PCI or ISA cards on the PC target) and can connect them to an arbitrary number of Virtual Local Area Networks (VLANs). Host TAP devices can be connected to any QEMU VLAN. VLAN can be connected between separate instances of QEMU to -simulate large networks. For simpler usage, a non priviledged user mode +simulate large networks. For simpler usage, a non privileged user mode network stack can replace the TAP device to have a basic network connection. @@ -1195,7 +1354,7 @@ so download OpenVPN from : @url{http://openvpn.net/}. By using the option @option{-net user} (default configuration if no @option{-net} option is specified), QEMU uses a completely user mode -network stack (you don't need root priviledge to use the virtual +network stack (you don't need root privilege to use the virtual network). The virtual network configuration is the following: @example @@ -1204,7 +1363,7 @@ network). The virtual network configuration is the following: | (10.0.2.2) | ----> DNS server (10.0.2.3) - | + | ----> SMB server (10.0.2.4) @end example @@ -1218,7 +1377,7 @@ the address 10.0.2.2 and verify that you got an address in the range 10.0.2.x from the QEMU virtual DHCP server. Note that @code{ping} is not supported reliably to the internet as it -would require root priviledges. It means you can only ping the local +would require root privileges. It means you can only ping the local router (10.0.2.2). When using the built-in TFTP server, the router is also the TFTP @@ -1298,6 +1457,12 @@ Pass through the host device identified by @var{bus.addr} @item @code{host:vendor_id:product_id} Pass through the host device identified by @var{vendor_id:product_id} (Linux only) +@item @code{wacom-tablet} +Virtual Wacom PenPartner tablet. This device is similar to the @code{tablet} +above but it can be used with the tslib library because in addition to touch +coordinates it reports touch pressure. +@item @code{keyboard} +Standard USB keyboard. Will override the PS/2 keyboard (if present). @end table @node host_usb_devices @@ -1308,7 +1473,7 @@ using it. USB devices requiring real time streaming (i.e. USB Video Cameras) are not supported yet. @enumerate -@item If you use an early Linux 2.4 kernel, verify that no Linux driver +@item If you use an early Linux 2.4 kernel, verify that no Linux driver is actually using the USB device. A simple way to do that is simply to disable the corresponding kernel module by renaming it from @file{mydriver.o} to @file{mydriver.o.disabled}. @@ -1325,7 +1490,7 @@ chown -R myuid /proc/bus/usb @end example @item Launch QEMU and do in the monitor: -@example +@example info usbhost Device 1.2, speed 480 Mb/s Class 00: USB device 1234:5678, USB DISK @@ -1334,7 +1499,7 @@ You should see the list of the devices you can use (Never try to use hubs, it won't work). @item Add the device in QEMU by using: -@example +@example usb_add host:1234:5678 @end example @@ -1348,6 +1513,213 @@ plugged. You can use the option @option{-usbdevice} to do the same. When relaunching QEMU, you may have to unplug and plug again the USB device to make it work again (this is a bug). +@node vnc_security +@section VNC security + +The VNC server capability provides access to the graphical console +of the guest VM across the network. This has a number of security +considerations depending on the deployment scenarios. + +@menu +* vnc_sec_none:: +* vnc_sec_password:: +* vnc_sec_certificate:: +* vnc_sec_certificate_verify:: +* vnc_sec_certificate_pw:: +* vnc_generate_cert:: +@end menu +@node vnc_sec_none +@subsection Without passwords + +The simplest VNC server setup does not include any form of authentication. +For this setup it is recommended to restrict it to listen on a UNIX domain +socket only. For example + +@example +qemu [...OPTIONS...] -vnc unix:/home/joebloggs/.qemu-myvm-vnc +@end example + +This ensures that only users on local box with read/write access to that +path can access the VNC server. To securely access the VNC server from a +remote machine, a combination of netcat+ssh can be used to provide a secure +tunnel. + +@node vnc_sec_password +@subsection With passwords + +The VNC protocol has limited support for password based authentication. Since +the protocol limits passwords to 8 characters it should not be considered +to provide high security. The password can be fairly easily brute-forced by +a client making repeat connections. For this reason, a VNC server using password +authentication should be restricted to only listen on the loopback interface +or UNIX domain sockets. Password ayuthentication is requested with the @code{password} +option, and then once QEMU is running the password is set with the monitor. Until +the monitor is used to set the password all clients will be rejected. + +@example +qemu [...OPTIONS...] -vnc :1,password -monitor stdio +(qemu) change vnc password +Password: ******** +(qemu) +@end example + +@node vnc_sec_certificate +@subsection With x509 certificates + +The QEMU VNC server also implements the VeNCrypt extension allowing use of +TLS for encryption of the session, and x509 certificates for authentication. +The use of x509 certificates is strongly recommended, because TLS on its +own is susceptible to man-in-the-middle attacks. Basic x509 certificate +support provides a secure session, but no authentication. This allows any +client to connect, and provides an encrypted session. + +@example +qemu [...OPTIONS...] -vnc :1,tls,x509=/etc/pki/qemu -monitor stdio +@end example + +In the above example @code{/etc/pki/qemu} should contain at least three files, +@code{ca-cert.pem}, @code{server-cert.pem} and @code{server-key.pem}. Unprivileged +users will want to use a private directory, for example @code{$HOME/.pki/qemu}. +NB the @code{server-key.pem} file should be protected with file mode 0600 to +only be readable by the user owning it. + +@node vnc_sec_certificate_verify +@subsection With x509 certificates and client verification + +Certificates can also provide a means to authenticate the client connecting. +The server will request that the client provide a certificate, which it will +then validate against the CA certificate. This is a good choice if deploying +in an environment with a private internal certificate authority. + +@example +qemu [...OPTIONS...] -vnc :1,tls,x509verify=/etc/pki/qemu -monitor stdio +@end example + + +@node vnc_sec_certificate_pw +@subsection With x509 certificates, client verification and passwords + +Finally, the previous method can be combined with VNC password authentication +to provide two layers of authentication for clients. + +@example +qemu [...OPTIONS...] -vnc :1,password,tls,x509verify=/etc/pki/qemu -monitor stdio +(qemu) change vnc password +Password: ******** +(qemu) +@end example + +@node vnc_generate_cert +@subsection Generating certificates for VNC + +The GNU TLS packages provides a command called @code{certtool} which can +be used to generate certificates and keys in PEM format. At a minimum it +is neccessary to setup a certificate authority, and issue certificates to +each server. If using certificates for authentication, then each client +will also need to be issued a certificate. The recommendation is for the +server to keep its certificates in either @code{/etc/pki/qemu} or for +unprivileged users in @code{$HOME/.pki/qemu}. + +@menu +* vnc_generate_ca:: +* vnc_generate_server:: +* vnc_generate_client:: +@end menu +@node vnc_generate_ca +@subsubsection Setup the Certificate Authority + +This step only needs to be performed once per organization / organizational +unit. First the CA needs a private key. This key must be kept VERY secret +and secure. If this key is compromised the entire trust chain of the certificates +issued with it is lost. + +@example +# certtool --generate-privkey > ca-key.pem +@end example + +A CA needs to have a public certificate. For simplicity it can be a self-signed +certificate, or one issue by a commercial certificate issuing authority. To +generate a self-signed certificate requires one core piece of information, the +name of the organization. + +@example +# cat > ca.info < server.info < server-key.pem +# certtool --generate-certificate \ + --load-ca-certificate ca-cert.pem \ + --load-ca-privkey ca-key.pem \ + --load-privkey server server-key.pem \ + --template server.info \ + --outfile server-cert.pem +@end example + +The @code{server-key.pem} and @code{server-cert.pem} files should now be securely copied +to the server for which they were generated. The @code{server-key.pem} is security +sensitive and should be kept protected with file mode 0600 to prevent disclosure. + +@node vnc_generate_client +@subsubsection Issuing client certificates + +If the QEMU VNC server is to use the @code{x509verify} option to validate client +certificates as its authentication mechanism, each client also needs to be issued +a certificate. The client certificate contains enough metadata to uniquely identify +the client, typically organization, state, city, building, etc. On the host holding +the secure CA private key: + +@example +# cat > client.info < client-key.pem +# certtool --generate-certificate \ + --load-ca-certificate ca-cert.pem \ + --load-ca-privkey ca-key.pem \ + --load-privkey client-key.pem \ + --template client.info \ + --outfile client-cert.pem +@end example + +The @code{client-key.pem} and @code{client-cert.pem} files should now be securely +copied to the client for which they were generated. + @node gdb_usage @section GDB usage @@ -1407,7 +1779,7 @@ cannot simulate exactly. When using a 2.6 guest Linux kernel, verify that the 4G/4G patch is not activated because QEMU is slower with this patch. The QEMU Accelerator Module is also much slower in this case. Earlier Fedora -Core 3 Linux kernel (< 2.6.9-1.724_FC3) were known to incorporte this +Core 3 Linux kernel (< 2.6.9-1.724_FC3) were known to incorporate this patch by default. Newer kernels don't have it. @subsection Windows @@ -1454,7 +1826,7 @@ Bartlett): go to the Control Panel => Add/Remove Hardware & Next => Add/Troubleshoot a device => Add a new device & Next => No, select the hardware from a list & Next => NT Apm/Legacy Support & Next => Next (again) a few times. Now the driver is installed and Windows 2000 now -correctly instructs QEMU to shutdown at the appropriate moment. +correctly instructs QEMU to shutdown at the appropriate moment. @subsubsection Share a directory between Unix and Windows @@ -1489,14 +1861,15 @@ problem. QEMU is a generic emulator and it emulates many non PC machines. Most of the options are similar to the PC emulator. The -differences are mentionned in the following sections. +differences are mentioned in the following sections. @menu * QEMU PowerPC System emulator:: -* Sparc32 System emulator invocation:: -* Sparc64 System emulator invocation:: -* MIPS System emulator invocation:: -* ARM System emulator invocation:: +* Sparc32 System emulator:: +* Sparc64 System emulator:: +* MIPS System emulator:: +* ARM System emulator:: +* ColdFire System emulator:: @end menu @node QEMU PowerPC System emulator @@ -1508,13 +1881,13 @@ or PowerMac PowerPC system. QEMU emulates the following PowerMac peripherals: @itemize @minus -@item -UniNorth PCI Bridge +@item +UniNorth PCI Bridge @item PCI VGA compatible card with VESA Bochs Extensions -@item +@item 2 PMAC IDE interfaces with hard disk and CD-ROM support -@item +@item NE2000 PCI adapters @item Non Volatile RAM @@ -1525,15 +1898,15 @@ VIA-CUDA with ADB keyboard and mouse. QEMU emulates the following PREP peripherals: @itemize @minus -@item +@item PCI Bridge @item PCI VGA compatible card with VESA Bochs Extensions -@item +@item 2 IDE interfaces with hard disk and CD-ROM support @item Floppy disk -@item +@item NE2000 network adapters @item Serial port @@ -1552,23 +1925,23 @@ The following options are specific to the PowerPC emulation: @table @option -@item -g WxH[xDEPTH] +@item -g WxH[xDEPTH] Set the initial VGA graphic mode. The default is 800x600x15. @end table -@c man end +@c man end More information is available at @url{http://perso.magic.fr/l_indien/qemu-ppc/}. -@node Sparc32 System emulator invocation -@section Sparc32 System emulator invocation +@node Sparc32 System emulator +@section Sparc32 System emulator Use the executable @file{qemu-system-sparc} to simulate a SparcStation 5 -(sun4m architecture). The emulation is somewhat complete. +or SparcStation 10 (sun4m architecture). The emulation is somewhat complete. QEMU emulates the following sun4m peripherals: @@ -1577,7 +1950,7 @@ QEMU emulates the following sun4m peripherals: IOMMU @item TCX Frame buffer -@item +@item Lance (Am7990) Ethernet @item Non Volatile RAM M48T08 @@ -1588,6 +1961,8 @@ and power/reset logic ESP SCSI controller with hard disk and CD-ROM support @item Floppy drive +@item +CS4231 sound device (only on SS-5, not working yet) @end itemize The number of peripherals is fixed in the architecture. @@ -1603,20 +1978,34 @@ Solaris kernels don't work. @c man begin OPTIONS -The following options are specific to the Sparc emulation: +The following options are specific to the Sparc32 emulation: @table @option -@item -g WxH +@item -g WxHx[xDEPTH] -Set the initial TCX graphic mode. The default is 1024x768. +Set the initial TCX graphic mode. The default is 1024x768x8, currently +the only other possible mode is 1024x768x24. + +@item -prom-env string + +Set OpenBIOS variables in NVRAM, for example: + +@example +qemu-system-sparc -prom-env 'auto-boot?=false' \ + -prom-env 'boot-device=sd(0,2,0):d' -prom-env 'boot-args=linux single' +@end example + +@item -M [SS-5|SS-10] + +Set the emulated machine type. Default is SS-5. @end table -@c man end +@c man end -@node Sparc64 System emulator invocation -@section Sparc64 System emulator invocation +@node Sparc64 System emulator +@section Sparc64 System emulator Use the executable @file{qemu-system-sparc64} to simulate a Sun4u machine. The emulator is not usable for anything yet. @@ -1625,7 +2014,7 @@ QEMU emulates the following sun4u peripherals: @itemize @minus @item -UltraSparc IIi APB PCI Bridge +UltraSparc IIi APB PCI Bridge @item PCI VGA compatible card with VESA Bochs Extensions @item @@ -1634,26 +2023,68 @@ Non Volatile RAM M48T59 PC-compatible serial ports @end itemize -@node MIPS System emulator invocation -@section MIPS System emulator invocation +@node MIPS System emulator +@section MIPS System emulator Use the executable @file{qemu-system-mips} to simulate a MIPS machine. -The emulator is able to boot a Linux kernel and to run a Linux Debian -installation from NFS. The following devices are emulated: +Three different machine types are emulated: + +@itemize @minus +@item +A generic ISA PC-like machine "mips" +@item +The MIPS Malta prototype board "malta" +@item +An ACER Pica "pica61" +@end itemize + +The generic emulation is supported by Debian 'Etch' and is able to +install Debian into a virtual disk image. The following devices are +emulated: @itemize @minus -@item -MIPS R4K CPU +@item +MIPS 24Kf CPU @item PC style serial port @item +PC style IDE disk +@item NE2000 network card @end itemize -More information is available in the QEMU mailing-list archive. +The Malta emulation supports the following devices: -@node ARM System emulator invocation -@section ARM System emulator invocation +@itemize @minus +@item +Core board with MIPS 24Kf CPU and Galileo system controller +@item +PIIX4 PCI/USB/SMbus controller +@item +The Multi-I/O chip's serial device +@item +PCnet32 PCI network card +@item +Malta FPGA serial device +@item +Cirrus VGA graphics card +@end itemize + +The ACER Pica emulation supports: + +@itemize @minus +@item +MIPS R4000 CPU +@item +PC-style IRQ and DMA controllers +@item +PC Keyboard +@item +IDE controller +@end itemize + +@node ARM System emulator +@section ARM System emulator Use the executable @file{qemu-system-arm} to simulate a ARM machine. The ARM Integrator/CP board is emulated with the following @@ -1661,15 +2092,17 @@ devices: @itemize @minus @item -ARM926E or ARM1026E CPU +ARM926E, ARM1026E or ARM946E CPU @item Two PL011 UARTs -@item +@item SMC 91c111 Ethernet adapter @item PL110 LCD controller @item PL050 KMI with PS/2 keyboard and mouse. +@item +PL181 MultiMedia Card Interface with SD card. @end itemize The ARM Versatile baseboard is emulated with the following devices: @@ -1681,7 +2114,7 @@ ARM926E CPU PL190 Vectored Interrupt Controller @item Four PL011 UARTs -@item +@item SMC 91c111 Ethernet adapter @item PL110 LCD controller @@ -1690,20 +2123,124 @@ PL050 KMI with PS/2 keyboard and mouse. @item PCI host bridge. Note the emulated PCI bridge only provides access to PCI memory space. It does not provide access to PCI IO space. -This means some devices (eg. ne2k_pci NIC) are not useable, and others -(eg. rtl8139 NIC) are only useable when the guest drivers use the memory +This means some devices (eg. ne2k_pci NIC) are not usable, and others +(eg. rtl8139 NIC) are only usable when the guest drivers use the memory mapped control registers. @item PCI OHCI USB controller. @item LSI53C895A PCI SCSI Host Bus Adapter with hard disk and CD-ROM devices. +@item +PL181 MultiMedia Card Interface with SD card. +@end itemize + +The ARM RealView Emulation baseboard is emulated with the following devices: + +@itemize @minus +@item +ARM926E CPU +@item +ARM AMBA Generic/Distributed Interrupt Controller +@item +Four PL011 UARTs +@item +SMC 91c111 Ethernet adapter +@item +PL110 LCD controller +@item +PL050 KMI with PS/2 keyboard and mouse +@item +PCI host bridge +@item +PCI OHCI USB controller +@item +LSI53C895A PCI SCSI Host Bus Adapter with hard disk and CD-ROM devices +@item +PL181 MultiMedia Card Interface with SD card. +@end itemize + +The XScale-based clamshell PDA models ("Spitz", "Akita", "Borzoi" +and "Terrier") emulation includes the following peripherals: + +@itemize @minus +@item +Intel PXA270 System-on-chip (ARM V5TE core) +@item +NAND Flash memory +@item +IBM/Hitachi DSCM microdrive in a PXA PCMCIA slot - not in "Akita" +@item +On-chip OHCI USB controller +@item +On-chip LCD controller +@item +On-chip Real Time Clock +@item +TI ADS7846 touchscreen controller on SSP bus +@item +Maxim MAX1111 analog-digital converter on I@math{^2}C bus +@item +GPIO-connected keyboard controller and LEDs +@item +Secure Digital card connected to PXA MMC/SD host +@item +Three on-chip UARTs +@item +WM8750 audio CODEC on I@math{^2}C and I@math{^2}S busses @end itemize A Linux 2.6 test image is available on the QEMU web site. More information is available in the QEMU mailing-list archive. -@node QEMU Linux User space emulator -@chapter QEMU Linux User space emulator +@node ColdFire System emulator +@section ColdFire System emulator + +Use the executable @file{qemu-system-m68k} to simulate a ColdFire machine. +The emulator is able to boot a uClinux kernel. + +The M5208EVB emulation includes the following devices: + +@itemize @minus +@item +MCF5208 ColdFire V2 Microprocessor (ISA A+ with EMAC). +@item +Three Two on-chip UARTs. +@item +Fast Ethernet Controller (FEC) +@end itemize + +The AN5206 emulation includes the following devices: + +@itemize @minus +@item +MCF5206 ColdFire V2 Microprocessor. +@item +Two on-chip UARTs. +@end itemize + +@node QEMU User space emulator +@chapter QEMU User space emulator + +@menu +* Supported Operating Systems :: +* Linux User space emulator:: +* Mac OS X/Darwin User space emulator :: +@end menu + +@node Supported Operating Systems +@section Supported Operating Systems + +The following OS are supported in user space emulation: + +@itemize @minus +@item +Linux (referred as qemu-linux-user) +@item +Mac OS X/Darwin (referred as qemu-darwin-user) +@end itemize + +@node Linux User space emulator +@section Linux User space emulator @menu * Quick Start:: @@ -1713,26 +2250,27 @@ information is available in the QEMU mailing-list archive. @end menu @node Quick Start -@section Quick Start +@subsection Quick Start In order to launch a Linux process, QEMU needs the process executable -itself and all the target (x86) dynamic libraries used by it. +itself and all the target (x86) dynamic libraries used by it. @itemize @item On x86, you can just try to launch any process by using the native libraries: -@example +@example qemu-i386 -L / /bin/ls @end example @code{-L /} tells that the x86 dynamic linker must be searched with a @file{/} prefix. -@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): +@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): -@example +@example qemu-i386 -L / qemu-i386 -L / /bin/ls @end example @@ -1741,7 +2279,7 @@ qemu-i386 -L / qemu-i386 -L / /bin/ls @code{LD_LIBRARY_PATH} is not set: @example -unset LD_LIBRARY_PATH +unset LD_LIBRARY_PATH @end example Then you can launch the precompiled @file{ls} x86 executable: @@ -1763,7 +2301,7 @@ qemu-i386 /usr/local/qemu-i386/bin/qemu-i386 \ @end itemize @node Wine launch -@section Wine launch +@subsection Wine launch @itemize @@ -1776,7 +2314,7 @@ qemu-i386 /usr/local/qemu-i386/bin/ls-i386 @end example @item Download the binary x86 Wine install -(@file{qemu-XXX-i386-wine.tar.gz} on the QEMU web page). +(@file{qemu-XXX-i386-wine.tar.gz} on the QEMU web page). @item Configure Wine on your account. Look at the provided script @file{/usr/local/qemu-i386/@/bin/wine-conf.sh}. Your previous @@ -1792,7 +2330,7 @@ qemu-i386 /usr/local/qemu-i386/wine/bin/wine \ @end itemize @node Command line options -@section Command line options +@subsection Command line options @example usage: qemu-i386 [-h] [-d] [-L path] [-s size] program [arguments...] @@ -1801,7 +2339,7 @@ usage: qemu-i386 [-h] [-d] [-L path] [-s size] program [arguments...] @table @option @item -h Print the help -@item -L path +@item -L path Set the x86 elf interpreter prefix (default=/usr/local/qemu-i386) @item -s size Set the x86 stack size in bytes (default=524288) @@ -1817,7 +2355,7 @@ Act as if the host page size was 'pagesize' bytes @end table @node Other binaries -@section Other binaries +@subsection Other binaries @command{qemu-arm} is also capable of running ARM "Angel" semihosted ELF binaries (as implemented by the arm-elf and arm-eabi Newlib/GDB @@ -1829,6 +2367,91 @@ coldfire uClinux bFLT format binaries. The binary format is detected automatically. +@node Mac OS X/Darwin User space emulator +@section Mac OS X/Darwin User space emulator + +@menu +* Mac OS X/Darwin Status:: +* Mac OS X/Darwin Quick Start:: +* Mac OS X/Darwin Command line options:: +@end menu + +@node Mac OS X/Darwin Status +@subsection Mac OS X/Darwin Status + +@itemize @minus +@item +target x86 on x86: Most apps (Cocoa and Carbon too) works. [1] +@item +target PowerPC on x86: Not working as the ppc commpage can't be mapped (yet!) +@item +target PowerPC on PowerPC: Most apps (Cocoa and Carbon too) works. [1] +@item +target x86 on PowerPC: most utilities work. Cocoa and Carbon apps are not yet supported. +@end itemize + +[1] If you're host commpage can be executed by qemu. + +@node Mac OS X/Darwin Quick Start +@subsection Quick Start + +In order to launch a Mac OS X/Darwin process, QEMU needs the process executable +itself and all the target dynamic libraries used by it. If you don't have the FAT +libraries (you're running Mac OS X/ppc) you'll need to obtain it from a Mac OS X +CD or compile them by hand. + +@itemize + +@item On x86, you can just try to launch any process by using the native +libraries: + +@example +qemu-i386 /bin/ls +@end example + +or to run the ppc version of the executable: + +@example +qemu-ppc /bin/ls +@end example + +@item On ppc, you'll have to tell qemu where your x86 libraries (and dynamic linker) +are installed: + +@example +qemu-i386 -L /opt/x86_root/ /bin/ls +@end example + +@code{-L /opt/x86_root/} tells that the dynamic linker (dyld) path is in +@file{/opt/x86_root/usr/bin/dyld}. + +@end itemize + +@node Mac OS X/Darwin Command line options +@subsection Command line options + +@example +usage: qemu-i386 [-h] [-d] [-L path] [-s size] program [arguments...] +@end example + +@table @option +@item -h +Print the help +@item -L path +Set the library root path (default=/) +@item -s size +Set the stack size in bytes (default=524288) +@end table + +Debug options: + +@table @option +@item -d +Activate log (logfile=/tmp/qemu.log) +@item -p pagesize +Act as if the host page size was 'pagesize' bytes +@end table + @node compilation @chapter Compilation from the sources @@ -1863,39 +2486,15 @@ make install @end example to install QEMU in @file{/usr/local}. -@subsection Tested tool versions +@subsection GCC version In order to compile QEMU successfully, it is very important that you -have the right tools. The most important one is gcc. I cannot guaranty -that QEMU works if you do not use a tested gcc version. Look at -'configure' and 'Makefile' if you want to make a different gcc -version work. - -@example -host gcc binutils glibc linux distribution ----------------------------------------------------------------------- -x86 3.2 2.13.2 2.1.3 2.4.18 - 2.96 2.11.93.0.2 2.2.5 2.4.18 Red Hat 7.3 - 3.2.2 2.13.90.0.18 2.3.2 2.4.20 Red Hat 9 - -PowerPC 3.3 [4] 2.13.90.0.18 2.3.1 2.4.20briq - 3.2 - -Alpha 3.3 [1] 2.14.90.0.4 2.2.5 2.2.20 [2] Debian 3.0 - -Sparc32 2.95.4 2.12.90.0.1 2.2.5 2.4.18 Debian 3.0 - -ARM 2.95.4 2.12.90.0.1 2.2.5 2.4.9 [3] Debian 3.0 - -[1] On Alpha, QEMU needs the gcc 'visibility' attribute only available - for gcc version >= 3.3. -[2] Linux >= 2.4.20 is necessary for precise exception support - (untested). -[3] 2.4.9-ac10-rmk2-np1-cerf2 - -[4] gcc 2.95.x generates invalid code when using too many register -variables. You must use gcc 3.x on PowerPC. -@end example +have the right tools. The most important one is gcc. On most hosts and +in particular on x86 ones, @emph{gcc 4.x is not supported}. If your +Linux distribution includes a gcc 4.x compiler, you can usually +install an older version (it is invoked by @code{gcc32} or +@code{gcc34}). The QEMU configure script automatically probes for +these older versions so that usually you don't have to do anything. @node Windows @section Windows @@ -1905,7 +2504,7 @@ variables. You must use gcc 3.x on PowerPC. @url{http://www.mingw.org/}. You can find detailed installation instructions in the download section and the FAQ. -@item Download +@item Download the MinGW development library of SDL 1.2.x (@file{SDL-devel-1.2.x-@/mingw32.tar.gz}) from @url{http://www.libsdl.org}. Unpack it in a temporary place, and @@ -1914,14 +2513,14 @@ directory. Edit the @file{sdl-config} script so that it gives the correct SDL directory when invoked. @item Extract the current version of QEMU. - + @item Start the MSYS shell (file @file{msys.bat}). -@item Change to the QEMU directory. Launch @file{./configure} and +@item Change to the QEMU directory. Launch @file{./configure} and @file{make}. If you have problems using SDL, verify that @file{sdl-config} can be launched from the MSYS command line. -@item You can install QEMU in @file{Program Files/Qemu} by typing +@item You can install QEMU in @file{Program Files/Qemu} by typing @file{make install}. Don't forget to copy @file{SDL.dll} in @file{Program Files/Qemu}. @@ -1935,24 +2534,24 @@ correct SDL directory when invoked. Install the MinGW cross compilation tools available at @url{http://www.mingw.org/}. -@item +@item Install the Win32 version of SDL (@url{http://www.libsdl.org}) by unpacking @file{i386-mingw32msvc.tar.gz}. Set up the PATH environment variable so that @file{i386-mingw32msvc-sdl-config} can be launched by the QEMU configuration script. -@item +@item Configure QEMU for Windows cross compilation: @example ./configure --enable-mingw32 @end example If necessary, you can change the cross-prefix according to the prefix -choosen for the MinGW tools with --cross-prefix. You can also use +chosen for the MinGW tools with --cross-prefix. You can also use --prefix to set the Win32 install path. -@item You can install QEMU in the installation directory by typing +@item You can install QEMU in the installation directory by typing @file{make install}. Don't forget to copy @file{SDL.dll} in the -installation directory. +installation directory. @end itemize