Bug 161083
Summary: | Wrong version number. Too old version. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Nils Toedtmann <bugzilla.redhat.com> |
Component: | xen | Assignee: | Rik van Riel <riel> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-06-20 21:07:42 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nils Toedtmann
2005-06-20 14:47:27 UTC
+1 from me for this request. I agree with the verion number issue, but it's too late to fix that for FC4. As for upgrading to a new Xen snapshot, that also requires changing the kernel, since the handling of ACPI moved from Xen into domain 0. I tried upgrading rawhide to a newer Xen (before FC4), but that version did not boot on my test system, so I decided to stay with the version from FC4 test 3. I agree on the /boot/xen-<version>.gz idea in principle, but in practice it turns out that things break far too often if the xen.gz does not match the installed utilities - that interface is also still in flux. IMHO the proper fix for the xenU kernel living outside of the domain's filesystem is to have a Xen bootloader - which is available upstream and will be in newer Xen RPMs for rawhide. That way the kernel can just live inside the domU. I will upgrade Xen in rawhide, once Xensource has a Xenolinux for 2.6.12. |