Jump to content
Welcome to our new Citrix community!
  • 0

Updating Xen hosts - yum?


jon yeargers

Question

12 answers to this question

Recommended Posts

  • 0
1 hour ago, Alan Lantz said:

I would think something like OMSA technically breaks the official Citrix support as well. If it came down

to it with Dom0 issues they could make you uninstall it before troubleshooting. 

 

--Alan--

 

Yes, you really want to be careful about doing anything that might void your support contract (if you have one) or breaking something, regardless of whether you have support or not.

 

-=Tobias

Link to comment
  • 0

This is an interesting question, that we also encountered in XCP-ng, which doesn't use "packs" update but `yum` directly. For Citrix Hypervisor, you are using "Updates" which are basically ISO file, containing signed RPMs by Citrix. So you don't have a Yum repo like for CentOS or Red Hat distro.

 

Here is what we choose to tell for XCP-ng (which is NOT XenServer/CH but it's reasonable advice anyway)

* If your needed package is available on CentOS and doesn't have any dependency, and doesn't interfere with kernel it might work without any issue

* NEVER enable a whole repository because this will break your install

* if you are pretty sure the package is without any risk, you can enable the repo ONLY during the yum command, eg yum install packagename --enablerepo='epel'

 

Again, that's the advice we gave on XCP-ng, in the meantime we are working to embed/put a repo for very low risk packages, like htop and similar ones.

Link to comment
  • 0
9 hours ago, Olivier Lambert said:

This is an interesting question, that we also encountered in XCP-ng, which doesn't use "packs" update but `yum` directly. For Citrix Hypervisor, you are using "Updates" which are basically ISO file, containing signed RPMs by Citrix. So you don't have a Yum repo like for CentOS or Red Hat distro.

 

Here is what we choose to tell for XCP-ng (which is NOT XenServer/CH but it's reasonable advice anyway)

* If your needed package is available on CentOS and doesn't have any dependency, and doesn't interfere with kernel it might work without any issue

* NEVER enable a whole repository because this will break your install

* if you are pretty sure the package is without any risk, you can enable the repo ONLY during the yum command, eg yum install packagename --enablerepo='epel'

 

Again, that's the advice we gave on XCP-ng, in the meantime we are working to embed/put a repo for very low risk packages, like htop and similar ones.

 

If you're on a private net or behind various firewalls, it take a bit more to get around those hurdles. See for example: https://www.mycugc.org/blogs/cugc-blogs/2017/02/21/direct-updating-of-modern-dell-server-and-peripher

 

-=Tobias

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...