Xen 4.3 Roadmap

  • 168,315 views
Uploaded on

The Xen 4.3 release we will experiment with a roadmap: an informal set of features and changes that we as a community will be aiming at for the 4.3 release. The roadmap is flexible, but will be used …

The Xen 4.3 release we will experiment with a roadmap: an informal set of features and changes that we as a community will be aiming at for the 4.3 release. The roadmap is flexible, but will be used as a guide to coordinate our efforts, as well as a benchmark to let us know when 4.3 will be ready to release.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • Very Good
    Are you sure you want to
    Your message goes here
    Be the first to like this
No Downloads

Views

Total Views
168,315
On Slideshare
0
From Embeds
0
Number of Embeds
15

Actions

Shares
Downloads
40
Comments
1
Likes
0

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. Planning for Xen 4.3
  • 2. Adding structure to the release process● 4.2 “Release coordinator”: Ian Campbell – Tracking blocking features and bugs● Citrix xen.org team: tracking improvements● 4.3 Release coordinator: George Dunlap – Tracking features and improvements – Guiding community discussions● Ultimately community decided
  • 3. Xen 4.3: When?● Time-based or feature-based?● Xen 4.2 – 4.1 released March 25 2011 – 17 months – Development → Release → Distros● Xen 4.3: Aiming for 9 months – June 2013 release – 6 weeks of RCs, 6 weeks of polishing – March 2013 feature freeze
  • 4. Tracking features● Big reason for delay: libxl stable interface – No one realized how much more work there was!● Looking ahead: What can we finish by 4.3? – Lots!
  • 5. Group: Feature Parity● Upstream feature parity – Blktap3 – Default to qemu-upstream● Qemu stubdomain / dom0 parity – PV audio
  • 6. Blktap3: blktap for pvops● Blktap2: Enable user-space interposition on block device – QCOW – VHD – Snapshotting● Not upstreamable (DKMS packages avail)● Blktap3: Fully user-space
  • 7. Group: Scalability● Ram limit (16 TiB)● Raising event-channel limits
  • 8. Event channel scalability● Event pending, 2-level bit array – 32-bit: 1024 – 64-bit: 4096● Each PV service requires 1 event channel – Disk, net, console, xenstore = 4 – 32-bit: max 256 guests
  • 9. Group: Performance● NUMA – Real NUMA affinity – Guest memory migration – Virtual NUMA topology● PVH – PV with HVM extensions● Persistent grants● Multi-page blk, net rings
  • 10. PVH: PV + HVM● PV developed before HVM, HAP available● Issues – Ugly hooks in Linux – PT-heavy operations still slow – 64-bit system calls● PVH: Use HVM extensions to remove MMU pvops
  • 11. The Virtualization Spectrum● Disk/network?● Interrupts / timers?● Emulated motherboard, BIOS?● Legacy boot?● Privileged instructions?● Pagetables (pvops MMU)?
  • 12. Group: New Technologies● ARM servers● Openvswitch integration● EFI: Signed xen image from build
  • 13. xl improvements● vm import/export● USB pass-through● Backend driver script rationalization
  • 14. Group: New features● Nested virtualization – Win* “WinXP compatibility mode”● Full-VM snapshotting / cloning● Storage migration
  • 15. Getting feedback● How do developers know what users want?● Uservoice.com – Suggest improvements – Vote on which ones are the most important● http://xenorg.uservoice.com
  • 16. Conclusion and Questions● Release cycle – March 2013 feature freeze – June 2013 release● Lots of great features!● xenorg.uservoice.com