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

[Xen-users] Fedora Core 4 Questions and Building a 2.4 domU kernel


  • To: <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Brian Kosick" <Bkosick@xxxxxxxxxxx>
  • Date: Thu, 18 Aug 2005 11:30:38 -0600
  • Date: Thu, 18 Aug 2005 11:30:38 -0600
  • Delivery-date: Thu, 18 Aug 2005 17:31:48 +0000
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcWkGvQLCzBO2UibQomhb4rMiBVe3g==
  • Thread-topic: Fedora Core 4 Questions and Building a 2.4 domU kernel

Hi Everyone,

I've been using and testing Xen for use in the QA Lab that I manage.   I
have FC4 setup and a few FC4 domU's running without a hitch using the
xen rpm's that come with FC4.  This morning, after a few days of banging
my head on a very hard object, I finally got a RHEL3 (Update 4) domU
working, but using the 2.6 domU kernel that FC4 provides.  (I can post
instructions if anyone would like them).  I would like to compile a 2.4
domU for my RHEL3 domU, but have been unable to do so.   My questions
are as follows.

1)  Does FC4 provide tools to build new dom0/U kernels using the
20050522 snapshot?  I have been unable to find any.

2)  I have downloaded the lasted Xen-unstable snapshot using the
mercurial tools, and have been attempting to compile a 2.4 domU, but I
keep getting mkbuildtree errors.  (hg pull/hg update)

make[2]: Entering directory `/root/xen-unstable.hg'
rm -rf linux-2.4.30-xenU
cp -al ref-linux-2.4.30 linux-2.4.30-xenU
# Apply arch-xen patches
( cd linux-2.4-xen-sparse ; \
          ./mkbuildtree ../linux-2.4.30-xenU )
no Linux 2.6 sparse tree
at ../linux-2.4-xen-sparse/../linux-2.6-xen-sparse
make[2]: *** [linux-2.4.30-xenU/include/linux/autoconf.h] Error 1
make[2]: Leaving directory `/root/xen-unstable.hg'
make[1]: *** [linux-2.4-xenU-build] Error 2
make[1]: Leaving directory `/root/xen-unstable.hg'
make: *** [kernels] Error 1

After browsing this mailing list, there appear to be a few people that
have been trying to update the 2.4 patch tree, but have not actually
tested it to see if it builds, I have been following Shahzad Chohan's
posts/requests for help with interest as it seems that we are in a
similar situation.

I built a 2.4 domU kernel using Xen 2.07, but it fails to boot giving a
Xen version mismatch error:

ERROR: Error constructing guest OS
op_create> Exception creating domain:
Traceback (most recent call last):
  File
"/usr/lib/python2.4/site-packages/xen/xend/server/SrvDomainDir.py", line
65, in op_create
    deferred = self.xd.domain_create(config)
  File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line
354, in domain_create
    deferred = XendDomainInfo.vm_create(config)
  File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 193,
in vm_create
    return vm.construct(config)
  File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 463,
in construct
    self.construct_image()
  File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 497,
in construct_image
    self.image_handler(self, image)
  File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 1166, in vm_image_linux
    vm.create_domain("linux", kernel, ramdisk, cmdline)
  File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 825,
in create_domain
    self.build_domain(ostype, kernel, ramdisk, cmdline, memmap)
  File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py",
line 805,
in build_domain
    vcpus          = self.vcpus)
error: (0, 'Error')
ERROR: Will only load images built for Xen v3.0
ERROR: Actually saw:
'GUEST_OS=linux,GUEST_VER=2.4,XEN_VER=2.0,VIRT_BASE=0xC0000000'

Thanks in advance,
Brian Kosick

Attachment: signature.asc
Description: This is a digitally signed message part

Attachment: smime.p7s
Description: S/MIME cryptographic signature

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