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.
Description
rhel7 guest will be shutoff when click "Reboot" after installation on rhel5 xen host
Version:
rhel5 host version:
# uname -r
2.6.18-371.el5xen
# rpm -qa libvirt virt-manager
libvirt-0.8.2-29.el5_9.1
virt-manager-0.6.1-16.el5
rhel7 guest:
RHEL-7.0-20140403.3 tree
How reproducible:
100%
Steps to Reproduce:
1.Launch virt-manager.
2.Create a new rhel 7 guest,use http or iso to install a hvm guest.
3.After installation finished,click "Reboot" button of installation GUI,see the screenshot.The guest will be shutdown instead of reboot.
4.If I boot the guest manually and click "reboot" button from virt-manager GUI,it can be rebooted successfully.
Actual results：
As described.
Expected results:
Step 3,guest can be rebooted successfully.
Additional info:
Tried xm to install rhel7 guest,the above issue can not be reproduced.
There is no related log file from libvirt or virt-manager.
(In reply to Harald Hoyer from comment #3)
> (In reply to tingting zheng from comment #1)
> > Created attachment 884817[details]
> > screenshot of reboot
>
> why do you think this is a dracut bug?
As step 4 shows,I can reboot guest successfully through "reboot" button from virt-manager GUI,so I think it is not virt-manager's issue.
In additional,tried xm to install rhel7 guest,the above issue can not be reproduced,so I excluded for xen.
Actually I am not sure which component it belongs,pls feel free to move to the correct component.
Comment 5RHEL Program Management
2014-04-19 05:47:53 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
(In reply to tingting zheng from comment #6)
> When installing rhel6.5/rhel6.6 guest on rhel5 xen host can also hit this
> issue.
reassigning to kernel
Can reproduce with libvirt-0.8.2-29.el5_9.1, virt-manager-0.6.1-16.el5
Steps to reproduce:
1. Launch virt-manager.
2. Create a new rhel 7 guest,use iso to install a hvm guest.
3. After installation finished,click "Reboot" button of installation GUI, the guest will be shutdown instead of reboot.
I can not find any useful log file, in /var/log/xen/qemu-dm.31361.log i can see the following line when i reboot the guest:
reset requested in cpu_handle_ioreq.
Issued domain 37 reboot
Comment 12Vitaly Kuznetsov
2015-06-05 11:33:29 UTC
RHEL7 as a guest on RHEL5 Xen is unsupported and as far as I understand this issue doesn't reproduce on newer Xen deployments or AWS. Please reopen this bug if you think it needs fixing.