Bug 702806

Summary: Virtual Guests hang after restarting the libvirt daemon
Product: Red Hat Enterprise Linux 5 Reporter: Francisco Lopez <flopezyg>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 5.6CC: cww, dallan, jdenemar, jwest, ubeck
Target Milestone: ---   
Target Release: 5.8   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-15 21:26:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
messages of the guests none

Description Francisco Lopez 2011-05-07 10:34:36 UTC 
Description of problem:

Guests in a clustered environment have to be killed to reinitiate them. 
The normal shutdown process hangs forever

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

RHEL 6.0

How reproducible:

Always

Steps to Reproduce:
[root@rhel50-64 ~]# service libvirt-guests restart
Running guests on default URI: virt05, virt06, virt07, virt08
Shutting down guests on default URI...
Shutting down virt05: 64           error: operation failed: could not query memo
ry balloon allocation
Shutting down virt06: 63           error: operation failed: could not query memo
ry balloon allocation
Shutting down virt07: 63

Hier steht es mehrere Minuten obwohl ich SHUTDOWN_TIMEOUT=90
in /etc/sysconfig/libvirt-guests gesetzt habe.

does not continue without a kill of the process.

root@rhel50-64 ~]# kill -9 15909

/etc/init.d/libvirt-guests: line 55: 15909 Killed                  virsh $conn "$@" < /dev/null
Shutting down virt08: done
Resuming guests on default URI...
Resuming guest virt05: done
Resuming guest virt06: done
Resuming guest virt07: Fehler: Domain virt07 konnte nicht gestartet werden
Fehler: Timed out during operation: cannot acquire state change lock
Resuming guest virt08: done
[root@rhel50-64 ~]#

[root@rhel50-64 ~]# virsh destroy virt07
Fehler: Löschen der Domain virt07 gescheitert
Fehler: Timed out during operation: cannot acquire state change lock

[root@rhel50-64 ~]# service libvirtd restart
Stopping libvirtd daemon:                             [  OK  ]
Starting libvirtd daemon:                             [  OK  ]
[root@rhel50-64 ~]# virsh start virt07
Domain virt07 gestartet

[root@rhel50-64 ~]#
  
Actual results:

see above

Expected results:

Guests should restart without having them killed.  

Additional info:
Comment 2 Francisco Lopez 2011-05-07 10:54:51 UTC 
Created attachment 497503 [details]
messages of the guests

documents the hanging process
Comment 3 RHEL Program Management 2011-05-08 06:00:25 UTC 
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 4 Jiri Denemark 2011-05-09 07:57:54 UTC 
(In reply to comment #0)
> Hier steht es mehrere Minuten obwohl ich SHUTDOWN_TIMEOUT=90
> in /etc/sysconfig/libvirt-guests gesetzt habe.

Hmm, could you provide all messages in English?
Comment 5 Jiri Denemark 2011-05-12 08:51:56 UTC 
Why did you move this bug to RHEL-5? The bug report says it's RHEL 6.0 which is affected. Which one is correct? And could you please provide the whole description in English instead of a mixture of English and German?