Bug 20910 - libvirtd verliert Verbindung zu Xen, keine Statusinformation für Domain-0 und VMs
libvirtd verliert Verbindung zu Xen, keine Statusinformation für Domain-0 und...
Status: CLOSED WONTFIX
Product: UCS
Classification: Unclassified
Component: Virtualization - Xen
UCS 2.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-12-08 09:52 CET by Arvid Requate
Modified: 2023-06-28 10:46 CEST (History)
4 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2010-12-08 09:52:27 CET
Der libvirtd verliert weiterhin relativ häufig die Verbindung zu Xen, sodass der Status der VMs nicht mehr abgefragt werden kann. Vielleicht wäre es sinnvoll die Ausgabe von "virsh -c xen+unix:/// list" regelmäßig auf "Domain-0" zu überprüfen:


root@xen1:~# virsh -c xen+unix:/// list 
 Id Name                 State
----------------------------------

root@xen1:~# virsh -c xen:/// list 
 Id Name                 State
----------------------------------
  0 Domain-0             running
  2 win-s5XbTOpWy1       no state
  3 win-DMWnNAWvMa       idle
Comment 1 Stefan Gohmann univentionstaff 2011-02-28 20:05:57 CET
Arvid, hattest du das für OpenDVDI implementiert?
Comment 2 Arvid Requate univentionstaff 2011-03-01 09:09:24 CET
Ja, in 
svn diff -r20638:21536 univention-dvs-node/univention-dvs-create-desktop
Comment 3 Stefan Gohmann univentionstaff 2013-02-21 12:30:03 CET
Ich glaube das ist in UCS 3 kein Problem mehr.
Comment 4 Philipp Hahn univentionstaff 2013-09-24 14:40:13 CEST
Vermutlich erneut mit UCS-3.2 aufgetreten:

# tail /var/log/univention/virtual-machine-manager-daemon-errors.log
=== 26685 === Tue, 24 Sep 2013 13:04:07 +0200 ===
uvmm-check.sh: uvmm does not response like expected. Restarting uvmmd now.
ERROR:
Error while waiting for answer: 104

# umc-command -U Administrator -P univention -r uvmm/domain/query -o nodePattern="$MASTER" -o domainPattern="*" | grep state
24.09.13 14:23:48.964  DEBUG_INIT
    'state': 'NOSTATE',
    'state': 'NOSTATE',
    'state': 'NOSTATE',
    'state': 'NOSTATE',
    'state': 'NOSTATE',

# uvmm query xen://master.virt.test/ | grep state
              'state': 0,
              'state': 0,
              'state': 0,
              'state': 1,
              'state': 0,
              'state': 0,

# virsh -c xen://master.virt.test/ list
error: unable to connect to server at 'master.virt.test:16514': Verbindungsaufbau abgelehnt
error: failed to connect to the hypervisor

# kill -9 3125
# /etc/init.d/libvirt-bin restart
# virsh list
Comment 5 Tim Petersen univentionstaff 2014-02-24 14:32:55 CET
Heute erneut beim Kunden beobachtet
Comment 6 Tim Petersen univentionstaff 2014-02-24 14:37:21 CET
(In reply to Tim Petersen from comment #5)
> Heute erneut beim Kunden beobachtet

In zwei Virtualisierungsumgebungen beim Kunden je für einen Server
Comment 7 Stefan Gohmann univentionstaff 2016-04-25 07:52:55 CEST
This issue has been filed against UCS 2.4.

UCS 2.4 is out of maintenance and many UCS components have vastly changed in
later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug".
In this case please provide detailed information on how this issue is affecting
you.