CentOS virt - Sep 2015 - CentOS 7 Xen 4.4.3 packages available for in virt7-xen-44-testing

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 at 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 at 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:
> 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.
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