Hide Forgot
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
Dafna, please reproduce this again with newest libvirt - note that bug 624252 was fixed by libvirt-0.8.7-14.
yes - must have been libvirt. cannot reproduce - closing bug