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

Re: [Xen-devel] Re: [Xen-users] [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6)


  • To: Digimer <linux@xxxxxxxxxxx>, Pasi Kärkkäinen <pasik@xxxxxx>
  • From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
  • Date: Mon, 29 Nov 2010 10:40:48 -0800 (PST)
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 29 Nov 2010 10:42:36 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=qT4Xy+XBs+dzB+QU40mJJddt8Aah7v+R0J2yppitpz7/QiKm6B6/sp4R9ewfmxCHUj72Fby8qs8kpGC7tFF0o7iAXrD8L/l5aPtGchdGCCz+QVQboVOz5Fm/ozQBqCQz0aJIou12HGAqNqscz9o7khcEdwvkPaMfh9mWywRw5sc=;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

----------------------------------------------------------------------------
Just one line has to be edited in MY's kernel.spec for F12
----------------------------------------------------------------------------
[root@ServerTest x86_64]# ./inst.sh
Loaded plugins: refresh-packagekit, rhnplugin
Setting up Install Process
Examining kernel-2.6.32.26-174.xendom0.el6.x86_64.rpm: kernel-2.6.32.26-174.xendom0.el6.x86_64
Marking kernel-2.6.32.26-174.xendom0.el6.x86_64.rpm as an update to kernel-2.6.32-71.el6.x86_64
Examining kernel-debuginfo-2.6.32.26-174.xendom0.el6.x86_64.rpm: kernel-debuginfo-2.6.32.26-174.xendom0.el6.x86_64
Marking kernel-debuginfo-2.6.32.26-174.xendom0.el6.x86_64.rpm to be installed
Examining kernel-debuginfo-common-x86_64-2.6.32.26-174.xendom0.el6.x86_64.rpm: kernel-debuginfo-common-x86_64-2.6.32.26-174.xendom0.el6.x86_64
Marking kernel-debuginfo-common-x86_64-2.6.32.26-174.xendom0.el6.x86_64.rpm to be installed
Examining kernel-devel-2.6.32.26-174.xendom0.el6.x86_64.rpm: kernel-devel-2.6.32.26-174.xendom0.el6.x86_64
Marking kernel-devel-2.6.32.26-174.xendom0.el6.x86_64.rpm as an update to kernel-devel-2.6.32-71.el6.x86_64
Examining kernel-headers-2.6.32.26-174.xendom0.el6.x86_64.rpm: kernel-headers-2.6.32.26-174.xendom0.el6.x86_64
Marking kernel-headers-2.6.32.26-174.xendom0.el6.x86_64.rpm as an update to kernel-headers-2.6.32-71.el6.x86_64
Resolving Dependencies
--> Running transaction check
---> Package kernel.x86_64 0:2.6.32.26-174.xendom0.el6 set to be installed
---> Package kernel-debuginfo.x86_64 0:2.6.32.26-174.xendom0.el6 set to be updated
---> Package kernel-debuginfo-common-x86_64.x86_64 0:2.6.32.26-174.xendom0.el6 set to be updated
---> Package kernel-devel.x86_64 0:2.6.32.26-174.xendom0.el6 set to be installed
---> Package kernel-headers.x86_64 0:2.6.32.26-174.xendom0.el6 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

===================================================================================================================
 Package             Arch   Version                    Repository                                             Size
===================================================================================================================
Installing:
 kernel           x86_64 2.6.32.26-174.xendom0.el6  /kernel-2.6.32.26-174.xendom0.el6.x86_64               91 M
 kernel-debuginfo  x86_64 2.6.32.26-174.xendom0.el6  /kernel-debuginfo-2.6.32.26-174.xendom0.el6.x86_64    1.1 G
 kernel-debuginfo-common-x86_64          x86_64 2.6.32.26-174.xendom0.el6  /kernel-debuginfo-common-x86_64-2.6.32.26-174.xendom0.el6.x86_64  151 M
 kernel-devel    x86_64 2.6.32.26-174.xendom0.el6  /kernel-devel-2.6.32.26-174.xendom0.el6.x86_64        22 M
Updating:
 kernel-headers  x86_64 2.6.32.26-174.xendom0.el6  /kernel-headers-2.6.32.26-174.xendom0.el6.x86_64      2.3 M

Transaction Summary
===================================================================================================================
Install       4 Package(s)
Upgrade       1 Package(s)

Total size: 1.4 G
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Installing     : kernel-2.6.32.26-174.xendom0.el6.x86_64                           1/6

grubby fatal error: unable to find a suitable template => May be ignored

Installing     : kernel-debuginfo-common-x86_64-2.6.32.26-174.xendom0.el6.x86_64   2/6
Installing     : kernel-debuginfo-2.6.32.26-174.xendom0.el6.x86_64                 3/6
Updating       : kernel-headers-2.6.32.26-174.xendom0.el6.x86_64                   4/6
Installing     : kernel-devel-2.6.32.26-174.xendom0.el6.x86_64                     5/6
Cleanup        : kernel-headers-2.6.32-71.el6.x86_64                               6/6

Installed:  kernel.x86_64
0:2.6.32.26-174.xendom0.el6                                                                       
  kernel-debuginfo.x86_64 0:2.6.32.26-174.xendom0.el6                                                             
  kernel-debuginfo-common-x86_64.x86_64 0:2.6.32.26-174.xendom0.el6                                               
  kernel-devel.x86_64 0:2.6.32.26-174.xendom0.el6                                                                 

Updated:
  kernel-headers.x86_64 0:2.6.32.26-174.xendom0.el6                                                               

Complete!

Reboot with new kernel

[root@ServerTest ~]# xm info
host                   : ServerTest
release                : 2.6.32.26-174.xendom0.el6.x86_64
version                : #1 SMP Mon Nov 29 20:12:24 MSK 2010
machine                : x86_64
nr_cpus                : 4
nr_nodes               : 1
cores_per_socket       : 4
threads_per_core       : 1
cpu_mhz                : 2833
hw_caps                : bfebfbff:20100800:00000000:00000940:0008e3fd:00000000:00000001:00000000
virt_caps              : hvm
total_memory           : 8190
free_memory            : 7070
node_to_cpu            : node0:0-3
node_to_memory         : node0:7070
node_to_dma32_mem      : node0:3259
max_node_id            : 0
xen_major              : 4
xen_minor              : 0
xen_extra              : .1
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          : unavailable
xen_commandline        : dom0_mem=1024M loglvl=all guest_loglvl=all
cc_compiler            : gcc version 4.4.4 20100726 (Red Hat 4.4.4-13) (GCC)
cc_compile_by          : root
cc_compile_domain      : (none)
cc_compile_date        : Mon Nov 29 10:24:07 MSK 2010
xend_config_format     : 4

Boris.

--- On Thu, 11/18/10, Pasi Kärkkäinen <pasik@xxxxxx> wrote:

From: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: [Xen-devel] Re: [Xen-users] [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6)
To: "Digimer" <linux@xxxxxxxxxxx>
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Date: Thursday, November 18, 2010, 3:37 PM

On Thu, Nov 18, 2010 at 03:14:32PM -0500, Digimer wrote:
> On 11/18/2010 03:00 PM, Pasi Kärkkäinen wrote:
>> Hello,
>>
>> If you're interested in running Xen 4.0 hypervisor/dom0 on RHEL6,
>> take a look at here: http://wiki.xen.org/xenwiki/RHEL6Xen4Tutorial
>>
>> It explains steps needed to rebuild Xen 4.0.1 src.rpm from Fedora on RHEL6,
>> and how to fetch dom0 capable 2.6.32.x kernel from upstream git repository.
>>
>> It also shows how to get libvirt/virt-manager working with Xen on RHEL6.
>>
>> Hopefully it helps :)
>>
>> -- Pasi
>
> I was in the middle of trying to resolve the dependencies yesterday and 
> today. I'll give this a run through and provide feedback when done. 
> Thanks kindly!
>

All that should be fine.. if not, let me know, and I'll fix it!

-- Pasi


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

_______________________________________________
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®.