On 28 februarie 2016 12:45:05 EET, Karanbir Singh <mail-lists@xxxxxxxxx> wrote: >On 27/02/16 12:52, Yamaban wrote: >> On Sat, 27 Feb 2016 13:20, Scot P. Floess wrote: >>> >>> Hit the send key before actually typing anything :( >>> >>> Was going to say - ah OK didn't understand your original question. >>> I'm not entirely sure - I just followed directions :) However, you >>> ask a reasonable question. >>> >>> On Sat, 27 Feb 2016, Karanbir Singh wrote: >>> >>>> On 27/02/16 01:41, Scot P. Floess wrote: >>>> > > From George's original email, I had to: >>>> > > * Install centos-release-xen from centos-extras >>>> > > Then a yum update followed by a yum install xen. >>>> > > That worked for me... >>>> > >>>> i had to do something similar, but my question is - one cant run >xen >>>> without the kernel, so why not have the xen package require the >xen >>>> kernel as a prereq ? >> >> IMHO, the best way to solve this would a additional line in the >spec-file: >> "Provide: kernel-dom0" for those kernel that are provide this >> functionality. >> >> Then the xen-packages could "Require: kernel-dom0" >> no matter which way the kernel functionality came to be. >> >> Maybe ask even across distros for such a implemention, >> to get a more coherent experience for xen. > >yeah, the CentOS-5 and 6 Xen stacks already do something similar - >which >is why I was expecting the CentOS 7 one to do that as well. Let me work >this with George and see where he thinks. > >Regards AFAICS, a simple "Requires: kernel >= 3.18" in the xen package should be enough, at least for the CentOS ecosystem... although I think that elrepo's kernels, on purpose, do not provide "kernel" but "'kernel-ml". _______________________________________________ CentOS-virt mailing list CentOS-virt@xxxxxxxxxx https://lists.centos.org/mailman/listinfo/centos-virt
