Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Mobile Virtualization using the Xen Technologies


Published on

Xen has been very successful on servers, and yet there are substantial areas where Xen can evolve further. In this talk Jun will discuss a compelling area where the Xen technologies can be applied to -- Mobile virtualization. Using Android as an example, the talk will explore two types of usage models, 1) Android as a guest, 2) Android as the host, showing the benefits of using the Xen technologies.

Published in: Technology, Business
  • Be the first to comment

Mobile Virtualization using the Xen Technologies

  1. 1. Mobile  Virtualiza/on  using  the  Xen  Technologies  Jun  Nakajima  Intel  Corpora9on  Sponsored  by:   &   &  
  2. 2. Legal DisclaimerŸ  INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL® PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL’S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF INTEL® PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. INTEL PRODUCTS ARE NOT INTENDED FOR USE IN MEDICAL, LIFE SAVING, OR LIFE SUSTAINING APPLICATIONS.Ÿ  Intel may make changes to specifications and product descriptions at any time, without notice.Ÿ  All products, dates, and figures specified are preliminary based on current expectations, and are subject to change without notice.Ÿ  Intel, processors, chipsets, and desktop boards may contain design defects or errors known as errata, which may cause the product to deviate from published specifications. Current characterized errata are available on request.Ÿ  Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.Ÿ  *Other names and brands may be claimed as the property of others.Ÿ  Copyright © 2011 Intel Corporation. Xen Summit Asia 2011 2
  3. 3. AgendaŸ Mobile VirtualizationŸ PC/Server vs. Mobile device virtualizationŸ Example: Android™ VirtualizationŸ Advantages of Xen Technologies and OpportunitiesŸ Xen-Based Android* ArchitectureŸ Innovation/Research Required for Xen Mobile Virtualization XenSummit Asia 2011 *: Simply Android for Android™ hereafter 3
  4. 4. What’s Mobile Virtualization?Ÿ Virtualization of mobile platforms –  E.g. Android as a guest on laptop, desktop, cloud… –  BlueStacks*, Android EmulatorŸ Virtualization on mobile platforms –  E.g. Android as the host such as smartphone, tablet –  Red Bend*, Mobile Virtual Platform* (VMware*), Motorola Atrix 4G*Ÿ Combination –  E.g. Android guest on Android host XenSummit Asia 2011 4
  5. 5. Why Mobile Virtualization?Ÿ Many devices and many reasons –  Dual personality (business, personal) –  Multiple OS (e.g. Android + Windows*) –  Security enhancements –  “Secure Xen on ARM” (Samsung*) –  Reusing existing software stacksŸ Potential drawbacks –  Virtualization overhead affecting performance and power, higher latency –  Extra efforts to rebase, certify –  More complex XenSummit Asia 2011 5
  6. 6. PC/Server vs. Mobile Device VirtualizationŸ Typical VMMs virtualize PC/servers –  No mobile devices support, such as GPS, accelerometer, gyroscope, touch screen, telephony, etc. –  No skin support. –  Qemu has some mobile devices support XenSummit Asia 2011 6
  7. 7. Example: Android VirtualizationŸ Android Emulator in Android SDK –  Android-specific modifications to qemu –  Framebuffer, sound, tty, serial, MMC, NAND, etc. –  Software emulation for ARM and x86 –  Emulator with hardware-assist (e.g. Intel® VT) for x86 –  KVM on Linux* today (about 10x faster). Available since SDK Tools Revision 12**. –  Porting to Xen should be easy –  GLES H/W acceleration(via qemu_pipe)Ÿ Android Guest –  Linux (“Goldfish” kernel) + PV devices **: XenSummit Asia 2011 7
  8. 8. Opportunities for XenŸ Goldfish kernel –  32-bit UP HVM Linux kernel (2.6.29 as of today) –  Works well for SDK environment, Save/Restore feature. –  Can be very expensive on mobile devicesŸ Xen PV –  PVOPS kernel: lower virtualization overhead and/or eliminate need for hardware-assisted virtualization –  No qemu: frontends for mobile devices to avoid dependency on qemuŸ Live migration –  Example: Between laptop and cloudXenSummit Asia 2011 8
  9. 9. Hypervisor Architecture ConsiderationsType 1: Bare metal Hypervisor Type 2: OS ‘Hosted’A pure Hypervisor that runs directly on A Hypervisor that runs within a Host OSthe hardware and hosts Guest OS’s. and hosts Guest OS’s inside of it, using the host OS services to provide the virtual environment. VMn User-level VMM VMn VM1 VM0 VM0 Device User Models Apps Guest OS Guest OS and Apps and Apps Host OS Hypervisor Device Ring-0 VM MonitorDevice Drivers / Models Drivers Kernel Scheduler MMUHost HW Host HW Memory CPUs I/O Memory CPUs I/O XenSummit Asia 2011 isola,on  +   Provides    par,,on   Low  cost,  no  addi,onal  drivers     reliability,  higher  security  Other names and brands may be claimed as the property of others.
  10. 10. More Opportunities − Architectural Advantage of Xen Ÿ  Thin hypervisor VMn –  Open sourceDomain 0 VM1 –  Proprietary code in guestsHigh-level Monitor VM0 Device Models Guest OS Ÿ  Use Linux in upstream and AppsLinux –  Take full advantage of PV –  PV on HVM Device Models Xen Hypervisor (Timer, Interrupt) –  No additional device drivers (Linux 3.x dom0) Memory CPUs Host HW Ÿ  Use hardware assistance I/O for unmodified guests Hybrid Architecture XenSummit Asia 2011 10
  11. 11. Xen-Based Android w/o HVM Domain 0 Domain 1 Domain N Guest Control App Host Guest *OS Libxenlingh/Bionic (libc) Linux PVOPS Kernel Linux PVOPS Kernel Native Device Backend Virtual Frontend Virtual Drivers driver Drivers Callback / Hypercall Xen Hypervisor Event channel Physical Host HardwareXenSummit Asia 2011 11
  12. 12. Xen-Based Android w/ HVM Domain 0 Domain 1 Domain N Device models (qemu-dm) Device models (stubdomain) Guest Control App Host Guest *OS Libxenlingh/Bionic (libc)Linux PVOPS Kernel Backend Virtual Frontend Virtual Native Device drivers Drivers Drivers Virtual Platform Callback / Hypercall VMExit Xen Hypervisor Event channel Physical Host HardwareXenSummit Asia 2011 12
  13. 13. Innovation/Research Required for Xen Mobile VirtualizationŸ Power management –  Optimized for mobile devicesŸ Realtime –  RTOS guests supportŸ SecurityŸ Mobile device virtualization XenSummit Asia 2011 13
  14. 14. ConclusionŸ Mobile virtualization will be more importantŸ Xen has unique advantages there –  Thin hypervisor, driving innovations for virtualization –  Keeping PVOPS for dom0 in Linux upstream is keyŸ Proposed Xen-based Android systemŸ Let’s get started! XenSummit Asia 2011 14