Facing the Reality: Virtualization in a Microkernelbased Operating System. Matthias Lange, MOS, January 26th, 2016

Size: px

Start display at page:

Download "Facing the Reality: Virtualization in a Microkernelbased Operating System. Matthias Lange, MOS, January 26th, 2016"

Estella Wright
6 years ago
Views:

1 Facing the Reality: Virtualization in a Microkernelbased Operating System Matthias Lange, MOS, January 26th, 2016 matthias.lange@kernkonzept.com

beyond CPU and memory virtualization Sharply distinguish between

2 Today's take aways Microkernel systems are used to build real-world systems being deployed to customers Understand what's beyond CPU and memory virtualization Sharply distinguish between Nanovisor, Microvisor, Microhypervisor, Secuvisor, Trustvisor and Budweiser.

3 Short Recap Hypervisor vs. VMM Virtualization "styles" L4Linux

4 Virtualization Objectives Reuse existing/legacy software Security Consolidation

5 Microkernel as Hypervisor Less code, less errors Improvements over monolithic kernels Fault isolation Improved access control Flexibility Needs runtime environment

6 Fiasco.OC + L4Re 3rd gen. microkernel + runtime environment x86, ARM (and MIPS), SMP support, 64bit support SVM, VT-x, ARM VE, (MIPS VM) L4Re provides basic services Virtual Machines are just a special type of task State Page table

7 VM Non-root mode Root mode... Driver Service VMM (e.g. Karma) L4Re Runtime Environment L4Re Microkernel SVM / VT-x Support Ring 3 Ring 0 x86-style Virtualization

8 ARM Hardware Assisted Virtualization Non-secure World Secure World PL0 User Trusted Services PL1 Kernel Trusted OS Monitor

9 ARM Hardware Assisted Virtualization Non-secure World Secure World PL0 User User Trusted Services PL1 Kernel Kernel Trusted OS PL2 Hypervisor PL3 Monitor

10 ARM Hardware Assisted Virtualization Non-secure World Secure World PL0 User L4Re App Trusted Services PL1 Kernel VMM Trusted OS PL2 L4Re Microkernel PL3 Monitor

native Firefox Gimp Up-to-date Linux L4Linux kernel

11 Virtualization: L4Linux Applicable to non-virtualizable platforms Binary compatible to native Firefox Gimp Up-to-date Linux L4Linux kernel Secure App Native App Infrastructure Microkernel Hardware (CPU, Memory, Devices)

12 Taming the Robots

15 Device Accumulation Private Business Development You name it

16 Security Emerging threats Existing OS not secure Future applications ehealth Mobile payment (NFC) Encrypted voice and text

17 Security cont. "Everybody" wants its own secure smartphone Governments Businesses

18 What can we do? picture

19 Patch OS? Bad update record Fragmentation

20 Add security layer?* Change middleware Improve permission model cf. Butler Lampson, 1972

21 L4Android Framework Make L4Linux run Android

22 Applications Browser VPN Secure Voice Phone Home Contacts Calendar Application Framework Notification Manager Activity Manager Window Manager Resource Manager Package Manager Telephony Manager Location Manager Media Manager Surface Manager Crypto Manager User Linux Kernel Kernel Display Driver Camera Driver Flash Driver NFC Driver Power Mgmt Audio Driver... Keypad Driver Wifi Driver Smartcard Instead of this...

23 Applications Browser VPN Secure Voice Phone Home Contacts Calendar Application Framework Notification Manager Activity Manager Window Manager Resource Manager Package Manager Telephony Manager Location Manager Media Manager Surface Manager Crypto Manager Glue / HAL Platform support Display Driver Camera Driver Flash Driver NFC Driver Power Mgmt Audio Driver... Keypad Driver Wifi Driver Smartcard User Microkernel Kernel... we want this

24 Steps and Building Blocks picture

25 Prototype Architecture VM (private) VM Android userlevel software stack (unmodified) Busybox L4Android Kernel L4Android Kernel Platform support & device drivers mag fb-drv L4Linux (GPIO, Touch, Display, ) Runtime Environment sigma0 io moe Fiasco.OC

