search

xcp-ng / xcp

Entry point for issues and wiki. Also contains some scripts and sources.
https://xcp-ng.org
1.3k stars 74 forks source link

Update candidate: xcp-ng-pv-tools with support for new distros #293

Closed stormi closed 4 years ago

stormi commented 5 years ago

For XCP-ng 8.0 for now.

Installation:

# first make sure to eject the tools ISO image from existing VMs

# then:
yum update xcp-ng-pv-tools --enablerepo=xcp-ng-testing

Then the install.sh script will be able to detect RHEL 8 and its derivatives.

stormi commented 5 years ago

Update: a new revision of the package now also adds tentative support for:

I didn't test those myself because I don't use them, so I'm counting on community feedback!

iServU commented 5 years ago

Updated hypervisor packages as referenced, uninstall xcp-ng tools from VM, rebooted.

This time after selecting the xcp-ng tools via xcp-ng center, mounting the cdrom drive and running the bash install command without the distro flags, it actually installed (which it refused to do before without the distro and version flags).

Another VM reboot and still, the memory usage doesn't show in xcp-ng center. Annotation 2019-10-18 193300

During xcp-ng tools install, I did notice the same version being installed as before the above update. Ran xe-toolstack-restart just to be sure but no go!

The following changes will be made to this Virtual Machine:

This issue caused me to rebuild a VM from scratch based on the CentOS7 template with a CloudLinux ISO. This worked perfectly after installing xcp-ng tools. I'm decommissioning the old VM soon so I'm happy to run tests.

However, please be mindful that this is a production hypervisor.

stormi commented 5 years ago

@iServU thanks for testing. If I understand correctly, your old CloudLinux VM does not report memory usage but the new one does? Apart from memory usage, are the tools detected? I don't know how to check that in XCP-ng Center. In Xen Orchestra you'd see Hardware virtualization with paravirtualization drivers enabled (PVHVM) if the tools are detected. On the old VM, is xe-daemon currently running. If not, what's the status of the xe-linux-distribution service?

maxcuttins commented 4 years ago

On 7.6, I got 2 warning. They seems to me a typo in the code

Running transaction
  Updating   : xen-hypervisor-4.7.6-6.6.xcpng.x86_64                       1/18 
  Updating   : xen-dom0-libs-4.7.6-6.6.xcpng.x86_64                        2/18 
  Updating   : xen-libs-4.7.6-6.6.xcpng.x86_64                             3/18 
  Updating   : xen-tools-4.7.6-6.6.xcpng.x86_64                            4/18 
  Updating   : xen-dom0-tools-4.7.6-6.6.xcpng.x86_64                       5/18 
  Updating   : 2:microcode_ctl-2.1-26.xs6.xcpng.x86_64                     6/18 
  Updating   : kernel-4.4.52-4.0.13.x86_64                                 7/18 
  Updating   : xcp-ng-xapi-plugins-1.5.0-1.xcpng.noarch                    8/18 
  Updating   : xcp-ng-pv-tools-7.41.0-6.el7.centos.noarch                  9/18 
/opt/xensource/libexec/unmount_halted_xstools.sh: line 10: [: ==: unary operator expected
/opt/xensource/libexec/unmount_halted_xstools.sh: line 10: [: ==: unary operator expected
No need to scan rhe tools SR since this is not the master
  Cleanup    : xen-dom0-tools-4.7.6-6.5.1.xcpng.x86_64                    10/18 
  Cleanup    : 2:microcode_ctl-2.1-26.xs5.1.xcpng.x86_64                  11/18 
  Cleanup    : kernel-4.4.52-4.0.12.x86_64                                12/18 
  Cleanup    : xcp-ng-xapi-plugins-1.4.0-1.xcpng.noarch                   13/18
stormi commented 4 years ago

@maxcuttins Thanks for the report. This is not really related to the update candidate this issue is about, so could you open a separate issue?

stormi commented 4 years ago

Update published, without alpine linux support because was I had done didn't work.