~ubuntu-branches/ubuntu/hardy/kvm/hardy-backports : revision 19

1

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html401/loose.dtd">

2

<html>

3

4

<!--

5

Written by: Lionel Cons <Lionel.Cons@cern.ch> (original author)

6

Karl Berry <karl@freefriends.org>

7

Olaf Bachmann <obachman@mathematik.uni-kl.de>

8

and many others.

9

Maintained by: Many creative people.

10

Send bugs and suggestions to <texi2html-bug@nongnu.org>

11

12

-->

13

<head>

14

<title>QEMU Emulator User Documentation</title>

15

16

17

18

19

20

21

22

23

<!--

24

a.summary-letter {text-decoration: none}

25

pre.display {font-family: serif}

26

pre.format {font-family: serif}

27

pre.menu-comment {font-family: serif}

28

pre.menu-preformatted {font-family: serif}

29

pre.smalldisplay {font-family: serif; font-size: smaller}

30

pre.smallexample {font-size: smaller}

31

pre.smallformat {font-family: serif; font-size: smaller}

32

pre.smalllisp {font-size: smaller}

33

span.roman {font-family:serif; font-weight:normal;}

34

span.sansserif {font-family:sans-serif; font-weight:normal;}

35

ul.toc {list-style: none}

36

-->

37

</style>

38

39

40

</head>

41

42

43

44

45

46

47

48

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

49

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

50

51

</tr></table>

52

<h1 class="settitle">QEMU Emulator User Documentation

53

</h1>

54

55

56

<tr><td align="left" valign="top"><a href="#SEC1">1. Introduction</a></td><td>  </td><td align="left" valign="top">

57

</td></tr>

58

<tr><td align="left" valign="top"><a href="#SEC3">2. Installation</a></td><td>  </td><td align="left" valign="top">

59

</td></tr>

60

<tr><td align="left" valign="top"><a href="#SEC7">3. QEMU PC System emulator</a></td><td>  </td><td align="left" valign="top">

61

</td></tr>

62

<tr><td align="left" valign="top"><a href="#SEC58">4. QEMU System emulator for non PC targets</a></td><td>  </td><td align="left" valign="top">

63

</td></tr>

64

<tr><td align="left" valign="top"><a href="#SEC65">5. QEMU User space emulator</a></td><td>  </td><td align="left" valign="top">

65

</td></tr>

66

<tr><td align="left" valign="top"><a href="#SEC76">6. Compilation from the sources</a></td><td>  </td><td align="left" valign="top"></td></tr>

67

<tr><td align="left" valign="top"><a href="#SEC83">7. Index</a></td><td>  </td><td align="left" valign="top">

68

</td></tr>

69

</table>

70

71

72

73

74

75

76

77

78

79

80

81

82

83

84

85

86

87

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

88

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

89

90

</tr></table>

91

<h1 class="chapter"> 1. Introduction </h1>

92

93

94

<tr><td align="left" valign="top"><a href="#SEC2">1.1 Features</a></td><td>  </td><td align="left" valign="top"></td></tr>

95

</table>

96

97

98

99

100

101

102

103

104

105

106

107

108

109

110

111

112

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

113

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

114

115

</tr></table>

116

<h2 class="section"> 1.1 Features </h2>

117

118

<p>QEMU is a FAST! processor emulator using dynamic translation to

119

achieve good emulation speed.

120

</p>

121

<p>QEMU has two operating modes:

122

</p>

123

124

<li>-

125

Full system emulation. In this mode, QEMU emulates a full system (for

126

example a PC), including one or several processors and various

127

peripherals. It can be used to launch different Operating Systems

128

without rebooting the PC or to debug system code.

129

130

</li><li>-

131

User mode emulation. In this mode, QEMU can launch

132

processes compiled for one CPU on another CPU. It can be used to

133

