Xen 4.4.3 Packages Available In Virt6-xen-44-testing
So first of all, if you’ve used the CBS before, please note the name change — it’s no longer virt6-testing, but virt6-xen-44-testing.
Easiest way to install:
rpm -ivh http://cbs.CentOS.org/repos/virt6-xen-44-testing/x86_64/os/Packages/CentOS-release-xen-7-7.el6.x86_64.rpm
This will set up yum repositories for both the eventual release repositories (enabled by default), and the community build system repositories (disabled by default).
At the moment, all packages will be stored in the virt-xen-44-testing repository. You can either enable this by default by editing
/etc/yum.repos.d/VirtSIG-Xen.repo, or by adding
“–enablerepo=virt-xen-44-testing”.
If you want, you can edit defaults /etc/sysconfig/xen-kernel
Next, run ‘yum update’ to get the new kernel:
yum –enablerepo=virt-xen-44-testing update kernel
Now install xen:
yum –enablerepo=virt-xen-44-testing install xen
This should grab both xen and the updated kernel package. It should also automatically:
* Add default commandline parameters for Xen and Linux when booting under Xen
* Arrange for xen to come up first in the grub
* Set the default boot entry to Xen.
That’s it! Reboot and you should be good to go.
Libvirt packages haven’t been rebuilt — not sure if they work or not. If they don’t, let me know and I’ll re-submit them..
Please report any problems or feedback to this list.
-George
5 thoughts on - Xen 4.4.3 Packages Available In Virt6-xen-44-testing
George,
Just an FYI – I tried to run the rpm command and none of the repos showed up enabled by default.
I tried enabling them manually, but I get this error:
Scot P. Floess RHCT (Certificate Number 605010084735240)
Chief Architect FlossWare http://sourceforge.net/projects/flossware
http://flossware.sourceforge.net
https://github.com/organizations/FlossWare
George,
Never mind – I had an old Xen repo I was trying to use some time ago… This was me.
Sorry!
Flossy
Scot P. Floess RHCT (Certificate Number 605010084735240)
Chief Architect FlossWare http://sourceforge.net/projects/flossware
http://flossware.sourceforge.net
https://github.com/organizations/FlossWare
Yes, that’s because the CBS is is not meant to be for production use, but only for building and testing. This is for two reasons:
1. The CBS itself is not mirrored, nor provisioned for massive use
2. The binaries in the CBS are not signed, and thus are risky to use in a production environment due to the ease with which one could perform a man-in-the-middle attack
After they’ve been in -testing for a week, they’ll be signed and pushed to the main c6 xen4CentOS repos (which are enabled by default).
-George
George,
Ack and understood. Makes perfect sense…
Thanks!
Scot P. Floess RHCT (Certificate Number 605010084735240)
Chief Architect FlossWare http://sourceforge.net/projects/flossware
http://flossware.sourceforge.net
https://github.com/organizations/FlossWare
Yep — forgot to say, thanks for the feedback!
-George