From: Digimer <linux@alteeve.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6)
Date: Thu, 18 Nov 2010 23:30:11 -0500 [thread overview]
Message-ID: <4CE5FD53.8060804@alteeve.com> (raw)
In-Reply-To: <20101118200025.GH2754@reaktio.net>
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
Hi Pasi,
I ran into a problem at the libvirt stage. After applying your patch
and while building the spec I got the error below. Might you have some
advice?
I did get Xen 4.0.1 installed and dom0 running, so I am already
further than I was before you released your tutorial. I had been stuck
on the qemu-nbd step. :)
Digimer
Making check in xencapsdata
make[1]: Entering directory
`/root/rpmbuild/BUILD/libvirt-0.8.1/tests/xencapsdata'
make[1]: Nothing to be done for `check'.
make[1]: Leaving directory
`/root/rpmbuild/BUILD/libvirt-0.8.1/tests/xencapsdata'
make[1]: Entering directory `/root/rpmbuild/BUILD/libvirt-0.8.1/tests'
make check-TESTS
make[2]: Entering directory `/root/rpmbuild/BUILD/libvirt-0.8.1/tests'
TEST: virshtest
................ 16 OK
PASS: virshtest
PASS: nodeinfotest
TEST: statstest
........................................ 40
................................... 75 OK
PASS: statstest
TEST: qparamtest
................................ 32 OK
PASS: qparamtest
TEST: capabilityschematest
............ 12 OK
PASS: capabilityschematest
TEST: interfaceschematest
.................. 18 OK
PASS: interfaceschematest
TEST: networkschematest
........... 11 OK
PASS: networkschematest
TEST: storagepoolschematest
...................... 22 OK
PASS: storagepoolschematest
TEST: storagevolschematest
............ 12 OK
PASS: storagevolschematest
TEST: domainschematest
........................................ 40
........................................ 80
........................................ 120
........................................ 160
........................................ 200
........ 208 OK
PASS: domainschematest
TEST: nodedevschematest
.............. 14 OK
PASS: nodedevschematest
TEST: nwfilterschematest
.............................. 30 OK
PASS: nwfilterschematest
TEST: test_conf.sh
.. 2 OK
PASS: test_conf.sh
PASS: cpuset
PASS: daemon-conf
PASS: define-dev-segfault
PASS: int-overflow
PASS: libvirtd-fail
PASS: libvirtd-pool
PASS: read-bufsiz
PASS: read-non-seekable
PASS: start
PASS: undefine
PASS: vcpupin
TEST: virsh-all
........................................ 40
........................................ 80
........................................ 120
.................. 138 OK
PASS: virsh-all
PASS: virsh-schedinfo
PASS: virsh-synopsis
TEST: xml2sexprtest
........................................ 40
... 43 OK
PASS: xml2sexprtest
TEST: sexpr2xmltest
........................................ 40
.. 42 OK
PASS: sexpr2xmltest
TEST: xmconfigtest
........................................ 40
................ 56 OK
PASS: xmconfigtest
TEST: xencapstest
!!!!!!!!!! 10 FAIL
FAIL: xencapstest
TEST: qemuxml2argvtest
........................................ 40
........................................ 80
............ 92 OK
PASS: qemuxml2argvtest
TEST: qemuxml2xmltest
........................................ 40
............ 52 OK
PASS: qemuxml2xmltest
TEST: qemuargv2xmltest
........................................ 40
................ 56 OK
PASS: qemuargv2xmltest
TEST: qemuhelptest
......... 9 OK
PASS: qemuhelptest
TEST: nwfilterxml2xmltest
.............................. 30 OK
PASS: nwfilterxml2xmltest
TEST: esxutilstest
.... 4 OK
PASS: esxutilstest
TEST: vmx2xmltest
....................................... 39 OK
PASS: vmx2xmltest
TEST: xml2vmxtest
.................................. 34 OK
PASS: xml2vmxtest
PASS: seclabeltest
TEST: eventtest
........... 11 OK
PASS: eventtest
TEST: networkxml2xmltest
..... 5 OK
PASS: networkxml2xmltest
TEST: storagevolxml2xmltest
...... 6 OK
PASS: storagevolxml2xmltest
TEST: storagepoolxml2xmltest
........... 11 OK
PASS: storagepoolxml2xmltest
TEST: nodedevxml2xmltest
............. 13 OK
PASS: nodedevxml2xmltest
TEST: interfacexml2xmltest
................... 19 OK
PASS: interfacexml2xmltest
====================
1 of 46 tests failed
====================
make[2]: *** [check-TESTS] Error 1
make[2]: Leaving directory `/root/rpmbuild/BUILD/libvirt-0.8.1/tests'
make[1]: *** [check-am] Error 2
make[1]: Leaving directory `/root/rpmbuild/BUILD/libvirt-0.8.1/tests'
make: *** [check-recursive] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.Tjv2Ff (%check)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.Tjv2Ff (%check)
--
Digimer
E-Mail: digimer@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin: http://nodeassassin.org
next prev parent reply other threads:[~2010-11-19 4:30 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 20:00 [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6) Pasi Kärkkäinen
2010-11-18 20:14 ` Digimer
2010-11-18 20:37 ` [Xen-users] " Pasi Kärkkäinen
2010-11-29 18:40 ` [Xen-devel] " Boris Derzhavets
2010-11-29 19:40 ` Boris Derzhavets
2010-11-30 3:50 ` Digimer
2010-11-30 6:04 ` Boris Derzhavets
2010-11-30 14:43 ` Digimer
2010-11-30 14:45 ` Re: [Xen-users] " Boris Derzhavets
2010-11-30 14:46 ` [Xen-devel] " Digimer
2010-12-01 9:11 ` Re: [Xen-users] " Boris Derzhavets
2010-11-30 18:29 ` Pasi Kärkkäinen
2010-11-23 11:55 ` [Xen-devel] " Boris Derzhavets
2010-11-23 12:23 ` Re: [Xen-users] " Pasi Kärkkäinen
2010-11-23 12:31 ` Boris Derzhavets
2010-11-18 20:23 ` Rudi Ahlers
2010-11-18 20:39 ` [Xen-users] " Pasi Kärkkäinen
2010-11-19 17:08 ` Digimer
2010-11-19 17:11 ` [Xen-users] " Pasi Kärkkäinen
2010-11-19 18:04 ` Digimer
2010-11-19 18:28 ` Pasi Kärkkäinen
2010-11-19 19:07 ` Digimer
2010-11-19 19:15 ` [Xen-users] " Pasi Kärkkäinen
2010-11-22 15:08 ` [Xen-devel] " Konrad Rzeszutek Wilk
2010-11-22 15:26 ` Digimer
2010-11-22 15:59 ` Re: [Xen-users] " Konrad Rzeszutek Wilk
2010-11-18 20:44 ` Pasi Kärkkäinen
2010-11-18 20:57 ` M A Young
2010-11-18 21:02 ` Pasi Kärkkäinen
2010-11-19 4:30 ` Digimer [this message]
2010-11-19 6:57 ` Pasi Kärkkäinen
2010-11-19 15:38 ` Digimer
2010-11-19 16:22 ` Digimer
2010-11-19 16:26 ` Pasi Kärkkäinen
2010-11-19 16:43 ` Digimer
2011-11-19 11:59 ` [Xen-users] " beeckmans.o
2010-11-23 12:24 ` Re: [Xen-users] [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6) xen fails to build Boris Derzhavets
2010-11-23 12:35 ` Michal Novotny
2010-11-23 12:45 ` Boris Derzhavets
2010-11-23 19:09 ` [Xen-devel] " Pasi Kärkkäinen
2010-11-23 19:23 ` Re: [Xen-users] " Boris Derzhavets
2010-11-23 13:03 ` [Xen-devel] " Boris Derzhavets
2010-11-23 14:20 ` [Xen-devel] Re: [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6) . Link for Libvirt 0.8.1 Boris Derzhavets
2010-11-23 14:36 ` Digimer
2010-11-23 19:15 ` Pasi Kärkkäinen
2010-11-23 18:42 ` Re: [Xen-users] " Pasi Kärkkäinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CE5FD53.8060804@alteeve.com \
--to=linux@alteeve.com \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.