launch the Wine Windows API emulator (<a href="http://www.winehq.org">http://www.winehq.org</a>) or

134

to ease cross-compilation and cross-debugging.

135

136

</li></ul>

137

138

<p>QEMU can run without an host kernel driver and yet gives acceptable

139

performance.

140

</p>

141

<p>For system emulation, the following hardware targets are supported:

142

</p><ul class="toc">

143

<li> PC (x86 or x86_64 processor)

144

</li><li> ISA PC (old style PC without PCI bus)

145

</li><li> PREP (PowerPC processor)

146

</li><li> G3 BW PowerMac (PowerPC processor)

147

</li><li> Mac99 PowerMac (PowerPC processor, in progress)

148

</li><li> Sun4m (32-bit Sparc processor)

149

</li><li> Sun4u (64-bit Sparc processor, in progress)

150

</li><li> Malta board (32-bit MIPS processor)

151

</li><li> ARM Integrator/CP (ARM926E, 1026E or 946E processor)

152

</li><li> ARM Versatile baseboard (ARM926E)

153

</li><li> ARM RealView Emulation baseboard (ARM926EJ-S)

154

</li><li> Spitz, Akita, Borzoi and Terrier PDAs (PXA270 processor)

155

</li><li> Freescale MCF5208EVB (ColdFire V2).

156

</li><li> Arnewsh MCF5206 evaluation board (ColdFire V2).

157

</li></ul>

158

159

<p>For user emulation, x86, PowerPC, ARM, MIPS, Sparc32/64 and ColdFire(m68k) CPUs are supported.

160

</p>

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

177

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

178

179

</tr></table>

180

<h1 class="chapter"> 2. Installation </h1>

181

182

<p>If you want to compile QEMU yourself, see <a href="#SEC76">Compilation from the sources</a>.

183

</p>

184

185

<tr><td align="left" valign="top"><a href="#SEC4">2.1 Linux</a></td><td>  </td><td align="left" valign="top"></td></tr>

186

<tr><td align="left" valign="top"><a href="#SEC5">2.2 Windows</a></td><td>  </td><td align="left" valign="top"></td></tr>

187

<tr><td align="left" valign="top"><a href="#SEC6">2.3 Mac OS X</a></td><td>  </td><td align="left" valign="top"> Macintosh

188

</td></tr>

189

</table>

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

207

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

208

209

</tr></table>

210

<h2 class="section"> 2.1 Linux </h2>

211

212

<p>If a precompiled package is available for your distribution - you just

213

have to install it. Otherwise, see <a href="#SEC76">Compilation from the sources</a>.

214

</p>

215

216

217

218

219

220

221

222

223

224

225

226

227

228

229

230

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

231

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

232

233

</tr></table>

234

<h2 class="section"> 2.2 Windows </h2>

235

236

<p>Download the experimental binary installer at

237

<a href="http://www.free.oszoo.org/download.html">http://www.free.oszoo.org/download.html</a>.

238

</p>

239

240

241

242

243

244

245

246

247

248

249

250

251

252

253

254

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

255

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

256

257

</tr></table>

258

259

260

<p>Download the experimental binary installer at

261

<a href="http://www.free.oszoo.org/download.html">http://www.free.oszoo.org/download.html</a>.

262

</p>

263

264

265

266

267

268

269

270

271

272

273

274

275

276

277

278

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

279

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

280

281

</tr></table>

282

<h1 class="chapter"> 3. QEMU PC System emulator </h1>

283

284

285

<tr><td align="left" valign="top"><a href="#SEC8">3.1 Introduction</a></td><td>  </td><td align="left" valign="top"></td></tr>

286

<tr><td align="left" valign="top"><a href="#SEC9">3.2 Quick Start</a></td><td>  </td><td align="left" valign="top"></td></tr>

287

<tr><td align="left" valign="top"><a href="#SEC10">3.3 Invocation</a></td><td>  </td><td align="left" valign="top"></td></tr>

288

289

<tr><td align="left" valign="top"><a href="#SEC12">3.5 QEMU Monitor</a></td><td>  </td><td align="left" valign="top"></td></tr>

290

<tr><td align="left" valign="top"><a href="#SEC15">3.6 Disk Images</a></td><td>  </td><td align="left" valign="top"></td></tr>

291

<tr><td align="left" valign="top"><a href="#SEC25">3.7 Network emulation</a></td><td>  </td><td align="left" valign="top"></td></tr>

292

<tr><td align="left" valign="top"><a href="#SEC32">3.8 Direct Linux Boot</a></td><td>  </td><td align="left" valign="top"></td></tr>

293

<tr><td align="left" valign="top"><a href="#SEC33">3.9 USB emulation</a></td><td>  </td><td align="left" valign="top"></td></tr>

294

<tr><td align="left" valign="top"><a href="#SEC36">3.10 VNC security</a></td><td>  </td><td align="left" valign="top"></td></tr>

295

<tr><td align="left" valign="top"><a href="#SEC46">3.11 GDB usage</a></td><td>  </td><td align="left" valign="top"></td></tr>

296

<tr><td align="left" valign="top"><a href="#SEC47">3.12 Target OS specific information</a></td><td>  </td><td align="left" valign="top"></td></tr>

297

</table>

298

299

300

301

302

303

304

305

306

307

308

309

310

311

312

313

314

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

315

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

316

317

</tr></table>

318

<h2 class="section"> 3.1 Introduction </h2>

319

320

321

<p>The QEMU PC System emulator simulates the

322

following peripherals:

323

</p>

324

325

<li>-

326

i440FX host PCI bridge and PIIX3 PCI to ISA bridge

327

</li><li>-

328

Cirrus CLGD 5446 PCI VGA card or dummy VGA card with Bochs VESA

329

extensions (hardware level, including all non standard modes).

330

</li><li>-

331

PS/2 mouse and keyboard

332

</li><li>-

333

2 PCI IDE interfaces with hard disk and CD-ROM support

334

</li><li>-

335

Floppy disk

336

</li><li>-

337

PCI/ISA PCI network adapters

338

</li><li>-

339

Serial ports

340

</li><li>-

341

Creative SoundBlaster 16 sound card

342

</li><li>-

343

ENSONIQ AudioPCI ES1370 sound card

344

</li><li>-

345

Adlib(OPL2) - Yamaha YM3812 compatible chip

346

</li><li>-

347

PCI UHCI USB controller and a virtual USB hub.

348

</li></ul>

349

350

<p>SMP is supported with up to 255 CPUs.

351

</p>

352

<p>Note that adlib is only available when QEMU was configured with

353

-enable-adlib

354

</p>

355

<p>QEMU uses the PC BIOS from the Bochs project and the Plex86/Bochs LGPL

356

VGA BIOS.

357

</p>

358

<p>QEMU uses YM3812 emulation by Tatsuyuki Satoh.

359

</p>

360

361

362

363

364

365

366

367

368

369

370

371

372

373

374

375

376

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

377

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

378

379

</tr></table>

380

<h2 class="section"> 3.2 Quick Start </h2>

381

382

<p>Download and uncompress the linux image (‘<tt>linux.img</tt>’) and type:

383

</p>

384

<table><tr><td> </td><td><pre class="example">qemu linux.img

385

</pre></td></tr></table>

386

387

<p>Linux should boot and give you a prompt.

388

</p>

389

390

391

392

393

394

395

396

397

398

399

400

401

402

403

404

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

405

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

406

407

</tr></table>

408

<h2 class="section"> 3.3 Invocation </h2>

409

410

<table><tr><td> </td><td><pre class="example">usage: qemu [options] [disk_image]

411

</pre></td></tr></table>

412

413

<p><var>disk_image</var> is a raw hard disk image for IDE hard disk 0.

414

</p>

415

<p>General options:

416

</p><dl compact="compact">

417

<dt> ‘<samp>-M machine</samp>’</dt>

418

<dd><p>Select the emulated machine (<code>-M ?</code> for list)

419

</p>

420

</dd>

421

422

423

<dd><p>Use <var>file</var> as floppy disk 0/1 image (see section <a href="#SEC15">Disk Images</a>). You can

424

use the host floppy by using ‘<tt>/dev/fd0</tt>’ as filename (see section <a href="#SEC20">Using host drives</a>).

425

</p>

426

</dd>

427

428

429

430

431

<dd><p>Use <var>file</var> as hard disk 0, 1, 2 or 3 image (see section <a href="#SEC15">Disk Images</a>).

432

</p>

433

</dd>

434

<dt> ‘<samp>-cdrom file</samp>’</dt>

435

<dd><p>Use <var>file</var> as CD-ROM image (you cannot use ‘<samp>-hdc</samp>’ and and

436

‘<samp>-cdrom</samp>’ at the same time). You can use the host CD-ROM by

437

using ‘<tt>/dev/cdrom</tt>’ as filename (see section <a href="#SEC20">Using host drives</a>).

438

</p>

439

</dd>

440

441

<dd><p>Boot on floppy (a), hard disk (c), CD-ROM (d), or Etherboot (n). Hard disk boot

442

is the default.

443

</p>

444

</dd>

445

<dt> ‘<samp>-snapshot</samp>’</dt>

446

<dd><p>Write to temporary files instead of disk image files. In this case,

447

the raw disk image you use is not written back. You can however force

448

the write back by pressing <C-a s> (see section <a href="#SEC15">Disk Images</a>).

449

</p>

450

</dd>

451

<dt> ‘<samp>-no-fd-bootchk</samp>’</dt>

452

<dd><p>Disable boot signature checking for floppy disks in Bochs BIOS. It may

453

be needed to boot from old floppy disks.

454

</p>

455

</dd>

456

457

<dd><p>Set virtual RAM size to <var>megs</var> megabytes. Default is 128 MB.

458

</p>

459

</dd>

460

461

<dd><p>Simulate an SMP system with <var>n</var> CPUs. On the PC target, up to 255

462

CPUs are supported.

463

</p>

464

</dd>

465

<dt> ‘<samp>-audio-help</samp>’</dt>

466

<dd>

467

<p>Will show the audio subsystem help: list of drivers, tunable

468

parameters.

469

</p>

470

</dd>

471

<dt> ‘<samp>-soundhw card1,card2,... or -soundhw all</samp>’</dt>

472

<dd>

473

<p>Enable audio and selected sound hardware. Use ? to print all

474

available sound hardware.

475

</p>

476

<table><tr><td> </td><td><pre class="example">qemu -soundhw sb16,adlib hda

477

qemu -soundhw es1370 hda

478

qemu -soundhw all hda

479

qemu -soundhw ?

480

</pre></td></tr></table>

481

482

</dd>

483

<dt> ‘<samp>-localtime</samp>’</dt>

484

<dd><p>Set the real time clock to local time (the default is to UTC

485

time). This option is needed to have correct date in MS-DOS or

486

Windows.

487

</p>

488

</dd>

489

<dt> ‘<samp>-pidfile file</samp>’</dt>

490

<dd><p>Store the QEMU process PID in <var>file</var>. It is useful if you launch QEMU

491

from a script.

492

</p>

493

</dd>

494

<dt> ‘<samp>-daemonize</samp>’</dt>

495

<dd><p>Daemonize the QEMU process after initialization. QEMU will not detach from

496

standard IO until it is ready to receive connections on any of its devices.

497

This option is a useful way for external programs to launch QEMU without having

498

to cope with initialization race conditions.

499

</p>

500

</dd>

501

502

<dd><p>Use it when installing Windows 2000 to avoid a disk full bug. After

503

Windows 2000 is installed, you no longer need this option (this option

504

slows down the IDE transfers).

505

</p>

506

</dd>

507

<dt> ‘<samp>-option-rom file</samp>’</dt>

508

<dd><p>Load the contents of file as an option ROM. This option is useful to load

509

things like EtherBoot.

510

</p>

511

</dd>

512

<dt> ‘<samp>-name string</samp>’</dt>

513

<dd><p>Sets the name of the guest. This name will be display in the SDL window

514

caption. The name will also be used for the VNC server.

515

</p>

516

</dd>

517

</dl>

518

519

<p>Display options:

520

</p><dl compact="compact">

521

<dt> ‘<samp>-nographic</samp>’</dt>

522

<dd>

523

<p>Normally, QEMU uses SDL to display the VGA output. With this option,

524

you can totally disable graphical output so that QEMU is a simple

525

command line application. The emulated serial port is redirected on

526

the console. Therefore, you can still use QEMU to debug a Linux kernel

527

with a serial console.

528

</p>

529

</dd>

530

<dt> ‘<samp>-no-frame</samp>’</dt>

531

<dd>

532

<p>Do not use decorations for SDL windows and start them using the whole

533

available screen space. This makes the using QEMU in a dedicated desktop

534

workspace more convenient.

535

</p>

536

</dd>

537

<dt> ‘<samp>-full-screen</samp>’</dt>

538

<dd><p>Start in full screen.

539

</p>

540

</dd>

541

<dt> ‘<samp>-vnc display[,option[,option[,...]]]</samp>’</dt>

542

<dd>

543

<p>Normally, QEMU uses SDL to display the VGA output. With this option,

544

you can have QEMU listen on VNC display <var>display</var> and redirect the VGA

545

display over the VNC session. It is very useful to enable the usb

546

tablet device when using this option (option ‘<samp>-usbdevice

547

tablet</samp>’). When using the VNC display, you must use the ‘<samp>-k</samp>’

548

parameter to set the keyboard layout if you are not using en-us. Valid

549

syntax for the <var>display</var> is

550

</p>

551

552

<dt> <code><var>interface:d</var></code></dt>

553

<dd>

554

<p>TCP connections will only be allowed from <var>interface</var> on display <var>d</var>.

555

By convention the TCP port is 5900+<var>d</var>. Optionally, <var>interface</var> can

556

be omitted in which case the server will bind to all interfaces.

557

</p>

558

</dd>

559

560

<dd>

561

<p>Connections will be allowed over UNIX domain sockets where <var>path</var> is the

562

location of a unix socket to listen for connections on.

563

</p>

564

</dd>

565

566

<dd>

567

<p>VNC is initialized by not started. The monitor <code>change</code> command can be used

568

to later start the VNC server.

569

</p>

570

</dd>

571

</dl>

572

573

<p>Following the <var>display</var> value there may be one or more <var>option</var> flags

574

separated by commas. Valid options are

575

</p>

576

577

<dt> <code><var>password</var></code></dt>

578

<dd>

579

<p>Require that password based authentication is used for client connections.

580

The password must be set separately using the <code>change</code> command in the

581

<a href="#SEC12">QEMU Monitor</a>

582

</p>

583

</dd>

584

585

<dd>

586

<p>Require that client use TLS when communicating with the VNC server. This

587

uses anonymous TLS credentials so is susceptible to a man-in-the-middle

588

attack. It is recommended that this option be combined with either the

589

<var>x509</var> or <var>x509verify</var> options.

590

</p>

591

</dd>

592

<dt> <code><var>x509=/path/to/certificate/dir</var></code></dt>

593

<dd>

594

<p>Valid if <var>tls</var> is specified. Require that x509 credentials are used

595

for negotiating the TLS session. The server will send its x509 certificate

596

to the client. It is recommended that a password be set on the VNC server

597

to provide authentication of the client when this is used. The path following

598

this option specifies where the x509 certificates are to be loaded from.

599

See the <a href="#SEC36">VNC security</a> section for details on generating certificates.

600

</p>

601

</dd>

602

<dt> <code><var>x509verify=/path/to/certificate/dir</var></code></dt>

603

<dd>

604

<p>Valid if <var>tls</var> is specified. Require that x509 credentials are used

605

for negotiating the TLS session. The server will send its x509 certificate

606

to the client, and request that the client send its own x509 certificate.

607

The server will validate the client's certificate against the CA certificate,

608

and reject clients when validation fails. If the certificate authority is

609

trusted, this is a sufficient authentication mechanism. You may still wish

610

to set a password on the VNC server as a second authentication layer. The

611

path following this option specifies where the x509 certificates are to

612

be loaded from. See the <a href="#SEC36">VNC security</a> section for details on generating

613

certificates.

614

</p>

615

</dd>

616

</dl>

617

618

</dd>

619

<dt> ‘<samp>-k language</samp>’</dt>

620

<dd>

621

<p>Use keyboard layout <var>language</var> (for example <code>fr</code> for

622

French). This option is only needed where it is not easy to get raw PC

623

keycodes (e.g. on Macs, with some X11 servers or with a VNC

624

display). You don't normally need to use it on PC/Linux or PC/Windows

625

hosts.

626

</p>

627

<p>The available layouts are:

628

</p><table><tr><td> </td><td><pre class="example">ar de-ch es fo fr-ca hu ja mk no pt-br sv

629

da en-gb et fr fr-ch is lt nl pl ru th

630

de en-us fi fr-be hr it lv nl-be pt sl tr

631

</pre></td></tr></table>

632

633

<p>The default is <code>en-us</code>.

634

</p>

635

</dd>

636

</dl>

637

638

<p>USB options:

639

</p><dl compact="compact">

640

641

<dd><p>Enable the USB driver (will be the default soon)

642

</p>

643

</dd>

644

<dt> ‘<samp>-usbdevice devname</samp>’</dt>

645

<dd><p>Add the USB device <var>devname</var>. See section <a href="#SEC34">Connecting USB devices</a>.

646

</p></dd>

647

</dl>

648

649

<p>Network options:

650

</p>

651

652

<dt> ‘<samp>-net nic[,vlan=n][,macaddr=addr][,model=type]</samp>’</dt>

653

<dd><p>Create a new Network Interface Card and connect it to VLAN <var>n</var> (<var>n</var>

654

= 0 is the default). The NIC is an ne2k_pci by default on the PC

655

target. Optionally, the MAC address can be changed. If no

656

‘<samp>-net</samp>’ option is specified, a single NIC is created.

657

Qemu can emulate several different models of network card.

658

Valid values for <var>type</var> are

659

<code>i82551</code>, <code>i82557b</code>, <code>i82559er</code>,

660

<code>ne2k_pci</code>, <code>ne2k_isa</code>, <code>pcnet</code>, <code>rtl8139</code>,

661

<code>smc91c111</code>, <code>lance</code> and <code>mcf_fec</code>.

662

Not all devices are supported on all targets. Use -net nic,model=?

663

for a list of available devices for your target.

664

</p>

665

</dd>

666

<dt> ‘<samp>-net user[,vlan=n][,hostname=name]</samp>’</dt>

667

<dd><p>Use the user mode network stack which requires no administrator

668

privilege to run. ‘<samp>hostname=name</samp>’ can be used to specify the client

669

hostname reported by the builtin DHCP server.

670

</p>

671

</dd>

672

<dt> ‘<samp>-net tap[,vlan=n][,fd=h][,ifname=name][,script=file]</samp>’</dt>

673

<dd><p>Connect the host TAP network interface <var>name</var> to VLAN <var>n</var> and

674

use the network script <var>file</var> to configure it. The default

675

network script is ‘<tt>/etc/qemu-ifup</tt>’. Use ‘<samp>script=no</samp>’ to

676

disable script execution. If <var>name</var> is not

677

provided, the OS automatically provides one. ‘<samp>fd=h</samp>’ can be

678

used to specify the handle of an already opened host TAP interface. Example:

679

</p>

680

<table><tr><td> </td><td><pre class="example">qemu linux.img -net nic -net tap

681

</pre></td></tr></table>

682

683

<p>More complicated example (two NICs, each one connected to a TAP device)

684

</p><table><tr><td> </td><td><pre class="example">qemu linux.img -net nic,vlan=0 -net tap,vlan=0,ifname=tap0 \

685

-net nic,vlan=1 -net tap,vlan=1,ifname=tap1

686

</pre></td></tr></table>

687

688

689

</dd>

690

<dt> ‘<samp>-net socket[,vlan=n][,fd=h][,listen=[host]:port][,connect=host:port]</samp>’</dt>

691

<dd>

692

<p>Connect the VLAN <var>n</var> to a remote VLAN in another QEMU virtual

693

machine using a TCP socket connection. If ‘<samp>listen</samp>’ is

694

specified, QEMU waits for incoming connections on <var>port</var>

695

(<var>host</var> is optional). ‘<samp>connect</samp>’ is used to connect to

696

another QEMU instance using the ‘<samp>listen</samp>’ option. ‘<samp>fd=h</samp>’

697

specifies an already opened TCP socket.

698

</p>

699

<p>Example:

700

</p><table><tr><td> </td><td><pre class="example"># launch a first QEMU instance

701

qemu linux.img -net nic,macaddr=52:54:00:12:34:56 \

702

-net socket,listen=:1234

703

# connect the VLAN 0 of this instance to the VLAN 0

704

# of the first instance

705

qemu linux.img -net nic,macaddr=52:54:00:12:34:57 \

706

-net socket,connect=127.0.0.1:1234

707

</pre></td></tr></table>

708

709

</dd>

710

<dt> ‘<samp>-net socket[,vlan=n][,fd=h][,mcast=maddr:port]</samp>’</dt>

711

<dd>

712

<p>Create a VLAN <var>n</var> shared with another QEMU virtual

713

machines using a UDP multicast socket, effectively making a bus for

714

every QEMU with same multicast address <var>maddr</var> and <var>port</var>.

715

NOTES:

716

</p><ol>

717

<li>

718

Several QEMU can be running on different hosts and share same bus (assuming

719

correct multicast setup for these hosts).

720

</li><li>

721

mcast support is compatible with User Mode Linux (argument ‘<samp>eth<var>N</var>=mcast</samp>’), see

722

<a href="http://user-mode-linux.sf.net">http://user-mode-linux.sf.net</a>.

723

</li><li>

724

Use ‘<samp>fd=h</samp>’ to specify an already opened UDP multicast socket.

725

</li></ol>

726

727

<p>Example:

728

</p><table><tr><td> </td><td><pre class="example"># launch one QEMU instance

729

qemu linux.img -net nic,macaddr=52:54:00:12:34:56 \

730

-net socket,mcast=230.0.0.1:1234

731

# launch another QEMU instance on same "bus"

732

qemu linux.img -net nic,macaddr=52:54:00:12:34:57 \

733

-net socket,mcast=230.0.0.1:1234

734

# launch yet another QEMU instance on same "bus"

735

qemu linux.img -net nic,macaddr=52:54:00:12:34:58 \

736

-net socket,mcast=230.0.0.1:1234

737

</pre></td></tr></table>

738

739

<p>Example (User Mode Linux compat.):

740

</p><table><tr><td> </td><td><pre class="example"># launch QEMU instance (note mcast address selected

741

# is UML's default)

742

qemu linux.img -net nic,macaddr=52:54:00:12:34:56 \

743

-net socket,mcast=239.192.168.1:1102

744

# launch UML

745

/path/to/linux ubd0=/path/to/root_fs eth0=mcast

746

</pre></td></tr></table>

747

748

</dd>

749

750

<dd><p>Indicate that no network devices should be configured. It is used to

751

override the default configuration (‘<samp>-net nic -net user</samp>’) which

752

is activated if no ‘<samp>-net</samp>’ options are provided.

753

</p>

754

</dd>

755

756

<dd><p>When using the user mode network stack, activate a built-in TFTP

757

server. The files in <var>dir</var> will be exposed as the root of a TFTP server.

758

The TFTP client on the guest must be configured in binary mode (use the command

759

<code>bin</code> of the Unix TFTP client). The host IP address on the guest is as

760

usual 10.0.2.2.

761

</p>

762

</dd>

763

<dt> ‘<samp>-bootp file</samp>’</dt>

764

<dd><p>When using the user mode network stack, broadcast <var>file</var> as the BOOTP

765

filename. In conjunction with ‘<samp>-tftp</samp>’, this can be used to network boot

766

a guest from a local directory.

767

</p>

768

<p>Example (using pxelinux):

769

</p><table><tr><td> </td><td><pre class="example">qemu -hda linux.img -boot n -tftp /path/to/tftp/files -bootp /pxelinux.0

770

</pre></td></tr></table>

771

772

</dd>

773

774

<dd><p>When using the user mode network stack, activate a built-in SMB

775

server so that Windows OSes can access to the host files in ‘<tt>dir</tt>’

776

transparently.

777

</p>

778

<p>In the guest Windows OS, the line:

779

</p><table><tr><td> </td><td><pre class="example">10.0.2.4 smbserver

780

</pre></td></tr></table>

781

<p>must be added in the file ‘<tt>C:\WINDOWS\LMHOSTS</tt>’ (for windows 9x/Me)

782

or ‘<tt>C:\WINNT\SYSTEM32\DRIVERS\ETC\LMHOSTS</tt>’ (Windows NT/2000).

783

</p>

784

<p>Then ‘<tt>dir</tt>’ can be accessed in ‘<tt>\\smbserver\qemu</tt>’.

785

</p>

786

<p>Note that a SAMBA server must be installed on the host OS in

787

‘<tt>/usr/sbin/smbd</tt>’. QEMU was tested successfully with smbd version

788

2.2.7a from the Red Hat 9 and version 3.0.10-1.fc3 from Fedora Core 3.

789

</p>

790

</dd>

791

<dt> ‘<samp>-redir [tcp|udp]:host-port:[guest-host]:guest-port</samp>’</dt>

792

<dd>

793

<p>When using the user mode network stack, redirect incoming TCP or UDP

794

connections to the host port <var>host-port</var> to the guest

795

<var>guest-host</var> on guest port <var>guest-port</var>. If <var>guest-host</var>

796

is not specified, its value is 10.0.2.15 (default address given by the

797

built-in DHCP server).

798

</p>

799

<p>For example, to redirect host X11 connection from screen 1 to guest

800

screen 0, use the following:

801

</p>

802

<table><tr><td> </td><td><pre class="example"># on the host

803

qemu -redir tcp:6001::6000 [...]

804

# this host xterm should open in the guest X11 server

805

xterm -display :1

806

</pre></td></tr></table>

807

808

<p>To redirect telnet connections from host port 5555 to telnet port on

809

the guest, use the following:

810

</p>

811

<table><tr><td> </td><td><pre class="example"># on the host

812

qemu -redir tcp:5555::23 [...]

813

telnet localhost 5555

814

</pre></td></tr></table>

815

816

<p>Then when you use on the host <code>telnet localhost 5555</code>, you

817

connect to the guest telnet server.

818

</p>

819

</dd>

820

</dl>

821

822

<p>Linux boot specific: When using these options, you can use a given

823

Linux kernel without installing it in the disk image. It can be useful

824

for easier testing of various kernels.

825

</p>

826

827

<dt> ‘<samp>-kernel bzImage</samp>’</dt>

828

<dd><p>Use <var>bzImage</var> as kernel image.

829

</p>

830

</dd>

831

<dt> ‘<samp>-append cmdline</samp>’</dt>

832

<dd><p>Use <var>cmdline</var> as kernel command line

833

</p>

834

</dd>

835

<dt> ‘<samp>-initrd file</samp>’</dt>

836

<dd><p>Use <var>file</var> as initial ram disk.

837

</p>

838

</dd>

839

</dl>

840

841

<p>Debug/Expert options:

842

</p><dl compact="compact">

843

<dt> ‘<samp>-serial dev</samp>’</dt>

844

<dd><p>Redirect the virtual serial port to host character device

845

<var>dev</var>. The default device is <code>vc</code> in graphical mode and

846

<code>stdio</code> in non graphical mode.

847

</p>

848

<p>This option can be used several times to simulate up to 4 serials

849

ports.

850

</p>

851

<p>Use <code>-serial none</code> to disable all serial ports.

852

</p>

853

<p>Available character devices are:

854

</p><dl compact="compact">

855

856

<dd><p>Virtual console. Optionally, a width and height can be given in pixel with

857

</p><table><tr><td> </td><td><pre class="example">vc:800x600

858

</pre></td></tr></table>

859

<p>It is also possible to specify width or height in characters:

860

</p><table><tr><td> </td><td><pre class="example">vc:80Cx24C

861

</pre></td></tr></table>

862

</dd>

863

864

<dd><p>[Linux only] Pseudo TTY (a new PTY is automatically allocated)

865

</p></dd>

866

867

<dd><p>No device is allocated.

868

</p></dd>

869

870

<dd><p>void device

871

</p></dd>

872

873

<dd><p>[Linux only] Use host tty, e.g. ‘<tt>/dev/ttyS0</tt>’. The host serial port

874

parameters are set according to the emulated ones.

875

</p></dd>

876

<dt> <code>/dev/parportN</code></dt>

877

<dd><p>[Linux only, parallel port only] Use host parallel port

878

<var>N</var>. Currently SPP and EPP parallel port features can be used.

879

</p></dd>

880

<dt> <code>file:filename</code></dt>

881

<dd><p>Write output to filename. No character can be read.

882

</p></dd>

883

<dt> <code>stdio</code></dt>

884

<dd><p>[Unix only] standard input/output

885

</p></dd>

886

<dt> <code>pipe:filename</code></dt>

887

<dd><p>name pipe <var>filename</var>

888

</p></dd>

889

890

<dd><p>[Windows only] Use host serial port <var>n</var>

891

</p></dd>

892

<dt> <code>udp:[remote_host]:remote_port[@[src_ip]:src_port]</code></dt>

893

<dd><p>This implements UDP Net Console. When <var>remote_host</var> or <var>src_ip</var> are not specified they default to <code>0.0.0.0</code>. When not using a specified <var>src_port</var> a random port is automatically chosen.

894

</p>

895

<p>If you just want a simple readonly console you can use <code>netcat</code> or

896

<code>nc</code>, by starting qemu with: <code>-serial udp::4555</code> and nc as:

897

<code>nc -u -l -p 4555</code>. Any time qemu writes something to that port it

898

will appear in the netconsole session.

899

</p>

900

<p>If you plan to send characters back via netconsole or you want to stop

901

and start qemu a lot of times, you should have qemu use the same

902

source port each time by using something like <code>-serial

903

udp::4555@:4556</code> to qemu. Another approach is to use a patched

904

version of netcat which can listen to a TCP port and send and receive

905

characters via udp. If you have a patched version of netcat which

906

activates telnet remote echo and single char transfer, then you can

907

use the following options to step up a netcat redirector to allow

908

telnet on port 5555 to access the qemu port.

909

</p><dl compact="compact">

910

<dt> <code>Qemu Options:</code></dt>

911

<dd><p>-serial udp::4555@:4556

912

</p></dd>

913

<dt> <code>netcat options:</code></dt>

914

<dd><p>-u -P 4555 -L 0.0.0.0:4556 -t -p 5555 -I -T

915

</p></dd>

916

<dt> <code>telnet options:</code></dt>

917

<dd><p>localhost 5555

918

</p></dd>

919

</dl>

920

921

922

</dd>

923

<dt> <code>tcp:[host]:port[,server][,nowait][,nodelay]</code></dt>

924

<dd><p>The TCP Net Console has two modes of operation. It can send the serial

925

I/O to a location or wait for a connection from a location. By default

926

the TCP Net Console is sent to <var>host</var> at the <var>port</var>. If you use

927

the <var>server</var> option QEMU will wait for a client socket application

928

to connect to the port before continuing, unless the <code>nowait</code>

929

option was specified. The <code>nodelay</code> option disables the Nagle buffering

930

algorithm. If <var>host</var> is omitted, 0.0.0.0 is assumed. Only

931

one TCP connection at a time is accepted. You can use <code>telnet</code> to

932

connect to the corresponding character device.

933

</p><dl compact="compact">

934

<dt> <code>Example to send tcp console to 192.168.0.2 port 4444</code></dt>

935

<dd><p>-serial tcp:192.168.0.2:4444

936

</p></dd>

937

<dt> <code>Example to listen and wait on port 4444 for connection</code></dt>

938

<dd><p>-serial tcp::4444,server

939

</p></dd>

940

<dt> <code>Example to not wait and listen on ip 192.168.0.100 port 4444</code></dt>

941

<dd><p>-serial tcp:192.168.0.100:4444,server,nowait

942

</p></dd>

943

</dl>

944

945

</dd>

946

<dt> <code>telnet:host:port[,server][,nowait][,nodelay]</code></dt>

947

<dd><p>The telnet protocol is used instead of raw tcp sockets. The options

948

work the same as if you had specified <code>-serial tcp</code>. The

949

difference is that the port acts like a telnet server or client using

950

telnet option negotiation. This will also allow you to send the

951

MAGIC_SYSRQ sequence if you use a telnet that supports sending the break

952

sequence. Typically in unix telnet you do it with Control-] and then

953

type "send break" followed by pressing the enter key.

954

</p>

955

</dd>

956

<dt> <code>unix:path[,server][,nowait]</code></dt>

957

<dd><p>A unix domain socket is used instead of a tcp socket. The option works the

958

same as if you had specified <code>-serial tcp</code> except the unix domain socket

959

<var>path</var> is used for connections.

960

</p>

961

</dd>

962

<dt> <code>mon:dev_string</code></dt>

963

<dd><p>This is a special option to allow the monitor to be multiplexed onto

964

another serial port. The monitor is accessed with key sequence of

965

<Control-a> and then pressing <c>. See monitor access

966

<a href="#SEC11">Keys</a> in the -nographic section for more keys.

967

<var>dev_string</var> should be any one of the serial devices specified

968

above. An example to multiplex the monitor onto a telnet server

969

listening on port 4444 would be:

970

</p><dl compact="compact">

971

<dt> <code>-serial mon:telnet::4444,server,nowait</code></dt>

972

</dl>

973

974

</dd>

975

</dl>

976

977

</dd>

978

<dt> ‘<samp>-parallel dev</samp>’</dt>

979

<dd><p>Redirect the virtual parallel port to host device <var>dev</var> (same

980

devices as the serial port). On Linux hosts, ‘<tt>/dev/parportN</tt>’ can

981

be used to use hardware devices connected on the corresponding host

982

parallel port.

983

</p>

984

<p>This option can be used several times to simulate up to 3 parallel

985

ports.

986

</p>

987

<p>Use <code>-parallel none</code> to disable all parallel ports.

988

</p>

989

</dd>

990

<dt> ‘<samp>-monitor dev</samp>’</dt>

