Description of problem: Installation of Fedora 7 as a Xen Guest OS gets stuck when no drives are presented to the user to use to install the OS. Version-Release number of selected component (if applicable): F7 How reproducible: Always Steps to Reproduce: 1. Create new domain in Virtual Manager 2. Point media URL to good mirror. 3. Proceed through Anaconda screens until partitioning screen 4. Here you are stuck with no drive choices. 5. If you try to proceed an error pops up telling you there are no drives. Actual results: Cannot select a drive to partition. Installation stuck here. Expected results: Can select a drive to partition for installation. Installation completes. Additional info: Host: FC6 Host kernel: 2.6.20-1.2952.fc6xen Xen: 3.0.3-9
This was a file-based Domain.
Have the same thing happening with Vmware-workstation 5.5.2. Host FC6 2.6.20-1.2952. Default creation of a vm chooses SCSII, but no drives are presented on which to install. Manually editing config, deleting the SCSI disk and adding an IDE allows one to do the install but I am getting lots of disk errors reported by the guest kernel.
I retried this over the weekend with a new image and new domain and this time the 'xvda' partition was available. So I don't know why it wouldn't show up before but at least this time it worked.
I suspect this may be a dup of bug 239572, basically an SELinux problem which is now fixed.
Hello, I'm reviewing this bug as part of the kernel bug triage project, an attempt to isolate current bugs in the fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug and will try and assist you in resolving it if I can. There hasn't been much activity on this bug for a while and it appears to be fixed as per comment 4. Could you tell me if you are still having problems with the latest kernel? I have re-assigned to the xen team who may be able to shed more light on this. If the problem no longer exists then please close this bug or I'll do so in a few days if there is no additional information lodged. Cheers Chris
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. 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 WONTFIX if it remains open with a Fedora 'version' of '7'. 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 prior to Fedora 7's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 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 please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you. 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. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists. Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs: http://docs.fedoraproject.org/release-notes/ The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. Fedora 7 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. Thank you for reporting this bug and we are sorry it could not be fixed.