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