991

<dd><p>Redirect the monitor to host device <var>dev</var> (same devices as the

992

serial port).

993

The default device is <code>vc</code> in graphical mode and <code>stdio</code> in

994

non graphical mode.

995

</p>

996

</dd>

997

<dt> ‘<samp>-echr numeric_ascii_value</samp>’</dt>

998

<dd><p>Change the escape character used for switching to the monitor when using

999

monitor and serial sharing. The default is <code>0x01</code> when using the

1000

<code>-nographic</code> option. <code>0x01</code> is equal to pressing

1001

<code>Control-a</code>. You can select a different character from the ascii

1002

control keys where 1 through 26 map to Control-a through Control-z. For

1003

instance you could use the either of the following to change the escape

1004

character to Control-t.

1005

</p><dl compact="compact">

1006

1007

1008

</dl>

1009

1010

</dd>

1011

1012

<dd><p>Wait gdb connection to port 1234 (see section <a href="#SEC46">GDB usage</a>).

1013

</p></dd>

1014

1015

<dd><p>Change gdb connection port. <var>port</var> can be either a decimal number

1016

to specify a TCP port, or a host device (same devices as the serial port).

1017

</p></dd>

1018

1019

<dd><p>Do not start CPU at startup (you must type 'c' in the monitor).

1020

</p></dd>

1021

1022

<dd><p>Output log in /tmp/qemu.log

1023

</p></dd>

1024

<dt> ‘<samp>-hdachs c,h,s,[,t]</samp>’</dt>

1025

<dd><p>Force hard disk 0 physical geometry (1 <= <var>c</var> <= 16383, 1 <=

1026

<var>h</var> <= 16, 1 <= <var>s</var> <= 63) and optionally force the BIOS

1027

translation mode (<var>t</var>=none, lba or auto). Usually QEMU can guess

1028

all those parameters. This option is useful for old MS-DOS disk

1029

images.

1030

</p>

1031

</dd>

1032

1033

<dd><p>Set the directory for the BIOS, VGA BIOS and keymaps.

1034

</p>

1035

</dd>

1036

1037

<dd><p>Simulate a standard VGA card with Bochs VBE extensions (default is

1038

Cirrus Logic GD5446 PCI VGA). If your guest OS supports the VESA 2.0

1039

VBE extensions (e.g. Windows XP) and if you want to use high

1040

resolution modes (>= 1280x1024x16) then you should use this option.

1041

</p>

1042

</dd>

1043

1044

<dd><p>Disable ACPI (Advanced Configuration and Power Interface) support. Use

1045

it if your guest OS complains about ACPI problems (PC target machine

1046

only).

1047

</p>

1048

</dd>

1049

<dt> ‘<samp>-no-reboot</samp>’</dt>

1050

<dd><p>Exit instead of rebooting.

1051

</p>

1052

</dd>

1053

<dt> ‘<samp>-loadvm file</samp>’</dt>

1054

<dd><p>Start right away with a saved state (<code>loadvm</code> in monitor)

1055

</p>

1056

</dd>

1057

<dt> ‘<samp>-semihosting</samp>’</dt>

1058

<dd><p>Enable semihosting syscall emulation (ARM and M68K target machines only).

1059

</p>

1060

<p>On ARM this implements the "Angel" interface.

1061

On M68K this implements the "ColdFire GDB" interface used by libgloss.

1062

</p>

1063

<p>Note that this allows guest direct access to the host filesystem,

1064

so should only be used with trusted guest OS.

1065

</p></dd>

1066

</dl>

1067

1068

1069

1070

1071

1072

1073

1074

1075

1076

1077

1078

1079

1080

1081

1082

1083

1084

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

1085

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

1086

1087

</tr></table>

1088

1089

1090

1091

<p>During the graphical emulation, you can use the following keys:

1092

</p><dl compact="compact">

1093

1094

<dd><p>Toggle full screen

1095

</p>

1096

</dd>

1097

1098

<dd><p>Switch to virtual console 'n'. Standard console mappings are:

1099

</p><dl compact="compact">

1100

1101

<dd><p>Target system display

1102

</p></dd>

1103

1104

<dd><p>Monitor

1105

</p></dd>

1106

1107

<dd><p>Serial port

1108

</p></dd>

1109

</dl>

1110

1111

</dd>

1112

1113

<dd><p>Toggle mouse and keyboard grab.

1114

</p></dd>

1115

</dl>

1116

1117

<p>In the virtual consoles, you can use <Ctrl-Up>, <Ctrl-Down>,

1118

<Ctrl-PageUp> and <Ctrl-PageDown> to move in the back log.

1119

</p>

1120

<p>During emulation, if you are using the ‘<samp>-nographic</samp>’ option, use

1121

<Ctrl-a h> to get terminal commands:

1122

</p>

1123

1124

1125

<dd><p>Print this help

1126

</p></dd>

1127

1128

<dd><p>Exit emulator

1129

</p></dd>

1130

1131

<dd><p>Save disk data back to file (if -snapshot)

1132

</p></dd>

1133

1134

<dd><p>toggle console timestamps

1135

</p></dd>

1136

1137

<dd><p>Send break (magic sysrq in Linux)

1138

</p></dd>

1139

1140

<dd><p>Switch between console and monitor

1141

</p></dd>

1142

1143

<dd><p>Send Ctrl-a

1144

</p></dd>

1145

</dl>

1146

1147

1148

1149

1150

1151

1152

1153

1154

1155

1156

1157

1158

1159

1160

1161

1162

1163

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

1164

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

1165

1166

</tr></table>

1167

<h2 class="section"> 3.5 QEMU Monitor </h2>

1168

1169

<p>The QEMU monitor is used to give complex commands to the QEMU

1170

emulator. You can use it to:

1171

</p>

1172

1173

<li>-

1174

Remove or insert removable media images

1175

(such as CD-ROM or floppies)

1176

1177

</li><li>-

1178

Freeze/unfreeze the Virtual Machine (VM) and save or restore its state

1179

from a disk file.

1180

1181

</li><li>- Inspect the VM state without an external debugger.

1182

1183

</li></ul>

1184

1185

1186

1187

1188

1189

1190

1191

1192

1193

1194

1195

1196

1197

1198

1199

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

1200

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

1201

1202

</tr></table>

1203

<h3 class="subsection"> 3.5.1 Commands </h3>

1204

1205

<p>The following commands are available:

1206

</p>

1207

1208

1209

<dd><p>Show the help for all commands or just for command <var>cmd</var>.

1210

</p>

1211

</dd>

1212

<dt> ‘<samp>commit</samp>’</dt>

1213

<dd><p>Commit changes to the disk images (if -snapshot is used)

1214

</p>

1215

</dd>

1216

<dt> ‘<samp>info subcommand</samp>’</dt>

1217

<dd><p>show various information about the system state

1218

</p>

1219

1220

<dt> ‘<samp>info network</samp>’</dt>

1221

<dd><p>show the various VLANs and the associated devices

1222

</p></dd>

1223

<dt> ‘<samp>info block</samp>’</dt>

1224

<dd><p>show the block devices

1225

</p></dd>

1226

<dt> ‘<samp>info registers</samp>’</dt>

1227

<dd><p>show the cpu registers

1228

</p></dd>

1229

<dt> ‘<samp>info history</samp>’</dt>

1230

<dd><p>show the command line history

1231

</p></dd>

1232

1233

<dd><p>show emulated PCI device

1234

</p></dd>

1235

1236

<dd><p>show USB devices plugged on the virtual USB hub

1237

</p></dd>

1238

<dt> ‘<samp>info usbhost</samp>’</dt>

1239

<dd><p>show all USB host devices

1240

</p></dd>

1241

<dt> ‘<samp>info capture</samp>’</dt>

1242

<dd><p>show information about active capturing

1243

</p></dd>

1244

<dt> ‘<samp>info snapshots</samp>’</dt>

1245

<dd><p>show list of VM snapshots

1246

</p></dd>

1247

1248

<dd><p>show which guest mouse is receiving events

1249

</p></dd>

1250

</dl>

1251

1252

</dd>

1253

1254

<dd><p>Quit the emulator.

1255

</p>

1256

</dd>

1257

<dt> ‘<samp>eject [-f] device</samp>’</dt>

1258

<dd><p>Eject a removable medium (use -f to force it).

1259

</p>

1260

</dd>

1261

<dt> ‘<samp>change device setting</samp>’</dt>

1262

<dd>

1263

<p>Change the configuration of a device

1264

</p>

1265

1266

<dt> ‘<samp>change <var>diskdevice</var> <var>filename</var></samp>’</dt>

1267

<dd><p>Change the medium for a removable disk device to point to <var>filename</var>. eg

1268

</p>

1269

<table><tr><td> </td><td><pre class="example">(qemu) change cdrom /path/to/some.iso

1270

</pre></td></tr></table>

1271

1272

</dd>

1273

<dt> ‘<samp>change vnc <var>display,options</var></samp>’</dt>

1274

<dd><p>Change the configuration of the VNC server. The valid syntax for <var>display</var>

1275

and <var>options</var> are described at <a href="#SEC10">Invocation</a>. eg

1276

</p>

1277

<table><tr><td> </td><td><pre class="example">(qemu) change vnc localhost:1

1278

</pre></td></tr></table>

1279

1280

</dd>

1281

<dt> ‘<samp>change vnc password</samp>’</dt>

1282

<dd>

1283

<p>Change the password associated with the VNC server. The monitor will prompt for

1284

the new password to be entered. VNC passwords are only significant upto 8 letters.

1285

eg.

1286

</p>

1287

<table><tr><td> </td><td><pre class="example">(qemu) change vnc password

1288

Password: ********

1289

</pre></td></tr></table>

1290

1291

</dd>

1292

</dl>

1293

1294

</dd>

1295

<dt> ‘<samp>screendump filename</samp>’</dt>

1296

<dd><p>Save screen into PPM image <var>filename</var>.

1297

</p>

1298

</dd>

1299

<dt> ‘<samp>mouse_move dx dy [dz]</samp>’</dt>

1300

<dd><p>Move the active mouse to the specified coordinates <var>dx</var> <var>dy</var>

1301

with optional scroll axis <var>dz</var>.

1302

</p>

1303

</dd>

1304

<dt> ‘<samp>mouse_button val</samp>’</dt>

1305

<dd><p>Change the active mouse button state <var>val</var> (1=L, 2=M, 4=R).

1306

</p>

1307

</dd>

1308

<dt> ‘<samp>mouse_set index</samp>’</dt>

1309

<dd><p>Set which mouse device receives events at given <var>index</var>, index

1310

can be obtained with

1311

</p><table><tr><td> </td><td><pre class="example">info mice

1312

</pre></td></tr></table>

1313

1314

</dd>

1315

<dt> ‘<samp>wavcapture filename [frequency [bits [channels]]]</samp>’</dt>

1316

<dd><p>Capture audio into <var>filename</var>. Using sample rate <var>frequency</var>

1317

bits per sample <var>bits</var> and number of channels <var>channels</var>.

1318

</p>

1319

<p>Defaults:

1320

</p><ul class="toc">

1321

<li>- Sample rate = 44100 Hz - CD quality

1322

</li><li>- Bits = 16

1323

</li><li>- Number of channels = 2 - Stereo

1324

</li></ul>

1325

1326

</dd>

1327

<dt> ‘<samp>stopcapture index</samp>’</dt>

1328

<dd><p>Stop capture with a given <var>index</var>, index can be obtained with

1329

</p><table><tr><td> </td><td><pre class="example">info capture

1330

</pre></td></tr></table>

1331

1332

</dd>

1333

1334

<dd><p>Activate logging of the specified items to ‘<tt>/tmp/qemu.log</tt>’.

1335

</p>

1336

</dd>

1337

<dt> ‘<samp>savevm [tag|id]</samp>’</dt>

1338

<dd><p>Create a snapshot of the whole virtual machine. If <var>tag</var> is

1339

provided, it is used as human readable identifier. If there is already

1340

a snapshot with the same tag or ID, it is replaced. More info at

1341

<a href="#SEC18">VM snapshots</a>.

1342

</p>

1343

</dd>

1344

<dt> ‘<samp>loadvm tag|id</samp>’</dt>

1345

<dd><p>Set the whole virtual machine to the snapshot identified by the tag

1346

<var>tag</var> or the unique snapshot ID <var>id</var>.

1347

</p>

1348

</dd>

1349

<dt> ‘<samp>delvm tag|id</samp>’</dt>

1350

<dd><p>Delete the snapshot identified by <var>tag</var> or <var>id</var>.

1351

</p>

1352

</dd>

1353

1354

<dd><p>Stop emulation.

1355

</p>

1356

</dd>

1357

1358

<dd><p>Resume emulation.

1359

</p>

1360

</dd>

1361

<dt> ‘<samp>gdbserver [port]</samp>’</dt>

1362

<dd><p>Start gdbserver session (default port=1234)

1363

</p>

1364

</dd>

1365

1366

<dd><p>Virtual memory dump starting at <var>addr</var>.

1367

</p>

1368

</dd>

1369

1370

<dd><p>Physical memory dump starting at <var>addr</var>.

1371

</p>

1372

<p><var>fmt</var> is a format which tells the command how to format the

1373

data. Its syntax is: ‘<samp>/{count}{format}{size}</samp>’

1374

</p>

1375

1376

<dt> <var>count</var></dt>

1377

<dd><p>is the number of items to be dumped.

1378

</p>

1379

</dd>

1380

<dt> <var>format</var></dt>

1381

<dd><p>can be x (hex), d (signed decimal), u (unsigned decimal), o (octal),

1382

c (char) or i (asm instruction).

1383

</p>

1384

</dd>

1385

1386

<dd><p>can be b (8 bits), h (16 bits), w (32 bits) or g (64 bits). On x86,

1387

<code>h</code> or <code>w</code> can be specified with the <code>i</code> format to

1388

respectively select 16 or 32 bit code instruction size.

1389

</p>

1390

</dd>

1391

</dl>

1392

1393

<p>Examples:

1394

</p><ul class="toc">

1395

<li>

1396

Dump 10 instructions at the current instruction pointer:

1397

<table><tr><td> </td><td><pre class="example">(qemu) x/10i $eip

1398

0x90107063: ret

1399

0x90107064: sti

1400

0x90107065: lea 0x0(%esi,1),%esi

1401

0x90107069: lea 0x0(%edi,1),%edi

1402

0x90107070: ret

1403

0x90107071: jmp 0x90107080

1404

0x90107073: nop

1405

0x90107074: nop

1406

0x90107075: nop

1407

0x90107076: nop

1408

</pre></td></tr></table>

1409

1410

</li><li>

1411

Dump 80 16 bit values at the start of the video memory.

1412

<table><tr><td> </td><td><pre class="smallexample">(qemu) xp/80hx 0xb8000

1413

0x000b8000: 0x0b50 0x0b6c 0x0b65 0x0b78 0x0b38 0x0b36 0x0b2f 0x0b42

1414

0x000b8010: 0x0b6f 0x0b63 0x0b68 0x0b73 0x0b20 0x0b56 0x0b47 0x0b41

1415

0x000b8020: 0x0b42 0x0b69 0x0b6f 0x0b73 0x0b20 0x0b63 0x0b75 0x0b72

1416

0x000b8030: 0x0b72 0x0b65 0x0b6e 0x0b74 0x0b2d 0x0b63 0x0b76 0x0b73

1417

0x000b8040: 0x0b20 0x0b30 0x0b35 0x0b20 0x0b4e 0x0b6f 0x0b76 0x0b20

1418

0x000b8050: 0x0b32 0x0b30 0x0b30 0x0b33 0x0720 0x0720 0x0720 0x0720

1419

0x000b8060: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720

1420

0x000b8070: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720

1421

0x000b8080: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720

1422

0x000b8090: 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720 0x0720

1423

</pre></td></tr></table>

1424

</li></ul>

1425

1426

</dd>

1427

<dt> ‘<samp>p or print/fmt expr</samp>’</dt>

1428

<dd>

1429

<p>Print expression value. Only the <var>format</var> part of <var>fmt</var> is

1430

used.

1431

</p>

1432

</dd>

1433

<dt> ‘<samp>sendkey keys</samp>’</dt>

1434

<dd>

1435

<p>Send <var>keys</var> to the emulator. Use <code>-</code> to press several keys

1436

simultaneously. Example:

1437

</p><table><tr><td> </td><td><pre class="example">sendkey ctrl-alt-f1

1438

</pre></td></tr></table>

1439

1440

<p>This command is useful to send keys that your graphical user interface

1441

intercepts at low level, such as <code>ctrl-alt-f1</code> in X Window.

1442

</p>

1443

</dd>

1444

<dt> ‘<samp>system_reset</samp>’</dt>

1445

<dd>

1446

<p>Reset the system.

1447

</p>

1448

</dd>

1449

<dt> ‘<samp>usb_add devname</samp>’</dt>

1450

<dd>

1451

<p>Add the USB device <var>devname</var>. For details of available devices see

1452

<a href="#SEC34">Connecting USB devices</a>

1453

</p>

1454

</dd>

1455

<dt> ‘<samp>usb_del devname</samp>’</dt>

1456

<dd>

1457

<p>Remove the USB device <var>devname</var> from the QEMU virtual USB

1458

hub. <var>devname</var> has the syntax <code>bus.addr</code>. Use the monitor

1459

command <code>info usb</code> to see the devices you can remove.

1460

</p>

1461

</dd>

1462

</dl>

1463

1464

1465

1466

1467

1468

1469

1470

1471

1472

1473

1474

1475

1476

1477

1478

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

1479

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

1480

1481

</tr></table>

1482

<h3 class="subsection"> 3.5.2 Integer expressions </h3>

1483

1484

<p>The monitor understands integers expressions for every integer

1485

argument. You can use register names to get the value of specifics

1486

CPU registers by prefixing them with <em>$</em>.

1487

</p>

1488

1489

1490

1491

1492

1493

1494

1495

1496

1497

1498

1499

1500

1501

1502

1503

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

1504

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

1505

1506

</tr></table>

1507

<h2 class="section"> 3.6 Disk Images </h2>

1508

1509

<p>Since version 0.6.1, QEMU supports many disk image formats, including

1510

growable disk images (their size increase as non empty sectors are

1511

written), compressed and encrypted disk images. Version 0.8.3 added

1512

the new qcow2 disk image format which is essential to support VM

1513

snapshots.

1514

</p>

1515

1516

<tr><td align="left" valign="top"><a href="#SEC16">3.6.1 Quick start for disk image creation</a></td><td>  </td><td align="left" valign="top"></td></tr>

1517

<tr><td align="left" valign="top"><a href="#SEC17">3.6.2 Snapshot mode</a></td><td>  </td><td align="left" valign="top"></td></tr>

1518

<tr><td align="left" valign="top"><a href="#SEC18">3.6.3 VM snapshots</a></td><td>  </td><td align="left" valign="top"></td></tr>

1519

