• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
LCA14: LCA14-101: ARM VM Standards
 

LCA14: LCA14-101: ARM VM Standards

on

  • 240 views

Resource: LCA14

Resource: LCA14
Name: LCA14-101: ARM VM Standards
Date: 03-03-2014
Speaker: Christoffer Dall
Video: https://www.youtube.com/watch?v=Qh3SX3p3B74

Statistics

Views

Total Views
240
Views on SlideShare
240
Embed Views
0

Actions

Likes
0
Downloads
12
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    LCA14: LCA14-101: ARM VM Standards LCA14: LCA14-101: ARM VM Standards Presentation Transcript

    • Mon-3-Mar, 10:05am, Christoffer Dall LCA14-101: ARM VM Standards
    • • Discussion at LCU13 • Trying to answer main question: How do distribution vendors package and ship ARM VMs so that they can be expected to run on the ARM hypervisors out there? Background
    • • RFC sent to: • cross-distro@lists.linaro.org • kvmarm@lists.cs.columbia.edu • kvm@vger.kernel.org • linux-arm-kernel@lists.infradead.org • xen-devel@lists.xen.org Proposed ARM VM Image Spec
    • • Build single image, run everywhere • Valid recommendations for both aarch32 and aarch64 • The SBSA doesn’t cover it • Mandated EL2 • Mandates pl011 • aarch32 not supported Goal
    • • Must be well-defined • Must be GPT with EFI application in EFI System Partition (ESP) • Must use removable path (no preexisting UEFI config) • Supports both KVM and Xen • Example: Grub2 as EFI application loads Linux Image Format
    • • Required: Must be able to boot EFI application in ESP • Obvious recommendation is UEFI implementation • Linaro is already working on this • Recommended to support persistent environment storage: • Supports adding disks later • Supports running installers later • Firmware distributed as part of distribution, not with VM image Virtual Firmware
    • • The Linux kernel boot protocol requires an FDT • Even when using ACPI and UEFI • FDT -> UEFI System Table -> ACPI root pointer • Therefore: • ACPI is discoverable through FDT, or • the FDT describes the system directly Hardware Description
    • • Must support at least one of: • (1) aarch32 on aarch32 • (2) aarch32 on aarch64 • (3) aarch64 on aarch64 • Mandatory peripherals: • Serial console (pl011, virtio-console, or Xen PV console) • GICv2 or newer • Architected Timer • Hotpluggable bus (virtual PCIe or Xen PV bus) VM Platform
    • • Must support GICv2 and newer. Maintaining backwards compatibility. • Strongly recommended to support all of: • block, network, console, balloon drivers, e.g. • virtio-pci • virtio-mmio • Xen PV drivers • Will leverage mach-virt kernel facilities, but these are loosely coupled concepts. Guest OS Recommendations
    • • Mandate serial port (reduced pl011) • Use cases for ACPI (device assignment, verification, unification) • Fixed memory map (UEFI) • Issue concerning kernel comand line (console=?) Open Questions
    • • RFC: http://lists.linaro.org/pipermail/cross-distro/2014-February/000589.html • Questions? Resources and Questions
    • More about Linaro Connect: http://connect.linaro.org More about Linaro: http://www.linaro.org/about/ More about Linaro engineering: http://www.linaro.org/engineering/ Linaro members: www.linaro.org/members