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

Re: [Xen-users] xen Installation through YUM


  • To: Boris Derzhavets <bderzhavets@xxxxxxxxx>
  • From: kishore kumar <bodkekumar@xxxxxxxxx>
  • Date: Fri, 26 Feb 2010 14:23:37 -0800
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 26 Feb 2010 14:25:10 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=XFfJc31joTBCcYqfxUPtQjVzulZVUU5tDNj2qiBay9MmX6rpiqcn00CDiHQmzbXONS EBU5ejr0Rhfj25mqVlunTWXEpRyPo6h3hq8dlR+RawvVccLdgqTHLlYdLCVjUYnD2a7y x/g86uCia0TIvI3q4xpPF++Zyz4Zd4RNeLGKg=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>


I have already set gpgcheck=0 in /etc/yum.conf  file.
 
I did not clearly understood on what you said in the next line.........
 
to install unsigned rpms supposed to be built latter.
Activate rpmbuild on F12:-

# yum install transfig texi2html libaio-devel dev86 \
  glibc-devel.i686 e2fsprogs-devel gitk mkinitrd
what should I do can you please clarify me on the above statements you said???
 
I followed your next step and downloaded xen-3.4.2-2.fc13.src.rpm from internet and started doing the steps mentioned by you.  but at the very step I get the messages saying
 
After I ran the rpm -iv xen-3.4.2-2.fc13.src.rpm
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
warning: user mockbuild does not exist - using root
warning: group mockbuild does not exist - using root
 
Any idea what went wrong again??
 
THanks
bk

 
On Fri, Feb 26, 2010 at 5:39 AM, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
Set in /etc/yum.conf set gpgcheck=0 ( temporarily )
to install unsigned rpms supposed to be built latter.
Activate rpmbuild on F12:-

# yum install transfig texi2html libaio-devel dev86 \
  glibc-devel.i686 e2fsprogs-devel gitk mkinitrd

1. Install Xen 3.4.2 via xen-3.4.2-2.fc13.src.rpm. Download from Net xen-3.4.2-2.fc13.src.rpm. Now :-

# rpm -iv xen-3.4.2-2.fc13.src.rpm
# cd
# cd rpmbuild/SPEC
# rpmbuild -bb ./xen.spec
# cd ../RPMS/x86_64
yum install xen-3.4.2-2.fc12.x86_64.rpm \
xen-debuginfo-3.4.2-2.fc12.x86_64.rpm \
xen-devel-3.4.2-2.fc12.x86_64.rpm \
xen-doc-3.4.2-2.fc12.x86_64.rpm \
xen-hypervisor-3.4.2-2.fc12.x86_64.rpm \
xen-libs-3.4.-2.fc12.x86_64.rpm \
xen-runtime-3.4.2-2.fc12.x86_64.rpm

Xen Hypervisor 3.4.2 installed

2. Install Libvirt

# yum install libvirt libvirt-python python-virtinst \
virt-manager virt-viewer

PVOPS kernel 2.6.31.6 may be installed via Jeremy Fitzhardinge
Git Repository to support Xen 3.4.2 Dom0.

# git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git linux-2.6-xen
# cd linux-2.6-xen
# make menuconfig ( setup Xen Dom0 support)
# make -j(x)(number_of_kernels)
# make modules_install install

You may also want to build 2.6.32.9 pvops

# git checkout origin/xen/stable -b  xen/stable

I just switched from xen/master ( default 2.6.31.6 ) to xen/stable (the most recent supposed to become LTS - 2.6.32.9)

Boris.

--- On Fri, 2/26/10, Pasi Kärkkäinen <pasik@xxxxxx> wrote:

From: Pasi Kärkkäinen <pasik@xxxxxx>
Subject: Re: [Xen-users] xen Installation through YUM
To: "kishore kumar" <bodkekumar@xxxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Date: Friday, February 26, 2010, 4:50 AM

