RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

I'm not able to boot to the anaconda for these OS:

* Fedora 16 (when installing using fedora-updates repo)

Machine will stuck right after reboot, just blank screen with '_' character
in VNC session. The CPU usage of KVM on hypervisor is 100%.

* Fedora 17 (netinstall)

Machine is stuck in booting (see attached screenshot)

* Fedora 18 (netinstall)

Same story as Fedora 17

Version-Release number of selected component (if applicable):

RHEV-M 3.1 (si18.1)
qemu-kvm-rhev (0.12.1.2, 2.295.el6_3.2)
qemu-kvm (0.12.1.2, 2.295.el6_3.2)

Steps to Reproduce:

1. Upload ISO image for Fedora netinstall (F17, F18)
2. Create VM, 15 GB thin provisioning, 1 virtio NIC
3. Boot machine
4. Start VNC session
5. Remove quite boot option in boot splash screen
6. Boot.
  
Actual results:

See screenshot. For all these tree issues, the CPU load of qemu process is 100%.

Expected results:

Fedora should boot.

Created attachment 614854 [details]
Screenshot from VNC session

can you boot them from virt-manager/plain qemu-kvm?

(In reply to comment #1)
> Created attachment 614854 [details]
> Screenshot from VNC session

You are trying netinstall, could it be that the NetInstall has a reduced drivers set that do not support virtio net?

Did you try with alternative network cards?

Yes, I tried all network cards and also I tried the standard Live installation CD. All with no success :-(

I've just tested on my setup with Fedora 16 live CD, it's the same. 

Moving this bug to qemu.

*** This bug has been marked as a duplicate of bug 839156 ***