Your SlideShare is downloading. ×
LCA14: LCA14-101: ARM VM Standards
LCA14: LCA14-101: ARM VM Standards
LCA14: LCA14-101: ARM VM Standards
LCA14: LCA14-101: ARM VM Standards
LCA14: LCA14-101: ARM VM Standards
LCA14: LCA14-101: ARM VM Standards
LCA14: LCA14-101: ARM VM Standards
LCA14: LCA14-101: ARM VM Standards
LCA14: LCA14-101: ARM VM Standards
LCA14: LCA14-101: ARM VM Standards
LCA14: LCA14-101: ARM VM Standards
LCA14: LCA14-101: ARM VM Standards
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

LCA14: LCA14-101: ARM VM Standards

261

Published on

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

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
261
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
20
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Mon-3-Mar, 10:05am, Christoffer Dall LCA14-101: ARM VM Standards
  • 2. • 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
  • 3. • 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
  • 4. • 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
  • 5. • 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
  • 6. • 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
  • 7. • 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
  • 8. • 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
  • 9. • 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
  • 10. • 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
  • 11. • RFC: http://lists.linaro.org/pipermail/cross-distro/2014-February/000589.html • Questions? Resources and Questions
  • 12. 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

×