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 490282[details]
logs
Description of problem:
After shutting down a guest from GUI (twice in stop button) and than trying to start it again, the guest will fail to run.
when doing grep on Dwon from vdsm.log I see that the fowllowing warning:
Thread-103018::WARNING::2011-04-06 09:30:02,908::vm::575::vm.Vm::(_set_lastStatus) vmId=`ab196f48-12e2-40be-a0a0-b4d775a4d2fd`::trying to set state to Up when already Down
Thread-103025::WARNING::2011-04-06 09:30:05,056::vm::575::vm.Vm::(_set_lastStatus) vmId=`ab196f48-12e2-40be-a0a0-b4d775a4d2fd`::trying to set state to Powering down when already Down
Version-Release number of selected component (if applicable):
ic108
[root@south-02 ~]# rpm -qa |grep vdsm
vdsm-4.9-57.el6.x86_64
vdsm-debug-plugin-4.9-57.el6.x86_64
vdsm-cli-4.9-57.el6.x86_64
vdsm-debuginfo-4.9-57.el6.x86_64
[root@south-02 ~]# rpm -qa |grep kvm
qemu-kvm-debuginfo-0.12.1.2-2.152.el6.x86_64
qemu-kvm-0.12.1.2-2.152.el6.x86_64
[root@south-02 ~]# rpm -qa |grep kernel
dracut-kernel-004-38.el6.noarch
kernel-firmware-2.6.32-128.el6.noarch
kernel-2.6.32-128.el6.x86_64
kernel-2.6.32-118.el6.x86_64
kernel-2.6.32-94.el6.x86_64
abrt-addon-kerneloops-1.1.16-1.el6.x86_64
How reproducible:
80%
Steps to Reproduce:
1. start a VM
2. when VM is powering up -> shut down VM using the stop button (pressing it twice)
3. after VM is down -> start it
Actual results:
VM will fail to run again
Expected results:
VM should run
Additional info: vdsm and backend logs
which libvirt version are you using? the logs looks too similar to bug 624252. Can you reproduce this after setting auth_unix_rw="none" in libvirtd.conf?
Created attachment 490523[details]
new log
libvirt:
libvirt-client-0.8.7-11.el6.x86_64
libvirt-debuginfo-0.8.7-11.el6.x86_64
libvirt-0.8.7-11.el6.x86_64
libvirt-python-0.8.7-11.el6.x86_64
libvirt-devel-0.8.7-11.el6.x86_64
libvorbis-1.2.3-4.el6.x86_64
libvisual-0.4.0-9.1.el6.x86_64
yes, I was able to recreate even after changing uth_unix_rw="none" in libvirtd.conf
new log attached
Created attachment 490282 [details] logs Description of problem: After shutting down a guest from GUI (twice in stop button) and than trying to start it again, the guest will fail to run. when doing grep on Dwon from vdsm.log I see that the fowllowing warning: Thread-103018::WARNING::2011-04-06 09:30:02,908::vm::575::vm.Vm::(_set_lastStatus) vmId=`ab196f48-12e2-40be-a0a0-b4d775a4d2fd`::trying to set state to Up when already Down Thread-103025::WARNING::2011-04-06 09:30:05,056::vm::575::vm.Vm::(_set_lastStatus) vmId=`ab196f48-12e2-40be-a0a0-b4d775a4d2fd`::trying to set state to Powering down when already Down Version-Release number of selected component (if applicable): ic108 [root@south-02 ~]# rpm -qa |grep vdsm vdsm-4.9-57.el6.x86_64 vdsm-debug-plugin-4.9-57.el6.x86_64 vdsm-cli-4.9-57.el6.x86_64 vdsm-debuginfo-4.9-57.el6.x86_64 [root@south-02 ~]# rpm -qa |grep kvm qemu-kvm-debuginfo-0.12.1.2-2.152.el6.x86_64 qemu-kvm-0.12.1.2-2.152.el6.x86_64 [root@south-02 ~]# rpm -qa |grep kernel dracut-kernel-004-38.el6.noarch kernel-firmware-2.6.32-128.el6.noarch kernel-2.6.32-128.el6.x86_64 kernel-2.6.32-118.el6.x86_64 kernel-2.6.32-94.el6.x86_64 abrt-addon-kerneloops-1.1.16-1.el6.x86_64 How reproducible: 80% Steps to Reproduce: 1. start a VM 2. when VM is powering up -> shut down VM using the stop button (pressing it twice) 3. after VM is down -> start it Actual results: VM will fail to run again Expected results: VM should run Additional info: vdsm and backend logs