Hide Forgot
Description of problem: xen does not boot into current kernel "ERR: no-real-mode edd=off" HW: P4, HT enabled, 2GB RAM OS: kernel: 3.11.1-300 i686+PAE xen: 4.3.0-4 libvirt: - Version-Release number of selected component (if applicable): - doing a standard fedora 20 installation from netinstall iso (minimal) -- install xen (yum install xen -y) --- optional: install libvirt ---- restart and select xen boot option(s) How reproducible: - always Steps to Reproduce: - as outlined above Actual results: - got stuck in the first line -- just can see: ERR: no-real-mode edd=off Expected results: - boot in xen dom0 environment Additional info: Don't know which component to blame for! Issue might be redirected. - xen? - modified i686 kernel? - grub xen boot-script options? Tested newer fedora 21 kernel(-PAE) and xen version but no success!
I suspect there are two separate issues. If by P4 you mean Pentium 4 then I think the main issue is that xen-4.3 drops support for a 32-bit hypervisor. The hypervisor in the i686 package is actually 64-bit as a 32-bit dom0 will still work with it given suitable hardware. The second issue is that the grub2-config is generating xen configuration that adds options it shouldn't to the xen hypervisor line.
You`re right. P4 addresses a Pentium 4 cpu. As is understand you correctly xen 4.3.x does not provide a 32bit dom0 on 32-bit hardware anylonger. So if 32-bit dom0 support is dropped in general and wouldn't be backported (as I've to admit that P4 isn't a very modern processor), I'll stay with F19 xor Xen 4.2.x. Thanks for pointing that out.
You're right, 32-bit hypervisor dom0 support has been dropped as already announced on xen mailing list. Time to afford newer hardware, then KVM will be an additonal option. Maybe a litte off-topic: Tested the latest xen 4.2.x version for F20 (alpha) on a 32-bit baremetal system and Fedora comes up with priviledged domain. Is there a convenient way to remain at a specific (old) XEN package version, inlcuding related packages, like - libvirt - python-virtinst - virt-manager while installing a fresh Fedora Release? After packages are installed those might be excluded in yum.conf from future update. I manually downloaded a few older packages of xen, libvirt, python-virtinst, virt-manager and used 'yum --disablerepo=updates-testing --exlcude=xyz' but ran into dependency problems with conflicting xen 4.2 packages which are supposed to be updated to 4.3 ... No doubt 4.2 support will be dropped sometime as xen development turns to 4.3 and above. So I'm afraid F19 will be the latest version which offers support for 4.2 xen branch.
BTW 32-bit Dom0 is still completely supported, but Xen itself only runs in 64-bit mode.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.