Xen VT Status and TODO Lists for Xen-Summit

Total Page:16

File Type:pdf, Size:1020Kb

Xen VT Status and TODO Lists for Xen-Summit XenXen VTVT statusstatus andand TODOTODO listslists forfor XenXen--summitsummit Arun Sharma, Asit Mallick, Jun Nakajima, Sunil Saxena ® R OutlineOutline • VMX Guests Status Summary • Status Domain0 restructuring – PCI/IOAPIC X86-64 VMX guests enhancements à QEMU Device Models à Paravirtualized drivers Guest FW • TODO list 2 R Copyright Intel Corp VMXVMX GuestsGuests StatusStatus SummarySummary • VMX: Full support of 32-bit unmodified Linux guests without FW on IA-32 platforms à Includes support of standard PC platform devices 32-bit unmodified Linux guest support without FW added to EM64T • Making Good progress on (Q2) Domain0 restructuring – PCI/IOAPIC X86-64 support (64-bit unmodified guests) VMX guests enhancements à Device models, paravirtualized drivers Guest FW • In plan (Q3) SMP support for VMX guests, IPF VT guests, performance, installation 3 R Copyright Intel Corp Domain0Domain0 restructuringrestructuring –– PCI/IOAPICPCI/IOAPIC • Xen IO architecture today Xen enumerates PCI devices Xen partitions the devices among domains • Adds complexity to Xen Complex PCI configurations, need for ACPI Many workarounds for PCI hardware bugs needed • Proposed Solution Move all PCI device enumeration code to Domain0 à Including full support of ACPI Also requires enabling PCI, Local and I/O APIC 4 R Copyright Intel Corp Domain0 restructuring – PCI/IOAPIC (cont.) • Splitting of Resources and Device Enumeration Xen à Owns Local APIC, IOAPIC including assignment of interrupt vectors à ACPI tables parsing only (no AML interpreter) Domain0 à Full ACPI support – Need to map ACPI tables into domain0 – Xen passes ACPI table pointer in shared_info_t à Local APIC – Stubs to satisfy MP parsing à IO APIC – Accessed by Domain0 using hypercalls • Primarily to set interrupt redirection entry à PCI Device Enumeration 5 R Copyright Intel Corp Domain0 restructuring – PCI/IOAPIC (Status) • A patch against xeno-unstable.bk exists and boots on some machines • Need to validate on a wider variety of machines Especially ones with complex PCI configurations • Other outstanding works MSI support à Need to covert Domain0 IRQ to vector (hypercall) Partitioning of devices between domains PCI Hotplug support Hotplug of I/O APICs? 6 R Copyright Intel Corp X86X86--6464 StatusStatus • It’s in unstable BK tree • Stable and usable Multi-user mode, e.g. login from remote and build the kernel • What’s left DomU support. Tested to build 32-bit VMX domain SMP support, 32-bit binary support, IOMMU, writable page tables, NUMA support? Performance tuning Running on big machines (# of CPUs, memory, I/O) • Need help from community Actively build, test, use. Finish what’s left 7 R Copyright Intel Corp X86X86--6464 –– RestructuringRestructuring • Need to have common chipset/platform code among {x86-32, x86-64} x {Linux, XenoLinux} for better code maintenance No compelling reasons for them to be slightly different: time.c, smp.c, smpboot.c, several headers Shared files with x86 as much as possible, but not enough à Timer, PCI, microcode, etc. We can use the same code for x86-32 and x86-64 more for xenolinux à Initialization à Chipset/platform support – PCI, APIC, ACPI, interrupt management, most of trap handling, timer management à Processor specific part – CPU detection, most of context switching à SMP support 8 R Copyright Intel Corp X86X86--6464 StatusStatus –– VMXVMX guestsguests • 32-bit VMX guests are available on both 32-bit and 64-bit VT-x Xen • Working on: 64-bit guests support à 4-level/3-level shadow mode support Enhanced 32-bit support à PAE, eXecute Disable (XD) support on 64-bit VT-x Xen Extend shadow code to support 4-level cleanly to support both types of guests SMP guest support à Local and I/O APIC support Test more on MP systems 9 R Copyright Intel Corp VMXVMX GuestsGuests Enhancements:Enhancements: DeviceDevice ModelsModels • What we have today Bochs device models providing à PS/2 kbd/mouse, CMOS/RTC, Timer (8254), Generic PCI bridge, EIDE, VGA, Serial ports, NMI Ports, Floppy, NIC NE2K (ISA), Local APIC, IOAPIC, CDROM, USB à Gaps: SCSI, PCI NIC, IDE-DMA • What we are planning to do: switch to QEMU Get PCI NIC and IDE-DMA for free Code written in C Need to implement some functionality (for eg: APIC) either from – unstable or Bochs Status: Implementation complete, under regression/performance testing. 10 R Copyright Intel Corp VMXVMX GuestsGuests Enhancements:Enhancements: VBD/VNICVBD/VNIC Domain 0 Domain N Guest VM (VMX domain) Xenolinux (xm/xend) Control Models Device Panel 3P Req/Resp Unmodified 3D Ring Buffer AppEvent Channel Linux PCI Device VBD FE Virtual Drivers (Virtual Event Driver Channel) Virtual driver Virtual VNIC Backend Guest BIOS 0D 1P Native Device Virtual Platform Drivers Callback VMExit Event channel 0P Control Interface Scheduler Event Channel Hypercalls Processor Memory I/O: PIT, APIC, PIC PCI, ACPI Xen Hypervisor 11 R Copyright Intel Corp VMXVMX GuestsGuests Enhancements:Enhancements: VBD/VNICVBD/VNIC StatusStatus • Basic implementation complete Not integrated with PCI virtual event channel device model Testing/performance analysis in progress • Work remaining Use of grant tables instead of mpa 12 R Copyright Intel Corp GuestGuest FWFW ArchitectureArchitecture Domain 0 VMX domain Control Panel Unmodified Linux Boot Loader xm c xend a Web client Emulator/Execution Environment b ROM BIOS (Real Mode code @ 0xF000:0) PICDevice ModelsDispatcher 5 VGA BIOS (Real Mode code @0xC000:0) IDE BIOS Data (Generated by ROM BIOS) SCSI Net 1 VMExit Physical Device Drivers 2 6 4 Arch -> request packet Send event Send event - Decode I/O - response packet - request packet - Creat request packet 7 3 Port x Resp ->Arch state VMexit -> Port n Control Interface Scheduler Event Channel Hypercalls Processor Memory I/O: PIT, APIC, PIC PCI, ACPI Hypervisor 13 R Copyright Intel Corp GuestGuest FWFW StatusStatus • Real Mode Emulator Implementation complete and integrated into Guest FW execution environment • ROM BIOS Using BOCHS/Plex86 ROM BIOS Extended to E820 memory map to be dynamic Adding ACPI support • VGA BIOS Using BOCHS/Plex86 VGA BIOS • Control Panel Enhancements Enhanced to load Execution environment, ROM BIOS and VGA BIOS in a VMX domain 14 R Copyright Intel Corp TODOTODO • > 4 Gig memory support for 32-bit Xen and 32-bit domains PAE support • Discontigous memory support in Xen • 32-bit/64-bit MP Guests • Debugger / Crash dump • Performance monitoring tools • Scheduler enhancements for load balancing • Power-management 15 R Copyright Intel Corp.
Recommended publications
  • Virtual Machine Technologies and Their Application in the Delivery of ICT
    Virtual Machine Technologies and Their Application In The Delivery Of ICT William McEwan accq.ac.nz n Christchurch Polytechnic Institute of Technology Christchurch, New Zealand [email protected] ABSTRACT related areas - a virtual machine or network of virtual machines can be specially configured, allowing an Virtual Machine (VM) technology was first ordinary user supervisor rights, and it can be tested implemented and developed by IBM to destruction without any adverse effect on the corporation in the early 1960's as a underlying host system. mechanism for providing multi-user facilities This paper hopes to also illustrate how VM in a secure mainframe computing configurations can greatly reduce our dependency on environment. In recent years the power of special purpose, complex, and expensive laboratory personal computers has resulted in renewed setups. It also suggests the important additional role interest in the technology. This paper begins that VM and VNL is likely to play in offering hands-on by describing the development of VM. It practical experience to students in a distance e- discusses the different approaches by which learning environment. a VM can be implemented, and it briefly considers the advantages and disadvantages Keywords: Virtual Machines, operating systems, of each approach. VM technology has proven networks, e-learning, infrastructure, server hosting. to be extremely useful in facilitating the Annual NACCQ, Hamilton New Zealand July, 2002 www. Annual NACCQ, Hamilton New Zealand July, teaching of multiple operating systems. It th offers an alternative to the traditional 1. INTRODUCTION approaches of using complex combinations Virtual Machine (VM) technology is not new. It was of specially prepared and configured OS implemented on mainframe computing systems by the images installed via the network or installed IBM Corporation in the early 1960’s (Varian 1997 pp permanently on multiple partitions or on 3-25, Gribben 1989 p.2, Thornton 2000 p.3, Sugarman multiple physical hard drives.
    [Show full text]
  • OLD PRETENDER Lovrenc Gasparin, Fotolia
    COVER STORY Bochs Emulator Legacy emulator OLD PRETENDER Lovrenc Gasparin, Fotolia Gasparin, Lovrenc Bochs, the granddaddy of all emulators, is alive and kicking; thanks to regular vitamin jabs, the lively old pretender can even handle Windows XP. BY TIM SCHÜRMANN he PC emulator Bochs first saw the 2.2.6 version in the Universe reposi- box). This also applies if you want to the light of day in 1994. Bochs’ tory; you will additionally need to install run Bochs on a pre-Pentium CPU, such Tinventor, Kevin Lawton, distrib- the Bximage program. (Bximage is al- as a 486. uted the emulator under a commercial li- ready part of the Bochs RPM for open- After installation, the program will cense before selling to French Linux ven- SUSE.) If worst comes to worst, you can simulate a complete PC, including CPU, dor Mandriva (which was then known always build your own Bochs from the graphics, sound card, and network inter- as MandrakeSoft). Mandriva freed the source code (see the “Building Bochs” face. The virtual PC in a PC works so emulator from its commercial chains, re- leasing Bochs under the LGPL license. Building Bochs If you prefer to build your own Bochs, or an additional --enable-ne2000 parameter Installation if you have no alternative, you will first to configure. The extremely long list of Bochs has now found a new home at need to install the C++ compiler and de- parameters in the user manual [2] gives SourceForge.net [1] (Figure 1). You can veloper packages for the X11 system. you a list of available options.
    [Show full text]
  • Introduction to Virtualization Virtualization
    Introduction to Virtualization Prashant Shenoy Computer Science CS691D: Hot-OS Lecture 2, page 1 Virtualization • Virtualization: extend or replace an existing interface to mimic the behavior of another system. – Introduced in 1970s: run legacy software on newer mainframe hardware • Handle platform diversity by running apps in VMs – Portability and flexibility Computer Science CS691D: Hot-OS Lecture 2, page 2 Types of Interfaces • Different types of interfaces – Assembly instructions – System calls – APIs • Depending on what is replaced /mimiced, we obtain different forms of virtualization Computer Science CS691D: Hot-OS Lecture 2, page 3 Types of Virtualization • Emulation – VM emulates/simulates complete hardware – Unmodified guest OS for a different PC can be run • Bochs, VirtualPC for Mac, QEMU • Full/native Virtualization – VM simulates “enough” hardware to allow an unmodified guest OS to be run in isolation • Same hardware CPU – IBM VM family, VMWare Workstation, Parallels,… Computer Science CS691D: Hot-OS Lecture 2, page 4 Types of virtualization • Para-virtualization – VM does not simulate hardware – Use special API that a modified guest OS must use – Hypercalls trapped by the Hypervisor and serviced – Xen, VMWare ESX Server • OS-level virtualization – OS allows multiple secure virtual servers to be run – Guest OS is the same as the host OS, but appears isolated • apps see an isolated OS – Solaris Containers, BSD Jails, Linux Vserver • Application level virtualization – Application is gives its own copy of components that are not shared • (E.g., own registry files, global objects) - VE prevents conflicts – JVM Computer Science CS691D: Hot-OS Lecture 2, page 5 Examples • Application-level virtualization: “process virtual machine” • VMM /hypervisor Computer Science CS691D: Hot-OS Lecture 2, page 6 The Architecture of Virtual Machines J Smith and R.
    [Show full text]
  • Virtualizing Servers with Xen
    Virtualization Xen Features Escalabilidade Performance QoS Implementation Future Virtualizing servers with Xen Evaldo Gardenali VI International Conference of Unix at UNINET Virtualization Xen Features Escalabilidade Performance QoS Implementation Future Outline Virtualization Xen Features Scalability Performance Quality of Service Implementation Future of Xen Virtualization Xen Features Escalabilidade Performance QoS Implementation Future Overview Why? Support heterogeneous environments: Linux r 2.4 e 2.6, NetBSD r , Plan9 r FreeBSD r , OpenSolaris r Consolidate work Legacy Systems Gradual Upgrade Service Isolation Quality of Service Isolated testing and development Ease of administration Ease of relocation and migration Virtualization Xen Features Escalabilidade Performance QoS Implementation Future Virtualization Techniques Single System Image: Ensim r , Vservers, CKRM, VirtuozzoTM, BSD r jail(), Solaris r Zones √ Groups processes in “resource containers” Hard to get isolation × Emulation: QEMU, Bochs √ Portable Extremely slow × Virtualization: VMware r , VirtualPC r √ Runs unmodified Operating Systems Virtualizing x86 is inefficient × User Mode Kernel: User Mode Linux, CoLinux Guest runs as a process on the host OS × Low performance (I/O, context switches) × Paravirtualization: Xen r , Denali √ Excellent performance Requires port to special architecture × Virtualization Xen Features Escalabilidade Performance QoS Implementation Future Virtualization Techniques Single System Image: Ensim r , Vservers, CKRM, VirtuozzoTM, BSD r jail(), Solaris
    [Show full text]
  • Virtualization of Linux Based Computers: the Linux-Vserver Project
    VirtualizationVirtualization ofof LinuxLinux basedbased computers:computers: thethe LinuxLinux--VServerVServer projectproject BenoBenoîîtt desdes Ligneris,Ligneris, Ph.Ph. D.D. [email protected] Objectives:Objectives: Objectives:Objectives: 1)1) PresentPresent thethe availableavailable programsprograms thatthat cancan provideprovide aa virtualizationvirtualization ofof LinuxLinux computerscomputers withwith differentdifferent technologies.technologies. Objectives:Objectives: 1)1) PresentPresent thethe availableavailable programsprograms thatthat cancan provideprovide aa virtualizationvirtualization ofof LinuxLinux computerscomputers withwith differentdifferent technologies.technologies. 2)2) FocusFocus onon LinuxLinux--VServers:VServers: aa veryvery lightweightlightweight andand effectiveeffective technologytechnology forfor thethe regularregular LinuxLinux useruser notnot interstedintersted inin KernelKernel hacking.hacking. PlanPlan PlanPlan ● IntroductionIntroduction PlanPlan ● IntroductionIntroduction ● OverviewOverview ofof thethe availableavailable technologytechnology PlanPlan ● IntroductionIntroduction ● OverviewOverview ofof thethe availableavailable technologytechnology ● ClassificationClassification ofof thethe problems:problems: usageusage criteriacriteria PlanPlan ● IntroductionIntroduction ● OverviewOverview ofof thethe availableavailable technologytechnology ● ClassificationClassification ofof thethe problems:problems: usageusage criteriacriteria ● ComparativeComparative studystudy ofof thethe existingexisting
    [Show full text]
  • Parallels Desktop® Upgrade to Windows 7 User's Guide
    Parallels Desktop® Upgrade to Windows 7 User's Guide Copyright © 1999-2010 Parallels Holdings, Ltd. and its affiliates. All rights reserved. Parallels Holdings, Ltd. c/o Parallels International GMbH. Parallels International GmbH Vordergasse 49 CH8200 Schaffhausen Switzerland Tel: + 49 (6151) 42996 - 0 Fax: + 49 (6151) 42996 - 255 www.parallels.com Copyright © 1999-2010 Parallels Holdings, Ltd. and its affiliates. All rights reserved. This product is protected by United States and international copyright laws. The product’s underlying technology, patents, and trademarks are listed at http://www.parallels.com/trademarks. Microsoft, Windows, Windows Server, Windows NT, Windows Vista, and MS-DOS are registered trademarks of Microsoft Corporation. Linux is a registered trademark of Linus Torvalds. Mac is a registered trademark of Apple, Inc. All other marks and names mentioned herein may be trademarks of their respective owners. 3 Contents Introduction 5 About Parallels Desktop Upgrade to Windows 7......................................................................................... 5 About This Guide......................................................................................................................................... 6 Organization of This Guide .............................................................................................................. 6 Documentation Conventions............................................................................................................. 7 Getting Help................................................................................................................................................
    [Show full text]
  • Virtualization Technologies Overview Course: CS 490 by Mendel
    Virtualization technologies overview Course: CS 490 by Mendel Rosenblum Name Can boot USB GUI Live 3D Snaps Live an OS on mem acceleration hot of migration another ory runnin disk alloc g partition ation system as guest Bochs partially partially Yes No Container s Cooperati Yes[1] Yes No No ve Linux (supporte d through X11 over networkin g) Denali DOSBox Partial (the Yes No No host OS can provide DOSBox services with USB devices) DOSEMU No No No FreeVPS GXemul No No Hercules Hyper-V iCore Yes Yes No Yes No Virtual Accounts Imperas Yes Yes Yes Yes OVP (Eclipse) Tools Integrity Yes No Yes Yes No Yes (HP-UX Virtual (Integrity guests only, Machines Virtual Linux and Machine Windows 2K3 Manager in near future) (add-on) Jail No Yes partially Yes No No No KVM Yes [3] Yes Yes [4] Yes Supported Yes [5] with VMGL [6] Linux- VServer LynxSec ure Mac-on- Yes Yes No No Linux Mac-on- No No Mac OpenVZ Yes Yes Yes Yes No Yes (using Xvnc and/or XDMCP) Oracle Yes Yes Yes Yes Yes VM (manage d by Oracle VM Manager) OVPsim Yes Yes Yes Yes (Eclipse) Padded Yes Yes Yes Cell for x86 (Green Hills Software) Padded Yes Yes Yes No Cell for PowerPC (Green Hills Software) Parallels Yes, if Boot Yes Yes Yes DirectX 9 Desktop Camp is and for Mac installed OpenGL 2.0 Parallels No Yes Yes No partially Workstati on PearPC POWER Yes Yes No Yes No Yes (on Hypervis POWER 6- or (PHYP) based systems, requires PowerVM Enterprise Licensing) QEMU Yes Yes Yes [4] Some code Yes done [7]; Also supported with VMGL [6] QEMU w/ Yes Yes Yes Some code Yes kqemu done [7]; Also module supported
    [Show full text]
  • Kvm – Kernel Based Virtual Machine
    KVM – KERNEL BASED VIRTUAL MACHINE BACKGROUND Virtualization has begun to transform the way that enterprises are deploying and managing their infrastructure, providing the foundation for a truly agile enterprise, so that IT can deliver an infrastructure that is flexible, scalable, and most importantly economical by efficiently utilizing resources. 10 years ago virtualization was unheard of in the x86 market it was reserved for mainframe and high end UNIX systems. Over the last 3 to 4 years there has been exponential growth in the virtualization market both in terms of customer adoption and in terms of the rise of the number vendors in the virtualization space; from new hypervisor vendors to virtualization management vendors too numerous to mention. VIRTUALIZING THE X86 ARCHITECTURE The x86 architecture has proven to be the dominate platform in enterprise computing, moving from its humble beginnings in desktop systems to now, powering the large enterprise applications that run businesses across the globe. The current generation of x86 CPUs include features such as large scale multi-threading with 8 or more processing cores, support for large memory systems with NUMA and integrated memory controllers, high speed CPU interconnects and chipset for support for advanced reliability, availability and serviceability (RAS) features. These features were once reserved for mainframe and high end UNIX systems, today x86 servers with 2 or 4 sockets are replacing expensive UNIX/RISC systems while delivering better performance and 4 and 8 socket servers are challenging mainframe class systems. While the x86 platform has evolved significantly over it's lifetime it has maintained it's core architecture to provide backward compatibility.
    [Show full text]
  • Operating System Support for Virtual Machines Samuel T
    Proceedings of the 2003 USENIX Technical Conference Operating System Support for Virtual Machines Samuel T. King, George W. Dunlap, Peter M. Chen Computer Science and Engineering Division Department of Electrical Engineering and Computer Science University of Michigan http://www.eecs.umich.edu/CoVirt Abstract: A virtual-machine monitor (VMM) is a use- VMM is called a virtual machine. The hardware emu- ful technique for adding functionality below existing lated by the VMM typically is similar or identical to the operating system and application software. One class of hardware on which the VMM is running. VMMs (called Type II VMMs) builds on the abstrac- tions provided by a host operating system. Type II Virtual machines were first developed and used in VMMs are elegant and convenient, but their perfor- the 1960s, with the best-known example being IBM’s mance is currently an order of magnitude slower than VM/370 [Goldberg74]. Several properties of virtual that achieved when running outside a virtual machine (a machines have made them helpful for a wide variety of standalone system). In this paper, we examine the rea- uses. First, they can create the illusion of multiple vir- sons for this large overhead for Type II VMMs. We find tual machines on a single physical machine. These mul- that a few simple extensions to a host operating system tiple virtual machines can be used to run applications on can make it a much faster platform for running a VMM. different operating systems, to allow students to experi- Taking advantage of these extensions reduces virtualiza- ment conveniently with building their own operating tion overhead for a Type II VMM to 14-35% overhead, system [Nieh00], to enable existing operating systems to even for workloads that exercise the virtual machine run on shared-memory multiprocessors [Bugnion97], intensively.
    [Show full text]
  • Virtually Linux Virtualization Techniques in Linux
    Virtually Linux Virtualization Techniques in Linux Chris Wright OSDL [email protected] Abstract ware1 or software [16, 21, 19], may include any subset of a machine’s resources, and has Virtualization provides an abstraction layer a wide variety of applications. Such usages mapping a virtual resource to a real resource. include machine emulation, hardware consol- Such an abstraction allows one machine to be idation, resource isolation, quality of service carved into many virtual machines as well as resource allocation, and transparent resource allowing a cluster of machines to be viewed redirection. Applications of these usage mod- as one. Linux provides a wealth of virtual- els include virtual hosting, security, high avail- ization offerings. The technologies range in ability, high throughput, testing, and ease of the problems they solve, the models they are administration. useful in, and their respective maturity. This It is interesting to note that differing virtual- paper surveys some of the current virtualiza- ization models may have inversely correlated tion techniques available to Linux users, and proportions of virtual to physical resources. it reviews ways to leverage these technologies. For example, the method of carving up a sin- Virtualization can be used to provide things gle machine into multiple machines—useful such as quality of service resource allocation, in hardware consolidation or virtual hosting— resource isolation for security or sandboxing, looks quite different from a single system im- transparent resource redirection for availability age (SSI) [15]—useful in clustering. This pa- and throughput, and simulation environments per primarily focuses on providing multiple for testing and debugging. virtual instances of a single physical resource, however, it does cover some examples of a sin- 1 Introduction gle virtual resource mapping to multiple phys- ical resources.
    [Show full text]
  • Challenges in Firmware Re-Hosting, Emulation, and Analysis
    Challenges in Firmware Re-Hosting, Emulation, and Analysis CHRISTOPHER WRIGHT, Purdue University WILLIAM A. MOEGLEIN, Sandia National Laboratories SAURABH BAGCHI, Purdue University MILIND KULKARNI, Purdue University ABRAHAM A. CLEMENTS, Sandia National Laboratories System emulation and firmware re-hosting have become popular techniques to answer various security and performance related questions, such as, does a firmware contain security vulnerabilities or meet timing requirements when run on a specific hardware platform. While this motivation for emulation and binary analysis has previously been explored and reported, starting to either work or research in the field is difficult. To this end, we provide a comprehensive guide for the practitioner or system emulation researcher. We layout common challenges faced during firmware re-hosting, explaining successive steps and surveying common tools used to overcome these challenges. We provide classification techniques on five different axes, including emulator methods, system type, fidelity, emulator purpose, and control. These classifications and comparison criteria enable the practitioner to determine the appropriate tool for emulation. We use our classifications to categorize popular works in the field and present 28 common challenges faced when creating, emulating and analyzing a system, from obtaining firmwares to post emulation analysis. CCS Concepts: • Computer systems organization → Embedded and cyber-physical systems; Firmware; Embedded hardware; Embedded software; Real-time systems; • Hardware → Simulation and emulation. Additional Key Words and Phrases: Firmware re-hosting, system emulation, embedded systems, emulation fidelity, emulator classification, binary analysis, reverse engineering, emulation challenges ACM Reference Format: Christopher Wright, William A. Moeglein, Saurabh Bagchi, Milind Kulkarni, and Abraham A. Clements. 2020. Challenges in Firmware Re-Hosting, Emulation, and Analysis.
    [Show full text]
  • The Black Art of DOS Emulation on Raspberry Pi
    The Black Art of DOS emulation on Raspberry Pi Using FastDOSBox. By : [email protected] www.norisc-nofun.co.uk Version 1.0 – May 2013, Author : Franck / NoRiscNoFun , [email protected] – twitter : @Noriscnofun1 Table of Contents What is DOS emulation for who and for what ?..................................................................................3 Why choosing FastDOSBox for DOS emulation on the Rpi ?............................................................4 Installing FastDOSBox on the Raspberry Pi........................................................................................5 For RISC OS....................................................................................................................................5 For Raspbian....................................................................................................................................5 Recommended Raspberry Pi CPU settings for FastDOSBox..............................................................6 Recommended configuration settings for FastDOSBox......................................................................7 [dosbox] Section..............................................................................................................................7 [render] Section................................................................................................................................7 [cpu] Section....................................................................................................................................7
    [Show full text]