DOCSLIB.ORG

Oracle VM Virtualbox Programming Guide and Reference

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Oracle VM VirtualBox R Programming Guide and Reference Version 4.3.2 c 2004-2013 Oracle Corporation http://www.virtualbox.org Contents 1 Introduction 19 1.1 Modularity: the building blocks of VirtualBox................... 19 1.2 Two guises of the same “Main API”: the web service or COM/XPCOM...... 20 1.3 About web services in general............................ 21 1.4 Running the web service............................... 22 1.4.1 Command line options of vboxwebsrv................... 22 1.4.2 Authenticating at web service logon.................... 23 2 Environment-specific notes 25 2.1 Using the object-oriented web service (OOWS)................... 25 2.1.1 The object-oriented web service for JAX-WS................ 25 2.1.2 The object-oriented web service for Python................ 27 2.1.3 The object-oriented web service for PHP................. 28 2.2 Using the raw web service with any language................... 28 2.2.1 Raw web service example for Java with Axis............... 28 2.2.2 Raw web service example for Perl..................... 29 2.2.3 Programming considerations for the raw web service.......... 30 2.3 Using COM/XPCOM directly............................. 34 2.3.1 Python COM API.............................. 34 2.3.2 Common Python bindings layer...................... 34 2.3.3 C++ COM API............................... 35 2.3.4 Event queue processing........................... 36 2.3.5 Visual Basic and Visual Basic Script (VBS) on Windows hosts...... 37 2.3.6 C binding to XPCOM API.......................... 37 3 Basic VirtualBox concepts; some examples 41 3.1 Obtaining basic machine information. Reading attributes............. 41 3.2 Changing machine settings. Sessions........................ 41 3.3 Launching virtual machines............................. 42 3.4 VirtualBox events................................... 42 4 The VirtualBox shell 44 5 Classes (interfaces) 46 5.1 IAdditionsFacility................................... 46 5.1.1 Attributes.................................. 46 5.2 IAdditionsStateChangedEvent (IEvent)....................... 46 5.3 IAppliance....................................... 47 5.3.1 Attributes.................................. 48 5.3.2 createVFSExplorer.............................. 49 5.3.3 getWarnings................................. 49 5.3.4 importMachines............................... 49 5.3.5 interpret................................... 49 5.3.6 read..................................... 49 5.3.7 write..................................... 50 5.4 IAudioAdapter..................................... 50 2 Contents 5.4.1 Attributes.................................. 50 5.5 IBIOSSettings..................................... 50 5.5.1 Attributes.................................. 51 5.6 IBandwidthControl.................................. 52 5.6.1 Attributes.................................. 52 5.6.2 createBandwidthGroup........................... 52 5.6.3 deleteBandwidthGroup........................... 52 5.6.4 getAllBandwidthGroups........................... 52 5.6.5 getBandwidthGroup............................. 52 5.7 IBandwidthGroup................................... 53 5.7.1 Attributes.................................. 53 5.8 IBandwidthGroupChangedEvent (IEvent)...................... 53 5.8.1 Attributes.................................. 53 5.9 ICPUChangedEvent (IEvent)............................. 53 5.9.1 Attributes.................................. 54 5.10 ICPUExecutionCapChangedEvent (IEvent)..................... 54 5.10.1 Attributes.................................. 54 5.11 ICanShowWindowEvent (IVetoEvent)........................ 54 5.12 IClipboardModeChangedEvent (IEvent)....................... 54 5.12.1 Attributes.................................. 54 5.13 IConsole........................................ 55 5.13.1 Attributes.................................. 55 5.13.2 adoptSavedState............................... 57 5.13.3 attachUSBDevice.............................. 58 5.13.4 createSharedFolder............................. 58 5.13.5 deleteSnapshot............................... 58 5.13.6 deleteSnapshotAndAllChildren....................... 59 5.13.7 deleteSnapshotRange............................ 60 5.13.8 detachUSBDevice.............................. 60 5.13.9 discardSavedState.............................. 61 5.13.10 findUSBDeviceByAddress.......................... 61 5.13.11 findUSBDeviceById............................. 61 5.13.12 getDeviceActivity.............................. 61 5.13.13 getGuestEnteredACPIMode......................... 62 5.13.14 getPowerButtonHandled.......................... 62 5.13.15 pause..................................... 62 5.13.16 powerButton................................. 62 5.13.17 powerDown................................. 62 5.13.18 powerUp................................... 63 5.13.19 powerUpPaused............................... 63 5.13.20 removeSharedFolder............................ 63 5.13.21 reset..................................... 64 5.13.22 restoreSnapshot............................... 64 5.13.23 resume.................................... 64 5.13.24 saveState................................... 65 5.13.25 sleepButton................................. 65 5.13.26 takeSnapshot................................ 65 5.13.27 teleport.................................... 66 5.14 IDHCPServer..................................... 66 5.14.1 Attributes.................................. 66 5.14.2 addGlobalOption.............................. 67 5.14.3 addVmSlotOption.............................. 67 5.14.4 getMacOptions................................ 68 3 Contents 5.14.5 getVmSlotOptions.............................. 68 5.14.6 removeVmSlotOptions........................... 68 5.14.7 setConfiguration............................... 68 5.14.8 start..................................... 69 5.14.9 stop...................................... 69 5.15 IDirectory....................................... 69 5.15.1 Attributes.................................. 69 5.15.2 close..................................... 69 5.15.3 read..................................... 69 5.16 IDisplay........................................ 70 5.16.1 completeVHWACommand......................... 70 5.16.2 drawToScreen................................ 70 5.16.3 getFramebuffer............................... 71 5.16.4 getScreenResolution............................. 71 5.16.5 invalidateAndUpdate............................ 71 5.16.6 resizeCompleted............................... 71 5.16.7 setFramebuffer............................... 72 5.16.8 setSeamlessMode.............................. 72 5.16.9 setVideoModeHint.............................. 72 5.16.10 takeScreenShot............................... 73 5.16.11 takeScreenShotPNGToArray........................ 73 5.16.12 takeScreenShotToArray........................... 74 5.16.13 viewportChanged.............................. 74 5.17 IDragAndDropModeChangedEvent (IEvent).................... 74 5.17.1 Attributes.................................. 75 5.18 IEmulatedUSB..................................... 75 5.18.1 Attributes.................................. 75 5.18.2 webcamAttach................................ 75 5.18.3 webcamDetach............................... 75 5.19 IEvent......................................... 75 5.19.1 Attributes.................................. 76 5.19.2 setProcessed................................. 77 5.19.3 waitProcessed................................ 77 5.20 IEventListener..................................... 77 5.20.1 handleEvent................................. 77 5.21 IEventSource..................................... 77 5.21.1 createAggregator.............................. 78 5.21.2 createListener................................ 78 5.21.3 eventProcessed............................... 78 5.21.4 fireEvent................................... 78 5.21.5 getEvent................................... 78 5.21.6 registerListener............................... 79 5.21.7 unregisterListener.............................. 79 5.22 IEventSourceChangedEvent (IEvent)........................ 79 5.22.1 Attributes.................................. 79 5.23 IExtPack (IExtPackBase)............................... 80 5.23.1 queryObject................................. 80 5.24 IExtPackBase...................................... 80 5.24.1 Attributes.................................. 80 5.24.2 queryLicense................................. 82 5.25 IExtPackFile (IExtPackBase)............................. 82 5.25.1 Attributes.................................. 82 5.25.2 install..................................... 83 4 Contents 5.26 IExtPackManager................................... 83 5.26.1 Attributes.................................. 83 5.26.2 cleanup.................................... 83 5.26.3 find...................................... 83 5.26.4 isExtPackUsable............................... 84 5.26.5 openExtPackFile............................... 84 5.26.6 queryAllPlugInsForFrontend........................ 84 5.26.7 uninstall................................... 84 5.27 IExtPackPlugIn.................................... 84 5.27.1 Attributes.................................. 85 5.28 IExtraDataCanChangeEvent (IVetoEvent)...................... 85 5.28.1 Attributes.................................. 85 5.29 IExtraDataChangedEvent (IEvent).......................... 86 5.29.1 Attributes.................................. 86 5.30 IFile.......................................... 86 5.30.1 Attributes.................................. 86 5.30.2 close....................................
Recommended publications
  • Virtualization Getting Started Guide

    Virtualization Getting Started Guide

    Red Hat Enterprise Linux 7 Virtualization Getting Started Guide Introduction to virtualization technologies available with RHEL Last Updated: 2020-02-24 Red Hat Enterprise Linux 7 Virtualization Getting Started Guide Introduction to virtualization technologies available with RHEL Jiri Herrmann Red Hat Customer Content Services [email protected] Yehuda Zimmerman Red Hat Customer Content Services [email protected] Dayle Parker Red Hat Customer Content Services Laura Novich Red Hat Customer Content Services Jacquelynn East Red Hat Customer Content Services Scott Radvan Red Hat Customer Content Services Legal Notice Copyright © 2019 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
  • Fortianalyzer VM Install Guide This Document, Which Describes Installing Fortianalyzer VM in Your Virtual Environment

    Fortianalyzer VM Install Guide This Document, Which Describes Installing Fortianalyzer VM in Your Virtual Environment

    FortiAnalyzer VM - Install Guide VERSION 5.4 FORTINET DOCUMENT LIBRARY http://docs.fortinet.com FORTINET VIDEO GUIDE http://video.fortinet.com FORTINET BLOG https://blog.fortinet.com CUSTOMER SERVICE & SUPPORT https://support.fortinet.com FORTIGATE COOKBOOK http://cookbook.fortinet.com FORTINET TRAINING SERVICES http://www.fortinet.com/training FORTIGUARD CENTER http://www.fortiguard.com END USER LICENSE AGREEMENT http://www.fortinet.com/doc/legal/EULA.pdf FEEDBACK Email: [email protected] May 18, 2017 FortiAnalyzer VM 5.4 Install Guide 05-540-309958-20170518 TABLE OF CONTENTS Change Log 5 Introduction 6 FortiAnalyzer documentation 6 License and System Requirements 7 Licensing 7 Evaluation license 7 Minimum system requirements 8 Registration and Deployment 9 Register with Customer Service & Support 9 Deployment package 11 Deployment package contents 12 Deploying the appliance 13 Citrix XenServer deployment example 14 Create the virtual machine 14 Configure hardware settings 15 Start the virtual machine 17 Hyper-V deployment example 18 Create the virtual machine 18 Configure hardware settings 19 Start the virtual machine 23 KVM deployment example 24 Create the virtual machine 24 Configure hardware settings 26 Start the virtual machine 27 Open Xen deployment example 28 Create and configure the virtual machine 28 VMware deployment example 31 VMware vSphere 31 Deploy the OVF file 31 Configure hardware settings 34 Power on the virtual machine 35 Azure deployment example 37 Deploy the virtual machine 37 AWS deployment example 39 AWS Marketplace 1-Click Launch 39 AWS EC2 console 41 Initial Configuration 46 GUI access 46 Enable GUI access 46 Connect to the GUI 47 Upload the license file 48 Configure your FortiAnalyzer VM 48 Index 50 Change Log Change Log Date Change Description 2016-03-17 Initial release.
  • KVM Based Virtualization and Remote Management Srinath Reddy Pasunuru St

    KVM Based Virtualization and Remote Management Srinath Reddy Pasunuru St

    St. Cloud State University theRepository at St. Cloud State Culminating Projects in Information Assurance Department of Information Systems 5-2018 KVM Based Virtualization and Remote Management Srinath Reddy Pasunuru St. Cloud State University, [email protected] Follow this and additional works at: https://repository.stcloudstate.edu/msia_etds Recommended Citation Pasunuru, Srinath Reddy, "KVM Based Virtualization and Remote Management" (2018). Culminating Projects in Information Assurance. 53. https://repository.stcloudstate.edu/msia_etds/53 This Starred Paper is brought to you for free and open access by the Department of Information Systems at theRepository at St. Cloud State. It has been accepted for inclusion in Culminating Projects in Information Assurance by an authorized administrator of theRepository at St. Cloud State. For more information, please contact [email protected]. 1 KVM Based Virtualization and Remote Management by Srinath Reddy Pasunuru A Starred Paper Submitted to the Graduate Faculty of St. Cloud State University in Partial Fulfillment of the Requirements for the Degree Master of Science in Information Assurance May, 2018 Starred Paper Committee Susantha Herath, Chairperson Ezzat Kirmani Sneh Kalia 2 Abstract In the recent past, cloud computing is the most significant shifts and Kernel Virtual Machine (KVM) is the most commonly deployed hypervisor which are used in the IaaS layer of the cloud computing systems. The Hypervisor is the one which provides the complete virtualization environment which will intend to virtualize as much as hardware and systems which will include the CPUs, Memory, network interfaces and so on. Because of the virtualization technologies such as the KVM and others such as ESXi, there has been a significant decrease in the usage if the resources and decrease in the costs involved.
  • Oracle Berkeley DB Installation and Build Guide Release 18.1

    Oracle Berkeley DB Installation and Build Guide Release 18.1

    Oracle Berkeley DB Installation and Build Guide Release 18.1 Library Version 18.1.32 Legal Notice Copyright © 2002 - 2019 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. Berkeley DB, and Sleepycat are trademarks or registered trademarks of Oracle. All rights to these marks are reserved. No third- party use is permitted without the express prior written consent of Oracle. Other names may be trademarks of their respective owners. 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 any operating 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.
  • ZERTO VIRTUAL REPLICATION - PREREQUISITES & REQUIREMENTS for MICROSOFT HYPER-V ENVIRONMENTS ZVR-REH-5.5U3 Rev01 Dec2017

    ZERTO VIRTUAL REPLICATION - PREREQUISITES & REQUIREMENTS for MICROSOFT HYPER-V ENVIRONMENTS ZVR-REH-5.5U3 Rev01 Dec2017

    ZERTO VIRTUAL REPLICATION - PREREQUISITES & REQUIREMENTS FOR MICROSOFT HYPER-V ENVIRONMENTS ZVR-REH-5.5U3 Rev01 Dec2017 Zerto Virtual Replication is installed in a site with virtual machines to be protected as well as in the site where these virtual machines will be recovered. This document describes Zerto Virtual Replication - Prerequisites and Requirements for Microsoft Hyper-V Environments. For the requirements of VMware, Microsoft Azure or AWS protected sites, go to myZerto > Technical Documentation portal. ■ The Zerto Virtual Replication installation includes: ■ A Zerto Virtual Manager (ZVM): This is a Windows service, and manages replication at the site level. ■ A Virtual Replication Appliance (VRA): This is a virtual machine installed on each Hyper-V host to move the data to be replicated from the protected to the recovery site. ■ A Virtual Backup Appliance (VBA): This is a Windows service and manages offsite backups within Zerto Virtual Replication on each site. The VBA service runs on the same machine as the Zerto Virtual Manager service. ■ Zerto Virtual Replication can be installed at multiple sites and each site can be paired to any other site. ■ Each site is managed with the Zerto User Interface. ■ Zerto Virtual Replication also supports both the protected and recovery sites being managed by one SCVMM, for small branch offices. For example, from one datacenter to another datacenter, both managed by the same SCVMM. See the following sections: ■ “For Each Zerto Virtual Replication Hyper-V Site”, on page 1 ■ “Considerations and Guidelines”, on page 2 ■ “For Virtual Replication Appliances on the Hyper-V Host”, on page 3 ■ “Routable Networks”, on page 3 ■ “Minimum Bandwidth”, on page 3 ■ “Requirements for the Zerto Virtual Manager Web Client”, on page 3 ■ “Recommended Best Practices for the Zerto Virtual Replication Hyper-V Site”, on page 4 ■ “Open Firewall Ports for Hyper-V Environments”, on page 5 For Each Zerto Virtual Replication Hyper-V Site ■ Microsoft System Center 2012 R2, or 2016 with VMM (SCVMM) and at least one Hyper-V host.
  • Cisco Vwaas on Microsoft Hyper-V

    Cisco Vwaas on Microsoft Hyper-V

    Cisco vWAAS on Microsoft Hyper-V This chapter describes how to use Cisco vWAAS on Microsoft Hyper-V, and contains the following sections: • About Cisco vWAAS on Microsoft Hyper-V, on page 1 • Supported Host Platforms, Software Versions, and Disk Type, on page 2 • System Requirements for Cisco vWAAS on Microsoft Hyper-V, on page 2 • Deployment Options for Cisco vWAAS on Microsoft Hyper-V, on page 3 • OVA Package Formats for vWAAS on Microsoft Hyper-V, on page 4 • Installing Cisco vWAAS on Microsoft Hyper-V, on page 6 • Activating and Registering vWAAS on Hyper-V, on page 8 • Traffic Interception Methods for Cisco vWAAS on Microsoft Hyper-V, on page 9 • Operating Guidelines for Cisco vWAAS on Microsoft Hyper-V, on page 11 • Configuring GPT Disk Format for vWAAS-50000 on Hyper-V with Akamai Connect, on page 14 About Cisco vWAAS on Microsoft Hyper-V Microsoft Hyper-V, available for Cisco vWAAS in WAAS Version 6.1.x and later, is a native hypervisor for x86_64 systems to enable platform virtualization. Cisco vWAAS on Microsoft Hyper-V extends Cisco networking benefits to Microsoft Windows Server Hyper-V deployments. It improves utilization, consolidates server workloads, and reduces costs. To achieve this, Cisco vWAAS on Hyper-V uses hardware virtualization to enable multiple operating systems to run on a single host, and allows the operating systems to share the same underlying physical hardware. Cisco vWAAS on Microsoft Hyper-V supports all the WAN-optimization functionalities that are supported by physical Cisco WAAS devices. Physical memory for Cisco vWAAS on Hyper-V is provided by a Cisco UCS server.
  • Oracle Solaris 11 Cheat Sheet Dtrace

    Oracle Solaris 11 Cheat Sheet Dtrace

    Oracle Solaris 11 Administrator's Cheat Sheet for DTrace Oracle Solaris 11 Cheat Sheet DTrace What is DTrace? DTrace Command Components Oracle Solaris DTrace is a comprehensive, advanced tracing tool for troubleshooting A typical DTrace command has several components: systematic problems in real time. Administrators, integrators and developers can use DTrace to dynamically and safely observe live production systems for performance issues, A 4-tuple identifier provider:module:function:name, where module is a kernel including both applications and the operating system itself. DTrace allows you to explore • module or application library, and function and name are the routines that are to be your system to understand how it works, track down problems across many layers of software, and locate the cause of any aberrant behavior. Whether it’s at a high level global instrumented. If any of these are left black, it is equivalent to a wildcard match. For overview like memory consumption or CPU time, to much finer grained information like what example, to fire all entry routines in the syscall provider we would use the following: specific function calls are being made, DTrace gives the operational insights that have long syscall:::entry been missing in the data center. • A predicate, or relational expression, that determines whether any action should be Understanding DTrace providers and probes taken. For example, to check whether the process name matches bash we would use the following: /execname == “bash”/ Oracle Solaris 11 is littered with many different points of instrumentation – places of interest • An action for what should happen if the probe fires and the predicate is satisfied.
  • Oracle® Solaris 11.4 Dtrace

    Oracle® Solaris 11.4 Dtrace

    ® Oracle Solaris 11.4 DTrace (Dynamic Tracing) Guide Part No: E61035 November 2020 Oracle Solaris 11.4 DTrace (Dynamic Tracing) Guide Part No: E61035 Copyright © 2011, 2020, Oracle and/or its affiliates. License Restrictions Warranty/Consequential Damages Disclaimer 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. Warranty Disclaimer 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. Restricted Rights Notice 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, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software"
  • Lokke, a Hybrid Security Hypervisor

    Lokke, a Hybrid Security Hypervisor

    Lokke, a hybrid security hypervisor Otavio´ A. A. Silva1, Paulo L´ıcio de Geus1 1 Universidade Estadual de Campinas (Unicamp) [email protected] , [email protected] Abstract. This work did ample research on techniques used by advanced threats that aim to evade detection systems, elevate privileges and manipulate objects in a modern OS kernel, using the Windows 10 kernel as a test bench. Given state-of-the-art attacks in kernelspace, this work’s main goal is to design a se- cure mechanism to protect the OS kernel against a class of attacks, not relying upon any specific vector. This mechanism is based on hybrid virtualization and combines the advantages of Type 1 and 2 hypervisors, where the hypervisor runs at the same level as the OS kernel does, but within a privileged execution framework. The design of this security framework allows for the integration with other security subsystems, by providing security policies enforced by the hypervisor and independently of the kernel. 1. Introduction Modern OS kernels are built with security as a moving concept, where many approach were made to decrease the kernel overhead, enhance user-level switch and performance, with security policies integrated as best practices or bug fixing. This introduced in many aspects behaviors which were exploited by attacks in the fashion of OS design, as the first wildly use of buffer overflow attack, by the Morris Worm [22], or many user privileged elevations in Windows User Account Control[7]. Although, over the years, these attacks demanded changes in the design concept of any modern OS, as in dynamic libraries, process, and memory organization, most sophisticated attacks nowadays are still abusing in some fashion the behave of the OS to provide userspace services.
  • Solaris Dynamic Tracing Sun.Com/Software

    Solaris Dynamic Tracing Sun.Com/Software

    Solaris™ Dynamic Tracing Increasing Performance Through Complete Software Observability < Introducing Solaris™ Dynamic Tracing (DTrace) With the Solaris™ 10 Operating System (OS), Sun introduces Dynamic Tracing (DTrace): a dynamic tracing framework for troubleshooting systemic problems in real time on production systems. DTrace is designed to quickly identify the root cause of system performance problems. DTrace safely and dynamically instruments the running operating system kernel and running applications without rebooting the kernel and recompiling — or even restarting — appli- cations. And, when not explicitly enabled, DTrace has zero effect on the system. It is available on all supported Solaris OS platforms. Designed for use on production systems Provides single view of software stack DTrace is absolutely safe for use on production With DTrace, system administrators, integrators, systems. It has little impact when running, and developers can really see what the system and no impact on the system when not in use. is doing, as well as how the kernel and appli- Highlights Unlike other tools, it can be initiated dynami- cations interact with each other. It enables cally without rebooting the system, using users to formulate arbitrary questions and get • Designed for use on production special modes, restarting applications, or any concise answers, allowing them to find per- systems to find performance other changes to the kernel or applications. formance bottlenecks on development, pilot, bottlenecks and production systems. More generally, DTrace • Provides a single view of the DTrace provides accurate and concise informa- can be used to troubleshoot virtually any software stack — from kernel tion in real time. Questions are answered systemic problem — often finding problems to application, leading to rapid identification of performance immediately, eliminating the need to collect that have been plaguing a system for years.
  • Comparison of Platform Virtual Machines - Wikipedia

    Comparison of Platform Virtual Machines - Wikipedia

    Comparison of platform virtual machines - Wikipedia... http://en.wikipedia.org/wiki/Comparison_of_platform... Comparison of platform virtual machines From Wikipedia, the free encyclopedia The table below compares basic information about platform virtual machine (VM) packages. Contents 1 General Information 2 More details 3 Features 4 Other emulators 5 See also 6 References 7 External links General Information Name Creator Host CPU Guest CPU Bochs Kevin Lawton any x86, AMD64 CHARON-AXP Stromasys x86 (64 bit) DEC Alphaserver CHARON-VAX Stromasys x86, IA-64 VAX x86, x86-64, SPARC (portable: Contai ners (al so 'Zones') Sun Microsystems (Same as host) not tied to hardware) Dan Aloni helped by other Cooperati ve Li nux x86[1] (Same as parent) developers (1) Denal i University of Washington x86 x86 Peter Veenstra and Sjoerd with DOSBox any x86 community help DOSEMU Community Project x86, AMD64 x86 1 of 15 10/26/2009 12:50 PM Comparison of platform virtual machines - Wikipedia... http://en.wikipedia.org/wiki/Comparison_of_platform... FreeVPS PSoft (http://www.FreeVPS.com) x86, AMD64 compatible ARM, MIPS, M88K GXemul Anders Gavare any PowerPC, SuperH Written by Roger Bowler, Hercul es currently maintained by Jay any z/Architecture Maynard x64 + hardware-assisted Hyper-V Microsoft virtualization (Intel VT or x64,x86 AMD-V) OR1K, MIPS32, ARC600/ARC700, A (can use all OVP OVP Imperas [1] [2] Imperas OVP Tool s x86 (http://www.imperas.com) (http://www.ovpworld compliant models, u can write own to pu OVP APIs) i Core Vi rtual Accounts iCore Software
  • The Rise & Development of Illumos

    The Rise & Development of Illumos

    Fork Yeah! The Rise & Development of illumos Bryan Cantrill VP, Engineering [email protected] @bcantrill WTF is illumos? • An open source descendant of OpenSolaris • ...which itself was a branch of Solaris Nevada • ...which was the name of the release after Solaris 10 • ...and was open but is now closed • ...and is itself a descendant of Solaris 2.x • ...but it can all be called “SunOS 5.x” • ...but not “SunOS 4.x” — thatʼs different • Letʼs start at (or rather, near) the beginning... SunOS: A peopleʼs history • In the early 1990s, after a painful transition to Solaris, much of the SunOS 4.x engineering talent had left • Problems compounded by the adoption of an immature SCM, the Network Software Environment (NSE) • The engineers revolted: Larry McVoy developed a much simpler variant of NSE called NSElite (ancestor to git) • Using NSElite (and later, TeamWare), Roger Faulkner, Tim Marsland, Joe Kowalski and Jeff Bonwick led a sufficiently parallelized development effort to produce Solaris 2.3, “the first version that worked” • ...but with Solaris 2.4, management took over day-to- day operations of the release, and quality slipped again Solaris 2.5: Do or die • Solaris 2.5 absolutely had to get it right — Sun had new hardware, the UltraSPARC-I, that depended on it • To assure quality, the engineers “took over,” with Bonwick installed as the gatekeeper • Bonwick granted authority to “rip it out if itʼs broken" — an early BDFL model, and a template for later generations of engineering leadership • Solaris 2.5 shipped on schedule and at quality