26 Cebit 2011 Intel Moorestown prototype Virtualized Android + 2nd Linux + driver Linux No direct hardware access Only touchscreen and display No sensors No network

27 Implementation Steps Patch L4Linux with Android binder, wakelocks, ashmem, GPIO subsystem Required for touchscreen and display fb-drv: MMIO replay from Linux driver

28 Towards the L4Android Framework Support for ARM and x86 Android Generic hardware interface for both architectures Require no hardware modifications or extensions

29 Screenshot

30 VM (private) VM (dev) VM (business) Android! (unmodified) Android HAL L4Android Kernel Paravirt Drivers Android! (unmodified) Android HAL L4Android Kernel Paravirt Drivers Android! (unmodified) Android HAL L4Android Kernel Paravirt Drivers Platform support & device drivers Display Touch Sensors Power Source Low level busses Clocks GPIO Timer L4Linux (Fileserver, ) Runtime Environment Memory Mgr IO Mgr Roottask Microkernel User Kernel L4Android Architecture

31 Applications picture

32 Easy to use!

33 Usability vs. Security Security == bad usability

34 SiMKo

35 SiMKo3 Requirements Open Source Solution Emphasis on security (MAC, small TCB) Reuse legacy software with existing VS-NfD approval Commodity OS

36 VM (private) VM (business) Android! (unmodified) Android HAL L4Android Kernel Paravirt Drivers Simple Userland, no UI!! VPN, Multiplexing Driver L4Linux!! (Modem, Storage, Smartcard, Audio) Android! (unmodified) Android HAL L4Android Kernel Paravirt Drivers Platform support & device drivers Display Touch Sensors Power Source Power Mgmt I2C SPI GPIO Timer Clocks Runtime Environment Memory Mgr IO Mgr Roottask Microkernel User Kernel SiMKo3 Architecture Multi-server OS

37 Life & Work picture

38 Ultimate Goal

39 How? L4Windows? No source code (well, ReactOS) Port Wine to L4Re? Compatibility Develop VMM? Implement legacy devices Port existing VMM? KVM

40 L4KVM Feature-rich VMM (read: runs Windows) x86, requires CPU with hardware assisted virtualization Use KVM from within L4Linux Modify KVM to use Fiasco.OC's virtualization API Configure VMCS Handle guest memory Helpful test case

41 VM Non-root mode Qemu Root mode L4Linux KVM-L4 L4Re Runtime Environment L4Re Microkernel SVM / VT-x Support L4KVM Architecture

42 L4KVM Status Linux guests 32bit 64bit AMD SVM Intel Vt-x

43 Genua Security Laptop

44 Internet Corporate LAN

45 VM L4Linux KVM Userland, no UI!! VPN, Firewall L4OpenBSD Runtime Environment Memory Mgr IO Mgr Roottask Microkernel User Kernel Under the Hood

46 Challenges picture

47 How to boot for fast development cycles? Custom bootloader with USB and fastboot support.

48 Is there a serial interface? Multiplexed via micro USB port or audio jack.

49 How to develop native drivers? Read TRMs with pages. Read Linux drivers.

50 Reuse proprietary binary blobs? 3G baseband Audio! Use L4Linux as driver

51 Power management? Frequency scaling Shutdown idle cores

52 Today's take aways Microkernel systems are used to build real-world systems being deployed to customers Understand what's beyond CPU and memory virtualization Sharply distinguish between Nanovisor, Microvisor, Microhypervisor, Secuvisor, Trustvisor and Budweiser.

53 *visor nomenclature

54 VM VM VMM VMM Nanovisor Nanovisor

55 VM VM VMM VMM Microvisor Microvisor

56 VM VM VMM VMM Microhypervisor Microhypervisor

57 VM VM VMM VMM Trustvisor Trustvisor

58 VM VM VMM VMM Secuvisor Secuvisor

59 Budweiser

VIRTUALIZATION. Dresden, 2011/12/6. Julian Stecklina

VIRTUALIZATION. Dresden, 2011/12/6. Julian Stecklina Department of Computer Science Institute of Systems Architecture, Operating Systems Group VIRTUALIZATION Julian Stecklina (jsteckli@os.inf.tu-dresden.de) Dresden, 2011/12/6 00 Goals Give you an overview