From Fedora Project Wiki
No edit summary
No edit summary
Line 26: Line 26:
* Xen pv_ops dom0 kernel is the default kernel in Xen hypervisor 4.0 release.
* Xen pv_ops dom0 kernel is the default kernel in Xen hypervisor 4.0 release.
* M A Young has built unofficial pv_ops dom0 kernel RPMs for testing, available from [http://fedorapeople.org/~myoung/dom0/ his directory], [http://repos.fedorapeople.org/repos/myoung/dom0-kernel/ or from new directory]. For feedback or questions about these kernels you should email to [https://admin.fedoraproject.org/mailman/listinfo/virt fedora-virt] or [https://admin.fedoraproject.org/mailman/listinfo/xen fedora-xen] mailinglists.  
* M A Young has built unofficial pv_ops dom0 kernel RPMs for testing, available from [http://fedorapeople.org/~myoung/dom0/ his directory], [http://repos.fedorapeople.org/repos/myoung/dom0-kernel/ or from new directory]. For feedback or questions about these kernels you should email to [https://admin.fedoraproject.org/mailman/listinfo/virt fedora-virt] or [https://admin.fedoraproject.org/mailman/listinfo/xen fedora-xen] mailinglists.  
* Note that the latest pvops dom0 kernels require Xen hypervisor 4.0.1!! src.rpm for fedora available from: http://pasik.reaktio.net/fedora/xen-4.0.1-0.1.rc6.fc13.src.rpm or from: http://koji.fedoraproject.org/koji/taskinfo?taskID=2400559 .
* Note that the latest pvops dom0 kernels require Xen hypervisor 4.0.1!! src.rpm for fedora available from: http://pasik.reaktio.net/fedora/xen-4.0.1-0.2.fc13.src.rpm or from: http://koji.fedoraproject.org/koji/taskinfo?taskID=2426589 .
* If you want to build your own custom dom0 kernel, see the upstream [http://wiki.xensource.com/xenwiki/XenDom0Kernels XenDom0Kernels wiki page]
* If you want to build your own custom dom0 kernel, see the upstream [http://wiki.xensource.com/xenwiki/XenDom0Kernels XenDom0Kernels wiki page]
== Detailed Description ==
== Detailed Description ==

Revision as of 19:56, 25 August 2010

Feature Name

Summary

Dom0 support for pvops-based kernel to support hosting of Xen guests which has been lacking since Fedora 8.

Currently Fedora releases (9, 10, 11, 12, 13) contain Xen hypervisor and tools, but Xen dom0 (host) capable kernel is missing.

Owner

  • Name: None

Previously involved: EduardoHabkost, MarkMcLoughlin, Stephen Tweedie, Chris Wright, Juan Quintela, Markus Armbruster, Glauber Costa, DanielBerrange, ...

Current status

  • Last updated: 2010-08-16
  • Percentage of completion: 0%
  • Targeted release: F14
  • Dom0 status: awaiting upstream kernel support
  • Background:
Upstream status and build instructions, XenParavirtOps on xenwiki,
Upstream patches (git branches):

Detailed Description

See Features/XenPvops for a rationale. This feature just continues the paravirt_ops Xen effort to bring it back to feature parity with Fedora 8 Xen.

Scope

Work items:

  • Implement Dom0 support in upstream kernel (JeremyFitzhardinge)
  • Allow the hypervisor to boot bzImage kernels (see this patch included since xen-3.3.1-3.fc11)
  • Make 'new-kernel-pkg' aware of HYPERVISOR setting in /etc/sysconfig/xen
  • Wait for that upstream kernel version to be pulled into Fedora

How To Test

  • Install a Fedora host/Dom0 system
  • Turn on Xen Hypervisor by setting 'HYPERVISOR=/boot/xen-4.0.gz' in /etc/sysconfig/kernel and running some tool (TBD)
  • Turn on Xen Userspace by running 'chkconfig xend on'
  • Reboot
  • Observe presence of Xen via /sys/hypervisor/
  • Run 'xm list' and observe Domain-0
  • Use virt-install to deploy a Fedora 11/12/13 paravirt guest
  • Use virt-install to deploy a Fedora 11/12/13 fullyvirt guest
  • Use 'virsh' to save & restore a PV guest and HVM guest
  • Balloon down memory of a guest with virsh.

User Experience

  • Stock Fedora kernel supports Xen dom0
  • The Xen kernel does not lag behind the Fedora kernel
  • All features and hardware supported on baremetal also works on Xen Dom0
  • Can enable/disable use of HV via a /etc/sysconfig setting

Dependencies

  • Update to 'new-kernel-pkg' to know how to install HV

Contingency Plan

If Dom0 support is not ready, continue the status quo of only shipping with DomU support.

Documentation

Release Notes

Comments and Discussion