Xen Summit 2009 Shanghai Ras
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Xen Summit 2009 Shanghai Ras

on

  • 1,658 views

Xen.org community presentation from Xen Summit Asia 2009

Xen.org community presentation from Xen Summit Asia 2009

Statistics

Views

Total Views
1,658
Views on SlideShare
1,658
Embed Views
0

Actions

Likes
0
Downloads
3
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

Xen Summit 2009 Shanghai Ras Presentation Transcript

  • 1. Towards Mission Critical Xen -- RAS Enabling Update Jiang, Yunhong <yunhong.jiang@intel.com> Ke, Liping <liping.ke@intel.com> Liu, Jinsong <jinsong.liu@intel.com>
  • 2. Legal Information 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 may make changes to specifications and product descriptions at any time, without notice. All products, computer systems, dates, and figures specified are preliminary based on current expectations, and are subject to change without notice. Intel is a trademark of Intel Corporation in the U.S. and other countries. *Other names and brands may be claimed as the property of others. Copyright © 2009, Intel Corporation. All rights are protected. 2
  • 3. Agenda • Overview • CPU/Memory error handling • Host CPU hot-plug support • Guest vCPU Hot-plug 3
  • 4. Continuous Improvement on RAS Support February 2009 Now (Xen Summit North America 2009) CPU/Memory error •Infrastructure proposed Checked-in handling •Implementation WIP I/O error handling • Infrastructure proposed WIP for HVM guest support • PV guest supported Host CPU hot-add Not Started Yet checked-in Host memory hot-add Not started yet WIP Guest vCPU hot-plug Not started yet Ready for send out Guest vMem hot-plug Not started yet May not support 4
  • 5. Agenda • Overview • CPU/Memory error handling • Host CPU hot-plug support • Virtual CPU Hot-plug 5
  • 6. Why error handling enhancement – Motivation Pre-Virtualization – 1 App/svr, error kills 1 application X Post-Virtualization – ~5-10 App/svr HW/HV error kills all 5-10 applications X Error handling enhancements HW/HV error kills 1 virtual application that error localized X 6 Any difference in system hardware or software design or configuration may affect actual performance.  6
  • 7. Retrospect: CPU/Memory Error Handling • Error happens to CPU or Flow memory and is detected by hardware – E.g. ECC error in L3 Cache , ECC error in memory cell • A MCE (Machine Check Exception) is raised to Xen hypervisor • Xen hypervisor MCE handler will parse error information – Information from: MCE error code, MCE MSRs etc • Xen hypervisor take action to recover the error, e.g. – Offline a page for memory error – Killing impacted guest • System continues if error is recovered successfully – Log the error information in dom0 • Otherwise reset the system 7
  • 8. Retrospect: CPU/Memory Error Handling Architecture Dom0 DomU User space tools (FMA/ Mcelog) vIRQ vMCE vMCE handler handler handler Xen MCA Page offline telemetry MCA MSR Virt CPU offline Action Reset System MCA Handler MCE Hardware X Error Infrastructure is implemented Already by Ke, Liping/Frank van der Linden/ Christoph Egger 8
  • 9. Next Step for CPU/Memory Error Handling • Add xen awareness to Linux MCA tools • Support for more MCA error code – Now Supports two software recoverable Errors • UCR Errors detected by memory controller scrubbing • UCR Errors detected during L3 cache explicit write-backs • Enhancement to memory error handling (see next pages) 9
  • 10. Memory Error Handling– Current Solution • Reading access to broken memory affects data integrity – Whole system may even crash • Recover action from xen hypervisor Type Probability Action Free Depends on Offline the page workload memory Guest memory Large •Off line the page when it is freed • A virtual MCE is sent to guest Critical Memory Small Reset the system •Xen’s private data/heap •Shadow/HAP/IOMMU/P2M page tables •The granted memory used by backend service 10
  • 11. Memory Error Handling Enhancement (Cont’d) • Issue: Xen may access broken guest memory – Xen scans guest’s page tables when killing shadow mode guest • Xen hypervisor crashes if one page table page is broken – Xen access guest’s memory for instruction emulation – KExec access the broken pages – …… – Proposal: Avoid high-possibility access • Issues: guest’s access to broken memory is not prevented – Malicious guest can trigger system crash – Proposal: Detecting the access in Xen hypervisor in advance 11
  • 12. Agenda • Overview • CPU/Memory error handling • Host CPU hot-plug support • Guest vCPU Hot-plug 12
  • 13. Host CPU Hot-add Support • Host CPU hot-add works in Xen environment through 2 steps • Step 1: CPU is marked present – A CPU is hot-added to physical platform – Platform raise a interrupt (SCI) to dom0 – Dom0’s ACPI driver parses the ACPI table to get CPU information – Dom0’s ACPI driver notify Xen hypervisor of a new CPU added – The new CPU is marked present in xen hypervisor, but will not be scheduled • Step 2: management tools notify Xen hypervisor to bring the CPU online 13
  • 14. Host CPU Hot-add Dom0 Management Tools sysfs Xen PCPU ACPI Driver Driver Hypercall Hypercall Xen CPU Online CPU Add ACPI Notification HW CPU ACPI Patch is on the way to upstream 14
  • 15. Agenda • Overview • CPU/Memory error handling • Host CPU hot-plug support • Guest vCPU Hot-plug 15
  • 16. HVM Guest vCPU Hotplug • Hot-add/remove HVM guest’s vCPU dynamically – PV guest has vCPU hot-plug for a long time • Code is almost ready 16
  • 17. HVM Guest vCPU Hotplug Dom0 DomU QEMU Hot plug Control Driver Panel (xm vcpu-add) Virtual ACPI HW Virtual BIOS Virtual ACPI Table Notification Xen vCPU Management 17
  • 18. Next Step for RAS Effort • CPU/Memory Enhancement • PCI AER support for device assigned to HVM guest – Based on PCI-Express support in Qemu • Host memory hot-add support 18