Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 680114[details]
It includes engine.log and vdsm.log files.
Description of problem:
The virtual machine can not start in the rhevm si26.
And there is also error in the events of the rhevm:
2013-Jan-17, 14:53 Failed to run VM re (User: admin@internal). 100d2f53
2013-Jan-17, 14:53 Failed to run VM re on Host dell-per210-01.qe.lab.eng.nay.redhat.com. 100d2f53
2013-Jan-17, 14:53 VM re is down. Exit message: internal error Cannot find suitable CPU model for given data.
2013-Jan-17, 14:53 VM re was started by admin@internal (Host: dell-per210-01.qe.lab.eng.nay.redhat.com). 100d2f53
Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20130109.1.auto1389.el6
QE will retest this bug when we get the official rhevh build.
How reproducible:
100%
Steps to Reproduce:
1. Install rhev-hypervisor6-6.4-20130109.1.auto1389.el6
2. Configure network for rhev-h
3. Register rhev-h to rhevm via port 443.
4. Install virtual machine in rhevm.
5. Run the virtual machine.
Actual results:
After step5, virtual machine can not start.
Expected results:
After step5, virtual machine can start successfully.
Additional info:
Re-test this build on official RHEV-H 6.4 snapshot 4 build on SI26, rhev-hypervisor6-6.4-20130116.3.0.el6, this issue can not be reproduced, so close this bug as worksforme
Created attachment 680114 [details] It includes engine.log and vdsm.log files. Description of problem: The virtual machine can not start in the rhevm si26. And there is also error in the events of the rhevm: 2013-Jan-17, 14:53 Failed to run VM re (User: admin@internal). 100d2f53 2013-Jan-17, 14:53 Failed to run VM re on Host dell-per210-01.qe.lab.eng.nay.redhat.com. 100d2f53 2013-Jan-17, 14:53 VM re is down. Exit message: internal error Cannot find suitable CPU model for given data. 2013-Jan-17, 14:53 VM re was started by admin@internal (Host: dell-per210-01.qe.lab.eng.nay.redhat.com). 100d2f53 Version-Release number of selected component (if applicable): rhev-hypervisor6-6.4-20130109.1.auto1389.el6 QE will retest this bug when we get the official rhevh build. How reproducible: 100% Steps to Reproduce: 1. Install rhev-hypervisor6-6.4-20130109.1.auto1389.el6 2. Configure network for rhev-h 3. Register rhev-h to rhevm via port 443. 4. Install virtual machine in rhevm. 5. Run the virtual machine. Actual results: After step5, virtual machine can not start. Expected results: After step5, virtual machine can start successfully. Additional info: