[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] CentOS 5.x / 6.x Dom0



On Mon, Nov 21, 2011 at 7:48 PM, Randy Katz <rkatz@xxxxxxxxxxxxxxxxxxxxx> wrote:
> Hi,
>
> Excuse me for sounding ignorant, however, is there any reason why NOT to use
> Fedora 16 for this dom0?

If you want to use it for production then you need to know Fedora EOL
timeline for each release.  You are not going to upgrade Fedora so
often isn't it?

>
> Best regards,
> Randy Katz
>
> On 11/21/2011 2:01 AM, Alan Lam wrote:
>
> Hi Fajar,
>
>
>
> OK, brilliant! This should give me a decent path for CentOS 6.x then if I
> pursue that route.
>
>
>
> Thanks once again Fajar.
>
>
>
> Regards,
>
> Alan
>
>
>
> -----Original Message-----
> From: Fajar A. Nugraha [mailto:list@xxxxxxxxx]
> Sent: Monday, 21 November 2011 8:31 PM
> To: Alan Lam
> Cc: xen-users
> Subject: Re: [Xen-users] CentOS 5.x / 6.x Dom0
>
>
>
> On Mon, Nov 21, 2011 at 4:23 PM, Alan Lam <alan@xxxxxxxxxxxxxx> wrote:
>
>> I am using LV backed domUs in PV currently. I would like to maybe explore
>
>> HVM in future though so I'd like that option to remain open.
>
>
>
> only LV-vs-file matters. PV-vs-HVM shouldn't matter w.r.t. bkltap.
>
>
>
>> So if I grab the F16 kernel, recompile the RPM under CentOS 6.x, this
>> should
>
>> be OK for dom0 use?
>
>
>
> I needed to edit the SPEC a bit since some required packages is not
>
> available, or only older version is available, on RHEL6
>
>
>
> # diff -Naru kernel.fc16.spec kernel.spec
>
> --- kernel.fc16.spec    2011-10-26 23:27:50.000000000 -0400
>
> +++ kernel.spec   2011-11-02 04:57:48.279838912 -0400
>
> @@ -455,7 +455,8 @@
>
> # First the general kernel 2.6 required versions as per
>
> # Documentation/Changes
>
> #
>
> -%define kernel_dot_org_conflicts  ppp < 2.4.3-3, isdn4k-utils <
>
> 3.2-32, nfs-utils < 1.0.7-12, e2fsprogs < 1.37-4, util-linux < 2.12,
>
> jfsutils < 1.1.7-2, reiserfs-utils < 3.6.19-2, xfsprogs < 2.6.13-4,
>
> procps < 3.2.5-6.3, oprofile < 0.9.1-2, device-mapper-libs <
>
> 1.02.63-2, mdadm < 3.2.1-5
>
> +#%define kernel_dot_org_conflicts  ppp < 2.4.3-3, isdn4k-utils <
>
> 3.2-32, nfs-utils < 1.0.7-12, e2fsprogs < 1.37-4, util-linux < 2.12,
>
> jfsutils < 1.1.7-2, reiserfs-utils < 3.6.19-2, xfsprogs < 2.6.13-4,
>
> procps < 3.2.5-6.3, oprofile < 0.9.1-2, device-mapper-libs <
>
> 1.02.63-2, mdadm < 3.2.1-5
>
> +%define kernel_dot_org_conflicts  ppp < 2.4.3-3, isdn4k-utils <
>
> 3.2-32, nfs-utils < 1.0.7-12, e2fsprogs < 1.37-4, util-linux < 2.12,
>
> jfsutils < 1.1.7-2, reiserfs-utils < 3.6.19-2, xfsprogs < 2.6.13-4,
>
> procps < 3.2.5-6.3, oprofile < 0.9.1-2, mdadm < 3.2.1-5
>
>
>
> #
>
> # Then a series of requirements that are distribution specific, either
>
> @@ -473,7 +474,8 @@
>
> # Packages that need to be installed before the kernel is, because the
> %%post
>
> # scripts use them.
>
> #
>
> -%define kernel_prereq  fileutils, module-init-tools >= 3.16-2,
>
> initscripts >= 8.11.1-1, grubby >= 8.3-1
>
> +#%define kernel_prereq  fileutils, module-init-tools >= 3.16-2,
>
> initscripts >= 8.11.1-1, grubby >= 8.3-1
>
> +%define kernel_prereq  fileutils, module-init-tools, initscripts >=
>
> 8.11.1-1, grubby
>
> %define initrd_prereq  dracut >= 001-7
>
>
>
> ... and then build it with
>
>
>
> rpmbuild -ba --without tools kernel.spec
>
>
>
>>
>
>>
>
>>
>
>> Were there any catches, ie. other utils eg. udev and the likes that needed
>
>> to be updated before you could boot the F16 kernel?
>
>
>
> You need to edit grub.conf manually. Other than that, it should work.
>
>
>
> --
>
> Fajar
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.