Opened 5 years ago

Closed 5 years ago

#1967 closed defect (fixed)

Recover XEN setup

Reported by: matze Assignee:
Priority: P3 Milestone:
Module: Office-IT Keywords:
Cc: fred Blocked By:
Blocking: Platform: Unknown
Ready: no Confidential: no
Tester: Verified working:
Review URL(s):

Description

The XEN server seems to be configured quite randomly, tools from different stacks (e.g. xs and libvirt) are mixed together, and without internal documentation it's impossible to tell which tool stack is to be actually used. This should become cleaned up, especially since some operations currently only work with specific tool stacks.

Change History (5)

comment:1 Changed 5 years ago by fred

The following tools / toolstacks seem to be functional on the XEN host at the moment:

CLI:
xl (based on xenlight library, default toolstack as of Xen Project 4.1)
virsh (based on libvirt library) (needs to be started with "virsh -c xen:///" to connect to local XEN hypervisor)

GUI:
virt-manager (based on libvirt library)

installed but NOT working tools:
xm (deprecated since Xen 4.1)

Good background info on XEN toolstacks:
http://wiki.xen.org/wiki/Choice_of_Toolstacks

comment:2 Changed 5 years ago by fred

I've just read that one shouldn't mix different xenlight/libxl clients.
Since our VM seems to have been created using virt-manager (libvirt) we should probably stick to libvirt, i.e. virsh and virt-manager for managing them.
(config is in /etc/libvirt/libxl/*.xml)

comment:3 Changed 5 years ago by matze

Agreed. Do you plan to remove the tools not in use?

comment:4 Changed 5 years ago by fred

"xm" and "xl" belong to the package "xen-utils-common", which includes a lot of other xen-related files and scripts like

xen-utils-common: /etc/default/xend
xen-utils-common: /etc/default/xendomains
xen-utils-common: /etc/init.d/xen
xen-utils-common: /etc/init.d/xendomains
...
xen-utils-common: /etc/xen/scripts/network-bridge
xen-utils-common: /etc/xen/scripts/network-nat
xen-utils-common: /etc/xen/scripts/network-route
xen-utils-common: /etc/xen/scripts/qemu-ifup
xen-utils-common: /etc/xen/scripts/vif-bridge
xen-utils-common: /etc/xen/scripts/vif-common.sh
xen-utils-common: /etc/xen/scripts/vif-nat
xen-utils-common: /etc/xen/scripts/vif-openvswitch
xen-utils-common: /etc/xen/scripts/vif-route
xen-utils-common: /etc/xen/scripts/vif-setup
xen-utils-common: /etc/xen/scripts/vif2
xen-utils-common: /etc/xen/scripts/vscsi
...

I'm not sure if these files can also be removed without breaking XEN completely.
So I would rather not remove that package.

comment:5 Changed 5 years ago by fred

  • Resolution set to fixed
  • Status changed from new to closed

Since it is not economic to spend more time on finding out if or how the un-used toolstacks could be removed, we will just leave them for now.

Note: See TracTickets for help on using tickets.