One more: Something, it happens, that a virsh -command on the
commandline
prints out an error message similar to "Can't connect to
hypervisor"
(I can't
reproduce it at the moment). Multiple repeating the command works
well.
This happens not often - but sometimes..
I got the error again:
** Error1
libvir: Remote Fehler : connection already open
Fehler: Verbindung zum Hypervisor scheiterte
** Error2
libvir: Remote Fehler : no call waiting for reply with serial 0
Fehler: Verbindung zum Hypervisor scheiterte
regards
Danny
[root@xen03 xx]# virsh list
libvir: Remote Fehler : connection already open
Fehler: Verbindung zum Hypervisor scheiterte
[root@xen03 xx]# virsh list
Id Name Status
----------------------------------
11 POOL1-Pool-WinXP5-1234902964697-VM122 laufend
13 POOL1-Pool-WinXP5-1234902964697-VM127 laufend
14 POOL1-Pool-WinXP5-1234902964697-VM129 laufend
[root@xen03 xx]# virsh list
Id Name Status
----------------------------------
11 POOL1-Pool-WinXP5-1234902964697-VM122 laufend
13 POOL1-Pool-WinXP5-1234902964697-VM127 laufend
14 POOL1-Pool-WinXP5-1234902964697-VM129 laufend
[root@xen03 xx]# virsh list
libvir: Remote Fehler : no call waiting for reply with serial 0
Fehler: Verbindung zum Hypervisor scheiterte
[root@xen03 xx]# virsh list
Id Name Status
----------------------------------
11 POOL1-Pool-WinXP5-1234902964697-VM122 laufend
13 POOL1-Pool-WinXP5-1234902964697-VM127 laufend
14 POOL1-Pool-WinXP5-1234902964697-VM129 laufend
18 domain1234962052729 laufend
19 domain1234962449713 laufend