DOCSLIB.ORG

QEMU Emulator User Documentation I

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

QEMU Emulator User Documentation i Table of Contents 1 Introduction ::::::::::::::::::::::::::::::::::::: 1 1.1 Features :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 2 Installation::::::::::::::::::::::::::::::::::::::: 3 2.1 Linux :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 3 2.2 Windows ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 3 2.3 Mac OS X:::::::::::::::::::::::::::::::::::::::::::::::::::::: 3 3 QEMU PC System emulator ::::::::::::::::::: 4 3.1 Introduction :::::::::::::::::::::::::::::::::::::::::::::::::::: 4 3.2 Quick Start::::::::::::::::::::::::::::::::::::::::::::::::::::: 4 3.3 Invocation :::::::::::::::::::::::::::::::::::::::::::::::::::::: 5 3.4 Keys in the graphical frontends :::::::::::::::::::::::::::::::: 51 3.5 Keys in the character backend multiplexer ::::::::::::::::::::: 52 3.6 QEMU Monitor ::::::::::::::::::::::::::::::::::::::::::::::: 52 3.6.1 Commands ::::::::::::::::::::::::::::::::::::::::::::::: 52 3.6.2 Integer expressions:::::::::::::::::::::::::::::::::::::::: 63 3.7 Disk Images ::::::::::::::::::::::::::::::::::::::::::::::::::: 63 3.7.1 Quick start for disk image creation:::::::::::::::::::::::: 64 3.7.2 Snapshot mode ::::::::::::::::::::::::::::::::::::::::::: 64 3.7.3 VM snapshots :::::::::::::::::::::::::::::::::::::::::::: 64 3.7.4 qemu-img Invocation:::::::::::::::::::::::::::::::::::::: 65 3.7.5 qemu-nbd Invocation:::::::::::::::::::::::::::::::::::::: 73 3.7.6 qemu-ga Invocation ::::::::::::::::::::::::::::::::::::::: 75 3.7.7 Disk image file formats ::::::::::::::::::::::::::::::::::: 77 3.7.7.1 Read-only formats ::::::::::::::::::::::::::::::::::: 80 3.7.8 Using host drives ::::::::::::::::::::::::::::::::::::::::: 80 3.7.8.1 Linux:::::::::::::::::::::::::::::::::::::::::::::::: 81 3.7.8.2 Windows :::::::::::::::::::::::::::::::::::::::::::: 81 3.7.8.3 Mac OS X ::::::::::::::::::::::::::::::::::::::::::: 81 3.7.9 Virtual FAT disk images :::::::::::::::::::::::::::::::::: 81 3.7.10 NBD access ::::::::::::::::::::::::::::::::::::::::::::: 82 3.7.11 Sheepdog disk images:::::::::::::::::::::::::::::::::::: 82 3.7.12 iSCSI LUNs ::::::::::::::::::::::::::::::::::::::::::::: 83 3.7.13 GlusterFS disk images ::::::::::::::::::::::::::::::::::: 85 3.7.14 Secure Shell (ssh) disk images:::::::::::::::::::::::::::: 85 3.8 Network emulation :::::::::::::::::::::::::::::::::::::::::::: 86 3.8.1 VLANs ::::::::::::::::::::::::::::::::::::::::::::::::::: 86 3.8.2 Using TAP network interfaces::::::::::::::::::::::::::::: 86 3.8.2.1 Linux host ::::::::::::::::::::::::::::::::::::::::::: 86 3.8.2.2 Windows host ::::::::::::::::::::::::::::::::::::::: 87 3.8.3 Using the user mode network stack:::::::::::::::::::::::: 87 ii 3.8.4 Connecting VLANs between QEMU instances ::::::::::::: 87 3.9 Other Devices ::::::::::::::::::::::::::::::::::::::::::::::::: 87 3.9.1 Inter-VM Shared Memory device:::::::::::::::::::::::::: 87 3.9.1.1 Migration with ivshmem ::::::::::::::::::::::::::::: 88 3.9.1.2 ivshmem and hugepages:::::::::::::::::::::::::::::: 88 3.10 Direct Linux Boot :::::::::::::::::::::::::::::::::::::::::::: 88 3.11 USB emulation ::::::::::::::::::::::::::::::::::::::::::::::: 89 3.11.1 Connecting USB devices ::::::::::::::::::::::::::::::::: 89 3.11.2 Using host USB devices on a Linux host ::::::::::::::::: 90 3.12 VNC security :::::::::::::::::::::::::::::::::::::::::::::::: 90 3.12.1 Without passwords :::::::::::::::::::::::::::::::::::::: 91 3.12.2 With passwords ::::::::::::::::::::::::::::::::::::::::: 91 3.12.3 With x509 certificates ::::::::::::::::::::::::::::::::::: 91 3.12.4 With x509 certificates and client verification ::::::::::::: 91 3.12.5 With x509 certificates, client verification and passwords :: 91 3.12.6 With SASL authentication::::::::::::::::::::::::::::::: 92 3.12.7 With x509 certificates and SASL authentication:::::::::: 92 3.12.8 Generating certificates for VNC:::::::::::::::::::::::::: 92 3.12.8.1 Setup the Certificate Authority ::::::::::::::::::::: 92 3.12.8.2 Issuing server certificates:::::::::::::::::::::::::::: 93 3.12.8.3 Issuing client certificates :::::::::::::::::::::::::::: 93 3.12.9 Configuring SASL mechanisms::::::::::::::::::::::::::: 94 3.13 GDB usage::::::::::::::::::::::::::::::::::::::::::::::::::: 94 3.14 Target OS specific information:::::::::::::::::::::::::::::::: 95 3.14.1 Linux ::::::::::::::::::::::::::::::::::::::::::::::::::: 96 3.14.2 Windows :::::::::::::::::::::::::::::::::::::::::::::::: 96 3.14.2.1 SVGA graphic modes support::::::::::::::::::::::: 96 3.14.2.2 CPU usage reduction ::::::::::::::::::::::::::::::: 96 3.14.2.3 Windows 2000 disk full problem::::::::::::::::::::: 96 3.14.2.4 Windows 2000 shutdown :::::::::::::::::::::::::::: 96 3.14.2.5 Share a directory between Unix and Windows ::::::: 97 3.14.2.6 Windows XP security problem :::::::::::::::::::::: 97 3.14.3 MS-DOS and FreeDOS :::::::::::::::::::::::::::::::::: 97 3.14.3.1 CPU usage reduction ::::::::::::::::::::::::::::::: 97 4 QEMU System emulator for non PC targets :: 98 4.1 PowerPC System emulator::::::::::::::::::::::::::::::::::::: 98 4.2 Sparc32 System emulator :::::::::::::::::::::::::::::::::::::: 99 4.3 Sparc64 System emulator ::::::::::::::::::::::::::::::::::::: 100 4.4 MIPS System emulator ::::::::::::::::::::::::::::::::::::::: 100 4.5 ARM System emulator ::::::::::::::::::::::::::::::::::::::: 101 4.6 ColdFire System emulator :::::::::::::::::::::::::::::::::::: 104 4.7 Cris System emulator::::::::::::::::::::::::::::::::::::::::: 105 4.8 Microblaze System emulator :::::::::::::::::::::::::::::::::: 105 4.9 SH4 System emulator :::::::::::::::::::::::::::::::::::::::: 105 4.10 Xtensa System emulator::::::::::::::::::::::::::::::::::::: 105 iii 5 QEMU User space emulator ::::::::::::::::: 106 5.1 Supported Operating Systems :::::::::::::::::::::::::::::::: 106 5.2 Linux User space emulator:::::::::::::::::::::::::::::::::::: 106 5.2.1 Quick Start ::::::::::::::::::::::::::::::::::::::::::::: 106 5.2.2 Wine launch::::::::::::::::::::::::::::::::::::::::::::: 106 5.2.3 Command line options ::::::::::::::::::::::::::::::::::: 107 5.2.4 Other binaries ::::::::::::::::::::::::::::::::::::::::::: 108 5.3 BSD User space emulator::::::::::::::::::::::::::::::::::::: 108 5.3.1 BSD Status ::::::::::::::::::::::::::::::::::::::::::::: 108 5.3.2 Quick Start ::::::::::::::::::::::::::::::::::::::::::::: 108 5.3.3 Command line options ::::::::::::::::::::::::::::::::::: 108 6 Compilation from the sources:::::::::::::::: 110 6.1 Linux/Unix :::::::::::::::::::::::::::::::::::::::::::::::::: 110 6.1.1 Compilation ::::::::::::::::::::::::::::::::::::::::::::: 110 6.2 Windows ::::::::::::::::::::::::::::::::::::::::::::::::::::: 110 6.3 Cross compilation for Windows with Linux ::::::::::::::::::: 110 6.4 Mac OS X ::::::::::::::::::::::::::::::::::::::::::::::::::: 111 6.5 Make targets ::::::::::::::::::::::::::::::::::::::::::::::::: 112 Appendix A License :::::::::::::::::::::::::::: 113 Appendix B Index :::::::::::::::::::::::::::::: 114 B.1 Concept Index ::::::::::::::::::::::::::::::::::::::::::::::: 114 B.2 Function Index :::::::::::::::::::::::::::::::::::::::::::::: 114 B.3 Keystroke Index ::::::::::::::::::::::::::::::::::::::::::::: 117 B.4 Program Index::::::::::::::::::::::::::::::::::::::::::::::: 118 B.5 Data Type Index :::::::::::::::::::::::::::::::::::::::::::: 118 B.6 Variable Index ::::::::::::::::::::::::::::::::::::::::::::::: 118 1 1 Introduction 1.1 Features QEMU is a FAST! processor emulator using dynamic translation to achieve good emulation speed. QEMU has two operating modes: • Full system emulation. In this mode, QEMU emulates a full system (for example a PC), including one or several processors and various peripherals. It can be used to launch different Operating Systems without rebooting the PC or to debug system code. • User mode emulation. In this mode, QEMU can launch processes compiled for one CPU on another CPU. It can be used to launch the Wine Windows API emulator (http://www.winehq.org) or to ease cross-compilation and cross-debugging. QEMU can run without a host kernel driver and yet gives acceptable performance. For system emulation, the following hardware targets are supported: • PC (x86 or x86 64 processor) • ISA PC (old style PC without PCI bus) • PREP (PowerPC processor) • G3 Beige PowerMac (PowerPC processor) • Mac99 PowerMac (PowerPC processor, in progress) • Sun4m/Sun4c/Sun4d (32-bit Sparc processor) • Sun4u/Sun4v (64-bit Sparc processor, in progress) • Malta board (32-bit and 64-bit MIPS processors) • MIPS Magnum (64-bit MIPS processor) • ARM Integrator/CP (ARM) • ARM Versatile baseboard (ARM) • ARM RealView Emulation/Platform baseboard (ARM) • Spitz, Akita, Borzoi, Terrier and Tosa PDAs (PXA270 processor) • Luminary Micro LM3S811EVB (ARM Cortex-M3) • Luminary Micro LM3S6965EVB (ARM Cortex-M3) • Freescale MCF5208EVB (ColdFire V2). • Arnewsh MCF5206 evaluation board (ColdFire V2). • Palm Tungsten|E PDA (OMAP310 processor) • N800 and N810 tablets (OMAP2420 processor) • MusicPal (MV88W8618 ARM processor) • Gumstix "Connex" and "Verdex" motherboards (PXA255/270). • Siemens SX1 smartphone (OMAP310 processor) • AXIS-Devboard88 (CRISv32 ETRAX-FS). • Petalogix Spartan 3aDSP1800 MMU ref design (MicroBlaze). • Avnet LX60/LX110/LX200 boards (Xtensa) 2 For user emulation, x86 (32 and 64 bit), PowerPC (32 and 64 bit), ARM, MIPS (32 bit only), Sparc (32 and 64 bit), Alpha, ColdFire(m68k), CRISv32 and MicroBlaze CPUs are supported. 3 2 Installation If you want to compile QEMU yourself, see Chapter 6 [compilation],
Recommended publications
  • DAY ONE: Vsrx on KVM Verma & Kat - and Saves Tme Saves and Juniper Techlibrary Juniper Writen Writen in Tandem with the Juniper

    DAY ONE: Vsrx on KVM Verma & Kat - and Saves Tme Saves and Juniper Techlibrary Juniper Writen Writen in Tandem with the Juniper

    DAY ONE: vSRX on KVM Day One: vSRX on KVM is for network administrators, network architects, or engineers in- terested in quickly startng to use the Juniper Networks vSRX Virtual Firewall. Any tme you ONE: DAY need to design and test diferent topology use cases, train yourself or others, or even practce DAY ONE: vSRX on KVM certfcaton exams, this book covers such usage with step-by-step instructons and practcal examples. vSRX ON KVM Day One: vSRX on KVM requires Basic networking knowledge and a general understanding of the TCP/IP protocol suite, Linux systems, and Ubuntu. Writen in tandem with the Juniper vSRX documentaton, it curates links and tutorials with the Juniper TechLiBrary and saves tme for vSRX users by coordinatng deployment steps with the TechLibrary’s archives. Learn how to deploy vSRX instances today! IT’S DAY ONE AND YOU HAVE A JOB TO DO, SO LEARN HOW TO: Confgure the vSRX in a KVM environment Install vSRX’s prerequisite packages and confgure and deploy an instance of vSRX on KVM. and build lab topologies on day one. Create a single instance topology and then a mult-device topology using two vSRX instances. Design topologies for diferent use cases. Complete the three challenge topologies. Troubleshoot vSRX operatons. Verma & Kat ISBN 978-1941441893 5 1 6 0 0 By Rahul Verma & Madhavi Kat Juniper Networks Books are focused on network reliaBility and efficiency. Peruse the complete liBrary at www.juniper.net/books. 9 781941 441893 DAY ONE: vSRX on KVM Day One: vSRX on KVM is for network administrators, network architects, or engineers in- terested in quickly startng to use the Juniper Networks vSRX Virtual Firewall.
  • Validated Products List, 1995 No. 3: Programming Languages, Database

    Validated Products List, 1995 No. 3: Programming Languages, Database

    NISTIR 5693 (Supersedes NISTIR 5629) VALIDATED PRODUCTS LIST Volume 1 1995 No. 3 Programming Languages Database Language SQL Graphics POSIX Computer Security Judy B. Kailey Product Data - IGES Editor U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Computer Systems Laboratory Software Standards Validation Group Gaithersburg, MD 20899 July 1995 QC 100 NIST .056 NO. 5693 1995 NISTIR 5693 (Supersedes NISTIR 5629) VALIDATED PRODUCTS LIST Volume 1 1995 No. 3 Programming Languages Database Language SQL Graphics POSIX Computer Security Judy B. Kailey Product Data - IGES Editor U.S. DEPARTMENT OF COMMERCE Technology Administration National Institute of Standards and Technology Computer Systems Laboratory Software Standards Validation Group Gaithersburg, MD 20899 July 1995 (Supersedes April 1995 issue) U.S. DEPARTMENT OF COMMERCE Ronald H. Brown, Secretary TECHNOLOGY ADMINISTRATION Mary L. Good, Under Secretary for Technology NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY Arati Prabhakar, Director FOREWORD The Validated Products List (VPL) identifies information technology products that have been tested for conformance to Federal Information Processing Standards (FIPS) in accordance with Computer Systems Laboratory (CSL) conformance testing procedures, and have a current validation certificate or registered test report. The VPL also contains information about the organizations, test methods and procedures that support the validation programs for the FIPS identified in this document. The VPL includes computer language processors for programming languages COBOL, Fortran, Ada, Pascal, C, M[UMPS], and database language SQL; computer graphic implementations for GKS, COM, PHIGS, and Raster Graphics; operating system implementations for POSIX; Open Systems Interconnection implementations; and computer security implementations for DES, MAC and Key Management.
  • Oracle Solaris Administration Basic Administration

    Oracle Solaris Administration Basic Administration

    Oracle® Solaris Administration: Basic Administration Part No: E29492–03 June 2013 Copyright © 1998, 2013, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT END USERS. Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including anyoperating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications.
  • Sun Ultratm 5 Workstation Just the Facts

    Sun Ultratm 5 Workstation Just the Facts

    Sun UltraTM 5 Workstation Just the Facts Copyrights 1999 Sun Microsystems, Inc. All Rights Reserved. Sun, Sun Microsystems, the Sun logo, Ultra, PGX, PGX24, Solaris, Sun Enterprise, SunClient, UltraComputing, Catalyst, SunPCi, OpenWindows, PGX32, VIS, Java, JDK, XGL, XIL, Java 3D, SunVTS, ShowMe, ShowMe TV, SunForum, Java WorkShop, Java Studio, AnswerBook, AnswerBook2, Sun Enterprise SyMON, Solstice, Solstice AutoClient, ShowMe How, SunCD, SunCD 2Plus, Sun StorEdge, SunButtons, SunDials, SunMicrophone, SunFDDI, SunLink, SunHSI, SunATM, SLC, ELC, IPC, IPX, SunSpectrum, JavaStation, SunSpectrum Platinum, SunSpectrum Gold, SunSpectrum Silver, SunSpectrum Bronze, SunVIP, SunSolve, and SunSolve EarlyNotifier are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the United States and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the United States and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. UNIX is a registered trademark in the United States and other countries, exclusively licensed through X/Open Company, Ltd. OpenGL is a registered trademark of Silicon Graphics, Inc. Display PostScript and PostScript are trademarks of Adobe Systems, Incorporated, which may be registered in certain jurisdictions. Netscape is a trademark of Netscape Communications Corporation. DLT is claimed as a trademark of Quantum Corporation in the United States and other countries. Just the Facts May 1999 Positioning The Sun UltraTM 5 Workstation Figure 1. The Ultra 5 workstation The Sun UltraTM 5 workstation is an entry-level workstation based upon the 333- and 360-MHz UltraSPARCTM-IIi processors. The Ultra 5 is Sun’s lowest-priced workstation, designed to meet the needs of price-sensitive and volume-purchase customers in the personal workstation market without sacrificing performance.
  • Enhancing the Accuracy of Synthetic File System Benchmarks Salam Farhat Nova Southeastern University, Salalimo@Gmail.Com

    Enhancing the Accuracy of Synthetic File System Benchmarks Salam Farhat Nova Southeastern University, [email protected]

    Nova Southeastern University NSUWorks CEC Theses and Dissertations College of Engineering and Computing 2017 Enhancing the Accuracy of Synthetic File System Benchmarks Salam Farhat Nova Southeastern University, [email protected] This document is a product of extensive research conducted at the Nova Southeastern University College of Engineering and Computing. For more information on research and degree programs at the NSU College of Engineering and Computing, please click here. Follow this and additional works at: https://nsuworks.nova.edu/gscis_etd Part of the Computer Sciences Commons Share Feedback About This Item NSUWorks Citation Salam Farhat. 2017. Enhancing the Accuracy of Synthetic File System Benchmarks. Doctoral dissertation. Nova Southeastern University. Retrieved from NSUWorks, College of Engineering and Computing. (1003) https://nsuworks.nova.edu/gscis_etd/1003. This Dissertation is brought to you by the College of Engineering and Computing at NSUWorks. It has been accepted for inclusion in CEC Theses and Dissertations by an authorized administrator of NSUWorks. For more information, please contact [email protected]. Enhancing the Accuracy of Synthetic File System Benchmarks by Salam Farhat A dissertation submitted in partial fulfillment of the requirements for the degree of Doctor in Philosophy in Computer Science College of Engineering and Computing Nova Southeastern University 2017 We hereby certify that this dissertation, submitted by Salam Farhat, conforms to acceptable standards and is fully adequate in scope and quality to fulfill the dissertation requirements for the degree of Doctor of Philosophy. _____________________________________________ ________________ Gregory E. Simco, Ph.D. Date Chairperson of Dissertation Committee _____________________________________________ ________________ Sumitra Mukherjee, Ph.D. Date Dissertation Committee Member _____________________________________________ ________________ Francisco J.
  • HTTP-FUSE Xenoppix

    HTTP-FUSE Xenoppix

    HTTP-FUSE Xenoppix Kuniyasu Suzaki† Toshiki Yagi† Kengo Iijima† Kenji Kitagawa†† Shuichi Tashiro††† National Institute of Advanced Industrial Science and Technology† Alpha Systems Inc.†† Information-Technology Promotion Agency, Japan††† {k.suzaki,yagi-toshiki,k-iijima}@aist.go.jp [email protected], [email protected] Abstract a CD-ROM. Furthermore it requires remaking the entire CD-ROM when a bit of data is up- dated. The other solution is a Virtual Machine We developed “HTTP-FUSE Xenoppix” which which enables us to install many OSes and ap- boots Linux, Plan9, and NetBSD on Virtual plications easily. However, that requires in- Machine Monitor “Xen” with a small bootable stalling virtual machine software. (6.5MB) CD-ROM. The bootable CD-ROM in- cludes boot loader, kernel, and miniroot only We have developed “Xenoppix” [1], which and most part of files are obtained via Internet is a combination of CD/DVD bootable Linux with network loopback device HTTP-FUSE “KNOPPIX” [2] and Virtual Machine Monitor CLOOP. It is made from cloop (Compressed “Xen” [3, 4]. Xenoppix boots Linux (KNOP- Loopback block device) and FUSE (Filesys- PIX) as Host OS and NetBSD or Plan9 as Guest tem USErspace). HTTP-FUSE CLOOP can re- OS with a bootable DVD only. KNOPPIX construct a block device from many small block is advanced in automatic device detection and files of HTTP servers. In this paper we describe driver integration. It prepares the Xen environ- the detail of the implementation and its perfor- ment and Guest OSes don’t need to worry about mance. lack of device drivers.
  • SPARC/CPU-5V Technical Reference Manual

    SPARC/CPU-5V Technical Reference Manual

    SPARC/CPU-5V Technical Reference Manual P/N 203651 Edition 5.0 February 1998 FORCE COMPUTERS Inc./GmbH All Rights Reserved This document shall not be duplicated, nor its contents used for any purpose, unless express permission has been granted. Copyright by FORCE COMPUTERS CPU-5V Technical Reference Manual Table of Contents SECTION 1 INTRODUCTION ....................................................................................1 1. Getting Started ..................................................................................................................................... 1 1.1. The SPARC CPU-5V Technical Reference Manual Set.................................................................. 1 1.2. Summary of the SPARC CPU-5V ................................................................................................... 2 1.3. Specifications ................................................................................................................................... 4 1.3.1. Ordering Information........................................................................................................... 6 1.4. History of the Manual ...................................................................................................................... 9 SECTION 2 INSTALLATION ....................................................................................11 2. Introduction........................................................................................................................................ 11 2.1. Caution
  • How to Create a Custom Live CD for Secure Remote Incident Handling in the Enterprise

    How to Create a Custom Live CD for Secure Remote Incident Handling in the Enterprise

    How to Create a Custom Live CD for Secure Remote Incident Handling in the Enterprise Abstract This paper will document a process to create a custom Live CD for secure remote incident handling on Windows and Linux systems. The process will include how to configure SSH for remote access to the Live CD even when running behind a NAT device. The combination of customization and secure remote access will make this process valuable to incident handlers working in enterprise environments with limited remote IT support. Bert Hayes, [email protected] How to Create a Custom Live CD for Remote Incident Handling 2 Table of Contents Abstract ...........................................................................................................................................1 1. Introduction ............................................................................................................................5 2. Making Your Own Customized Debian GNU/Linux Based System........................................7 2.1. The Development Environment ......................................................................................7 2.2. Making Your Dream Incident Handling System...............................................................9 2.3. Hardening the Base Install.............................................................................................11 2.3.1. Managing Root Access with Sudo..........................................................................11 2.4. Randomizing the Handler Password at Boot Time ........................................................12
  • System Administration

    System Administration

    System Administration Varian NMR Spectrometer Systems With VNMR 6.1C Software Pub. No. 01-999166-00, Rev. C0503 System Administration Varian NMR Spectrometer Systems With VNMR 6.1C Software Pub. No. 01-999166-00, Rev. C0503 Revision history: A0800 – Initial release for VNMR 6.1C A1001 – Corrected errors on pg 120, general edit B0202 – Updated AutoTest B0602 – Added additional Autotest sections including VNMRJ update B1002 – Updated Solaris patch information and revised section 21.7, Autotest C0503 – Add additional Autotest sections including cryogenic probes Applicability: Varian NMR spectrometer systems with Sun workstations running Solaris 2.x and VNMR 6.1C software By Rolf Kyburz ([email protected]) Varian International AG, Zug, Switzerland, and Gerald Simon ([email protected]) Varian GmbH, Darmstadt, Germany Additional contributions by Frits Vosman, Dan Iverson, Evan Williams, George Gray, Steve Cheatham Technical writer: Mike Miller Technical editor: Dan Steele Copyright 2001, 2002, 2003 by Varian, Inc., NMR Systems 3120 Hansen Way, Palo Alto, California 94304 1-800-356-4437 http://www.varianinc.com All rights reserved. Printed in the United States. The information in this document has been carefully checked and is believed to be entirely reliable. However, no responsibility is assumed for inaccuracies. Statements in this document are not intended to create any warranty, expressed or implied. Specifications and performance characteristics of the software described in this manual may be changed at any time without notice. Varian reserves the right to make changes in any products herein to improve reliability, function, or design. Varian does not assume any liability arising out of the application or use of any product or circuit described herein; neither does it convey any license under its patent rights nor the rights of others.
  • Deep Compression

    Deep Compression

    COVER STORY Cloop DEEPBlock device compression COMPRESSION with the cloop module KYRO, photocase.com KYRO, The cloop module lets you manage compression at the block device 512 bytes), and they are usually used for random access storage like ramdisks, level. Read on to learn how Knoppix and other Live CDs fit all that CD-ROMs, floppy disks, hard disks, and hard disk partitions. software on a single disc. BY KLAUS KNOPPER Filesystems are a logical representa- tion of ordered data that is often present loop is a kernel block device block-based devices. If you look into the on a block device. A filesystem turns raw module used in Live CDs such output of ls -l /dev, you will easily recog- data into the familiar directory/file view. Cas Knoppix. The cloop module nize these devices by the prefix – c for The mount command is the bridge be- allows the system to read compressed character-based and b for block-based tween a block device partition and its data, usually from a file, thus creating devices – at the beginning of the output projection into a mount point directory. compressed virtual disks. Using cloop, line (see Listing 1). a Linux installation of about 2GB fits on Character-based devices, such as tape Cloop: A Compressed a single 700MB CD-R disc. In this article, drives, mice, and gamepads, provide se- Loopback Block Device I look at how cloop works and provide quential, character-by-character access One block device included in any Linux some insight into general kernel struc- to data.
  • QEMU Interface Introspection: from Hacks to Solutions

    QEMU Interface Introspection: from Hacks to Solutions

    QEMU interface introspection: From hacks to solutions Markus Armbruster <[email protected]> KVM Forum 2015 Part I What’s the problem? Interfacing with QEMU QEMU provides interfaces QMP Monitor Command line to management applications like libvirt QEMU evolves rapidly Many interface versions Our command line is big In v2.4: 139 total options -14 deprecated -2 internal use 123 supported options 0.57kg If I had a coin for each of them. It’s big: output of -help QEMU emulator version 2.3.93, Copyright (c) 2003-2008 Fabrice Bellard -alt-grab use Ctrl-Alt-Shift to grab mouse (instead of Ctrl-Alt) configure a network backend to connect to another network -incoming rdma:host:port[,ipv4][,ipv6] usage: upstream-qemu [options] [disk_image] -ctrl-grab use Right-Ctrl to grab mouse (instead of Ctrl-Alt) using an UDP tunnel -incoming unix:socketpath -no-quit disable SDL window close capability -netdev vhost-user,id=str,chardev=dev[,vhostforce=on|off] prepare for incoming migration, listen on ’disk_image’ is a raw hard disk image for IDE hard disk 0 -sdl enable SDL configure a vhost-user network, backed by a chardev ’dev’ specified protocol and socket address -spice [port=port][,tls-port=secured-port][,x509-dir=<dir>] -netdev hubport,id=str,hubid=n -incoming fd:fd Standard options: [,x509-key-file=<file>][,x509-key-password=<file>] configure a hub port on QEMU VLAN ’n’ -incoming exec:cmdline -h or -help display this help and exit [,x509-cert-file=<file>][,x509-cacert-file=<file>] -net nic[,vlan=n][,macaddr=mac][,model=type][,name=str][,addr=str][,vectors=v]
  • Virtfs—A Virtualization Aware File System Pass-Through

    Virtfs—A Virtualization Aware File System Pass-Through

    VirtFS—A virtualization aware File System pass-through Venkateswararao Jujjuri Eric Van Hensbergen Anthony Liguori IBM Linux Technology Center IBM Research Austin IBM Linux Technology Center [email protected] [email protected] [email protected] Badari Pulavarty IBM Linux Technology Center [email protected] Abstract operations into block device operations and then again into host file system operations. This paper describes the design and implementation of In addition to performance improvements over a tradi- a paravirtualized file system interface for Linux in the tional virtual block device, exposing guest file system KVM environment. Today’s solution of sharing host activity to the hypervisor provides greater insight to the files on the guest through generic network file systems hypervisor about the workload the guest is running. This like NFS and CIFS suffer from major performance and allows the hypervisor to make more intelligent decisions feature deficiencies as these protocols are not designed with respect to I/O caching and creates new opportuni- or optimized for virtualization. To address the needs of ties for hypervisor-based services like de-duplification. the virtualization paradigm, in this paper we are intro- ducing a new paravirtualized file system called VirtFS. In Section 2 of this paper, we explore more details about This new file system is currently under development and the motivating factors for paravirtualizing the file sys- is being built using QEMU, KVM, VirtIO technologies tem layer. In Section 3, we introduce the VirtFS design and 9P2000.L protocol. including an overview of the 9P protocol, which VirtFS is based on, along with a set of extensions introduced for greater Linux guest compatibility.