Updated Xen 4.4.3 packages have passed my local smoke tests, and are now available.
Full C7 release is still waiting on suitable testing for the libvirt packages.
If someone wants to step up to give the libvirt packages a decent smoke test, that will speed the C7 release process significantly. Otherwise it will have to wait until I get a chance to write some automated smoke tests.
In the mean time, here's how to install the core Xen packages:
rpm -ivh http://cbs.centos.org/repos/virt7-xen-44-testing/x86_64/os/Packages/centos-r...
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.
Please report any problems or feedback to this list.
-George
Hi,
On Wed, Sep 09, 2015 at 02:24:15PM +0100, George Dunlap wrote:
Updated Xen 4.4.3 packages have passed my local smoke tests, and are now available.
Full C7 release is still waiting on suitable testing for the libvirt packages.
If someone wants to step up to give the libvirt packages a decent smoke test, that will speed the C7 release process significantly. Otherwise it will have to wait until I get a chance to write some automated smoke tests.
I'm currently in the process of testing these latest Xen 4.4.3 rpms on centos7.
In the mean time, here's how to install the core Xen packages:
rpm -ivh http://cbs.centos.org/repos/virt7-xen-44-testing/x86_64/os/Packages/centos-r...
That link seems broken.. this one works: http://cbs.centos.org/repos/virt7-xen-44-testing/x86_64/os/Packages/centos-r...
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.
Please report any problems or feedback to this list.
-George
Thanks,
-- Pasi
On Mon, Sep 21, 2015 at 11:10:06AM +0300, Pasi Kärkkäinen wrote:
Hi,
On Wed, Sep 09, 2015 at 02:24:15PM +0100, George Dunlap wrote:
Updated Xen 4.4.3 packages have passed my local smoke tests, and are now available.
Full C7 release is still waiting on suitable testing for the libvirt packages.
If someone wants to step up to give the libvirt packages a decent smoke test, that will speed the C7 release process significantly. Otherwise it will have to wait until I get a chance to write some automated smoke tests.
I'm currently in the process of testing these latest Xen 4.4.3 rpms on centos7.
Actually I don't see libvirt rpms in the virt7-xen-44-testing repo. Which libvirt rpms should I be testing?
Currently I have these installed:
virt-viewer-0.6.0-12.el7.x86_64 libvirt-daemon-1.2.8-16.el7_1.4.x86_64 virt-manager-common-1.1.0-12.el7.noarch libvirt-client-1.2.8-16.el7_1.4.x86_64 libvirt-python-1.2.8-7.el7_1.1.x86_64 virt-manager-1.1.0-12.el7.noarch libvirt-daemon-driver-network-1.2.8-16.el7_1.4.x86_64 libvirt-daemon-config-network-1.2.8-16.el7_1.4.x86_64 libvirt-glib-0.1.7-3.el7.x86_64
In the mean time, here's how to install the core Xen packages:
rpm -ivh http://cbs.centos.org/repos/virt7-xen-44-testing/x86_64/os/Packages/centos-r...
That link seems broken.. this one works: http://cbs.centos.org/repos/virt7-xen-44-testing/x86_64/os/Packages/centos-r...
Thanks,
-- Pasi
On Mon, Sep 21, 2015 at 9:18 AM, Pasi Kärkkäinen pasik@iki.fi wrote:
On Mon, Sep 21, 2015 at 11:10:06AM +0300, Pasi Kärkkäinen wrote:
Hi,
On Wed, Sep 09, 2015 at 02:24:15PM +0100, George Dunlap wrote:
Updated Xen 4.4.3 packages have passed my local smoke tests, and are now available.
Full C7 release is still waiting on suitable testing for the libvirt packages.
If someone wants to step up to give the libvirt packages a decent smoke test, that will speed the C7 release process significantly. Otherwise it will have to wait until I get a chance to write some automated smoke tests.
I'm currently in the process of testing these latest Xen 4.4.3 rpms on centos7.
Actually I don't see libvirt rpms in the virt7-xen-44-testing repo. Which libvirt rpms should I be testing?
Oh, weird -- well I had it tagged for -candidate, but not for -testing. Probably because I hadn't even done a smoke test on it. :-)
Anyway, I've tagged it now.
That link seems broken.. this one works: http://cbs.centos.org/repos/virt7-xen-44-testing/x86_64/os/Packages/centos-r...
Yes, I've been doing work on the centos-release-xen package, and the release number at the end has to change with every update. Once we get centos-release-xen in mirrors, the "bootstrapping" problem should basically go away.
The latest version is actually -9 -- let me give that a quick smoke-test and push it to -testing.
-George
On Mon, Sep 21, 2015 at 11:24:23AM +0100, George Dunlap wrote:
On Mon, Sep 21, 2015 at 9:18 AM, Pasi Kärkkäinen pasik@iki.fi wrote:
On Mon, Sep 21, 2015 at 11:10:06AM +0300, Pasi Kärkkäinen wrote:
Hi,
On Wed, Sep 09, 2015 at 02:24:15PM +0100, George Dunlap wrote:
Updated Xen 4.4.3 packages have passed my local smoke tests, and are now available.
Full C7 release is still waiting on suitable testing for the libvirt packages.
If someone wants to step up to give the libvirt packages a decent smoke test, that will speed the C7 release process significantly. Otherwise it will have to wait until I get a chance to write some automated smoke tests.
I'm currently in the process of testing these latest Xen 4.4.3 rpms on centos7.
Actually I don't see libvirt rpms in the virt7-xen-44-testing repo. Which libvirt rpms should I be testing?
Oh, weird -- well I had it tagged for -candidate, but not for -testing. Probably because I hadn't even done a smoke test on it. :-)
Anyway, I've tagged it now.
OK. I can now see the libvirt 1.2.15-3.el7 rpms in the virt7-xen-44-testing repo, but it seems yum still doesn't pick them up:
# yum clean all # yum --enablerepo=virt-xen-44-testing update .. No packages marked for update
# rpm -qa | grep -i libvirt-daemon-1 libvirt-daemon-1.2.8-16.el7_1.4.x86_64
I guess I'll install those 1.2.15-3.el7 rpms manually.
Thanks,
-- Pasi
On Mon, Sep 21, 2015 at 01:46:36PM +0300, Pasi Kärkkäinen wrote:
OK. I can now see the libvirt 1.2.15-3.el7 rpms in the virt7-xen-44-testing repo, but it seems yum still doesn't pick them up:
# yum clean all # yum --enablerepo=virt-xen-44-testing update .. No packages marked for update
# rpm -qa | grep -i libvirt-daemon-1 libvirt-daemon-1.2.8-16.el7_1.4.x86_64
I guess I'll install those 1.2.15-3.el7 rpms manually.
It seems now the packages installed OK using yum aswell. I guess you or someone refreshed the repo :)
Anyway, here's something I noticed while testing xend bits:
# systemctl enable xend.service xend.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig xend on The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...).
"systemctl start xend.service" works OK though.. and after that xm works too.
Thanks,
-- Pasi
On Mon, Sep 21, 2015 at 4:18 PM, Pasi Kärkkäinen pasik@iki.fi wrote:
On Mon, Sep 21, 2015 at 01:46:36PM +0300, Pasi Kärkkäinen wrote:
OK. I can now see the libvirt 1.2.15-3.el7 rpms in the virt7-xen-44-testing repo, but it seems yum still doesn't pick them up:
# yum clean all # yum --enablerepo=virt-xen-44-testing update .. No packages marked for update
# rpm -qa | grep -i libvirt-daemon-1 libvirt-daemon-1.2.8-16.el7_1.4.x86_64
I guess I'll install those 1.2.15-3.el7 rpms manually.
It seems now the packages installed OK using yum aswell. I guess you or someone refreshed the repo :)
Updating the repos isn't actually triggered -- there's a script that runs every 10 minutes. So if you get old data, try again in 10 minutes or so. :-)
Anyway, here's something I noticed while testing xend bits:
# systemctl enable xend.service xend.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig xend on The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are:
- A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory.
- A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it.
- A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...).
"systemctl start xend.service" works OK though.. and after that xm works too.
Right -- I haven't tried xend under systemd. Given that xend is gone in 4.6, I'm considering whether to say "patches welcome" re fixing xend in 4.4 for C7...
-George
On Tue, Sep 22, 2015 at 12:08:12PM +0100, George Dunlap wrote:
Anyway, here's something I noticed while testing xend bits:
# systemctl enable xend.service xend.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig xend on The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are:
- A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory.
- A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it.
- A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...).
"systemctl start xend.service" works OK though.. and after that xm works too.
Right -- I haven't tried xend under systemd. Given that xend is gone in 4.6, I'm considering whether to say "patches welcome" re fixing xend in 4.4 for C7...
I'll try to investigate..
Thanks,
-- Pasi
-George
On Sat, Sep 26, 2015 at 08:51:37PM +0300, Pasi Kärkkäinen wrote:
On Tue, Sep 22, 2015 at 12:08:12PM +0100, George Dunlap wrote:
Anyway, here's something I noticed while testing xend bits:
# systemctl enable xend.service xend.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig xend on The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are:
- A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory.
- A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it.
- A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...).
"systemctl start xend.service" works OK though.. and after that xm works too.
Right -- I haven't tried xend under systemd. Given that xend is gone in 4.6, I'm considering whether to say "patches welcome" re fixing xend in 4.4 for C7...
I'll try to investigate..
Actually it seems those were "warnings" only.. xend does start automatically now on centos7. So it's not a problem really.
Thanks,
-- Pasi
-
George Dunlap -
Pasi Kärkkäinen