<tr><td align="left" valign="top"><a href="#SEC19">3.6.4 <code>qemu-img</code> Invocation</a></td><td>  </td><td align="left" valign="top"> qemu-img Invocation

1520

</td></tr>

1521

<tr><td align="left" valign="top"><a href="#SEC20">3.6.5 Using host drives</a></td><td>  </td><td align="left" valign="top"></td></tr>

1522

<tr><td align="left" valign="top"><a href="#SEC24">3.6.6 Virtual FAT disk images</a></td><td>  </td><td align="left" valign="top"></td></tr>

1523

</table>

1524

1525

1526

1527

1528

1529

1530

1531

1532

1533

1534

1535

1536

1537

1538

1539

1540

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

1541

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

1542

1543

</tr></table>

1544

<h3 class="subsection"> 3.6.1 Quick start for disk image creation </h3>

1545

1546

<p>You can create a disk image with the command:

1547

</p><table><tr><td> </td><td><pre class="example">qemu-img create myimage.img mysize

1548

</pre></td></tr></table>

1549

<p>where <var>myimage.img</var> is the disk image filename and <var>mysize</var> is its

1550

size in kilobytes. You can add an <code>M</code> suffix to give the size in

1551

megabytes and a <code>G</code> suffix for gigabytes.

1552

</p>

1553

<p>See <a href="#SEC19"><code>qemu-img</code> Invocation</a> for more information.

1554

</p>

1555

1556

1557

1558

1559

1560

1561

1562

1563

1564

1565

1566

1567

1568

1569

1570

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

1571

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

1572

1573

</tr></table>

1574

<h3 class="subsection"> 3.6.2 Snapshot mode </h3>

1575

1576

<p>If you use the option ‘<samp>-snapshot</samp>’, all disk images are

1577

considered as read only. When sectors in written, they are written in

1578

a temporary file created in ‘<tt>/tmp</tt>’. You can however force the

1579

write back to the raw disk images by using the <code>commit</code> monitor

1580

command (or <C-a s> in the serial console).

1581

</p>

1582

1583

1584

1585

1586

1587

1588

1589

1590

1591

1592

1593

1594

1595

1596

1597

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

1598

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

1599

1600

</tr></table>

1601

<h3 class="subsection"> 3.6.3 VM snapshots </h3>

1602

1603

<p>VM snapshots are snapshots of the complete virtual machine including

1604

CPU state, RAM, device state and the content of all the writable

1605

disks. In order to use VM snapshots, you must have at least one non

1606

removable and writable block device using the <code>qcow2</code> disk image

1607

format. Normally this device is the first virtual hard drive.

1608

</p>

1609

<p>Use the monitor command <code>savevm</code> to create a new VM snapshot or

1610

replace an existing one. A human readable name can be assigned to each

1611

snapshot in addition to its numerical ID.

1612

</p>

1613

<p>Use <code>loadvm</code> to restore a VM snapshot and <code>delvm</code> to remove

1614

a VM snapshot. <code>info snapshots</code> lists the available snapshots

1615

with their associated information:

1616

</p>

1617

<table><tr><td> </td><td><pre class="example">(qemu) info snapshots

1618

Snapshot devices: hda

1619

Snapshot list (from hda):

1620

ID TAG VM SIZE DATE VM CLOCK

1621

1 start 41M 2006-08-06 12:38:02 00:00:14.954

1622

2 40M 2006-08-06 12:43:29 00:00:18.633

1623

3 msys 40M 2006-08-06 12:44:04 00:00:23.514

1624

</pre></td></tr></table>

1625

1626

<p>A VM snapshot is made of a VM state info (its size is shown in

1627

<code>info snapshots</code>) and a snapshot of every writable disk image.

1628

The VM state info is stored in the first <code>qcow2</code> non removable

1629

and writable block device. The disk image snapshots are stored in

1630

every disk image. The size of a snapshot in a disk image is difficult

1631

to evaluate and is not shown by <code>info snapshots</code> because the

1632

associated disk sectors are shared among all the snapshots to save

1633

disk space (otherwise each snapshot would need a full copy of all the

1634

disk images).

1635

</p>

1636

<p>When using the (unrelated) <code>-snapshot</code> option

1637

(<a href="#SEC17">Snapshot mode</a>), you can always make VM snapshots,

1638

but they are deleted as soon as you exit QEMU.

1639

</p>

1640

<p>VM snapshots currently have the following known limitations:

1641

</p><ul class="toc">

1642

<li>

1643

They cannot cope with removable devices if they are removed or

1644

inserted after a snapshot is done.

1645

</li><li>

1646

A few device drivers still have incomplete snapshot support so their

1647

state is not saved or restored properly (in particular USB).

1648

</li></ul>

1649

1650

1651

1652

1653

1654

1655

1656

1657

1658

1659

1660

1661

1662

1663

1664

1665

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

1666

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

1667

1668

</tr></table>

1669

<h3 class="subsection"> 3.6.4 <code>qemu-img</code> Invocation </h3>

1670

1671

<table><tr><td> </td><td><pre class="example">usage: qemu-img command [command options]

1672

</pre></td></tr></table>

1673

1674

1675

<p>The following commands are supported:

1676

</p><dl compact="compact">

1677

<dt> ‘<samp>create [-e] [-6] [-b <var>base_image</var>] [-f <var>fmt</var>] <var>filename</var> [<var>size</var>]</samp>’</dt>

1678

<dt> ‘<samp>commit [-f <var>fmt</var>] <var>filename</var></samp>’</dt>

1679

<dt> ‘<samp>convert [-c] [-e] [-6] [-f <var>fmt</var>] <var>filename</var> [-O <var>output_fmt</var>] <var>output_filename</var></samp>’</dt>

1680

<dt> ‘<samp>info [-f <var>fmt</var>] <var>filename</var></samp>’</dt>

1681

</dl>

1682

1683

<p>Command parameters:

1684

</p><dl compact="compact">

1685

<dt> <var>filename</var></dt>

1686

<dd><p> is a disk image filename

1687

</p></dd>

1688

<dt> <var>base_image</var></dt>

1689

<dd><p>is the read-only disk image which is used as base for a copy on

1690

write image; the copy on write image only stores the modified data

1691

</p>

1692

</dd>

1693

1694

<dd><p>is the disk image format. It is guessed automatically in most cases. The following formats are supported:

1695

</p>

1696

1697

1698

<dd>

1699

<p>Raw disk image format (default). This format has the advantage of

1700

being simple and easily exportable to all other emulators. If your

1701

file system supports <em>holes</em> (for example in ext2 or ext3 on

1702

Linux or NTFS on Windows), then only the written sectors will reserve

1703

space. Use <code>qemu-img info</code> to know the real size used by the

1704

image or <code>ls -ls</code> on Unix/Linux.

1705

</p>

1706

</dd>

1707

1708

<dd><p>QEMU image format, the most versatile format. Use it to have smaller

1709

images (useful if your filesystem does not supports holes, for example

1710

on Windows), optional AES encryption, zlib based compression and

1711

support of multiple VM snapshots.

1712

</p></dd>

1713

1714

<dd><p>Old QEMU image format. Left for compatibility.

1715

</p></dd>

1716

1717

<dd><p>User Mode Linux Copy On Write image format. Used to be the only growable

1718

image format in QEMU. It is supported only for compatibility with

1719

previous versions. It does not work on win32.

1720

</p></dd>

1721

1722

<dd><p>VMware 3 and 4 compatible image format.

1723

</p></dd>

1724

<dt> <code>cloop</code></dt>

1725

<dd><p>Linux Compressed Loop image, useful only to reuse directly compressed

1726

CD-ROM images present for example in the Knoppix CD-ROMs.

1727

</p></dd>

1728

</dl>

1729

1730

</dd>

1731

1732

<dd><p>is the disk image size in kilobytes. Optional suffixes <code>M</code>

1733

(megabyte) and <code>G</code> (gigabyte) are supported

1734

</p>

1735

</dd>

1736

<dt> <var>output_filename</var></dt>

1737

<dd><p>is the destination disk image filename

1738

</p>

1739

</dd>

1740

<dt> <var>output_fmt</var></dt>

1741

<dd><p> is the destination format

1742

</p>

1743

</dd>

1744

1745

<dd><p>indicates that target image must be compressed (qcow format only)

1746

</p></dd>

1747

1748

<dd><p>indicates that the target image must be encrypted (qcow format only)

1749

</p></dd>

1750

1751

<dd><p>indicates that the target image must use compatibility level 6 (vmdk format only)

1752

</p></dd>

1753

</dl>

1754

1755

<p>Command description:

1756

</p>

1757

1758

<dt> ‘<samp>create [-6] [-e] [-b <var>base_image</var>] [-f <var>fmt</var>] <var>filename</var> [<var>size</var>]</samp>’</dt>

1759

<dd>

1760

<p>Create the new disk image <var>filename</var> of size <var>size</var> and format

1761

<var>fmt</var>.

1762

</p>

1763

<p>If <var>base_image</var> is specified, then the image will record only the

1764

differences from <var>base_image</var>. No size needs to be specified in

1765

this case. <var>base_image</var> will never be modified unless you use the

1766

<code>commit</code> monitor command.

1767

</p>

1768

</dd>

1769

<dt> ‘<samp>commit [-f <var>fmt</var>] <var>filename</var></samp>’</dt>

1770

<dd>

1771

<p>Commit the changes recorded in <var>filename</var> in its base image.

1772

</p>

1773

</dd>

1774

<dt> ‘<samp>convert [-c] [-e] [-f <var>fmt</var>] <var>filename</var> [-O <var>output_fmt</var>] <var>output_filename</var></samp>’</dt>

1775

<dd>

1776

<p>Convert the disk image <var>filename</var> to disk image <var>output_filename</var>

1777

using format <var>output_fmt</var>. It can be optionally encrypted

1778

(<code>-e</code> option) or compressed (<code>-c</code> option).

1779

</p>

1780

<p>Only the format <code>qcow</code> supports encryption or compression. The

1781

compression is read-only. It means that if a compressed sector is

1782

rewritten, then it is rewritten as uncompressed data.

1783

</p>

1784

<p>Encryption uses the AES format which is very secure (128 bit keys). Use

1785

a long password (16 characters) to get maximum protection.

1786

</p>

1787

<p>Image conversion is also useful to get smaller image when using a

1788

growable format such as <code>qcow</code> or <code>cow</code>: the empty sectors

1789

are detected and suppressed from the destination image.

1790

</p>

1791

</dd>

1792

<dt> ‘<samp>info [-f <var>fmt</var>] <var>filename</var></samp>’</dt>

1793

<dd>

1794

<p>Give information about the disk image <var>filename</var>. Use it in

1795

particular to know the size reserved on disk which can be different

1796

from the displayed size. If VM snapshots are stored in the disk image,

1797

they are displayed too.

1798

</p></dd>

1799

</dl>

1800

1801

1802

1803

1804

1805

1806

1807

1808

1809

1810

1811

1812

1813

1814

1815

1816

1817

1818

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

1819

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

1820

1821

</tr></table>

1822

<h3 class="subsection"> 3.6.5 Using host drives </h3>

1823

1824

<p>In addition to disk image files, QEMU can directly access host

1825

devices. We describe here the usage for QEMU version >= 0.8.3.

1826

</p>

1827

1828

1829

1830

1831

1832

1833

1834

1835

1836

1837

1838

1839

1840

1841

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

1842

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

1843

1844

</tr></table>

1845

<h4 class="subsubsection"> 3.6.5.1 Linux </h4>

1846

1847

<p>On Linux, you can directly use the host device filename instead of a

1848

disk image filename provided you have enough privileges to access

1849

it. For example, use ‘<tt>/dev/cdrom</tt>’ to access to the CDROM or

1850

‘<tt>/dev/fd0</tt>’ for the floppy.

1851

</p>

1852

1853

1854

<dd><p>You can specify a CDROM device even if no CDROM is loaded. QEMU has

1855

specific code to detect CDROM insertion or removal. CDROM ejection by

1856

the guest OS is supported. Currently only data CDs are supported.

1857

</p></dd>

1858

<dt> <code>Floppy</code></dt>

1859

<dd><p>You can specify a floppy device even if no floppy is loaded. Floppy

1860

removal is currently not detected accurately (if you change floppy

1861

without doing floppy access while the floppy is not loaded, the guest

1862

OS will think that the same floppy is loaded).

1863

</p></dd>

1864

<dt> <code>Hard disks</code></dt>

1865

<dd><p>Hard disks can be used. Normally you must specify the whole disk

1866

(‘<tt>/dev/hdb</tt>’ instead of ‘<tt>/dev/hdb1</tt>’) so that the guest OS can

1867

see it as a partitioned disk. WARNING: unless you know what you do, it

1868

is better to only make READ-ONLY accesses to the hard disk otherwise

1869

you may corrupt your host data (use the ‘<samp>-snapshot</samp>’ command

1870

line option or modify the device permissions accordingly).

1871

</p></dd>

1872

</dl>

1873

1874

1875

1876

1877

1878

1879

1880

1881

1882

1883

1884

1885

1886

1887

1888

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

1889

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

1890

1891

</tr></table>

1892

<h4 class="subsubsection"> 3.6.5.2 Windows </h4>

1893

1894

1895

1896

<dd><p>The preferred syntax is the drive letter (e.g. ‘<tt>d:</tt>’). The

1897

alternate syntax ‘<tt>\\.\d:</tt>’ is supported. ‘<tt>/dev/cdrom</tt>’ is

1898

supported as an alias to the first CDROM drive.

1899

</p>

1900

<p>Currently there is no specific code to handle removable media, so it

1901

is better to use the <code>change</code> or <code>eject</code> monitor commands to

1902

change or eject media.

1903

</p></dd>

1904

<dt> <code>Hard disks</code></dt>

1905

<dd><p>Hard disks can be used with the syntax: ‘<tt>\\.\PhysicalDriveN</tt>’

1906

where <var>N</var> is the drive number (0 is the first hard disk).

1907

</p>

1908

<p>WARNING: unless you know what you do, it is better to only make

1909

READ-ONLY accesses to the hard disk otherwise you may corrupt your

1910

host data (use the ‘<samp>-snapshot</samp>’ command line so that the

1911

modifications are written in a temporary file).

1912

</p></dd>

1913

</dl>

1914

1915

1916

1917

1918

1919

1920

1921

1922

1923

1924

1925

1926

1927

1928

1929

1930

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

1931

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

1932

1933

</tr></table>

1934

1935

1936

<p>‘<tt>/dev/cdrom</tt>’ is an alias to the first CDROM.

1937

</p>

1938

<p>Currently there is no specific code to handle removable media, so it

1939

is better to use the <code>change</code> or <code>eject</code> monitor commands to

1940

change or eject media.

1941

</p>

1942

1943

1944

1945

1946

1947

1948

1949

1950

1951

1952

1953

1954

1955

1956

1957

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

1958

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

1959

1960

</tr></table>

1961

<h3 class="subsection"> 3.6.6 Virtual FAT disk images </h3>

1962

1963

<p>QEMU can automatically create a virtual FAT disk image from a

1964

directory tree. In order to use it, just type:

1965

</p>

1966

<table><tr><td> </td><td><pre class="example">qemu linux.img -hdb fat:/my_directory

1967

</pre></td></tr></table>

1968

1969

<p>Then you access access to all the files in the ‘<tt>/my_directory</tt>’

1970

directory without having to copy them in a disk image or to export

1971

them via SAMBA or NFS. The default access is <em>read-only</em>.

1972

</p>

1973

<p>Floppies can be emulated with the <code>:floppy:</code> option:

1974

</p>

1975

<table><tr><td> </td><td><pre class="example">qemu linux.img -fda fat:floppy:/my_directory

1976

</pre></td></tr></table>

1977

1978

<p>A read/write support is available for testing (beta stage) with the

1979

<code>:rw:</code> option:

1980

</p>

1981

<table><tr><td> </td><td><pre class="example">qemu linux.img -fda fat:floppy:rw:/my_directory

1982

</pre></td></tr></table>

1983

1984

<p>What you should <em>never</em> do:

1985

</p><ul class="toc">

1986

<li> use non-ASCII filenames ;

1987

</li><li> use "-snapshot" together with ":rw:" ;

1988

</li><li> expect it to work when loadvm'ing ;

1989

</li><li> write to the FAT directory on the host system while accessing it with the guest system.

1990

</li></ul>

1991

1992

1993

1994

1995

1996

1997

1998

1999

2000

2001

2002

2003

2004

2005

2006

2007

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2008

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2009

2010

</tr></table>

2011

<h2 class="section"> 3.7 Network emulation </h2>

2012

2013

<p>QEMU can simulate several network cards (PCI or ISA cards on the PC

2014

target) and can connect them to an arbitrary number of Virtual Local

2015

Area Networks (VLANs). Host TAP devices can be connected to any QEMU

2016

VLAN. VLAN can be connected between separate instances of QEMU to

2017

simulate large networks. For simpler usage, a non privileged user mode

2018

network stack can replace the TAP device to have a basic network

2019

connection.

2020

</p>

2021

2022

2023

2024

2025

2026

2027

2028

2029

2030

2031

2032

2033

2034

2035

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2036

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2037

2038

</tr></table>

2039

<h3 class="subsection"> 3.7.1 VLANs </h3>

2040

2041

<p>QEMU simulates several VLANs. A VLAN can be symbolised as a virtual

2042

connection between several network devices. These devices can be for

2043

example QEMU virtual Ethernet cards or virtual Host ethernet devices

2044

(TAP devices).

2045

</p>

2046

2047

2048

2049

2050

2051

2052

2053

2054

2055

2056

2057

2058

2059

2060

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2061

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2062

2063

</tr></table>

2064

<h3 class="subsection"> 3.7.2 Using TAP network interfaces </h3>

2065

2066

<p>This is the standard way to connect QEMU to a real network. QEMU adds

2067

a virtual network device on your host (called <code>tapN</code>), and you

2068

can then configure it as if it was a real ethernet card.

2069

</p>

2070

2071

2072

2073

2074

2075

2076

2077

2078

2079

2080

2081

2082

2083

2084

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2085

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2086

2087

</tr></table>

2088

<h4 class="subsubsection"> 3.7.2.1 Linux host </h4>

2089

2090

<p>As an example, you can download the ‘<tt>linux-test-xxx.tar.gz</tt>’

2091

archive and copy the script ‘<tt>qemu-ifup</tt>’ in ‘<tt>/etc</tt>’ and

2092

configure properly <code>sudo</code> so that the command <code>ifconfig</code>

2093

contained in ‘<tt>qemu-ifup</tt>’ can be executed as root. You must verify

2094

that your host kernel supports the TAP network interfaces: the

2095

device ‘<tt>/dev/net/tun</tt>’ must be present.

2096

</p>

2097

<p>See <a href="#SEC10">Invocation</a> to have examples of command lines using the

2098

TAP network interfaces.

2099

</p>

2100

2101

2102

2103

2104

2105

2106

2107

2108

