On 02/02/2016 08:47 AM, Manuel Wolfshant wrote:
On 01/14/2016 06:57 PM, George Dunlap wrote:
As mentioned yesterday, Xen 4.6 packages are now available for testing. These also include an update to libvirt 1.3.0, in line with what's available for CentOS 7. Please test, particularly the upgrade if you can, and report any problems here.
To upgrade:
yum update --enablerepo=centos-virt-xen-testing
To install from scratch:
- Install centos-release-xen from centos-extras
yum install centos-release-xen
- Update to get the new kernel:
yum update
- Install the Xen packages from the centos-virt-xen-testing repo:
yum install --enablerepo=centos-virt-xen-testing xen
Keep in mind that there is still a bug in the upstream CentOS new-kernel script which for some people consistently fails to add an "initird" line to the Xen boot stanza. Check /boot/grub/grub.conf; the Xen stanza should look something like this:
title CentOS (3.18.21-17.el6.x86_64) root (hd0,0) kernel /xen.gz dom0_mem=1024M,max:1024M cpuinfo com1=115200,8n1 console=com1,tty loglvl=all guest_loglvl=all module /vmlinuz-3.18.21-17.el6.x86_64 ro root=/dev/mapper/VolGroup-lv_root rd_NO_LUKS LANG=en_US.UTF-8 rd_NO_MD rd_LVM_LV=VolGroup/lv_swap SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_LVM_LV=VolGroup/lv_root KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet module /initramfs-3.18.21-17.el6.x86_64.img
-George _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org https://lists.centos.org/mailman/listinfo/centos-virt
Hello
I've attempted to upgrade today to xen 4.6 ( because of somethingwhich seems to be a reincarnation of http://lists.xen.org/archives/html/xen-devel/2014-01/msg02259.html ) and I noticed that the new xen-runtime package tries to bring in a whole bunch of other packages:
Installing for dependencies: atk x86_64 1.30.0-1.el6 base 195 k avahi-libs x86_64 0.6.25-15.el6 base 55 k cairo x86_64 1.8.8-6.el6_6 base 309 k cups-libs x86_64 1:1.4.2-72.el6 base 321 k fontconfig x86_64 2.8.0-5.el6 base 186 k freetype x86_64 2.3.11-15.el6_6.1 base 361 k gdk-pixbuf2 x86_64 2.24.1-6.el6_7 updates 501 k gtk2 x86_64 2.24.23-6.el6 base 3.2 M hicolor-icon-theme noarch 0.11-1.1.el6 base 40 k jasper-libs x86_64 1.900.1-16.el6_6.3 base 137 k libXcomposite x86_64 0.4.3-4.el6 base 20 k libXcursor x86_64 1.1.14-2.1.el6 base 28 k libXft x86_64 2.3.1-2.el6 base 55 k libXi x86_64 1.7.2-2.2.el6 base 37 k libXinerama x86_64 1.1.3-2.1.el6 base 13 k libXrandr x86_64 1.4.1-2.1.el6 base 23 k libXrender x86_64 0.9.8-2.1.el6 base 24 k libthai x86_64 0.1.12-3.el6 base 183 k libtiff x86_64 3.9.4-10.el6_5 base 343 k pango x86_64 1.28.1-10.el6 base 351 k
Is this really needed ?
The packages are built in mock (a clean buildroot with only required packages) ... so only things called out as required by the spec file is in the build root.
We can look at the build root log here:
Searching for this line in the log:
Getting requirements for xen-4.6.0-9.el6.src
It seems that SDL-devel, ghostscript, libX11-devel and gtk2-devel are build requirements for xen-4.6 packages from that root.log .. so that adds in all the X and gtk devel packages for linking against.
Looking at the spec file:
In Lines 105 to 108, those requires are there, so they are going to pull in all the X and GNOME devel files that get linked against, so if those spec file dependencies are requires, the links will be produced.
I don't see any way to get rid of those requires unless one redesigns the packages.
Thanks, Johnny Hughes