]>
Commit | Line | Data |
---|---|---|
1 | \input texinfo @c -*- texinfo -*- | |
2 | ||
3 | @iftex | |
4 | @settitle QEMU CPU Emulator User Documentation | |
5 | @titlepage | |
6 | @sp 7 | |
7 | @center @titlefont{QEMU CPU Emulator User Documentation} | |
8 | @sp 3 | |
9 | @end titlepage | |
10 | @end iftex | |
11 | ||
12 | @chapter Introduction | |
13 | ||
14 | @section Features | |
15 | ||
16 | QEMU is a FAST! processor emulator using dynamic translation to | |
17 | achieve good emulation speed. | |
18 | ||
19 | QEMU has two operating modes: | |
20 | ||
21 | @itemize @minus | |
22 | ||
23 | @item | |
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. | |
28 | ||
29 | @item | |
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. | |
34 | ||
35 | @end itemize | |
36 | ||
37 | As QEMU requires no host kernel driver to run, it is very safe and | |
38 | easy to use. | |
39 | ||
40 | For system emulation, the following hardware targets are supported: | |
41 | @itemize | |
42 | @item PC (x86 processor) | |
43 | @item PREP (PowerPC processor) | |
44 | @item PowerMac (PowerPC processor, in progress) | |
45 | @end itemize | |
46 | ||
47 | For user emulation, x86, PowerPC, ARM, and SPARC CPUs are supported. | |
48 | ||
49 | @chapter Installation | |
50 | ||
51 | If you want to compile QEMU yourself, see @ref{compilation}. | |
52 | ||
53 | @section Linux | |
54 | ||
55 | Download the binary distribution (@file{qemu-XXX-i386.tar.gz}) and | |
56 | untar it as root in @file{/}: | |
57 | ||
58 | @example | |
59 | su | |
60 | cd / | |
61 | tar zxvf /tmp/qemu-XXX-i386.tar.gz | |
62 | @end example | |
63 | ||
64 | @section Windows | |
65 | ||
66 | Download the experimental binary installer at | |
67 | @url{http://www.freeoszoo.org/download.php}. | |
68 | ||
69 | @section Mac OS X | |
70 | ||
71 | Download the experimental binary installer at | |
72 | @url{http://www.freeoszoo.org/download.php}. | |
73 | ||
74 | @chapter QEMU PC System emulator invocation | |
75 | ||
76 | @section Introduction | |
77 | ||
78 | @c man begin DESCRIPTION | |
79 | ||
80 | The QEMU System emulator simulates a complete PC. | |
81 | ||
82 | In order to meet specific user needs, two versions of QEMU are | |
83 | available: | |
84 | ||
85 | @enumerate | |
86 | ||
87 | @item | |
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 | |
93 | OS. | |
94 | ||
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). | |
98 | ||
99 | @item | |
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. | |
103 | ||
104 | @end enumerate | |
105 | ||
106 | QEMU emulates the following PC peripherials: | |
107 | ||
108 | @itemize @minus | |
109 | @item | |
110 | i440FX host PCI bridge and PIIX3 PCI to ISA bridge | |
111 | @item | |
112 | Cirrus CLGD 5446 PCI VGA card or dummy VGA card with Bochs VESA | |
113 | extensions (hardware level, including all non standard modes). | |
114 | @item | |
115 | PS/2 mouse and keyboard | |
116 | @item | |
117 | 2 PCI IDE interfaces with hard disk and CD-ROM support | |
118 | @item | |
119 | Floppy disk | |
120 | @item | |
121 | NE2000 PCI network adapters | |
122 | @item | |
123 | Serial ports | |
124 | @item | |
125 | Soundblaster 16 card | |
126 | @end itemize | |
127 | ||
128 | QEMU uses the PC BIOS from the Bochs project and the Plex86/Bochs LGPL | |
129 | VGA BIOS. | |
130 | ||
131 | @c man end | |
132 | ||
133 | @section Quick Start | |
134 | ||
135 | Download and uncompress the linux image (@file{linux.img}) and type: | |
136 | ||
137 | @example | |
138 | qemu linux.img | |
139 | @end example | |
140 | ||
141 | Linux should boot and give you a prompt. | |
142 | ||
143 | @section Invocation | |
144 | ||
145 | @example | |
146 | @c man begin SYNOPSIS | |
147 | usage: qemu [options] [disk_image] | |
148 | @c man end | |
149 | @end example | |
150 | ||
151 | @c man begin OPTIONS | |
152 | @var{disk_image} is a raw hard disk image for IDE hard disk 0. | |
153 | ||
154 | General options: | |
155 | @table @option | |
156 | @item -fda file | |
157 | @item -fdb file | |
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. | |
160 | ||
161 | @item -hda file | |
162 | @item -hdb file | |
163 | @item -hdc file | |
164 | @item -hdd file | |
165 | Use @var{file} as hard disk 0, 1, 2 or 3 image (@xref{disk_images}). | |
166 | ||
167 | @item -cdrom file | |
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. | |
171 | ||
172 | @item -boot [a|c|d] | |
173 | Boot on floppy (a), hard disk (c) or CD-ROM (d). Hard disk boot is | |
174 | the default. | |
175 | ||
176 | @item -snapshot | |
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}). | |
180 | ||
181 | @item -m megs | |
182 | Set virtual RAM size to @var{megs} megabytes. Default is 128 MB. | |
183 | ||
184 | @item -nographic | |
185 | ||
186 | Normally, QEMU uses SDL to display the VGA output. With this option, | |
187 | you can totally disable graphical output so that QEMU is a simple | |
188 | command line application. The emulated serial port is redirected on | |
189 | the console. Therefore, you can still use QEMU to debug a Linux kernel | |
190 | with a serial console. | |
191 | ||
192 | @item -enable-audio | |
193 | ||
194 | The SB16 emulation is disabled by default as it may give problems with | |
195 | Windows. You can enable it manually with this option. | |
196 | ||
197 | @item -localtime | |
198 | Set the real time clock to local time (the default is to UTC | |
199 | time). This option is needed to have correct date in MS-DOS or | |
200 | Windows. | |
201 | ||
202 | @item -full-screen | |
203 | Start in full screen. | |
204 | ||
205 | @end table | |
206 | ||
207 | Network options: | |
208 | ||
209 | @table @option | |
210 | ||
211 | @item -n script | |
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. | |
215 | ||
216 | @item -macaddr addr | |
217 | ||
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. | |
221 | ||
222 | @item -tun-fd fd | |
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 | |
225 | example of its use. | |
226 | ||
227 | @item -user-net | |
228 | Use the user mode network stack. This is the default if no tun/tap | |
229 | network init script is found. | |
230 | ||
231 | @item -tftp prefix | |
232 | When using the user mode network stack, activate a built-in TFTP | |
233 | server. All filenames beginning with @var{prefix} can be downloaded | |
234 | from the host to the guest using a TFTP client. The TFTP client on the | |
235 | guest must be configured in binary mode (use the command @code{bin} of | |
236 | the Unix TFTP client). The host IP address on the guest is as usual | |
237 | 10.0.2.2. | |
238 | ||
239 | @item -smb dir | |
240 | When using the user mode network stack, activate a built-in SMB | |
241 | server so that Windows OSes can access to the host files in @file{dir} | |
242 | transparently. | |
243 | ||
244 | In the guest Windows OS, the line: | |
245 | @example | |
246 | 10.0.2.4 smbserver | |
247 | @end example | |
248 | must be added in the file @file{C:\WINDOWS\LMHOSTS} (for windows 9x/Me) | |
249 | or @file{C:\WINNT\SYSTEM32\DRIVERS\ETC\LMHOSTS} (Windows NT/2000). | |
250 | ||
251 | Then @file{dir} can be accessed in @file{\\smbserver\qemu}. | |
252 | ||
253 | Note that a SAMBA server must be installed on the host OS in | |
254 | @file{/usr/sbin/smbd}. QEMU was tested succesfully with smbd version | |
255 | 2.2.7a from the Red Hat 9. | |
256 | ||
257 | @item -redir [tcp|udp]:host-port:[guest-host]:guest-port | |
258 | ||
259 | When using the user mode network stack, redirect incoming TCP or UDP | |
260 | connections to the host port @var{host-port} to the guest | |
261 | @var{guest-host} on guest port @var{guest-port}. If @var{guest-host} | |
262 | is not specified, its value is 10.0.2.15 (default address given by the | |
263 | built-in DHCP server). | |
264 | ||
265 | For example, to redirect host X11 connection from screen 1 to guest | |
266 | screen 0, use the following: | |
267 | ||
268 | @example | |
269 | # on the host | |
270 | qemu -redir tcp:6001::6000 [...] | |
271 | # this host xterm should open in the guest X11 server | |
272 | xterm -display :1 | |
273 | @end example | |
274 | ||
275 | To redirect telnet connections from host port 5555 to telnet port on | |
276 | the guest, use the following: | |
277 | ||
278 | @example | |
279 | # on the host | |
280 | qemu -redir tcp:5555::23 [...] | |
281 | telnet localhost 5555 | |
282 | @end example | |
283 | ||
284 | Then when you use on the host @code{telnet localhost 5555}, you | |
285 | connect to the guest telnet server. | |
286 | ||
287 | @item -dummy-net | |
288 | Use the dummy network stack: no packet will be received by the network | |
289 | cards. | |
290 | ||
291 | @end table | |
292 | ||
293 | Linux boot specific. When using this options, you can use a given | |
294 | Linux kernel without installing it in the disk image. It can be useful | |
295 | for easier testing of various kernels. | |
296 | ||
297 | @table @option | |
298 | ||
299 | @item -kernel bzImage | |
300 | Use @var{bzImage} as kernel image. | |
301 | ||
302 | @item -append cmdline | |
303 | Use @var{cmdline} as kernel command line | |
304 | ||
305 | @item -initrd file | |
306 | Use @var{file} as initial ram disk. | |
307 | ||
308 | @end table | |
309 | ||
310 | Debug/Expert options: | |
311 | @table @option | |
312 | ||
313 | @item -serial dev | |
314 | Redirect the virtual serial port to host device @var{dev}. Available | |
315 | devices are: | |
316 | @table @code | |
317 | @item vc | |
318 | Virtual console | |
319 | @item pty | |
320 | [Linux only] Pseudo TTY (a new PTY is automatically allocated) | |
321 | @item null | |
322 | void device | |
323 | @item stdio | |
324 | [Unix only] standard input/output | |
325 | @end table | |
326 | The default device is @code{vc} in graphical mode and @code{stdio} in | |
327 | non graphical mode. | |
328 | ||
329 | This option can be used several times to simulate up to 4 serials | |
330 | ports. | |
331 | ||
332 | @item -monitor dev | |
333 | Redirect the monitor to host device @var{dev} (same devices as the | |
334 | serial port). | |
335 | The default device is @code{vc} in graphical mode and @code{stdio} in | |
336 | non graphical mode. | |
337 | ||
338 | @item -s | |
339 | Wait gdb connection to port 1234 (@xref{gdb_usage}). | |
340 | @item -p port | |
341 | Change gdb connection port. | |
342 | @item -S | |
343 | Do not start CPU at startup (you must type 'c' in the monitor). | |
344 | @item -d | |
345 | Output log in /tmp/qemu.log | |
346 | @item -isa | |
347 | Simulate an ISA-only system (default is PCI system). | |
348 | @item -std-vga | |
349 | Simulate a standard VGA card with Bochs VBE extensions (default is | |
350 | Cirrus Logic GD5446 PCI VGA) | |
351 | @item -loadvm file | |
352 | Start right away with a saved state (@code{loadvm} in monitor) | |
353 | @end table | |
354 | ||
355 | @c man end | |
356 | ||
357 | @section Keys | |
358 | ||
359 | @c man begin OPTIONS | |
360 | ||
361 | During the graphical emulation, you can use the following keys: | |
362 | @table @key | |
363 | @item Ctrl-Alt-f | |
364 | Toggle full screen | |
365 | ||
366 | @item Ctrl-Alt-n | |
367 | Switch to virtual console 'n'. Standard console mappings are: | |
368 | @table @emph | |
369 | @item 1 | |
370 | Target system display | |
371 | @item 2 | |
372 | Monitor | |
373 | @item 3 | |
374 | Serial port | |
375 | @end table | |
376 | ||
377 | @item Ctrl-Alt | |
378 | Toggle mouse and keyboard grab. | |
379 | @end table | |
380 | ||
381 | In the virtual consoles, you can use @key{Ctrl-Up}, @key{Ctrl-Down}, | |
382 | @key{Ctrl-PageUp} and @key{Ctrl-PageDown} to move in the back log. | |
383 | ||
384 | During emulation, if you are using the @option{-nographic} option, use | |
385 | @key{Ctrl-a h} to get terminal commands: | |
386 | ||
387 | @table @key | |
388 | @item Ctrl-a h | |
389 | Print this help | |
390 | @item Ctrl-a x | |
391 | Exit emulatior | |
392 | @item Ctrl-a s | |
393 | Save disk data back to file (if -snapshot) | |
394 | @item Ctrl-a b | |
395 | Send break (magic sysrq in Linux) | |
396 | @item Ctrl-a c | |
397 | Switch between console and monitor | |
398 | @item Ctrl-a Ctrl-a | |
399 | Send Ctrl-a | |
400 | @end table | |
401 | @c man end | |
402 | ||
403 | @ignore | |
404 | ||
405 | @setfilename qemu | |
406 | @settitle QEMU System Emulator | |
407 | ||
408 | @c man begin SEEALSO | |
409 | The HTML documentation of QEMU for more precise information and Linux | |
410 | user mode emulator invocation. | |
411 | @c man end | |
412 | ||
413 | @c man begin AUTHOR | |
414 | Fabrice Bellard | |
415 | @c man end | |
416 | ||
417 | @end ignore | |
418 | ||
419 | @end ignore | |
420 | ||
421 | ||
422 | @section QEMU Monitor | |
423 | ||
424 | The QEMU monitor is used to give complex commands to the QEMU | |
425 | emulator. You can use it to: | |
426 | ||
427 | @itemize @minus | |
428 | ||
429 | @item | |
430 | Remove or insert removable medias images | |
431 | (such as CD-ROM or floppies) | |
432 | ||
433 | @item | |
434 | Freeze/unfreeze the Virtual Machine (VM) and save or restore its state | |
435 | from a disk file. | |
436 | ||
437 | @item Inspect the VM state without an external debugger. | |
438 | ||
439 | @end itemize | |
440 | ||
441 | @subsection Commands | |
442 | ||
443 | The following commands are available: | |
444 | ||
445 | @table @option | |
446 | ||
447 | @item help or ? [cmd] | |
448 | Show the help for all commands or just for command @var{cmd}. | |
449 | ||
450 | @item commit | |
451 | Commit changes to the disk images (if -snapshot is used) | |
452 | ||
453 | @item info subcommand | |
454 | show various information about the system state | |
455 | ||
456 | @table @option | |
457 | @item info network | |
458 | show the network state | |
459 | @item info block | |
460 | show the block devices | |
461 | @item info registers | |
462 | show the cpu registers | |
463 | @item info history | |
464 | show the command line history | |
465 | @end table | |
466 | ||
467 | @item q or quit | |
468 | Quit the emulator. | |
469 | ||
470 | @item eject [-f] device | |
471 | Eject a removable media (use -f to force it). | |
472 | ||
473 | @item change device filename | |
474 | Change a removable media. | |
475 | ||
476 | @item screendump filename | |
477 | Save screen into PPM image @var{filename}. | |
478 | ||
479 | @item log item1[,...] | |
480 | Activate logging of the specified items to @file{/tmp/qemu.log}. | |
481 | ||
482 | @item savevm filename | |
483 | Save the whole virtual machine state to @var{filename}. | |
484 | ||
485 | @item loadvm filename | |
486 | Restore the whole virtual machine state from @var{filename}. | |
487 | ||
488 | @item stop | |
489 | Stop emulation. | |
490 | ||
491 | @item c or cont | |
492 | Resume emulation. | |
493 | ||
494 | @item gdbserver [port] | |
495 | Start gdbserver session (default port=1234) | |
496 | ||
497 | @item x/fmt addr | |
498 | Virtual memory dump starting at @var{addr}. | |
499 | ||
500 | @item xp /fmt addr | |
501 | Physical memory dump starting at @var{addr}. | |
502 | ||
503 | @var{fmt} is a format which tells the command how to format the | |
504 | data. Its syntax is: @option{/@{count@}@{format@}@{size@}} | |
505 | ||
506 | @table @var | |
507 | @item count | |
508 | is the number of items to be dumped. | |
509 | ||
510 | @item format | |
511 | can be x (hexa), d (signed decimal), u (unsigned decimal), o (octal), | |
512 | c (char) or i (asm instruction). | |
513 | ||
514 | @item size | |
515 | can be b (8 bits), h (16 bits), w (32 bits) or g (64 bits). On x86, | |
516 | @code{h} or @code{w} can be specified with the @code{i} format to | |
517 | respectively select 16 or 32 bit code instruction size. | |
518 | ||
519 | @end table | |
520 | ||
521 | Examples: | |
522 | @itemize | |
523 | @item | |
524 | Dump 10 instructions at the current instruction pointer: | |
525 | @example | |
526 | (qemu) x/10i $eip | |
527 | 0x90107063: ret | |
528 | 0x90107064: sti | |
529 | 0x90107065: lea 0x0(%esi,1),%esi | |
530 | 0x90107069: lea 0x0(%edi,1),%edi | |
531 | 0x90107070: ret | |
532 | 0x90107071: jmp 0x90107080 | |
533 | 0x90107073: nop | |
534 | 0x90107074: nop | |
535 | 0x90107075: nop | |
536 | 0x90107076: nop | |
537 | @end example | |
538 | ||
539 | @item | |
540 | Dump 80 16 bit values at the start of the video memory. | |
541 | @example | |
542 | (qemu) xp/80hx 0xb8000 | |
543 | 0x000b8000: 0x0b50 0x0b6c 0x0b65 0x0b78 0x0b38 0x0b36 0x0b2f 0x0b42 | |
544 | 0x000b8010: 0x0b6f 0x0b63 0x0b68 0x0b73 0x0b20 0x0b56 0x0b47 0x0b41 | |
545 | 0x000b8020: 0x0b42 0x0b69 0x0b6f 0x0b73 0x0b20 0x0b63 0x0b75 0x0b72 | |
546 | 0x000b8030: 0x0b72 0x0b65 0x0b6e 0x0b74 0x0b2d 0x0b63 0x0b76 0x0b73 | |
547 | 0x000b8040: 0x0b20 0x0b30 0x0b35 0x0b20 0x0b4e 0x0b6f 0x0b76 0x0b20 | |
548 | 0x000b8050: 0x0b32 0x0b30 0x0b30 0x0b33 0x0720 0x0720 0x0720 0x0720 | |
549 | 0x000b8060: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 | |
550 | 0x000b8070: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 | |
551 | 0x000b8080: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 | |
552 | 0x000b8090: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 | |
553 | @end example | |
554 | @end itemize | |
555 | ||
556 | @item p or print/fmt expr | |
557 | ||
558 | Print expression value. Only the @var{format} part of @var{fmt} is | |
559 | used. | |
560 | ||
561 | @item sendkey keys | |
562 | ||
563 | Send @var{keys} to the emulator. Use @code{-} to press several keys | |
564 | simultaneously. Example: | |
565 | @example | |
566 | sendkey ctrl-alt-f1 | |
567 | @end example | |
568 | ||
569 | This command is useful to send keys that your graphical user interface | |
570 | intercepts at low level, such as @code{ctrl-alt-f1} in X Window. | |
571 | ||
572 | @item system_reset | |
573 | ||
574 | Reset the system. | |
575 | ||
576 | @end table | |
577 | ||
578 | @subsection Integer expressions | |
579 | ||
580 | The monitor understands integers expressions for every integer | |
581 | argument. You can use register names to get the value of specifics | |
582 | CPU registers by prefixing them with @emph{$}. | |
583 | ||
584 | @node disk_images | |
585 | @section Disk Images | |
586 | ||
587 | @subsection Raw disk images | |
588 | ||
589 | The disk images can simply be raw images of the hard disk. You can | |
590 | create them with the command: | |
591 | @example | |
592 | dd of=myimage bs=1024 seek=mysize count=0 | |
593 | @end example | |
594 | where @var{myimage} is the image filename and @var{mysize} is its size | |
595 | in kilobytes. | |
596 | ||
597 | @subsection Snapshot mode | |
598 | ||
599 | If you use the option @option{-snapshot}, all disk images are | |
600 | considered as read only. When sectors in written, they are written in | |
601 | a temporary file created in @file{/tmp}. You can however force the | |
602 | write back to the raw disk images by pressing @key{C-a s}. | |
603 | ||
604 | NOTE: The snapshot mode only works with raw disk images. | |
605 | ||
606 | @subsection Copy On Write disk images | |
607 | ||
608 | QEMU also supports user mode Linux | |
609 | (@url{http://user-mode-linux.sourceforge.net/}) Copy On Write (COW) | |
610 | disk images. The COW disk images are much smaller than normal images | |
611 | as they store only modified sectors. They also permit the use of the | |
612 | same disk image template for many users. | |
613 | ||
614 | To create a COW disk images, use the command: | |
615 | ||
616 | @example | |
617 | qemu-mkcow -f myrawimage.bin mycowimage.cow | |
618 | @end example | |
619 | ||
620 | @file{myrawimage.bin} is a raw image you want to use as original disk | |
621 | image. It will never be written to. | |
622 | ||
623 | @file{mycowimage.cow} is the COW disk image which is created by | |
624 | @code{qemu-mkcow}. You can use it directly with the @option{-hdx} | |
625 | options. You must not modify the original raw disk image if you use | |
626 | COW images, as COW images only store the modified sectors from the raw | |
627 | disk image. QEMU stores the original raw disk image name and its | |
628 | modified time in the COW disk image so that chances of mistakes are | |
629 | reduced. | |
630 | ||
631 | If the raw disk image is not read-only, by pressing @key{C-a s} you | |
632 | can flush the COW disk image back into the raw disk image, as in | |
633 | snapshot mode. | |
634 | ||
635 | COW disk images can also be created without a corresponding raw disk | |
636 | image. It is useful to have a big initial virtual disk image without | |
637 | using much disk space. Use: | |
638 | ||
639 | @example | |
640 | qemu-mkcow mycowimage.cow 1024 | |
641 | @end example | |
642 | ||
643 | to create a 1 gigabyte empty COW disk image. | |
644 | ||
645 | NOTES: | |
646 | @enumerate | |
647 | @item | |
648 | COW disk images must be created on file systems supporting | |
649 | @emph{holes} such as ext2 or ext3. | |
650 | @item | |
651 | Since holes are used, the displayed size of the COW disk image is not | |
652 | the real one. To know it, use the @code{ls -ls} command. | |
653 | @end enumerate | |
654 | ||
655 | @subsection Convert VMware disk images to raw disk images | |
656 | ||
657 | You can use the tool @file{vmdk2raw} to convert VMware disk images to | |
658 | raw disk images directly usable by QEMU. The syntax is: | |
659 | @example | |
660 | vmdk2raw vmware_image output_image | |
661 | @end example | |
662 | ||
663 | @section Network emulation | |
664 | ||
665 | QEMU simulates up to 6 networks cards (NE2000 boards). Each card can | |
666 | be connected to a specific host network interface. | |
667 | ||
668 | @subsection Using tun/tap network interface | |
669 | ||
670 | This is the standard way to emulate network. QEMU adds a virtual | |
671 | network device on your host (called @code{tun0}), and you can then | |
672 | configure it as if it was a real ethernet card. | |
673 | ||
674 | As an example, you can download the @file{linux-test-xxx.tar.gz} | |
675 | archive and copy the script @file{qemu-ifup} in @file{/etc} and | |
676 | configure properly @code{sudo} so that the command @code{ifconfig} | |
677 | contained in @file{qemu-ifup} can be executed as root. You must verify | |
678 | that your host kernel supports the TUN/TAP network interfaces: the | |
679 | device @file{/dev/net/tun} must be present. | |
680 | ||
681 | See @ref{direct_linux_boot} to have an example of network use with a | |
682 | Linux distribution. | |
683 | ||
684 | @subsection Using the user mode network stack | |
685 | ||
686 | By using the option @option{-user-net} or if you have no tun/tap init | |
687 | script, QEMU uses a completely user mode network stack (you don't need | |
688 | root priviledge to use the virtual network). The virtual network | |
689 | configuration is the following: | |
690 | ||
691 | @example | |
692 | ||
693 | QEMU Virtual Machine <------> Firewall/DHCP server <-----> Internet | |
694 | (10.0.2.x) | (10.0.2.2) | |
695 | | | |
696 | ----> DNS server (10.0.2.3) | |
697 | | | |
698 | ----> SMB server (10.0.2.4) | |
699 | @end example | |
700 | ||
701 | The QEMU VM behaves as if it was behind a firewall which blocks all | |
702 | incoming connections. You can use a DHCP client to automatically | |
703 | configure the network in the QEMU VM. | |
704 | ||
705 | In order to check that the user mode network is working, you can ping | |
706 | the address 10.0.2.2 and verify that you got an address in the range | |
707 | 10.0.2.x from the QEMU virtual DHCP server. | |
708 | ||
709 | Note that @code{ping} is not supported reliably to the internet as it | |
710 | would require root priviledges. It means you can only ping the local | |
711 | router (10.0.2.2). | |
712 | ||
713 | When using the built-in TFTP server, the router is also the TFTP | |
714 | server. | |
715 | ||
716 | When using the @option{-redir} option, TCP or UDP connections can be | |
717 | redirected from the host to the guest. It allows for example to | |
718 | redirect X11, telnet or SSH connections. | |
719 | ||
720 | @node direct_linux_boot | |
721 | @section Direct Linux Boot | |
722 | ||
723 | This section explains how to launch a Linux kernel inside QEMU without | |
724 | having to make a full bootable image. It is very useful for fast Linux | |
725 | kernel testing. The QEMU network configuration is also explained. | |
726 | ||
727 | @enumerate | |
728 | @item | |
729 | Download the archive @file{linux-test-xxx.tar.gz} containing a Linux | |
730 | kernel and a disk image. | |
731 | ||
732 | @item Optional: If you want network support (for example to launch X11 examples), you | |
733 | must copy the script @file{qemu-ifup} in @file{/etc} and configure | |
734 | properly @code{sudo} so that the command @code{ifconfig} contained in | |
735 | @file{qemu-ifup} can be executed as root. You must verify that your host | |
736 | kernel supports the TUN/TAP network interfaces: the device | |
737 | @file{/dev/net/tun} must be present. | |
738 | ||
739 | When network is enabled, there is a virtual network connection between | |
740 | the host kernel and the emulated kernel. The emulated kernel is seen | |
741 | from the host kernel at IP address 172.20.0.2 and the host kernel is | |
742 | seen from the emulated kernel at IP address 172.20.0.1. | |
743 | ||
744 | @item Launch @code{qemu.sh}. You should have the following output: | |
745 | ||
746 | @example | |
747 | > ./qemu.sh | |
748 | Connected to host network interface: tun0 | |
749 | 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 | |
750 | BIOS-provided physical RAM map: | |
751 | BIOS-e801: 0000000000000000 - 000000000009f000 (usable) | |
752 | BIOS-e801: 0000000000100000 - 0000000002000000 (usable) | |
753 | 32MB LOWMEM available. | |
754 | On node 0 totalpages: 8192 | |
755 | zone(0): 4096 pages. | |
756 | zone(1): 4096 pages. | |
757 | zone(2): 0 pages. | |
758 | Kernel command line: root=/dev/hda sb=0x220,5,1,5 ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe console=ttyS0 | |
759 | ide_setup: ide2=noprobe | |
760 | ide_setup: ide3=noprobe | |
761 | ide_setup: ide4=noprobe | |
762 | ide_setup: ide5=noprobe | |
763 | Initializing CPU#0 | |
764 | Detected 2399.621 MHz processor. | |
765 | Console: colour EGA 80x25 | |
766 | Calibrating delay loop... 4744.80 BogoMIPS | |
767 | Memory: 28872k/32768k available (1210k kernel code, 3508k reserved, 266k data, 64k init, 0k highmem) | |
768 | Dentry cache hash table entries: 4096 (order: 3, 32768 bytes) | |
769 | Inode cache hash table entries: 2048 (order: 2, 16384 bytes) | |
770 | Mount cache hash table entries: 512 (order: 0, 4096 bytes) | |
771 | Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes) | |
772 | Page-cache hash table entries: 8192 (order: 3, 32768 bytes) | |
773 | CPU: Intel Pentium Pro stepping 03 | |
774 | Checking 'hlt' instruction... OK. | |
775 | POSIX conformance testing by UNIFIX | |
776 | Linux NET4.0 for Linux 2.4 | |
777 | Based upon Swansea University Computer Society NET3.039 | |
778 | Initializing RT netlink socket | |
779 | apm: BIOS not found. | |
780 | Starting kswapd | |
781 | Journalled Block Device driver loaded | |
782 | Detected PS/2 Mouse Port. | |
783 | pty: 256 Unix98 ptys configured | |
784 | Serial driver version 5.05c (2001-07-08) with no serial options enabled | |
785 | ttyS00 at 0x03f8 (irq = 4) is a 16450 | |
786 | ne.c:v1.10 9/23/94 Donald Becker (becker@scyld.com) | |
787 | Last modified Nov 1, 2000 by Paul Gortmaker | |
788 | NE*000 ethercard probe at 0x300: 52 54 00 12 34 56 | |
789 | eth0: NE2000 found at 0x300, using IRQ 9. | |
790 | RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize | |
791 | Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4 | |
792 | ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx | |
793 | hda: QEMU HARDDISK, ATA DISK drive | |
794 | ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 | |
795 | hda: attached ide-disk driver. | |
796 | hda: 20480 sectors (10 MB) w/256KiB Cache, CHS=20/16/63 | |
797 | Partition check: | |
798 | hda: | |
799 | Soundblaster audio driver Copyright (C) by Hannu Savolainen 1993-1996 | |
800 | NET4: Linux TCP/IP 1.0 for NET4.0 | |
801 | IP Protocols: ICMP, UDP, TCP, IGMP | |
802 | IP: routing cache hash table of 512 buckets, 4Kbytes | |
803 | TCP: Hash tables configured (established 2048 bind 4096) | |
804 | NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. | |
805 | EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended | |
806 | VFS: Mounted root (ext2 filesystem). | |
807 | Freeing unused kernel memory: 64k freed | |
808 | ||
809 | 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 | |
810 | ||
811 | QEMU Linux test distribution (based on Redhat 9) | |
812 | ||
813 | Type 'exit' to halt the system | |
814 | ||
815 | sh-2.05b# | |
816 | @end example | |
817 | ||
818 | @item | |
819 | Then you can play with the kernel inside the virtual serial console. You | |
820 | can launch @code{ls} for example. Type @key{Ctrl-a h} to have an help | |
821 | about the keys you can type inside the virtual serial console. In | |
822 | particular, use @key{Ctrl-a x} to exit QEMU and use @key{Ctrl-a b} as | |
823 | the Magic SysRq key. | |
824 | ||
825 | @item | |
826 | If the network is enabled, launch the script @file{/etc/linuxrc} in the | |
827 | emulator (don't forget the leading dot): | |
828 | @example | |
829 | . /etc/linuxrc | |
830 | @end example | |
831 | ||
832 | Then enable X11 connections on your PC from the emulated Linux: | |
833 | @example | |
834 | xhost +172.20.0.2 | |
835 | @end example | |
836 | ||
837 | You can now launch @file{xterm} or @file{xlogo} and verify that you have | |
838 | a real Virtual Linux system ! | |
839 | ||
840 | @end enumerate | |
841 | ||
842 | NOTES: | |
843 | @enumerate | |
844 | @item | |
845 | A 2.5.74 kernel is also included in the archive. Just | |
846 | replace the bzImage in qemu.sh to try it. | |
847 | ||
848 | @item | |
849 | qemu-fast creates a temporary file in @var{$QEMU_TMPDIR} (@file{/tmp} is the | |
850 | default) containing all the simulated PC memory. If possible, try to use | |
851 | a temporary directory using the tmpfs filesystem to avoid too many | |
852 | unnecessary disk accesses. | |
853 | ||
854 | @item | |
855 | In order to exit cleanly from qemu, you can do a @emph{shutdown} inside | |
856 | qemu. qemu will automatically exit when the Linux shutdown is done. | |
857 | ||
858 | @item | |
859 | You can boot slightly faster by disabling the probe of non present IDE | |
860 | interfaces. To do so, add the following options on the kernel command | |
861 | line: | |
862 | @example | |
863 | ide1=noprobe ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe | |
864 | @end example | |
865 | ||
866 | @item | |
867 | The example disk image is a modified version of the one made by Kevin | |
868 | Lawton for the plex86 Project (@url{www.plex86.org}). | |
869 | ||
870 | @end enumerate | |
871 | ||
872 | @node linux_compile | |
873 | @section Linux Kernel Compilation | |
874 | ||
875 | You can use any linux kernel with QEMU. However, if you want to use | |
876 | @code{qemu-fast} to get maximum performances, you must use a modified | |
877 | guest kernel. If you are using a 2.6 guest kernel, you can use | |
878 | directly the patch @file{linux-2.6-qemu-fast.patch} made by Rusty | |
879 | Russel available in the QEMU source archive. Otherwise, you can make the | |
880 | following changes @emph{by hand} to the Linux kernel: | |
881 | ||
882 | @enumerate | |
883 | @item | |
884 | The kernel must be mapped at 0x90000000 (the default is | |
885 | 0xc0000000). You must modify only two lines in the kernel source: | |
886 | ||
887 | In @file{include/asm/page.h}, replace | |
888 | @example | |
889 | #define __PAGE_OFFSET (0xc0000000) | |
890 | @end example | |
891 | by | |
892 | @example | |
893 | #define __PAGE_OFFSET (0x90000000) | |
894 | @end example | |
895 | ||
896 | And in @file{arch/i386/vmlinux.lds}, replace | |
897 | @example | |
898 | . = 0xc0000000 + 0x100000; | |
899 | @end example | |
900 | by | |
901 | @example | |
902 | . = 0x90000000 + 0x100000; | |
903 | @end example | |
904 | ||
905 | @item | |
906 | If you want to enable SMP (Symmetric Multi-Processing) support, you | |
907 | must make the following change in @file{include/asm/fixmap.h}. Replace | |
908 | @example | |
909 | #define FIXADDR_TOP (0xffffX000UL) | |
910 | @end example | |
911 | by | |
912 | @example | |
913 | #define FIXADDR_TOP (0xa7ffX000UL) | |
914 | @end example | |
915 | (X is 'e' or 'f' depending on the kernel version). Although you can | |
916 | use an SMP kernel with QEMU, it only supports one CPU. | |
917 | ||
918 | @item | |
919 | If you are not using a 2.6 kernel as host kernel but if you use a target | |
920 | 2.6 kernel, you must also ensure that the 'HZ' define is set to 100 | |
921 | (1000 is the default) as QEMU cannot currently emulate timers at | |
922 | frequencies greater than 100 Hz on host Linux systems < 2.6. In | |
923 | @file{include/asm/param.h}, replace: | |
924 | ||
925 | @example | |
926 | # define HZ 1000 /* Internal kernel timer frequency */ | |
927 | @end example | |
928 | by | |
929 | @example | |
930 | # define HZ 100 /* Internal kernel timer frequency */ | |
931 | @end example | |
932 | ||
933 | @end enumerate | |
934 | ||
935 | The file config-2.x.x gives the configuration of the example kernels. | |
936 | ||
937 | Just type | |
938 | @example | |
939 | make bzImage | |
940 | @end example | |
941 | ||
942 | As you would do to make a real kernel. Then you can use with QEMU | |
943 | exactly the same kernel as you would boot on your PC (in | |
944 | @file{arch/i386/boot/bzImage}). | |
945 | ||
946 | @node gdb_usage | |
947 | @section GDB usage | |
948 | ||
949 | QEMU has a primitive support to work with gdb, so that you can do | |
950 | 'Ctrl-C' while the virtual machine is running and inspect its state. | |
951 | ||
952 | In order to use gdb, launch qemu with the '-s' option. It will wait for a | |
953 | gdb connection: | |
954 | @example | |
955 | > qemu -s -kernel arch/i386/boot/bzImage -hda root-2.4.20.img -append "root=/dev/hda" | |
956 | Connected to host network interface: tun0 | |
957 | Waiting gdb connection on port 1234 | |
958 | @end example | |
959 | ||
960 | Then launch gdb on the 'vmlinux' executable: | |
961 | @example | |
962 | > gdb vmlinux | |
963 | @end example | |
964 | ||
965 | In gdb, connect to QEMU: | |
966 | @example | |
967 | (gdb) target remote localhost:1234 | |
968 | @end example | |
969 | ||
970 | Then you can use gdb normally. For example, type 'c' to launch the kernel: | |
971 | @example | |
972 | (gdb) c | |
973 | @end example | |
974 | ||
975 | Here are some useful tips in order to use gdb on system code: | |
976 | ||
977 | @enumerate | |
978 | @item | |
979 | Use @code{info reg} to display all the CPU registers. | |
980 | @item | |
981 | Use @code{x/10i $eip} to display the code at the PC position. | |
982 | @item | |
983 | Use @code{set architecture i8086} to dump 16 bit code. Then use | |
984 | @code{x/10i $cs*16+*eip} to dump the code at the PC position. | |
985 | @end enumerate | |
986 | ||
987 | @section Target OS specific information | |
988 | ||
989 | @subsection Linux | |
990 | ||
991 | To have access to SVGA graphic modes under X11, use the @code{vesa} or | |
992 | the @code{cirrus} X11 driver. For optimal performances, use 16 bit | |
993 | color depth in the guest and the host OS. | |
994 | ||
995 | When using a 2.6 guest Linux kernel, you should add the option | |
996 | @code{clock=pit} on the kernel command line because the 2.6 Linux | |
997 | kernels make very strict real time clock checks by default that QEMU | |
998 | cannot simulate exactly. | |
999 | ||
1000 | @subsection Windows | |
1001 | ||
1002 | If you have a slow host, using Windows 95 is better as it gives the | |
1003 | best speed. Windows 2000 is also a good choice. | |
1004 | ||
1005 | @subsubsection SVGA graphic modes support | |
1006 | ||
1007 | QEMU emulates a Cirrus Logic GD5446 Video | |
1008 | card. All Windows versions starting from Windows 95 should recognize | |
1009 | and use this graphic card. For optimal performances, use 16 bit color | |
1010 | depth in the guest and the host OS. | |
1011 | ||
1012 | @subsubsection CPU usage reduction | |
1013 | ||
1014 | Windows 9x does not correctly use the CPU HLT | |
1015 | instruction. The result is that it takes host CPU cycles even when | |
1016 | idle. You can install the utility from | |
1017 | @url{http://www.user.cityline.ru/~maxamn/amnhltm.zip} to solve this | |
1018 | problem. Note that no such tool is needed for NT, 2000 or XP. | |
1019 | ||
1020 | @subsubsection Windows 2000 disk full problems | |
1021 | ||
1022 | Currently (release 0.6.0) QEMU has a bug which gives a @code{disk | |
1023 | full} error during installation of some releases of Windows 2000. The | |
1024 | workaround is to stop QEMU as soon as you notice that your disk image | |
1025 | size is growing too fast (monitor it with @code{ls -ls}). Then | |
1026 | relaunch QEMU to continue the installation. If you still experience | |
1027 | the problem, relaunch QEMU again. | |
1028 | ||
1029 | Future QEMU releases are likely to correct this bug. | |
1030 | ||
1031 | @subsubsection Windows XP security problems | |
1032 | ||
1033 | Some releases of Windows XP install correctly but give a security | |
1034 | error when booting: | |
1035 | @example | |
1036 | A problem is preventing Windows from accurately checking the | |
1037 | license for this computer. Error code: 0x800703e6. | |
1038 | @end example | |
1039 | The only known workaround is to boot in Safe mode | |
1040 | without networking support. | |
1041 | ||
1042 | Future QEMU releases are likely to correct this bug. | |
1043 | ||
1044 | @subsection MS-DOS and FreeDOS | |
1045 | ||
1046 | @subsubsection CPU usage reduction | |
1047 | ||
1048 | DOS does not correctly use the CPU HLT instruction. The result is that | |
1049 | it takes host CPU cycles even when idle. You can install the utility | |
1050 | from @url{http://www.vmware.com/software/dosidle210.zip} to solve this | |
1051 | problem. | |
1052 | ||
1053 | @chapter QEMU PowerPC System emulator invocation | |
1054 | ||
1055 | Use the executable @file{qemu-system-ppc} to simulate a complete PREP | |
1056 | or PowerMac PowerPC system. | |
1057 | ||
1058 | QEMU emulates the following PowerMac peripherials: | |
1059 | ||
1060 | @itemize @minus | |
1061 | @item | |
1062 | UniNorth PCI Bridge | |
1063 | @item | |
1064 | PCI VGA compatible card with VESA Bochs Extensions | |
1065 | @item | |
1066 | 2 PMAC IDE interfaces with hard disk and CD-ROM support | |
1067 | @item | |
1068 | NE2000 PCI adapters | |
1069 | @item | |
1070 | Non Volatile RAM | |
1071 | @item | |
1072 | VIA-CUDA with ADB keyboard and mouse. | |
1073 | @end itemize | |
1074 | ||
1075 | QEMU emulates the following PREP peripherials: | |
1076 | ||
1077 | @itemize @minus | |
1078 | @item | |
1079 | PCI Bridge | |
1080 | @item | |
1081 | PCI VGA compatible card with VESA Bochs Extensions | |
1082 | @item | |
1083 | 2 IDE interfaces with hard disk and CD-ROM support | |
1084 | @item | |
1085 | Floppy disk | |
1086 | @item | |
1087 | NE2000 network adapters | |
1088 | @item | |
1089 | Serial port | |
1090 | @item | |
1091 | PREP Non Volatile RAM | |
1092 | @item | |
1093 | PC compatible keyboard and mouse. | |
1094 | @end itemize | |
1095 | ||
1096 | QEMU uses the Open Hack'Ware Open Firmware Compatible BIOS available at | |
1097 | @url{http://site.voila.fr/jmayer/OpenHackWare/index.htm}. | |
1098 | ||
1099 | You can read the qemu PC system emulation chapter to have more | |
1100 | informations about QEMU usage. | |
1101 | ||
1102 | @c man begin OPTIONS | |
1103 | ||
1104 | The following options are specific to the PowerPC emulation: | |
1105 | ||
1106 | @table @option | |
1107 | ||
1108 | @item -prep | |
1109 | Simulate a PREP system (default is PowerMAC) | |
1110 | ||
1111 | @item -g WxH[xDEPTH] | |
1112 | ||
1113 | Set the initial VGA graphic mode. The default is 800x600x15. | |
1114 | ||
1115 | @end table | |
1116 | ||
1117 | @c man end | |
1118 | ||
1119 | ||
1120 | More information is available at | |
1121 | @url{http://jocelyn.mayer.free.fr/qemu-ppc/}. | |
1122 | ||
1123 | @chapter QEMU User space emulator invocation | |
1124 | ||
1125 | @section Quick Start | |
1126 | ||
1127 | In order to launch a Linux process, QEMU needs the process executable | |
1128 | itself and all the target (x86) dynamic libraries used by it. | |
1129 | ||
1130 | @itemize | |
1131 | ||
1132 | @item On x86, you can just try to launch any process by using the native | |
1133 | libraries: | |
1134 | ||
1135 | @example | |
1136 | qemu-i386 -L / /bin/ls | |
1137 | @end example | |
1138 | ||
1139 | @code{-L /} tells that the x86 dynamic linker must be searched with a | |
1140 | @file{/} prefix. | |
1141 | ||
1142 | @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): | |
1143 | ||
1144 | @example | |
1145 | qemu-i386 -L / qemu-i386 -L / /bin/ls | |
1146 | @end example | |
1147 | ||
1148 | @item On non x86 CPUs, you need first to download at least an x86 glibc | |
1149 | (@file{qemu-runtime-i386-XXX-.tar.gz} on the QEMU web page). Ensure that | |
1150 | @code{LD_LIBRARY_PATH} is not set: | |
1151 | ||
1152 | @example | |
1153 | unset LD_LIBRARY_PATH | |
1154 | @end example | |
1155 | ||
1156 | Then you can launch the precompiled @file{ls} x86 executable: | |
1157 | ||
1158 | @example | |
1159 | qemu-i386 tests/i386/ls | |
1160 | @end example | |
1161 | You can look at @file{qemu-binfmt-conf.sh} so that | |
1162 | QEMU is automatically launched by the Linux kernel when you try to | |
1163 | launch x86 executables. It requires the @code{binfmt_misc} module in the | |
1164 | Linux kernel. | |
1165 | ||
1166 | @item The x86 version of QEMU is also included. You can try weird things such as: | |
1167 | @example | |
1168 | qemu-i386 /usr/local/qemu-i386/bin/qemu-i386 /usr/local/qemu-i386/bin/ls-i386 | |
1169 | @end example | |
1170 | ||
1171 | @end itemize | |
1172 | ||
1173 | @section Wine launch | |
1174 | ||
1175 | @itemize | |
1176 | ||
1177 | @item Ensure that you have a working QEMU with the x86 glibc | |
1178 | distribution (see previous section). In order to verify it, you must be | |
1179 | able to do: | |
1180 | ||
1181 | @example | |
1182 | qemu-i386 /usr/local/qemu-i386/bin/ls-i386 | |
1183 | @end example | |
1184 | ||
1185 | @item Download the binary x86 Wine install | |
1186 | (@file{qemu-XXX-i386-wine.tar.gz} on the QEMU web page). | |
1187 | ||
1188 | @item Configure Wine on your account. Look at the provided script | |
1189 | @file{/usr/local/qemu-i386/bin/wine-conf.sh}. Your previous | |
1190 | @code{$@{HOME@}/.wine} directory is saved to @code{$@{HOME@}/.wine.org}. | |
1191 | ||
1192 | @item Then you can try the example @file{putty.exe}: | |
1193 | ||
1194 | @example | |
1195 | qemu-i386 /usr/local/qemu-i386/wine/bin/wine /usr/local/qemu-i386/wine/c/Program\ Files/putty.exe | |
1196 | @end example | |
1197 | ||
1198 | @end itemize | |
1199 | ||
1200 | @section Command line options | |
1201 | ||
1202 | @example | |
1203 | usage: qemu-i386 [-h] [-d] [-L path] [-s size] program [arguments...] | |
1204 | @end example | |
1205 | ||
1206 | @table @option | |
1207 | @item -h | |
1208 | Print the help | |
1209 | @item -L path | |
1210 | Set the x86 elf interpreter prefix (default=/usr/local/qemu-i386) | |
1211 | @item -s size | |
1212 | Set the x86 stack size in bytes (default=524288) | |
1213 | @end table | |
1214 | ||
1215 | Debug options: | |
1216 | ||
1217 | @table @option | |
1218 | @item -d | |
1219 | Activate log (logfile=/tmp/qemu.log) | |
1220 | @item -p pagesize | |
1221 | Act as if the host page size was 'pagesize' bytes | |
1222 | @end table | |
1223 | ||
1224 | @node compilation | |
1225 | @chapter Compilation from the sources | |
1226 | ||
1227 | @section Linux/BSD | |
1228 | ||
1229 | Read the @file{README} which gives the related information. | |
1230 | ||
1231 | @section Windows | |
1232 | ||
1233 | @itemize | |
1234 | @item Install the current versions of MSYS and MinGW from | |
1235 | @url{http://www.mingw.org/}. You can find detailed installation | |
1236 | instructions in the download section and the FAQ. | |
1237 | ||
1238 | @item Download | |
1239 | the MinGW development library of SDL 1.2.x | |
1240 | (@file{SDL-devel-1.2.x-mingw32.tar.gz}) from | |
1241 | @url{http://www.libsdl.org}. Unpack it in a temporary place, and | |
1242 | unpack the archive @file{i386-mingw32msvc.tar.gz} in the MinGW tool | |
1243 | directory. Edit the @file{sdl-config} script so that it gives the | |
1244 | correct SDL directory when invoked. | |
1245 | ||
1246 | @item Extract the current version of QEMU. | |
1247 | ||
1248 | @item Start the MSYS shell (file @file{msys.bat}). | |
1249 | ||
1250 | @item Change to the QEMU directory. Launch @file{./configure} and | |
1251 | @file{make}. If you have problems using SDL, verify that | |
1252 | @file{sdl-config} can be launched from the MSYS command line. | |
1253 | ||
1254 | @item You can install QEMU in @file{Program Files/Qemu} by typing | |
1255 | @file{make install}. Don't forget to copy @file{SDL.dll} in | |
1256 | @file{Program Files/Qemu}. | |
1257 | ||
1258 | @end itemize | |
1259 | ||
1260 | @section Cross compilation for Windows with Linux | |
1261 | ||
1262 | @itemize | |
1263 | @item | |
1264 | Install the MinGW cross compilation tools available at | |
1265 | @url{http://www.mingw.org/}. | |
1266 | ||
1267 | @item | |
1268 | Install the Win32 version of SDL (@url{http://www.libsdl.org}) by | |
1269 | unpacking @file{i386-mingw32msvc.tar.gz}. Set up the PATH environment | |
1270 | variable so that @file{i386-mingw32msvc-sdl-config} can be launched by | |
1271 | the QEMU configuration script. | |
1272 | ||
1273 | @item | |
1274 | Configure QEMU for Windows cross compilation: | |
1275 | @example | |
1276 | ./configure --enable-mingw32 | |
1277 | @end example | |
1278 | If necessary, you can change the cross-prefix according to the prefix | |
1279 | choosen for the MinGW tools with --cross-prefix. You can also use | |
1280 | --prefix to set the Win32 install path. | |
1281 | ||
1282 | @item You can install QEMU in the installation directory by typing | |
1283 | @file{make install}. Don't forget to copy @file{SDL.dll} in the | |
1284 | installation directory. | |
1285 | ||
1286 | @end itemize | |
1287 | ||
1288 | Note: Currently, Wine does not seem able to launch | |
1289 | QEMU for Win32. | |
1290 | ||
1291 | @section Mac OS X | |
1292 | ||
1293 | The Mac OS X patches are not fully merged in QEMU, so you should look | |
1294 | at the QEMU mailing list archive to have all the necessary | |
1295 | information. | |
1296 |