2109

2110

2111

2112

2113

2114

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2115

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2116

2117

</tr></table>

2118

<h4 class="subsubsection"> 3.7.2.2 Windows host </h4>

2119

2120

<p>There is a virtual ethernet driver for Windows 2000/XP systems, called

2121

TAP-Win32. But it is not included in standard QEMU for Windows,

2122

so you will need to get it separately. It is part of OpenVPN package,

2123

so download OpenVPN from : <a href="http://openvpn.net/">http://openvpn.net/</a>.

2124

</p>

2125

2126

2127

2128

2129

2130

2131

2132

2133

2134

2135

2136

2137

2138

2139

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2140

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2141

2142

</tr></table>

2143

<h3 class="subsection"> 3.7.3 Using the user mode network stack </h3>

2144

2145

<p>By using the option ‘<samp>-net user</samp>’ (default configuration if no

2146

‘<samp>-net</samp>’ option is specified), QEMU uses a completely user mode

2147

network stack (you don't need root privilege to use the virtual

2148

network). The virtual network configuration is the following:

2149

</p>

2150

2151

QEMU VLAN <------> Firewall/DHCP server <-----> Internet

2152

| (10.0.2.2)

2153

|

2154

----> DNS server (10.0.2.3)

2155

|

2156

----> SMB server (10.0.2.4)

2157

</pre></td></tr></table>

2158

2159

<p>The QEMU VM behaves as if it was behind a firewall which blocks all

2160

incoming connections. You can use a DHCP client to automatically

2161

configure the network in the QEMU VM. The DHCP server assign addresses

2162

to the hosts starting from 10.0.2.15.

2163

</p>

2164

<p>In order to check that the user mode network is working, you can ping

2165

the address 10.0.2.2 and verify that you got an address in the range

2166

10.0.2.x from the QEMU virtual DHCP server.

2167

</p>

2168

<p>Note that <code>ping</code> is not supported reliably to the internet as it

2169

would require root privileges. It means you can only ping the local

2170

router (10.0.2.2).

2171

</p>

2172

<p>When using the built-in TFTP server, the router is also the TFTP

2173

server.

2174

</p>

2175

<p>When using the ‘<samp>-redir</samp>’ option, TCP or UDP connections can be

2176

redirected from the host to the guest. It allows for example to

2177

redirect X11, telnet or SSH connections.

2178

</p>

2179

2180

2181

2182

2183

2184

2185

2186

2187

2188

2189

2190

2191

2192

2193

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2194

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2195

2196

</tr></table>

2197

<h3 class="subsection"> 3.7.4 Connecting VLANs between QEMU instances </h3>

2198

2199

<p>Using the ‘<samp>-net socket</samp>’ option, it is possible to make VLANs

2200

that span several QEMU instances. See <a href="#SEC10">Invocation</a> to have a

2201

basic example.

2202

</p>

2203

2204

2205

2206

2207

2208

2209

2210

2211

2212

2213

2214

2215

2216

2217

2218

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2219

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2220

2221

</tr></table>

2222

<h2 class="section"> 3.8 Direct Linux Boot </h2>

2223

2224

<p>This section explains how to launch a Linux kernel inside QEMU without

2225

having to make a full bootable image. It is very useful for fast Linux

2226

kernel testing.

2227

</p>

2228

<p>The syntax is:

2229

</p><table><tr><td> </td><td><pre class="example">qemu -kernel arch/i386/boot/bzImage -hda root-2.4.20.img -append "root=/dev/hda"

2230

</pre></td></tr></table>

2231

2232

<p>Use ‘<samp>-kernel</samp>’ to provide the Linux kernel image and

2233

‘<samp>-append</samp>’ to give the kernel command line arguments. The

2234

‘<samp>-initrd</samp>’ option can be used to provide an INITRD image.

2235

</p>

2236

<p>When using the direct Linux boot, a disk image for the first hard disk

2237

‘<tt>hda</tt>’ is required because its boot sector is used to launch the

2238

Linux kernel.

2239

</p>

2240

<p>If you do not need graphical output, you can disable it and redirect

2241

the virtual serial port and the QEMU monitor to the console with the

2242

‘<samp>-nographic</samp>’ option. The typical command line is:

2243

</p><table><tr><td> </td><td><pre class="example">qemu -kernel arch/i386/boot/bzImage -hda root-2.4.20.img \

2244

-append "root=/dev/hda console=ttyS0" -nographic

2245

</pre></td></tr></table>

2246

2247

<p>Use <Ctrl-a c> to switch between the serial console and the

2248

monitor (see section <a href="#SEC11">Keys</a>).

2249

</p>

2250

2251

2252

2253

2254

2255

2256

2257

2258

2259

2260

2261

2262

2263

2264

2265

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2266

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2267

2268

</tr></table>

2269

<h2 class="section"> 3.9 USB emulation </h2>

2270

2271

<p>QEMU emulates a PCI UHCI USB controller. You can virtually plug

2272

virtual USB devices or real host USB devices (experimental, works only

2273

on Linux hosts). Qemu will automatically create and connect virtual USB hubs

2274

as necessary to connect multiple USB devices.

2275

</p>

2276

2277

<tr><td align="left" valign="top"><a href="#SEC34">3.9.1 Connecting USB devices</a></td><td>  </td><td align="left" valign="top">

2278

</td></tr>

2279

<tr><td align="left" valign="top"><a href="#SEC35">3.9.2 Using host USB devices on a Linux host</a></td><td>  </td><td align="left" valign="top">

2280

</td></tr>

2281

</table>

2282

2283

2284

2285

2286

2287

2288

2289

2290

2291

2292

2293

2294

2295

2296

2297

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2298

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2299

2300

</tr></table>

2301

<h3 class="subsection"> 3.9.1 Connecting USB devices </h3>

2302

2303

<p>USB devices can be connected with the ‘<samp>-usbdevice</samp>’ commandline option

2304

or the <code>usb_add</code> monitor command. Available devices are:

2305

</p>

2306

2307

<dt> <var><code>mouse</code></var></dt>

2308

<dd><p>Virtual Mouse. This will override the PS/2 mouse emulation when activated.

2309

</p></dd>

2310

<dt> <var><code>tablet</code></var></dt>

2311

<dd><p>Pointer device that uses absolute coordinates (like a touchscreen).

2312

This means qemu is able to report the mouse position without having

2313

to grab the mouse. Also overrides the PS/2 mouse emulation when activated.

2314

</p></dd>

2315

2316

<dd><p>Mass storage device based on <var>file</var> (see section <a href="#SEC15">Disk Images</a>)

2317

</p></dd>

2318

2319

<dd><p>Pass through the host device identified by <var>bus.addr</var>

2320

(Linux only)

2321

</p></dd>

2322

<dt> <var><code>host:vendor_id:product_id</code></var></dt>

2323

<dd><p>Pass through the host device identified by <var>vendor_id:product_id</var>

2324

(Linux only)

2325

</p></dd>

2326

<dt> <var><code>wacom-tablet</code></var></dt>

2327

<dd><p>Virtual Wacom PenPartner tablet. This device is similar to the <code>tablet</code>

2328

above but it can be used with the tslib library because in addition to touch

2329

coordinates it reports touch pressure.

2330

</p></dd>

2331

<dt> <var><code>keyboard</code></var></dt>

2332

<dd><p>Standard USB keyboard. Will override the PS/2 keyboard (if present).

2333

</p></dd>

2334

</dl>

2335

2336

2337

2338

2339

2340

2341

2342

2343

2344

2345

2346

2347

2348

2349

2350

2351

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2352

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2353

2354

</tr></table>

2355

<h3 class="subsection"> 3.9.2 Using host USB devices on a Linux host </h3>

2356

2357

<p>WARNING: this is an experimental feature. QEMU will slow down when

2358

using it. USB devices requiring real time streaming (i.e. USB Video

2359

Cameras) are not supported yet.

2360

</p>

2361

<ol>

2362

<li> If you use an early Linux 2.4 kernel, verify that no Linux driver

2363

is actually using the USB device. A simple way to do that is simply to

2364

disable the corresponding kernel module by renaming it from ‘<tt>mydriver.o</tt>’

2365

to ‘<tt>mydriver.o.disabled</tt>’.

2366

2367

</li><li> Verify that ‘<tt>/proc/bus/usb</tt>’ is working (most Linux distributions should enable it by default). You should see something like that:

2368

<table><tr><td> </td><td><pre class="example">ls /proc/bus/usb

2369

001 devices drivers

2370

</pre></td></tr></table>

2371

2372

</li><li> Since only root can access to the USB devices directly, you can either launch QEMU as root or change the permissions of the USB devices you want to use. For testing, the following suffices:

2373

<table><tr><td> </td><td><pre class="example">chown -R myuid /proc/bus/usb

2374

</pre></td></tr></table>

2375

2376

</li><li> Launch QEMU and do in the monitor:

2377

<table><tr><td> </td><td><pre class="example">info usbhost

2378

Device 1.2, speed 480 Mb/s

2379

Class 00: USB device 1234:5678, USB DISK

2380

</pre></td></tr></table>

2381