On Thu, Feb 25, 2010 at 06:04:26PM -0800, kishore kumar wrote:
>    HI,
>
>    I am trying to install xen through yum. Here is what I did.
>
>
>    [root@localhost Kishore]# yum install kernel-xen xen
>
>    Setting up Install Process
>
>    Resolving Dependencies
>
>    --> Running transaction check
>
>    ---> Package kernel.x86_64 0:2.6.31.9-174.fc12 set to be installed
>
>    --> Processing Dependency: kernel-firmware >= 2.6.31.9-174.fc12 for
>    package: kernel-2.6.31.9-174.fc12.x86_64
>
>    ---> Package xen.x86_64 0:3.4.2-1.fc12 set to be updated
>
>    --> Processing Dependency: xen-runtime = 3.4.2-1.fc12 for package:
>    xen-3.4.2-1.fc12.x86_64
>
>    --> Processing Dependency: PyXML for package: xen-3.4.2-1.fc12.x86_64
>
>    --> Running transaction check
>
>    ---> Package PyXML.x86_64 0:0.8.4-17.fc12 set to be updated
>
>    ---> Package kernel-firmware.noarch 0:2.6.31.9-174.fc12 set to be updated
>
>    ---> Package xen-runtime.x86_64 0:3.4.2-1.fc12 set to be updated
>
>    --> Processing Dependency: xen-libs = 3.4.2-1.fc12 for package:
>    xen-runtime-3.4.2-1.fc12.x86_64
>
>    --> Processing Dependency: xen-hypervisor-abi = 3.4 for package:
>    xen-runtime-3.4.2-1.fc12.x86_64
>
>    --> Running transaction check
>
>    ---> Package xen-hypervisor.x86_64 0:3.4.2-1.fc12 set to be updated
>
>    ---> Package xen-libs.x86_64 0:3.4.2-1.fc12 set to be updated
>
>    --> Finished Dependency Resolution
>
>    Dependencies Resolved
>
>    ================================================================================
>
>    Package Arch Version Repository Size
>
>    ================================================================================
>
>    Installing:
>
>    kernel x86_64 2.6.31.9-174.fc12 updates-released 20 M
>
>    xen x86_64 3.4.2-1.fc12 updates-released 898 k
>
>    Installing for dependencies:
>
>    PyXML x86_64 0.8.4-17.fc12 updates-released 906 k
>
>    xen-hypervisor x86_64 3.4.2-1.fc12 updates-released 2.9 M
>
>    xen-runtime x86_64 3.4.2-1.fc12 updates-released 4.0 M
>
>    Updating for dependencies:
>
>    kernel-firmware noarch 2.6.31.9-174.fc12 updates-released 906 k
>
>    xen-libs x86_64 3.4.2-1.fc12 updates-released 165 k
>
>    Transaction Summary
>
>    ================================================================================
>
>    Install 5 Package(s)
>
>    Upgrade 2 Package(s)
>
>    Total download size: 29 M
>
>    Is this ok [y/N]: y
>
>    Downloading Packages:
>
>    (1/7): PyXML-0.8.4-17.fc12.x86_64.rpm | 906 kB 00:00
>
>    (2/7): kernel-2.6.31.9-174.fc12.x86_64.rpm | 20 MB 00:02
>
>    (3/7): kernel-firmware-2.6.31.9-174.fc12.noarch.rpm | 906 kB 00:00
>
>    (4/7): xen-3.4.2-1.fc12.x86_64.rpm | 898 kB 00:00
>
>    (5/7): xen-hypervisor-3.4.2-1.fc12.x86_64.rpm | 2.9 MB 00:00
>
>    (6/7): xen-libs-3.4.2-1.fc12.x86_64.rpm | 165 kB 00:00
>
>    (7/7): xen-runtime-3.4.2-1.fc12.x86_64.rpm | 4.0 MB 00:00
>
>    --------------------------------------------------------------------------------
>
>    Total 6.7 MB/s | 29 MB 00:04
>
>    warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 signature: NOKEY, key ID
>    57bbccba
>
>     Public key for xen-libs-3.4.2-1.fc12.x86_64.rpm is not installed
>
>
>
>    Did Xen got installed with this?
>
>    Will the grub.conf be automatically updtaed after I run this command.
>    (But I dont see my grub.conf being updated)
>
>    Any Idea what went wrong here.
>

Fedora 12 doesn't include Xen dom0 capable kernel, see:
http://fedoraproject.org/wiki/Features/XenPvopsDom0

You need to get one of the 'testing' rpms, or compile it yourself.

-- Pasi


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