(→Current status: update gitweb links to upstream patches) |
No edit summary |
||
Line 12: | Line 12: | ||
== Current status == | == Current status == | ||
* Last updated: 2009- | * Last updated: 2009-07-06 | ||
* Percentage of completion: 0% | * Percentage of completion: 0% | ||
* Targeted release: F12 | * Targeted release: F12 or F13 | ||
* Dom0 status: awaiting upstream kernel support | * Dom0 status: awaiting upstream kernel support | ||
* Background: | * Background: | ||
: [http://wiki.xensource.com/xenwiki/XenParavirtOps Upstream status], | : [http://wiki.xensource.com/xenwiki/XenParavirtOps Upstream status, XenParavirtOps on xenwiki], | ||
: Upstream patches: | : Upstream patches: | ||
:* [http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen-tip/master xen-tip/master] - known-working branch, with only tested changes | :* [http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen-tip/master xen-tip/master] - known-working branch, with only tested changes | ||
:* [http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen-tip/next xen-tip/next] - current bleeding edge; should at least compile | :* [http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen-tip/next xen-tip/next] - current bleeding edge; should at least compile | ||
* News: [[FWN/Issue169#Success_with_Experimental_Fedora_10_pv_ops_dom0|FWN #169]], [[FWN/Issue152#Status_of_dom0_Support_in_Upstream_Kernel|FWN #152]], [[FWN/Issue137#State_of_Xen_in_Upstream_Linux|FWN #137]] | * News: [[FWN/Issue169#Success_with_Experimental_Fedora_10_pv_ops_dom0|FWN #169]], [[FWN/Issue152#Status_of_dom0_Support_in_Upstream_Kernel|FWN #152]], [[FWN/Issue137#State_of_Xen_in_Upstream_Linux|FWN #137]] | ||
: [http://lists.xensource.com/archives/html/xen-devel/2008-02/msg00047.html old status #1], [http://lists.xensource.com/archives/html/xen-devel/2008-02/msg00242.html old status #2] | : [http://lists.xensource.com/archives/html/xen-devel/2008-02/msg00047.html old status #1], [http://lists.xensource.com/archives/html/xen-devel/2008-02/msg00242.html old status #2], [http://lists.xensource.com/archives/html/xen-devel/2009-06/msg01193.html pv_ops dom0 status report, June 2009] | ||
* M A Young has built unofficial pv_ops dom0 kernel RPMs for testing, available from [http://fedorapeople.org/~myoung/dom0/ his directory]. For feedback or questions about these kernels you should email to fedora-xen or fedora-virt mailinglists. Note that these kernels are not meant for production use, they're only for beta testing. | |||
* 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 14:28, 6 July 2009
Feature Name
Summary
Dom0 support for pvops-based kernel
to support hosting of Xen guests which has been lacking since Fedora 8.
Owner
- Name: None
Previously involved: EduardoHabkost, MarkMcLoughlin, Stephen Tweedie, Chris Wright, Juan Quintela, Markus Armbruster, Glauber Costa, DanielBerrange, ...
Current status
- Last updated: 2009-07-06
- Percentage of completion: 0%
- Targeted release: F12 or F13
- Dom0 status: awaiting upstream kernel support
- Background:
- Upstream status, XenParavirtOps on xenwiki,
- Upstream patches:
- xen-tip/master - known-working branch, with only tested changes
- xen-tip/next - current bleeding edge; should at least compile
- M A Young has built unofficial pv_ops dom0 kernel RPMs for testing, available from his directory. For feedback or questions about these kernels you should email to fedora-xen or fedora-virt mailinglists. Note that these kernels are not meant for production use, they're only for beta testing.
- If you want to build your own custom dom0 kernel, see the upstream XenDom0Kernels wiki page
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-3.3.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 9/10 paravirt guest
- Use virt-install to deploy a Fedora 8 paravirt guest
- Use virt-install to deploy a Fedora 8/9/10 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
- 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.