<p>You should see the list of the devices you can use (Never try to use

2382

hubs, it won't work).

2383

</p>

2384

</li><li> Add the device in QEMU by using:

2385

<table><tr><td> </td><td><pre class="example">usb_add host:1234:5678

2386

</pre></td></tr></table>

2387

2388

<p>Normally the guest OS should report that a new USB device is

2389

plugged. You can use the option ‘<samp>-usbdevice</samp>’ to do the same.

2390

</p>

2391

</li><li> Now you can try to use the host USB device in QEMU.

2392

2393

</li></ol>

2394

2395

<p>When relaunching QEMU, you may have to unplug and plug again the USB

2396

device to make it work again (this is a bug).

2397

</p>

2398

2399

2400

2401

2402

2403

2404

2405

2406

2407

2408

2409

2410

2411

2412

2413

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2414

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2415

2416

</tr></table>

2417

<h2 class="section"> 3.10 VNC security </h2>

2418

2419

<p>The VNC server capability provides access to the graphical console

2420

of the guest VM across the network. This has a number of security

2421

considerations depending on the deployment scenarios.

2422

</p>

2423

2424

<tr><td align="left" valign="top"><a href="#SEC37">3.10.1 Without passwords</a></td><td>  </td><td align="left" valign="top">

2425

</td></tr>

2426

<tr><td align="left" valign="top"><a href="#SEC38">3.10.2 With passwords</a></td><td>  </td><td align="left" valign="top">

2427

</td></tr>

2428

<tr><td align="left" valign="top"><a href="#SEC39">3.10.3 With x509 certificates</a></td><td>  </td><td align="left" valign="top">

2429

</td></tr>

2430

<tr><td align="left" valign="top"><a href="#SEC40">3.10.4 With x509 certificates and client verification</a></td><td>  </td><td align="left" valign="top">

2431

</td></tr>

2432

<tr><td align="left" valign="top"><a href="#SEC41">3.10.5 With x509 certificates, client verification and passwords</a></td><td>  </td><td align="left" valign="top">

2433

</td></tr>

2434

<tr><td align="left" valign="top"><a href="#SEC42">3.10.6 Generating certificates for VNC</a></td><td>  </td><td align="left" valign="top">

2435

</td></tr>

2436

</table>

2437

2438

2439

2440

2441

2442

2443

2444

2445

2446

2447

2448

2449

2450

2451

2452

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2453

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2454

2455

</tr></table>

2456

<h3 class="subsection"> 3.10.1 Without passwords </h3>

2457

2458

<p>The simplest VNC server setup does not include any form of authentication.

2459

For this setup it is recommended to restrict it to listen on a UNIX domain

2460

socket only. For example

2461

</p>

2462

<table><tr><td> </td><td><pre class="example">qemu [...OPTIONS...] -vnc unix:/home/joebloggs/.qemu-myvm-vnc

2463

</pre></td></tr></table>

2464

2465

<p>This ensures that only users on local box with read/write access to that

2466

path can access the VNC server. To securely access the VNC server from a

2467

remote machine, a combination of netcat+ssh can be used to provide a secure

2468

tunnel.

2469

</p>

2470

2471

2472

2473

2474

2475

2476

2477

2478

2479

2480

2481

2482

2483

2484

2485

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2486

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2487

2488

</tr></table>

2489

<h3 class="subsection"> 3.10.2 With passwords </h3>

2490

2491

<p>The VNC protocol has limited support for password based authentication. Since

2492

the protocol limits passwords to 8 characters it should not be considered

2493

to provide high security. The password can be fairly easily brute-forced by

2494

a client making repeat connections. For this reason, a VNC server using password

2495

authentication should be restricted to only listen on the loopback interface

2496

or UNIX domain sockets. Password ayuthentication is requested with the <code>password</code>

2497

option, and then once QEMU is running the password is set with the monitor. Until

2498

the monitor is used to set the password all clients will be rejected.

2499

</p>

2500

<table><tr><td> </td><td><pre class="example">qemu [...OPTIONS...] -vnc :1,password -monitor stdio

2501

(qemu) change vnc password

2502

Password: ********

2503

(qemu)

2504

</pre></td></tr></table>

2505

2506

2507

2508

2509

2510

2511

2512

2513

2514

2515

2516

2517

2518

2519

2520

2521

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2522

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2523

2524

</tr></table>

2525

<h3 class="subsection"> 3.10.3 With x509 certificates </h3>

2526

2527

<p>The QEMU VNC server also implements the VeNCrypt extension allowing use of

2528

TLS for encryption of the session, and x509 certificates for authentication.

2529

The use of x509 certificates is strongly recommended, because TLS on its

2530

own is susceptible to man-in-the-middle attacks. Basic x509 certificate

2531

support provides a secure session, but no authentication. This allows any

2532

client to connect, and provides an encrypted session.

2533

</p>

2534

<table><tr><td> </td><td><pre class="example">qemu [...OPTIONS...] -vnc :1,tls,x509=/etc/pki/qemu -monitor stdio

2535

</pre></td></tr></table>

2536

2537

<p>In the above example <code>/etc/pki/qemu</code> should contain at least three files,

2538

<code>ca-cert.pem</code>, <code>server-cert.pem</code> and <code>server-key.pem</code>. Unprivileged

2539

users will want to use a private directory, for example <code>$HOME/.pki/qemu</code>.

2540

NB the <code>server-key.pem</code> file should be protected with file mode 0600 to

2541

only be readable by the user owning it.

2542

</p>

2543

2544

2545

2546

2547

2548

2549

2550

2551

2552

2553

2554

2555

2556

2557

2558

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2559

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2560

2561

</tr></table>

2562

<h3 class="subsection"> 3.10.4 With x509 certificates and client verification </h3>

2563

2564

<p>Certificates can also provide a means to authenticate the client connecting.

2565

The server will request that the client provide a certificate, which it will

2566

then validate against the CA certificate. This is a good choice if deploying

2567

in an environment with a private internal certificate authority.

2568

</p>

2569

<table><tr><td> </td><td><pre class="example">qemu [...OPTIONS...] -vnc :1,tls,x509verify=/etc/pki/qemu -monitor stdio

2570

</pre></td></tr></table>

2571

2572

2573

2574

2575

2576

2577

2578

2579

2580

2581

2582

2583

2584

2585

2586

2587

2588

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2589

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2590

2591

</tr></table>

2592

<h3 class="subsection"> 3.10.5 With x509 certificates, client verification and passwords </h3>

2593

2594

<p>Finally, the previous method can be combined with VNC password authentication

2595

to provide two layers of authentication for clients.

2596

</p>

2597

<table><tr><td> </td><td><pre class="example">qemu [...OPTIONS...] -vnc :1,password,tls,x509verify=/etc/pki/qemu -monitor stdio

2598

(qemu) change vnc password

2599

Password: ********

2600

(qemu)

2601

</pre></td></tr></table>

2602

2603

2604

2605

2606

2607

2608

2609

2610

2611

2612

2613

2614

2615

2616

2617

2618

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2619

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2620

2621

</tr></table>

2622

<h3 class="subsection"> 3.10.6 Generating certificates for VNC </h3>

2623

2624

<p>The GNU TLS packages provides a command called <code>certtool</code> which can

2625

be used to generate certificates and keys in PEM format. At a minimum it

2626

is neccessary to setup a certificate authority, and issue certificates to

2627

each server. If using certificates for authentication, then each client

2628

will also need to be issued a certificate. The recommendation is for the

2629

server to keep its certificates in either <code>/etc/pki/qemu</code> or for

2630

unprivileged users in <code>$HOME/.pki/qemu</code>.

2631

</p>

2632

2633

<tr><td align="left" valign="top"><a href="#SEC43">3.10.6.1 Setup the Certificate Authority</a></td><td>  </td><td align="left" valign="top">

2634

</td></tr>

2635

<tr><td align="left" valign="top"><a href="#SEC44">3.10.6.2 Issuing server certificates</a></td><td>  </td><td align="left" valign="top">

2636

</td></tr>

2637

<tr><td align="left" valign="top"><a href="#SEC45">3.10.6.3 Issuing client certificates</a></td><td>  </td><td align="left" valign="top">

2638

</td></tr>

2639

</table>

2640

2641

2642

2643

2644

2645

2646

2647

2648

2649

2650

2651

2652

2653

2654

2655

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2656

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2657

2658

</tr></table>

2659

<h4 class="subsubsection"> 3.10.6.1 Setup the Certificate Authority </h4>

2660

2661

<p>This step only needs to be performed once per organization / organizational

2662

unit. First the CA needs a private key. This key must be kept VERY secret

2663

and secure. If this key is compromised the entire trust chain of the certificates

2664

issued with it is lost.

2665

</p>

2666

<table><tr><td> </td><td><pre class="example"># certtool --generate-privkey > ca-key.pem

2667

</pre></td></tr></table>

2668

2669

<p>A CA needs to have a public certificate. For simplicity it can be a self-signed

2670

certificate, or one issue by a commercial certificate issuing authority. To

2671

generate a self-signed certificate requires one core piece of information, the

2672

name of the organization.

2673

</p>

2674

<table><tr><td> </td><td><pre class="example"># cat > ca.info <<EOF

2675

cn = Name of your organization

2676

ca

2677

cert_signing_key

2678

EOF

2679

# certtool --generate-self-signed \

2680

--load-privkey ca-key.pem

2681

--template ca.info \

2682

--outfile ca-cert.pem

2683

</pre></td></tr></table>

2684

2685

<p>The <code>ca-cert.pem</code> file should be copied to all servers and clients wishing to utilize

2686

TLS support in the VNC server. The <code>ca-key.pem</code> must not be disclosed/copied at all.

2687

</p>

2688

2689

2690

2691

2692

2693

2694

2695

2696

2697

2698

2699

2700

2701

2702

2703

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2704

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2705

2706

</tr></table>

2707

<h4 class="subsubsection"> 3.10.6.2 Issuing server certificates </h4>

2708

2709

<p>Each server (or host) needs to be issued with a key and certificate. When connecting

2710

the certificate is sent to the client which validates it against the CA certificate.

2711

The core piece of information for a server certificate is the hostname. This should

2712

be the fully qualified hostname that the client will connect with, since the client

2713

will typically also verify the hostname in the certificate. On the host holding the

2714

secure CA private key:

2715

</p>

2716

<table><tr><td> </td><td><pre class="example"># cat > server.info <<EOF

2717

organization = Name of your organization

2718

cn = server.foo.example.com

2719

tls_www_server

2720

encryption_key

2721

signing_key

2722

EOF

2723

# certtool --generate-privkey > server-key.pem

2724

# certtool --generate-certificate \

2725

--load-ca-certificate ca-cert.pem \

2726

--load-ca-privkey ca-key.pem \

2727

--load-privkey server server-key.pem \

2728

--template server.info \

2729

--outfile server-cert.pem

2730

</pre></td></tr></table>

2731

2732

<p>The <code>server-key.pem</code> and <code>server-cert.pem</code> files should now be securely copied

2733

to the server for which they were generated. The <code>server-key.pem</code> is security

2734

sensitive and should be kept protected with file mode 0600 to prevent disclosure.

2735

</p>

2736

2737

2738

2739

2740

2741

2742

2743

2744

2745

2746

2747

2748

2749

2750

2751

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2752

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2753

2754

</tr></table>

2755

<h4 class="subsubsection"> 3.10.6.3 Issuing client certificates </h4>

2756

2757

<p>If the QEMU VNC server is to use the <code>x509verify</code> option to validate client

2758

certificates as its authentication mechanism, each client also needs to be issued

2759

a certificate. The client certificate contains enough metadata to uniquely identify

2760

the client, typically organization, state, city, building, etc. On the host holding

2761

the secure CA private key:

2762

</p>

2763

<table><tr><td> </td><td><pre class="example"># cat > client.info <<EOF

2764

country = GB

2765

state = London

2766

locality = London

2767

organiazation = Name of your organization

2768

cn = client.foo.example.com

2769

tls_www_client

2770

encryption_key

2771

signing_key

2772

EOF

2773

# certtool --generate-privkey > client-key.pem

2774

# certtool --generate-certificate \

2775

--load-ca-certificate ca-cert.pem \

2776

--load-ca-privkey ca-key.pem \

2777

--load-privkey client-key.pem \

2778

--template client.info \

2779

--outfile client-cert.pem

2780

</pre></td></tr></table>

2781

2782

<p>The <code>client-key.pem</code> and <code>client-cert.pem</code> files should now be securely

2783

copied to the client for which they were generated.

2784

</p>

2785

2786

2787

2788

2789

2790

2791

2792

2793

2794

2795

2796

2797

2798

2799

2800

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2801

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2802

2803

</tr></table>

2804

<h2 class="section"> 3.11 GDB usage </h2>

2805

2806

<p>QEMU has a primitive support to work with gdb, so that you can do

2807

'Ctrl-C' while the virtual machine is running and inspect its state.

2808

</p>

2809

<p>In order to use gdb, launch qemu with the '-s' option. It will wait for a

2810

gdb connection:

2811

</p><table><tr><td> </td><td><pre class="example">> qemu -s -kernel arch/i386/boot/bzImage -hda root-2.4.20.img \

2812

-append "root=/dev/hda"

2813

Connected to host network interface: tun0

2814

Waiting gdb connection on port 1234

2815

</pre></td></tr></table>

2816

2817

<p>Then launch gdb on the 'vmlinux' executable:

2818

</p><table><tr><td> </td><td><pre class="example">> gdb vmlinux

2819

</pre></td></tr></table>

2820

2821

<p>In gdb, connect to QEMU:

2822

</p><table><tr><td> </td><td><pre class="example">(gdb) target remote localhost:1234

2823

</pre></td></tr></table>

2824

2825

<p>Then you can use gdb normally. For example, type 'c' to launch the kernel:

2826

</p><table><tr><td> </td><td><pre class="example">(gdb) c

2827

</pre></td></tr></table>

2828

2829

<p>Here are some useful tips in order to use gdb on system code:

2830

</p>

2831

<ol>

2832

<li>

2833

Use <code>info reg</code> to display all the CPU registers.

2834

</li><li>

2835

Use <code>x/10i $eip</code> to display the code at the PC position.

2836

</li><li>

2837

Use <code>set architecture i8086</code> to dump 16 bit code. Then use

2838

<code>x/10i $cs*16+$eip</code> to dump the code at the PC position.

2839

</li></ol>

2840

2841

2842

2843

2844

2845

2846

2847

2848

2849

2850

2851

2852

2853

2854

2855

2856

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2857

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2858

2859

</tr></table>

2860

<h2 class="section"> 3.12 Target OS specific information </h2>

2861

2862

2863

2864

2865

2866

2867

2868

2869

2870

2871

2872

2873

2874

2875

2876

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2877

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2878

2879

</tr></table>

2880

<h3 class="subsection"> 3.12.1 Linux </h3>

2881

2882

<p>To have access to SVGA graphic modes under X11, use the <code>vesa</code> or

2883

the <code>cirrus</code> X11 driver. For optimal performances, use 16 bit

2884

color depth in the guest and the host OS.

2885

</p>

2886

<p>When using a 2.6 guest Linux kernel, you should add the option

2887

<code>clock=pit</code> on the kernel command line because the 2.6 Linux

2888

kernels make very strict real time clock checks by default that QEMU

2889

cannot simulate exactly.

2890

</p>

2891

<p>When using a 2.6 guest Linux kernel, verify that the 4G/4G patch is

2892

not activated because QEMU is slower with this patch. The QEMU

2893

Accelerator Module is also much slower in this case. Earlier Fedora

2894

Core 3 Linux kernel (< 2.6.9-1.724_FC3) were known to incorporate this

2895

patch by default. Newer kernels don't have it.

2896

</p>

2897

2898

2899

2900

2901

2902

2903

2904

2905

2906

2907

2908

2909

2910

2911

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2912

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2913

2914

</tr></table>

2915

<h3 class="subsection"> 3.12.2 Windows </h3>

2916

2917

<p>If you have a slow host, using Windows 95 is better as it gives the

2918

best speed. Windows 2000 is also a good choice.

2919

</p>

2920

2921

2922

2923

2924

2925

2926

2927

2928

2929

2930

2931

2932

2933

2934

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2935

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2936

2937

</tr></table>

2938

<h4 class="subsubsection"> 3.12.2.1 SVGA graphic modes support </h4>

2939

2940

<p>QEMU emulates a Cirrus Logic GD5446 Video

2941

card. All Windows versions starting from Windows 95 should recognize

2942

and use this graphic card. For optimal performances, use 16 bit color

2943

depth in the guest and the host OS.

2944

</p>

2945

<p>If you are using Windows XP as guest OS and if you want to use high

2946

resolution modes which the Cirrus Logic BIOS does not support (i.e. >=

2947

1280x1024x16), then you should use the VESA VBE virtual graphic card

2948

(option ‘<samp>-std-vga</samp>’).

2949

</p>

2950

2951

2952

2953

2954

2955

2956

2957

2958

2959

2960

2961

2962

2963

2964

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2965

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2966

2967

</tr></table>

2968

<h4 class="subsubsection"> 3.12.2.2 CPU usage reduction </h4>

2969

2970

<p>Windows 9x does not correctly use the CPU HLT

2971

instruction. The result is that it takes host CPU cycles even when

2972

idle. You can install the utility from

2973

<a href="http://www.user.cityline.ru/~maxamn/amnhltm.zip">http://www.user.cityline.ru/~maxamn/amnhltm.zip</a> to solve this

2974

problem. Note that no such tool is needed for NT, 2000 or XP.

2975

</p>

2976

2977

2978

2979

2980

2981

2982

2983

2984

2985

2986

2987

2988

2989

2990

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

2991

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

2992

2993

</tr></table>

2994

<h4 class="subsubsection"> 3.12.2.3 Windows 2000 disk full problem </h4>

2995

2996

<p>Windows 2000 has a bug which gives a disk full problem during its

2997

installation. When installing it, use the ‘<samp>-win2k-hack</samp>’ QEMU

2998

option to enable a specific workaround. After Windows 2000 is

2999

installed, you no longer need this option (this option slows down the

3000

IDE transfers).

3001

</p>

3002

3003

3004

3005

3006

3007

3008

3009

3010

3011

3012

3013

3014

3015

3016

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3017

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3018

3019

</tr></table>

3020

<h4 class="subsubsection"> 3.12.2.4 Windows 2000 shutdown </h4>

3021

3022

<p>Windows 2000 cannot automatically shutdown in QEMU although Windows 98

3023

can. It comes from the fact that Windows 2000 does not automatically

3024

use the APM driver provided by the BIOS.

3025

</p>

3026

<p>In order to correct that, do the following (thanks to Struan

3027

Bartlett): go to the Control Panel => Add/Remove Hardware & Next =>

3028

Add/Troubleshoot a device => Add a new device & Next => No, select the

3029

hardware from a list & Next => NT Apm/Legacy Support & Next => Next

3030

(again) a few times. Now the driver is installed and Windows 2000 now

3031

correctly instructs QEMU to shutdown at the appropriate moment.

3032

</p>

3033

3034

3035

3036

3037

3038

3039

3040

3041

3042

3043

3044

3045

3046

3047

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3048

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3049

3050

</tr></table>

3051

<h4 class="subsubsection"> 3.12.2.5 Share a directory between Unix and Windows </h4>

3052

3053

<p>See <a href="#SEC10">Invocation</a> about the help of the option ‘<samp>-smb</samp>’.

3054

</p>

3055

3056

3057

3058

3059

3060

3061

3062

3063

3064

3065

3066

3067

3068

3069

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3070

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3071

3072

</tr></table>

3073

<h4 class="subsubsection"> 3.12.2.6 Windows XP security problem </h4>

3074

3075

<p>Some releases of Windows XP install correctly but give a security

3076

error when booting:

3077

</p><table><tr><td> </td><td><pre class="example">A problem is preventing Windows from accurately checking the

3078

license for this computer. Error code: 0x800703e6.

3079

</pre></td></tr></table>

3080

3081

<p>The workaround is to install a service pack for XP after a boot in safe

3082

mode. Then reboot, and the problem should go away. Since there is no

3083

network while in safe mode, its recommended to download the full

3084

installation of SP1 or SP2 and transfer that via an ISO or using the

3085

vvfat block device ("-hdb fat:directory_which_holds_the_SP").

3086

</p>

3087

3088

3089

3090

3091

3092

3093

3094

3095

3096

3097

3098

3099

3100

3101

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3102

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3103

3104

</tr></table>

3105

<h3 class="subsection"> 3.12.3 MS-DOS and FreeDOS </h3>

3106

3107

3108

3109

3110

3111

3112

3113

3114

3115

3116

3117

3118

3119

3120

3121

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3122

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3123

3124

</tr></table>

3125

<h4 class="subsubsection"> 3.12.3.1 CPU usage reduction </h4>

3126

3127

<p>DOS does not correctly use the CPU HLT instruction. The result is that

3128

it takes host CPU cycles even when idle. You can install the utility

3129

from <a href="http://www.vmware.com/software/dosidle210.zip">http://www.vmware.com/software/dosidle210.zip</a> to solve this

3130

problem.

3131

</p>

3132

3133

3134

3135

3136

3137

3138

3139

3140

3141

3142

3143

3144

3145

3146

3147

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3148

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3149

3150

</tr></table>

3151

<h1 class="chapter"> 4. QEMU System emulator for non PC targets </h1>

3152

3153

<p>QEMU is a generic emulator and it emulates many non PC

3154

machines. Most of the options are similar to the PC emulator. The

3155

differences are mentioned in the following sections.

3156

</p>

3157

3158

<tr><td align="left" valign="top"><a href="#SEC59">4.1 QEMU PowerPC System emulator</a></td><td>  </td><td align="left" valign="top">

3159

</td></tr>

3160

<tr><td align="left" valign="top"><a href="#SEC60">4.2 Sparc32 System emulator</a></td><td>  </td><td align="left" valign="top">

3161

</td></tr>

3162

<tr><td align="left" valign="top"><a href="#SEC61">4.3 Sparc64 System emulator</a></td><td>  </td><td align="left" valign="top">

3163

</td></tr>

3164

<tr><td align="left" valign="top"><a href="#SEC62">4.4 MIPS System emulator</a></td><td>  </td><td align="left" valign="top">

3165

</td></tr>

3166

<tr><td align="left" valign="top"><a href="#SEC63">4.5 ARM System emulator</a></td><td>  </td><td align="left" valign="top">

3167

</td></tr>

3168

<tr><td align="left" valign="top"><a href="#SEC64">4.6 ColdFire System emulator</a></td><td>  </td><td align="left" valign="top">

3169

</td></tr>

3170

</table>

3171

3172

3173

3174

3175

3176

3177

3178

3179

3180

3181

3182

3183

3184

3185

3186

3187

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3188

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3189

3190

</tr></table>

3191

<h2 class="section"> 4.1 QEMU PowerPC System emulator </h2>

3192

3193

<p>Use the executable ‘<tt>qemu-system-ppc</tt>’ to simulate a complete PREP

3194

or PowerMac PowerPC system.

3195

</p>

3196

<p>QEMU emulates the following PowerMac peripherals:

3197

</p>

3198

3199

<li>-

3200

UniNorth PCI Bridge

3201

</li><li>-

3202

PCI VGA compatible card with VESA Bochs Extensions

3203

</li><li>-

3204

2 PMAC IDE interfaces with hard disk and CD-ROM support

3205

</li><li>-

3206

NE2000 PCI adapters

3207

</li><li>-

3208

Non Volatile RAM

3209

</li><li>-

3210

VIA-CUDA with ADB keyboard and mouse.

3211

</li></ul>

3212

3213

<p>QEMU emulates the following PREP peripherals:

3214

</p>

3215

3216

<li>-

3217

PCI Bridge

3218

</li><li>-

3219

PCI VGA compatible card with VESA Bochs Extensions

3220

</li><li>-

3221

2 IDE interfaces with hard disk and CD-ROM support

3222

</li><li>-

3223

Floppy disk

3224

</li><li>-

3225

NE2000 network adapters

3226

</li><li>-

3227

Serial port

3228

</li><li>-

3229

PREP Non Volatile RAM

3230

</li><li>-

3231

PC compatible keyboard and mouse.

3232

</li></ul>

3233

3234

<p>QEMU uses the Open Hack'Ware Open Firmware Compatible BIOS available at

3235

<a href="http://perso.magic.fr/l_indien/OpenHackWare/index.htm">http://perso.magic.fr/l_indien/OpenHackWare/index.htm</a>.

3236

</p>

3237

3238

<p>The following options are specific to the PowerPC emulation:

3239

</p>

3240

3241

<dt> ‘<samp>-g WxH[xDEPTH]</samp>’</dt>

3242

<dd>

3243

<p>Set the initial VGA graphic mode. The default is 800x600x15.

3244

</p>

3245

</dd>

3246

</dl>

3247

3248

3249

3250

<p>More information is available at

3251

<a href="http://perso.magic.fr/l_indien/qemu-ppc/">http://perso.magic.fr/l_indien/qemu-ppc/</a>.

3252

</p>

3253

3254

3255

3256

3257

3258

3259

3260

3261

3262

3263

3264

3265

3266

3267

3268

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3269

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3270

3271

</tr></table>

3272

<h2 class="section"> 4.2 Sparc32 System emulator </h2>

3273

3274

<p>Use the executable ‘<tt>qemu-system-sparc</tt>’ to simulate a SparcStation 5

3275

or SparcStation 10 (sun4m architecture). The emulation is somewhat complete.

3276

</p>

3277

<p>QEMU emulates the following sun4m peripherals:

3278

</p>

3279

3280

<li>-

3281

IOMMU

3282

</li><li>-

3283

TCX Frame buffer

3284

</li><li>-

3285

Lance (Am7990) Ethernet

3286

</li><li>-

3287

Non Volatile RAM M48T08

3288

</li><li>-

3289

Slave I/O: timers, interrupt controllers, Zilog serial ports, keyboard

3290

and power/reset logic

3291

</li><li>-

3292

ESP SCSI controller with hard disk and CD-ROM support

3293

</li><li>-

3294

Floppy drive

3295

</li><li>-

3296

CS4231 sound device (only on SS-5, not working yet)

3297

</li></ul>

3298

3299

<p>The number of peripherals is fixed in the architecture.

3300

</p>

3301

<p>Since version 0.8.2, QEMU uses OpenBIOS

3302

<a href="http://www.openbios.org/">http://www.openbios.org/</a>. OpenBIOS is a free (GPL v2) portable

3303

firmware implementation. The goal is to implement a 100% IEEE

3304

1275-1994 (referred to as Open Firmware) compliant firmware.

3305

</p>

3306

<p>A sample Linux 2.6 series kernel and ram disk image are available on

3307

the QEMU web site. Please note that currently NetBSD, OpenBSD or

3308

Solaris kernels don't work.

3309

</p>

3310

3311

<p>The following options are specific to the Sparc32 emulation:

3312

</p>

3313

3314

<dt> ‘<samp>-g WxHx[xDEPTH]</samp>’</dt>

3315

<dd>

3316

<p>Set the initial TCX graphic mode. The default is 1024x768x8, currently

3317

the only other possible mode is 1024x768x24.

3318

</p>

3319

</dd>

3320

<dt> ‘<samp>-prom-env string</samp>’</dt>

3321

<dd>

3322

<p>Set OpenBIOS variables in NVRAM, for example:

3323

</p>

3324

<table><tr><td> </td><td><pre class="example">qemu-system-sparc -prom-env 'auto-boot?=false' \

3325

-prom-env 'boot-device=sd(0,2,0):d' -prom-env 'boot-args=linux single'

3326

</pre></td></tr></table>

3327

3328

</dd>

3329

3330

<dd>

3331

<p>Set the emulated machine type. Default is SS-5.

3332

</p>

3333

</dd>

3334

</dl>

3335

3336

3337

3338

3339

3340

3341

3342

3343

3344

3345

3346

3347

3348

3349

3350

3351

3352

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3353

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3354

3355

</tr></table>

3356

<h2 class="section"> 4.3 Sparc64 System emulator </h2>

3357

3358

<p>Use the executable ‘<tt>qemu-system-sparc64</tt>’ to simulate a Sun4u machine.

3359

The emulator is not usable for anything yet.

3360

</p>

3361

<p>QEMU emulates the following sun4u peripherals:

3362

</p>

3363

3364

<li>-

3365

UltraSparc IIi APB PCI Bridge

3366

</li><li>-

3367

PCI VGA compatible card with VESA Bochs Extensions

3368

</li><li>-

3369

Non Volatile RAM M48T59

3370

</li><li>-

3371

PC-compatible serial ports

3372

</li></ul>

3373

3374

3375

3376

3377

3378

3379

3380

3381

3382

3383

3384

3385

3386

3387

3388

3389

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3390

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3391

3392

</tr></table>

3393

<h2 class="section"> 4.4 MIPS System emulator </h2>

3394

3395

<p>Use the executable ‘<tt>qemu-system-mips</tt>’ to simulate a MIPS machine.

3396

Three different machine types are emulated:

3397

</p>

3398

3399

<li>-

3400

A generic ISA PC-like machine "mips"

3401

</li><li>-

3402

The MIPS Malta prototype board "malta"

3403

</li><li>-

3404

An ACER Pica "pica61"

3405

</li></ul>

3406

3407

<p>The generic emulation is supported by Debian 'Etch' and is able to

3408

install Debian into a virtual disk image. The following devices are

3409

emulated:

3410

</p>

3411

3412

<li>-

3413

MIPS 24Kf CPU

3414

</li><li>-

3415

PC style serial port

3416

</li><li>-

3417

PC style IDE disk

3418

</li><li>-

3419

NE2000 network card

3420

</li></ul>

3421

3422

<p>The Malta emulation supports the following devices:

3423

</p>

3424

3425

<li>-

3426

Core board with MIPS 24Kf CPU and Galileo system controller

3427

</li><li>-

3428

PIIX4 PCI/USB/SMbus controller

3429

</li><li>-

3430

The Multi-I/O chip's serial device

3431

</li><li>-

3432

PCnet32 PCI network card

3433

</li><li>-

3434

Malta FPGA serial device

3435

</li><li>-

3436

Cirrus VGA graphics card

3437

</li></ul>

3438

3439

<p>The ACER Pica emulation supports:

3440

</p>

3441

3442

<li>-

3443

MIPS R4000 CPU

3444

</li><li>-

3445

PC-style IRQ and DMA controllers

3446

</li><li>-

3447

PC Keyboard

3448

</li><li>-

3449

IDE controller

3450

</li></ul>

3451

3452

3453

3454

3455

3456

3457

3458

3459

3460

3461

3462

3463

3464

3465

3466

3467

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3468

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3469

3470

</tr></table>

3471

<h2 class="section"> 4.5 ARM System emulator </h2>

3472

3473

<p>Use the executable ‘<tt>qemu-system-arm</tt>’ to simulate a ARM

3474

machine. The ARM Integrator/CP board is emulated with the following

3475

devices:

3476

</p>

3477

3478

<li>-

3479

ARM926E, ARM1026E or ARM946E CPU

3480

</li><li>-

3481

Two PL011 UARTs

3482

</li><li>-

3483

SMC 91c111 Ethernet adapter

3484

</li><li>-

3485

PL110 LCD controller

3486

</li><li>-

3487

PL050 KMI with PS/2 keyboard and mouse.

3488

</li><li>-

3489

PL181 MultiMedia Card Interface with SD card.

3490

</li></ul>

3491

3492

<p>The ARM Versatile baseboard is emulated with the following devices:

3493

</p>

3494

3495

<li>-

3496

ARM926E CPU

3497

</li><li>-

3498

PL190 Vectored Interrupt Controller

3499

</li><li>-

3500

Four PL011 UARTs

3501

</li><li>-

3502

SMC 91c111 Ethernet adapter

3503

</li><li>-

3504

PL110 LCD controller

3505

</li><li>-

3506

PL050 KMI with PS/2 keyboard and mouse.

3507

</li><li>-

3508

PCI host bridge. Note the emulated PCI bridge only provides access to

3509

PCI memory space. It does not provide access to PCI IO space.

3510

This means some devices (eg. ne2k_pci NIC) are not usable, and others

3511

(eg. rtl8139 NIC) are only usable when the guest drivers use the memory

3512

mapped control registers.

3513

</li><li>-

3514

PCI OHCI USB controller.

3515

</li><li>-

3516

LSI53C895A PCI SCSI Host Bus Adapter with hard disk and CD-ROM devices.

3517

</li><li>-

3518

PL181 MultiMedia Card Interface with SD card.

3519

</li></ul>

3520

3521

<p>The ARM RealView Emulation baseboard is emulated with the following devices:

3522

</p>

3523

3524

<li>-

3525

ARM926E CPU

3526

</li><li>-

3527

ARM AMBA Generic/Distributed Interrupt Controller

3528

</li><li>-

3529

Four PL011 UARTs

3530

</li><li>-

3531

SMC 91c111 Ethernet adapter

3532

</li><li>-

3533

PL110 LCD controller

3534

</li><li>-

3535

PL050 KMI with PS/2 keyboard and mouse

3536

</li><li>-

3537

PCI host bridge

3538

</li><li>-

3539

PCI OHCI USB controller

3540

</li><li>-

3541

LSI53C895A PCI SCSI Host Bus Adapter with hard disk and CD-ROM devices

3542

</li><li>-

3543

PL181 MultiMedia Card Interface with SD card.

3544

</li></ul>

3545

3546

<p>The XScale-based clamshell PDA models ("Spitz", "Akita", "Borzoi"

3547

and "Terrier") emulation includes the following peripherals:

3548

</p>

3549

3550

<li>-

3551

Intel PXA270 System-on-chip (ARM V5TE core)

3552

</li><li>-

3553

NAND Flash memory

3554

</li><li>-

3555

IBM/Hitachi DSCM microdrive in a PXA PCMCIA slot - not in "Akita"

3556

</li><li>-

3557

On-chip OHCI USB controller

3558

</li><li>-

3559

On-chip LCD controller

3560

</li><li>-

3561

On-chip Real Time Clock

3562

</li><li>-

3563

TI ADS7846 touchscreen controller on SSP bus

3564

</li><li>-

3565

Maxim MAX1111 analog-digital converter on I<em>^2</em>C bus

3566

</li><li>-

3567

GPIO-connected keyboard controller and LEDs

3568

</li><li>-

3569

Secure Digital card connected to PXA MMC/SD host

3570

</li><li>-

3571

Three on-chip UARTs

3572

</li><li>-

3573

WM8750 audio CODEC on I<em>^2</em>C and I<em>^2</em>S busses

3574

</li></ul>

3575

3576

<p>A Linux 2.6 test image is available on the QEMU web site. More

3577

information is available in the QEMU mailing-list archive.

3578

</p>

3579

3580

3581

3582

3583

3584

3585

3586

3587

3588

3589

3590

3591

3592

3593

3594

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3595

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3596

3597

</tr></table>

3598

<h2 class="section"> 4.6 ColdFire System emulator </h2>

3599

3600

<p>Use the executable ‘<tt>qemu-system-m68k</tt>’ to simulate a ColdFire machine.

3601

The emulator is able to boot a uClinux kernel.

3602

</p>

3603

<p>The M5208EVB emulation includes the following devices:

3604

</p>

3605

3606

<li>-

3607

MCF5208 ColdFire V2 Microprocessor (ISA A+ with EMAC).

3608

</li><li>-

3609

Three Two on-chip UARTs.

3610

</li><li>-

3611

Fast Ethernet Controller (FEC)

3612

</li></ul>

3613

3614

<p>The AN5206 emulation includes the following devices:

3615

</p>

3616

3617

<li>-

3618

MCF5206 ColdFire V2 Microprocessor.

3619

</li><li>-

3620

Two on-chip UARTs.

3621

</li></ul>

3622

3623

3624

3625

3626

3627

3628

3629

3630

3631

3632

3633

3634

3635

3636

3637

3638

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3639

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3640

3641

</tr></table>

3642

<h1 class="chapter"> 5. QEMU User space emulator </h1>

3643

3644

3645

<tr><td align="left" valign="top"><a href="#SEC66">5.1 Supported Operating Systems</a></td><td>  </td><td align="left" valign="top">

3646

</td></tr>

3647

<tr><td align="left" valign="top"><a href="#SEC67">5.2 Linux User space emulator</a></td><td>  </td><td align="left" valign="top">

3648

</td></tr>

3649

<tr><td align="left" valign="top"><a href="#SEC72">5.3 Mac OS X/Darwin User space emulator</a></td><td>  </td><td align="left" valign="top">

3650

</td></tr>

3651

</table>

3652

3653

3654

3655

3656

3657

3658

3659

3660

3661

3662

3663

3664

3665

3666

3667

3668

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3669

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3670

3671

</tr></table>

3672

<h2 class="section"> 5.1 Supported Operating Systems </h2>

3673

3674

<p>The following OS are supported in user space emulation:

3675

</p>

3676

3677

<li>-

3678

Linux (referred as qemu-linux-user)

3679

</li><li>-

3680

Mac OS X/Darwin (referred as qemu-darwin-user)

3681

</li></ul>

3682

3683

3684

3685

3686

3687

3688

3689

3690

3691

3692

3693

3694

3695

3696

3697

3698

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3699

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3700

3701

</tr></table>

3702

<h2 class="section"> 5.2 Linux User space emulator </h2>

3703

3704

3705

<tr><td align="left" valign="top"><a href="#SEC68">5.2.1 Quick Start</a></td><td>  </td><td align="left" valign="top">

3706

</td></tr>

3707

<tr><td align="left" valign="top"><a href="#SEC69">5.2.2 Wine launch</a></td><td>  </td><td align="left" valign="top">

3708

</td></tr>

3709

<tr><td align="left" valign="top"><a href="#SEC70">5.2.3 Command line options</a></td><td>  </td><td align="left" valign="top">

3710

</td></tr>

3711

<tr><td align="left" valign="top"><a href="#SEC71">5.2.4 Other binaries</a></td><td>  </td><td align="left" valign="top">

3712

</td></tr>

3713

</table>

3714

3715

3716

3717

3718

3719

3720

3721

3722

3723

3724

3725

3726

3727

3728

3729

3730

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3731

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3732

3733

</tr></table>

3734

<h3 class="subsection"> 5.2.1 Quick Start </h3>

3735

3736

<p>In order to launch a Linux process, QEMU needs the process executable

3737

itself and all the target (x86) dynamic libraries used by it.

3738

</p>

3739

3740

<li> On x86, you can just try to launch any process by using the native

3741

libraries:

3742

3743

<table><tr><td> </td><td><pre class="example">qemu-i386 -L / /bin/ls

3744

</pre></td></tr></table>

3745

3746

<p><code>-L /</code> tells that the x86 dynamic linker must be searched with a

3747

‘<tt>/</tt>’ prefix.

3748

</p>

3749

</li><li> Since QEMU is also a linux process, you can launch qemu with

3750

qemu (NOTE: you can only do that if you compiled QEMU from the sources):

3751

3752

<table><tr><td> </td><td><pre class="example">qemu-i386 -L / qemu-i386 -L / /bin/ls

3753

</pre></td></tr></table>

3754

3755

</li><li> On non x86 CPUs, you need first to download at least an x86 glibc

3756

(‘<tt>qemu-runtime-i386-XXX-.tar.gz</tt>’ on the QEMU web page). Ensure that

3757

<code>LD_LIBRARY_PATH</code> is not set:

3758

3759

<table><tr><td> </td><td><pre class="example">unset LD_LIBRARY_PATH

3760

</pre></td></tr></table>

3761

3762

<p>Then you can launch the precompiled ‘<tt>ls</tt>’ x86 executable:

3763

</p>

3764

<table><tr><td> </td><td><pre class="example">qemu-i386 tests/i386/ls

3765

</pre></td></tr></table>

3766

<p>You can look at ‘<tt>qemu-binfmt-conf.sh</tt>’ so that

3767

QEMU is automatically launched by the Linux kernel when you try to

3768

launch x86 executables. It requires the <code>binfmt_misc</code> module in the

3769

Linux kernel.

3770

</p>

3771

</li><li> The x86 version of QEMU is also included. You can try weird things such as:

3772

<table><tr><td> </td><td><pre class="example">qemu-i386 /usr/local/qemu-i386/bin/qemu-i386 \

3773

/usr/local/qemu-i386/bin/ls-i386

3774

</pre></td></tr></table>

3775

3776

</li></ul>

3777

3778

3779

3780

3781

3782

3783

3784

3785

3786

3787

3788

3789

3790

3791

3792

3793

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3794

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3795

3796

</tr></table>

3797

<h3 class="subsection"> 5.2.2 Wine launch </h3>

3798

3799

3800

<li> Ensure that you have a working QEMU with the x86 glibc

3801

distribution (see previous section). In order to verify it, you must be

3802

able to do:

3803

3804

<table><tr><td> </td><td><pre class="example">qemu-i386 /usr/local/qemu-i386/bin/ls-i386

3805

</pre></td></tr></table>

3806

3807

</li><li> Download the binary x86 Wine install

3808

(‘<tt>qemu-XXX-i386-wine.tar.gz</tt>’ on the QEMU web page).

3809

3810

</li><li> Configure Wine on your account. Look at the provided script

3811

‘<tt>/usr/local/qemu-i386/bin/wine-conf.sh</tt>’. Your previous

3812

<code>${HOME}/.wine</code> directory is saved to <code>${HOME}/.wine.org</code>.

3813

3814

</li><li> Then you can try the example ‘<tt>putty.exe</tt>’:

3815

3816

<table><tr><td> </td><td><pre class="example">qemu-i386 /usr/local/qemu-i386/wine/bin/wine \

3817

/usr/local/qemu-i386/wine/c/Program\ Files/putty.exe

3818

</pre></td></tr></table>

3819

3820

</li></ul>

3821

3822

3823

3824

3825

3826

3827

3828

3829

3830

3831

3832

3833

3834

3835

3836

3837

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3838

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3839

3840

</tr></table>

3841

<h3 class="subsection"> 5.2.3 Command line options </h3>

3842

3843

<table><tr><td> </td><td><pre class="example">usage: qemu-i386 [-h] [-d] [-L path] [-s size] program [arguments...]

3844

</pre></td></tr></table>

3845

3846

3847

3848

<dd><p>Print the help

3849

</p></dd>

3850

3851

<dd><p>Set the x86 elf interpreter prefix (default=/usr/local/qemu-i386)

3852

</p></dd>

3853

3854

<dd><p>Set the x86 stack size in bytes (default=524288)

3855

</p></dd>

3856

</dl>

3857

3858

<p>Debug options:

3859

</p>

3860

3861

3862

<dd><p>Activate log (logfile=/tmp/qemu.log)

3863

</p></dd>

3864

<dt> ‘<samp>-p pagesize</samp>’</dt>

3865

<dd><p>Act as if the host page size was 'pagesize' bytes

3866

</p></dd>

3867

</dl>

3868

3869

3870

3871

3872

3873

3874

3875

3876

3877

3878

3879

3880

3881

3882

3883

3884

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3885

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3886

3887

</tr></table>

3888

<h3 class="subsection"> 5.2.4 Other binaries </h3>

3889

3890

<p><code>qemu-arm</code> is also capable of running ARM "Angel" semihosted ELF

3891

binaries (as implemented by the arm-elf and arm-eabi Newlib/GDB

3892

configurations), and arm-uclinux bFLT format binaries.

3893

</p>

3894

<p><code>qemu-m68k</code> is capable of running semihosted binaries using the BDM

3895

(m5xxx-ram-hosted.ld) or m68k-sim (sim.ld) syscall interfaces, and

3896

coldfire uClinux bFLT format binaries.

3897

</p>

3898

<p>The binary format is detected automatically.

3899

</p>

3900

3901

3902

3903

3904

3905

3906

3907

3908

3909

3910

3911

3912

3913

3914

3915

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3916

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3917

3918

</tr></table>

3919

<h2 class="section"> 5.3 Mac OS X/Darwin User space emulator </h2>

3920

3921

3922

<tr><td align="left" valign="top"><a href="#SEC73">5.3.1 Mac OS X/Darwin Status</a></td><td>  </td><td align="left" valign="top">

3923

</td></tr>

3924

<tr><td align="left" valign="top"><a href="#SEC74">5.3.2 Quick Start</a></td><td>  </td><td align="left" valign="top">

3925

</td></tr>

3926

<tr><td align="left" valign="top"><a href="#SEC75">5.3.3 Command line options</a></td><td>  </td><td align="left" valign="top">

3927

</td></tr>

3928

</table>

3929

3930

3931

3932

3933

3934

3935

3936

3937

3938

3939

3940

3941

3942

3943

3944

3945

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3946

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3947

3948

</tr></table>

3949

<h3 class="subsection"> 5.3.1 Mac OS X/Darwin Status </h3>

3950

3951

3952

<li>-

3953

target x86 on x86: Most apps (Cocoa and Carbon too) works. [1]

3954

</li><li>-

3955

target PowerPC on x86: Not working as the ppc commpage can't be mapped (yet!)

3956

</li><li>-

3957

target PowerPC on PowerPC: Most apps (Cocoa and Carbon too) works. [1]

3958

</li><li>-

3959

target x86 on PowerPC: most utilities work. Cocoa and Carbon apps are not yet supported.

3960

</li></ul>

3961

3962

<p>[1] If you're host commpage can be executed by qemu.

3963

</p>

3964

3965

3966

3967

3968

3969

3970

3971

3972

3973

3974

3975

3976

3977

3978

3979

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

3980

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

3981

3982

</tr></table>

3983

<h3 class="subsection"> 5.3.2 Quick Start </h3>

3984

3985

<p>In order to launch a Mac OS X/Darwin process, QEMU needs the process executable

3986

itself and all the target dynamic libraries used by it. If you don't have the FAT

3987

libraries (you're running Mac OS X/ppc) you'll need to obtain it from a Mac OS X

3988

CD or compile them by hand.

3989

</p>

3990

3991

<li> On x86, you can just try to launch any process by using the native

3992

libraries:

3993

3994

<table><tr><td> </td><td><pre class="example">qemu-i386 /bin/ls

3995

</pre></td></tr></table>

3996

3997

<p>or to run the ppc version of the executable:

3998

</p>

3999

<table><tr><td> </td><td><pre class="example">qemu-ppc /bin/ls

4000

</pre></td></tr></table>

4001

4002

</li><li> On ppc, you'll have to tell qemu where your x86 libraries (and dynamic linker)

4003

are installed:

4004

4005

<table><tr><td> </td><td><pre class="example">qemu-i386 -L /opt/x86_root/ /bin/ls

4006

</pre></td></tr></table>

4007

4008

<p><code>-L /opt/x86_root/</code> tells that the dynamic linker (dyld) path is in

4009

‘<tt>/opt/x86_root/usr/bin/dyld</tt>’.

4010

</p>

4011

</li></ul>

4012

4013

4014

4015

4016

4017

4018

4019

4020

4021

4022

4023

4024

4025

4026

4027

4028

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

4029

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

4030

4031

</tr></table>

4032

<h3 class="subsection"> 5.3.3 Command line options </h3>

4033

4034

<table><tr><td> </td><td><pre class="example">usage: qemu-i386 [-h] [-d] [-L path] [-s size] program [arguments...]

4035

</pre></td></tr></table>

4036

4037

4038

4039

<dd><p>Print the help

4040

</p></dd>

4041

4042

<dd><p>Set the library root path (default=/)

4043

</p></dd>

4044

4045

<dd><p>Set the stack size in bytes (default=524288)

4046

</p></dd>

4047

</dl>

4048

4049

<p>Debug options:

4050

</p>

4051

4052

4053

<dd><p>Activate log (logfile=/tmp/qemu.log)

4054

</p></dd>

4055

<dt> ‘<samp>-p pagesize</samp>’</dt>

4056

<dd><p>Act as if the host page size was 'pagesize' bytes

4057

</p></dd>

4058

</dl>

4059

4060

4061

4062

4063

4064

4065

4066

4067

4068

4069

4070

4071

4072

4073

4074

4075

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

4076

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

4077

4078

</tr></table>

4079

<h1 class="chapter"> 6. Compilation from the sources </h1>

4080

4081

4082

<tr><td align="left" valign="top"><a href="#SEC77">6.1 Linux/Unix</a></td><td>  </td><td align="left" valign="top">

4083

</td></tr>

4084

<tr><td align="left" valign="top"><a href="#SEC80">6.2 Windows</a></td><td>  </td><td align="left" valign="top">

4085

</td></tr>

4086

<tr><td align="left" valign="top"><a href="#SEC81">6.3 Cross compilation for Windows with Linux</a></td><td>  </td><td align="left" valign="top">

4087

</td></tr>

4088

4089

</td></tr>

4090

</table>

4091

4092

4093

4094

4095

4096

4097

4098

4099

4100

4101

4102

4103

4104

4105

4106

4107

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

4108

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

4109

4110

</tr></table>

4111

<h2 class="section"> 6.1 Linux/Unix </h2>

4112

4113

4114

4115

4116

4117

4118

4119

4120

4121

4122

4123

4124

4125

4126

4127

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

4128

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

4129

4130

</tr></table>

4131

<h3 class="subsection"> 6.1.1 Compilation </h3>

4132

4133

<p>First you must decompress the sources:

4134

</p><table><tr><td> </td><td><pre class="example">cd /tmp

4135

tar zxvf qemu-x.y.z.tar.gz

4136

cd qemu-x.y.z

4137

</pre></td></tr></table>

4138

4139

<p>Then you configure QEMU and build it (usually no options are needed):

4140

</p><table><tr><td> </td><td><pre class="example">./configure

4141

make

4142

</pre></td></tr></table>

4143

4144

<p>Then type as root user:

4145

</p><table><tr><td> </td><td><pre class="example">make install

4146

</pre></td></tr></table>

4147

<p>to install QEMU in ‘<tt>/usr/local</tt>’.

4148

</p>

4149

4150

4151

4152

4153

4154

4155

4156

4157

4158

4159

4160

4161

4162

4163

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

4164

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

4165

4166

</tr></table>

4167

<h3 class="subsection"> 6.1.2 GCC version </h3>

4168

4169

<p>In order to compile QEMU successfully, it is very important that you

4170

have the right tools. The most important one is gcc. On most hosts and

4171

in particular on x86 ones, <em>gcc 4.x is not supported</em>. If your

4172

Linux distribution includes a gcc 4.x compiler, you can usually

4173

install an older version (it is invoked by <code>gcc32</code> or

4174

<code>gcc34</code>). The QEMU configure script automatically probes for

4175

these older versions so that usually you don't have to do anything.

4176

</p>

4177

4178

4179

4180

4181

4182

4183

4184

4185

4186

4187

4188

4189

4190

4191

4192

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

4193

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

4194

4195

</tr></table>

4196

<h2 class="section"> 6.2 Windows </h2>

4197

4198

4199

<li> Install the current versions of MSYS and MinGW from

4200

<a href="http://www.mingw.org/">http://www.mingw.org/</a>. You can find detailed installation

4201

instructions in the download section and the FAQ.

4202

4203

</li><li> Download

4204

the MinGW development library of SDL 1.2.x

4205

(‘<tt>SDL-devel-1.2.x-mingw32.tar.gz</tt>’) from

4206

<a href="http://www.libsdl.org">http://www.libsdl.org</a>. Unpack it in a temporary place, and

4207

unpack the archive ‘<tt>i386-mingw32msvc.tar.gz</tt>’ in the MinGW tool

4208

directory. Edit the ‘<tt>sdl-config</tt>’ script so that it gives the

4209

correct SDL directory when invoked.

4210

4211

</li><li> Extract the current version of QEMU.

4212

4213

</li><li> Start the MSYS shell (file ‘<tt>msys.bat</tt>’).

4214

4215

</li><li> Change to the QEMU directory. Launch ‘<tt>./configure</tt>’ and

4216

‘<tt>make</tt>’. If you have problems using SDL, verify that

4217

‘<tt>sdl-config</tt>’ can be launched from the MSYS command line.

4218

4219

</li><li> You can install QEMU in ‘<tt>Program Files/Qemu</tt>’ by typing

4220

‘<tt>make install</tt>’. Don't forget to copy ‘<tt>SDL.dll</tt>’ in

4221

‘<tt>Program Files/Qemu</tt>’.

4222

4223

</li></ul>

4224

4225

4226

4227

4228

4229

4230

4231

4232

4233

4234

4235

4236

4237

4238

4239

4240

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

4241

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

4242

4243

</tr></table>

4244

<h2 class="section"> 6.3 Cross compilation for Windows with Linux </h2>

4245

4246

4247

<li>

4248

Install the MinGW cross compilation tools available at

4249

<a href="http://www.mingw.org/">http://www.mingw.org/</a>.

4250

4251

</li><li>

4252

Install the Win32 version of SDL (<a href="http://www.libsdl.org">http://www.libsdl.org</a>) by

4253

unpacking ‘<tt>i386-mingw32msvc.tar.gz</tt>’. Set up the PATH environment

4254

variable so that ‘<tt>i386-mingw32msvc-sdl-config</tt>’ can be launched by

4255

the QEMU configuration script.

4256

4257

</li><li>

4258

Configure QEMU for Windows cross compilation:

4259

<table><tr><td> </td><td><pre class="example">./configure --enable-mingw32

4260

</pre></td></tr></table>

4261

<p>If necessary, you can change the cross-prefix according to the prefix

4262

chosen for the MinGW tools with –cross-prefix. You can also use

4263

–prefix to set the Win32 install path.

4264

</p>

4265

</li><li> You can install QEMU in the installation directory by typing

4266

‘<tt>make install</tt>’. Don't forget to copy ‘<tt>SDL.dll</tt>’ in the

4267

installation directory.

4268

4269

</li></ul>

4270

4271

<p>Note: Currently, Wine does not seem able to launch

4272

QEMU for Win32.

4273

</p>

4274

4275

4276

4277

4278

4279

4280

4281

4282

4283

4284

4285

4286

4287

4288

4289

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

4290

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

4291

4292

</tr></table>

4293

4294

4295

<p>The Mac OS X patches are not fully merged in QEMU, so you should look

4296

at the QEMU mailing list archive to have all the necessary

4297

information.

4298

</p>

4299

4300

4301

4302

4303

4304

4305

4306

4307

4308

4309

4310

4311

4312

4313

4314

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

4315

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

4316

4317

</tr></table>

4318

<h1 class="chapter"> 7. Index </h1>

4319

4320

4321

4322

4323

4324

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

4325

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

4326

4327

</tr></table>

4328

<h1>Table of Contents</h1>

4329

4330

4331

4332

<li><a name="TOC1" href="#SEC1">1. Introduction</a>

4333

4334

<li><a name="TOC2" href="#SEC2">1.1 Features</a></li>

4335

</ul></li>

4336

<li><a name="TOC3" href="#SEC3">2. Installation</a>

4337

4338

<li><a name="TOC4" href="#SEC4">2.1 Linux</a></li>

4339

<li><a name="TOC5" href="#SEC5">2.2 Windows</a></li>

4340

4341

</ul></li>

4342

<li><a name="TOC7" href="#SEC7">3. QEMU PC System emulator</a>

4343

4344

<li><a name="TOC8" href="#SEC8">3.1 Introduction</a></li>

4345

<li><a name="TOC9" href="#SEC9">3.2 Quick Start</a></li>

4346

<li><a name="TOC10" href="#SEC10">3.3 Invocation</a></li>

4347

4348

<li><a name="TOC12" href="#SEC12">3.5 QEMU Monitor</a>

4349

4350

<li><a name="TOC13" href="#SEC13">3.5.1 Commands</a></li>

4351

<li><a name="TOC14" href="#SEC14">3.5.2 Integer expressions</a></li>

4352

</ul></li>

4353

<li><a name="TOC15" href="#SEC15">3.6 Disk Images</a>

4354

4355

<li><a name="TOC16" href="#SEC16">3.6.1 Quick start for disk image creation</a></li>

4356

<li><a name="TOC17" href="#SEC17">3.6.2 Snapshot mode</a></li>

4357

<li><a name="TOC18" href="#SEC18">3.6.3 VM snapshots</a></li>

4358

<li><a name="TOC19" href="#SEC19">3.6.4 <code>qemu-img</code> Invocation</a></li>

4359

<li><a name="TOC20" href="#SEC20">3.6.5 Using host drives</a>

4360

4361

<li><a name="TOC21" href="#SEC21">3.6.5.1 Linux</a></li>

4362

<li><a name="TOC22" href="#SEC22">3.6.5.2 Windows</a></li>

4363

4364

</ul></li>

4365

<li><a name="TOC24" href="#SEC24">3.6.6 Virtual FAT disk images</a></li>

4366

</ul></li>

4367

<li><a name="TOC25" href="#SEC25">3.7 Network emulation</a>

4368

4369

<li><a name="TOC26" href="#SEC26">3.7.1 VLANs</a></li>

4370

<li><a name="TOC27" href="#SEC27">3.7.2 Using TAP network interfaces</a>

4371

4372

<li><a name="TOC28" href="#SEC28">3.7.2.1 Linux host</a></li>

4373

<li><a name="TOC29" href="#SEC29">3.7.2.2 Windows host</a></li>

4374

</ul></li>

4375

<li><a name="TOC30" href="#SEC30">3.7.3 Using the user mode network stack</a></li>

4376

<li><a name="TOC31" href="#SEC31">3.7.4 Connecting VLANs between QEMU instances</a></li>

4377

</ul></li>

4378

<li><a name="TOC32" href="#SEC32">3.8 Direct Linux Boot</a></li>

4379

<li><a name="TOC33" href="#SEC33">3.9 USB emulation</a>

4380

4381

<li><a name="TOC34" href="#SEC34">3.9.1 Connecting USB devices</a></li>

4382

<li><a name="TOC35" href="#SEC35">3.9.2 Using host USB devices on a Linux host</a></li>

4383

</ul></li>

4384

<li><a name="TOC36" href="#SEC36">3.10 VNC security</a>

4385

4386

<li><a name="TOC37" href="#SEC37">3.10.1 Without passwords</a></li>

4387

<li><a name="TOC38" href="#SEC38">3.10.2 With passwords</a></li>

4388

<li><a name="TOC39" href="#SEC39">3.10.3 With x509 certificates</a></li>

4389

<li><a name="TOC40" href="#SEC40">3.10.4 With x509 certificates and client verification</a></li>

4390

<li><a name="TOC41" href="#SEC41">3.10.5 With x509 certificates, client verification and passwords</a></li>

4391

<li><a name="TOC42" href="#SEC42">3.10.6 Generating certificates for VNC</a>

4392

4393

<li><a name="TOC43" href="#SEC43">3.10.6.1 Setup the Certificate Authority</a></li>

4394

<li><a name="TOC44" href="#SEC44">3.10.6.2 Issuing server certificates</a></li>

4395

<li><a name="TOC45" href="#SEC45">3.10.6.3 Issuing client certificates</a></li>

4396

</ul>

4397

</li>

4398

</ul></li>

4399

<li><a name="TOC46" href="#SEC46">3.11 GDB usage</a></li>

4400

<li><a name="TOC47" href="#SEC47">3.12 Target OS specific information</a>

4401

4402

<li><a name="TOC48" href="#SEC48">3.12.1 Linux</a></li>

4403

<li><a name="TOC49" href="#SEC49">3.12.2 Windows</a>

4404

4405

<li><a name="TOC50" href="#SEC50">3.12.2.1 SVGA graphic modes support</a></li>

4406

<li><a name="TOC51" href="#SEC51">3.12.2.2 CPU usage reduction</a></li>

4407

<li><a name="TOC52" href="#SEC52">3.12.2.3 Windows 2000 disk full problem</a></li>

4408

<li><a name="TOC53" href="#SEC53">3.12.2.4 Windows 2000 shutdown</a></li>

4409

<li><a name="TOC54" href="#SEC54">3.12.2.5 Share a directory between Unix and Windows</a></li>

4410

<li><a name="TOC55" href="#SEC55">3.12.2.6 Windows XP security problem</a></li>

4411

</ul></li>

4412

<li><a name="TOC56" href="#SEC56">3.12.3 MS-DOS and FreeDOS</a>

4413

4414

<li><a name="TOC57" href="#SEC57">3.12.3.1 CPU usage reduction</a></li>

4415

</ul>

4416

</li>

4417

</ul>

4418

</li>

4419

</ul></li>

4420

<li><a name="TOC58" href="#SEC58">4. QEMU System emulator for non PC targets</a>

4421

4422

<li><a name="TOC59" href="#SEC59">4.1 QEMU PowerPC System emulator</a></li>

4423

<li><a name="TOC60" href="#SEC60">4.2 Sparc32 System emulator</a></li>

4424

<li><a name="TOC61" href="#SEC61">4.3 Sparc64 System emulator</a></li>

4425

<li><a name="TOC62" href="#SEC62">4.4 MIPS System emulator</a></li>

4426

<li><a name="TOC63" href="#SEC63">4.5 ARM System emulator</a></li>

4427

<li><a name="TOC64" href="#SEC64">4.6 ColdFire System emulator</a></li>

4428

</ul></li>

4429

<li><a name="TOC65" href="#SEC65">5. QEMU User space emulator</a>

4430

4431

<li><a name="TOC66" href="#SEC66">5.1 Supported Operating Systems</a></li>

4432

<li><a name="TOC67" href="#SEC67">5.2 Linux User space emulator</a>

4433

4434

<li><a name="TOC68" href="#SEC68">5.2.1 Quick Start</a></li>

4435

<li><a name="TOC69" href="#SEC69">5.2.2 Wine launch</a></li>

4436

<li><a name="TOC70" href="#SEC70">5.2.3 Command line options</a></li>

4437

<li><a name="TOC71" href="#SEC71">5.2.4 Other binaries</a></li>

4438

</ul></li>

4439

<li><a name="TOC72" href="#SEC72">5.3 Mac OS X/Darwin User space emulator</a>

4440

4441

<li><a name="TOC73" href="#SEC73">5.3.1 Mac OS X/Darwin Status</a></li>

4442

<li><a name="TOC74" href="#SEC74">5.3.2 Quick Start</a></li>

4443

<li><a name="TOC75" href="#SEC75">5.3.3 Command line options</a></li>

4444

</ul>

4445

</li>

4446

</ul></li>

4447

<li><a name="TOC76" href="#SEC76">6. Compilation from the sources</a>

4448

4449

<li><a name="TOC77" href="#SEC77">6.1 Linux/Unix</a>

4450

4451

<li><a name="TOC78" href="#SEC78">6.1.1 Compilation</a></li>

4452

<li><a name="TOC79" href="#SEC79">6.1.2 GCC version</a></li>

4453

</ul></li>

4454

<li><a name="TOC80" href="#SEC80">6.2 Windows</a></li>

4455

<li><a name="TOC81" href="#SEC81">6.3 Cross compilation for Windows with Linux</a></li>

4456

4457

</ul></li>

4458

<li><a name="TOC83" href="#SEC83">7. Index</a></li>

4459

</ul>

4460

</div>

4461

4462

4463

4464

4465

<td valign="middle" align="left">[<a href="#SEC_Contents" title="Table of contents">Contents</a>]</td>

4466

<td valign="middle" align="left">[<a href="#SEC83" title="Index">Index</a>]</td>

4467

4468

</tr></table>

4469

<h1>About This Document</h1>

4470

<p>

4471

This document was generated by <em>Soren Hansen</em> on <em>December, 4 2007</em> using <a href="http://www.nongnu.org/texi2html/"><em>texi2html 1.78</em></a>.

4472

</p>

4473

<p>

4474

The buttons in the navigation panels have the following meaning:

4475

</p>

4476

4477

<tr>

4478

<th> Button </th>

4479

4480

4481

4482

</tr>

4483

<tr>

4484

4485

4486

<td>Previous section in reading order</td>

4487

4488

</tr>

4489

<tr>

4490

4491

<td align="center">Forward</td>

4492

<td>Next section in reading order</td>

4493

4494

</tr>

4495

<tr>

4496

4497

<td align="center">FastBack</td>

4498

<td>Beginning of this chapter or previous chapter</td>

4499

4500

</tr>

4501

<tr>

4502

4503

4504

<td>Up section</td>

4505

4506

</tr>

4507

<tr>

4508

4509

<td align="center">FastForward</td>

4510

<td>Next chapter</td>

4511

4512

</tr>

4513

<tr>

4514

4515

4516

<td>Cover (top) of document</td>

4517

4518

</tr>

4519

<tr>

4520

<td align="center"> [Contents] </td>

4521

<td align="center">Contents</td>

4522

<td>Table of contents</td>

4523

4524

</tr>

4525

<tr>

4526

<td align="center"> [Index] </td>

4527

<td align="center">Index</td>

4528

<td>Index</td>

4529

4530

</tr>

4531

<tr>

4532

4533

<td align="center">About</td>

4534

<td>About (help)</td>

4535

4536

</tr>

4537

</table>

4538

4539

<p>

4540

where the <strong> Example </strong> assumes that the current position is at <strong> Subsubsection One-Two-Three </strong> of a document of the following structure:

4541

</p>

4542

4543

<ul>

4544

<li> 1. Section One

4545

<ul>

4546

<li>1.1 Subsection One-One

4547

<ul>

4548

4549

</ul>

4550

</li>

4551

<li>1.2 Subsection One-Two

4552

<ul>

4553

<li>1.2.1 Subsubsection One-Two-One</li>

4554

<li>1.2.2 Subsubsection One-Two-Two</li>

4555

<li>1.2.3 Subsubsection One-Two-Three    

4556

4557

<li>1.2.4 Subsubsection One-Two-Four</li>

4558

</ul>

4559

</li>

4560

<li>1.3 Subsection One-Three

4561

<ul>

4562

4563

</ul>

4564

</li>

4565

<li>1.4 Subsection One-Four</li>

4566

</ul>

4567

</li>

4568

</ul>

4569

4570

4571

<p>

4572

4573

This document was generated by <em>Soren Hansen</em> on <em>December, 4 2007</em> using <a href="http://www.nongnu.org/texi2html/"><em>texi2html 1.78</em></a>.

4574

</font>

4575

<br>

4576

4577

</p>

4578

</body>

4579

</html>