Bug 702806 - Virtual Guests hang after restarting the libvirt daemon
Summary: Virtual Guests hang after restarting the libvirt daemon
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: libvirt
Version: 5.6
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: 5.8
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-07 10:34 UTC by Francisco Lopez
Modified: 2018-11-14 14:56 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-15 21:26:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
messages of the guests (6.08 KB, text/plain)
2011-05-07 10:54 UTC, Francisco Lopez
no flags Details

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?


Note You need to log in before you can comment on or make changes to this bug.