[Pacemaker] Problem : Sometimes failed in the start of the guest(on KVM).
renayama19661014 at ybb.ne.jp
renayama19661014 at ybb.ne.jp
Fri Mar 19 01:46:12 UTC 2010
Hi,
I use VirtualDomain-RA and, on KVM, constitute a cluster.
However, a guest sometimes fails in start.
Mar 16 15:16:52 x3650e lrmd: [13457]: info: RA output: (guest-kvm1:start:stderr) error: Failed to
start domain kvm1 error: internal error unable to start guest: inet_listen: bind(ipv4,127.0.0.1,5900):
Address already in use inet_listen: FAILED
Mar 16 15:16:52 x3650e lrmd: [13457]: info: RA output: (guest-kvm3:start:stdout) Domain kvm3 started
Mar 16 15:16:52 x3650e crmd: [13460]: info: abort_transition_graph: te_update_diff:146 - Triggered
transition abort (complete=0, tag=transient_attributes, id=x3650f, magic=NA, cib=0.102.76) : Transient
attribute: update
Mar 16 15:16:52 x3650e VirtualDomain[13781]: ERROR: Failed to start virtual domain kvm1.
Is this a problem related to libvirt?
We are the next environment.
* RHEL5.4-64(kvm)
* libvirt-0.6.3-20.el5
* libvirt-python-0.6.3-20.el5
* libvirt-0.6.3-20.el5
* corosync-1.2.0.zip
* Cluster-Resource-Agents-bb7dc7b7f6e4.tar.gz
* Pacemaker-1-0-efdc0d8143dd.tar.gz
* Pacemaker-Python-GUI-a05fd62b2e13.tar.gz
* Reusable-Cluster-Components-65900eaaf453.tar.gz
Do know the solution of the problem?
Best Regards,
Hideo Yamauchi.
More information about the Pacemaker
mailing list