Mailing List Archive

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!

--
Digimer
E-Mail: digimer@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin: http://nodeassassin.org

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

On Thu, Nov 18, 2010 at 10:00 PM, Pasi Kärkkäinen <pasik@iki.fi> 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
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>


Thanx for sharing this, how's the performance, since it's a rebuild from FC?


--
Kind Regards
Rudi Ahlers
SoftDux

Website: http://www.SoftDux.com
Technical Blog: http://Blog.SoftDux.com
Office: 087 805 9573
Cell: 082 554 7532

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

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@lists.xensource.com
http://lists.xensource.com/xen-devel

On Thu, Nov 18, 2010 at 10:23:07PM +0200, Rudi Ahlers wrote:
> On Thu, Nov 18, 2010 at 10:00 PM, Pasi Kärkkäinen <pasik@iki.fi> 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
> >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> >
>
>
> Thanx for sharing this, how's the performance, since it's a rebuild from FC?
>

Fedora 14 xen-4.0.1-6 is pretty much the upstream xen.org 4.0.1 version,
just with a couple more bugfixes from xen-4.0-testing.hg (from xen-4.0.2-rc*),
so it should do well.

Note the kernel reference .config has debugging stuff enabled,
so that will slow down dom0.

-- Pasi


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

On Thu, Nov 18, 2010 at 10:23:07PM +0200, Rudi Ahlers wrote:
> On Thu, Nov 18, 2010 at 10:00 PM, Pasi Kärkkäinen <pasik@iki.fi> 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
> >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> >
>
>
> Thanx for sharing this, how's the performance, since it's a rebuild from FC?
>

And well.. RHEL6 is basicly combination of Fedora 12 and Fedora 13 :)

-- Pasi


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

On Thu, 18 Nov 2010, 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,

Interesting. I did look during the betas where I could build xen on RHEL6,
but there weren't enough dependent packages available at the time. I have
done a quick check now, and it looks like dev86 and iasl are missing on
i686 (which is what I was testing it on during the betas) so you probably
can't build your package in that case. x86_64 looks like it might work
though.
I was looking at this from the point of view of whether it would be
feasible to get xen into EPEL, but as it didn't seem to work I didn't seem
to work, I didn't put too much thought into it.

Michael Young

On Thu, Nov 18, 2010 at 08:57:23PM +0000, M A Young wrote:
> On Thu, 18 Nov 2010, 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,
>
> Interesting. I did look during the betas where I could build xen on
> RHEL6, but there weren't enough dependent packages available at the time.
> I have done a quick check now, and it looks like dev86 and iasl are
> missing on i686 (which is what I was testing it on during the betas) so
> you probably can't build your package in that case. x86_64 looks like it
> might work though.
> I was looking at this from the point of view of whether it would be
> feasible to get xen into EPEL, but as it didn't seem to work I didn't
> seem to work, I didn't put too much thought into it.
>

Ok. I haven't tried on 32bit (yet).
I did try using beta2, on x86_64, and that worked aswell.

The important part is to enable the 'Optional' channel in RHN,
otherwise half of the required packages are not available..

-- Pasi


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

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

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

On Thu, Nov 18, 2010 at 11:30:11PM -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
>
> 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?
>

It seems you didn't read well enough ;)

"Before rebuilding libvirt you need to boot into non-Xen environment! This is because some of the automated RHEL6 libvirt Xen-specific tests seem to fail in Xen dom0 environment, but work OK in baremetal."

-- Pasi


> 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
>
> TEST: xencapstest
> !!!!!!!!!! 10 FAIL
> FAIL: xencapstest


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

On 11/19/2010 01:57 AM, Pasi Kärkkäinen wrote:
>> 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?
>>
>
> It seems you didn't read well enough ;)
>
> "Before rebuilding libvirt you need to boot into non-Xen environment! This is because some of the automated RHEL6 libvirt Xen-specific tests seem to fail in Xen dom0 environment, but work OK in baremetal."
>
> -- Pasi

See, this is why I shouldn't be working until after midnight so many
nights. I fail to see the obvious. *sigh* :P

--
Digimer
E-Mail: digimer@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin: http://nodeassassin.org

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

On 11/19/2010 01:57 AM, Pasi Kärkkäinen wrote:
> It seems you didn't read well enough ;)
>
> "Before rebuilding libvirt you need to boot into non-Xen environment! This is because some of the automated RHEL6 libvirt Xen-specific tests seem to fail in Xen dom0 environment, but work OK in baremetal."
>
> -- Pasi

Heh, I'm hesitant to ask now, in case it's another instance of me
failing to read, but... :)

When I first start virt-manager, I get an error/warning saying that
'qemu-kvm' should be installed. I realize this isn't important, as we're
running Xen, but I wanted to try to resolve it just the same. So I tried
to install qemu-kvm from the rebuilt qemu RPMs made earlier in the
tutorial. This led to a requirement I've not been able to meet:

rpm -ivh rpmbuild/RPMS/x86_64/qemu-system-x86-0.12.5-1.el6.x86_64.rpm \
rpmbuild/RPMS/x86_64/qemu-kvm-0.12.5-1.el6.x86_64.rpm
error: Failed dependencies:
seabios-bin is needed by qemu-system-x86-2:0.12.5-1.el6.x86_64
yum provides \*/seabios-bin
Loaded plugins: refresh-packagekit, rhnplugin
No Matches found

I tried rebuilding 'seabios', but it didn't provide seabios-bin either.

Thanks, and sorry in advance if I am missing something obvious (again). :)

--
Digimer
E-Mail: digimer@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin: http://nodeassassin.org

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

On Fri, Nov 19, 2010 at 11:22:39AM -0500, Digimer wrote:
> On 11/19/2010 01:57 AM, Pasi Kärkkäinen wrote:
>> It seems you didn't read well enough ;)
>>
>> "Before rebuilding libvirt you need to boot into non-Xen environment! This is because some of the automated RHEL6 libvirt Xen-specific tests seem to fail in Xen dom0 environment, but work OK in baremetal."
>>
>> -- Pasi
>
> Heh, I'm hesitant to ask now, in case it's another instance of me
> failing to read, but... :)
>
> When I first start virt-manager, I get an error/warning saying that
> 'qemu-kvm' should be installed.
>

I haven't seen this error on my system.

> I realize this isn't important, as we're
> running Xen, but I wanted to try to resolve it just the same. So I tried
> to install qemu-kvm from the rebuilt qemu RPMs made earlier in the
> tutorial. This led to a requirement I've not been able to meet:
>
> rpm -ivh rpmbuild/RPMS/x86_64/qemu-system-x86-0.12.5-1.el6.x86_64.rpm \
> rpmbuild/RPMS/x86_64/qemu-kvm-0.12.5-1.el6.x86_64.rpm
> error: Failed dependencies:
> seabios-bin is needed by qemu-system-x86-2:0.12.5-1.el6.x86_64
> yum provides \*/seabios-bin
> Loaded plugins: refresh-packagekit, rhnplugin
> No Matches found

I don't think you should install those rpms, since RHEL6 already
has kvm included.

You need to only install the additional "qemu-common" rpm,
since that provides the stuff that Xen rpm depends on.

-- Pasi


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

On 11/19/2010 11:26 AM, Pasi Kärkkäinen wrote:
> On Fri, Nov 19, 2010 at 11:22:39AM -0500, Digimer wrote:
>> On 11/19/2010 01:57 AM, Pasi Kärkkäinen wrote:
>>> It seems you didn't read well enough ;)
>>>
>>> "Before rebuilding libvirt you need to boot into non-Xen environment! This is because some of the automated RHEL6 libvirt Xen-specific tests seem to fail in Xen dom0 environment, but work OK in baremetal."
>>>
>>> -- Pasi
>>
>> Heh, I'm hesitant to ask now, in case it's another instance of me
>> failing to read, but... :)
>>
>> When I first start virt-manager, I get an error/warning saying that
>> 'qemu-kvm' should be installed.
>>
>
> I haven't seen this error on my system.
>
>> I realize this isn't important, as we're
>> running Xen, but I wanted to try to resolve it just the same. So I tried
>> to install qemu-kvm from the rebuilt qemu RPMs made earlier in the
>> tutorial. This led to a requirement I've not been able to meet:
>>
>> rpm -ivh rpmbuild/RPMS/x86_64/qemu-system-x86-0.12.5-1.el6.x86_64.rpm \
>> rpmbuild/RPMS/x86_64/qemu-kvm-0.12.5-1.el6.x86_64.rpm
>> error: Failed dependencies:
>> seabios-bin is needed by qemu-system-x86-2:0.12.5-1.el6.x86_64
>> yum provides \*/seabios-bin
>> Loaded plugins: refresh-packagekit, rhnplugin
>> No Matches found
>
> I don't think you should install those rpms, since RHEL6 already
> has kvm included.
>
> You need to only install the additional "qemu-common" rpm,
> since that provides the stuff that Xen rpm depends on.

Indeed. More than anything, I am concerned that customers might see the
error and worry. I know it doesn't effect Xen at all. :)

Well, I'll move on then. I now need to get DRBD compiled against this
kernel. Thank you again.

--
Digimer
E-Mail: digimer@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin: http://nodeassassin.org

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

On 11/18/2010 03:39 PM, Pasi Kärkkäinen wrote:
> Note the kernel reference .config has debugging stuff enabled,
> so that will slow down dom0.
>
> -- Pasi

With regard to this;

I've been hoping to create a set of updated KVM vs. Xen benchmarks as
I've seen this asked for of late and existing data is >3 years old.

I would like to get the kernel setup relatively similarly to how it will
be setup if/when an RPM is provided for RHEL 6.

These are the DEBUG entries I found in .config from your tutorial. Which
are reasonable to set to n/m or just comment out? Did I miss anything
else I should change? Again, I'm not looking to optimize, just to get
closer to what the final generally available kernel will have.

CONFIG_XEN_DEBUG_FS=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_SLUB_DEBUG=y
CONFIG_HAVE_DMA_API_DEBUG=y
CONFIG_X86_DEBUGCTLMSR=y
CONFIG_PM_DEBUG=y
CONFIG_CPU_FREQ_DEBUG=y
CONFIG_CFG80211_DEBUGFS=y
CONFIG_MAC80211_DEBUGFS=y
CONFIG_DEBUG_DEVRES=y
CONFIG_DM_DEBUG=y
CONFIG_FIREWIRE_OHCI_DEBUG=y
CONFIG_MLX4_DEBUG=y
CONFIG_LIBERTAS_DEBUG=y
CONFIG_ATH5K_DEBUG=y
CONFIG_IWLWIFI_DEBUG=y
CONFIG_IWLWIFI_DEBUGFS=y
CONFIG_RT2X00_LIB_DEBUGFS=y
CONFIG_SND_DEBUG=y
CONFIG_SND_PCM_XRUN_DEBUG=y
CONFIG_INFINIBAND_MTHCA_DEBUG=y
CONFIG_INFINIBAND_IPOIB_DEBUG=y
CONFIG_INFINIBAND_IPOIB_DEBUG_DATA=y
CONFIG_JBD2_DEBUG=y
CONFIG_DLM_DEBUG=y
CONFIG_DEBUG_FS=y
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_SHIRQ=y
CONFIG_SCHED_DEBUG=y
CONFIG_DEBUG_OBJECTS=y
CONFIG_DEBUG_OBJECTS_FREE=y
CONFIG_DEBUG_OBJECTS_TIMERS=y
CONFIG_DEBUG_OBJECTS_ENABLE_DEFAULT=1
CONFIG_SLUB_DEBUG_ON=y
CONFIG_DEBUG_RT_MUTEXES=y
CONFIG_DEBUG_PI_LIST=y
CONFIG_DEBUG_SPINLOCK=y
CONFIG_DEBUG_MUTEXES=y
CONFIG_DEBUG_LOCK_ALLOC=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_VM=y
CONFIG_DEBUG_WRITECOUNT=y
CONFIG_DEBUG_MEMORY_INIT=y
CONFIG_DEBUG_LIST=y
CONFIG_DEBUG_SG=y
CONFIG_DEBUG_NOTIFIERS=y
CONFIG_FAULT_INJECTION_DEBUG_FS=y
CONFIG_DYNAMIC_DEBUG=y
CONFIG_DMA_API_DEBUG=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_STACK_USAGE=y
CONFIG_DEBUG_RODATA=y
CONFIG_DEBUG_RODATA_TEST=y
CONFIG_DEBUG_NX_TEST=m
CONFIG_DEBUG_BOOT_PARAMS=y
CONFIG_KEYS_DEBUG_PROC_KEYS=y

I realize a bunch of these are for hardware that has little or nothing
to do with Xen.

Thanks for any feedback.

--
Digimer
E-Mail: digimer@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin: http://nodeassassin.org

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

On Fri, Nov 19, 2010 at 12:08:30PM -0500, Digimer wrote:
> On 11/18/2010 03:39 PM, Pasi Kärkkäinen wrote:
>> Note the kernel reference .config has debugging stuff enabled,
>> so that will slow down dom0.
>>
>> -- Pasi
>
> With regard to this;
>
> I've been hoping to create a set of updated KVM vs. Xen benchmarks as
> I've seen this asked for of late and existing data is >3 years old.
>
> I would like to get the kernel setup relatively similarly to how it will
> be setup if/when an RPM is provided for RHEL 6.
>
> These are the DEBUG entries I found in .config from your tutorial. Which
> are reasonable to set to n/m or just comment out? Did I miss anything
> else I should change? Again, I'm not looking to optimize, just to get
> closer to what the final generally available kernel will have.
>

Yeah, you should definitely disable the various DEBUG options
for performance benchmarking.

-- Pasi

> CONFIG_XEN_DEBUG_FS=y
> CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
> CONFIG_SLUB_DEBUG=y
> CONFIG_HAVE_DMA_API_DEBUG=y
> CONFIG_X86_DEBUGCTLMSR=y
> CONFIG_PM_DEBUG=y
> CONFIG_CPU_FREQ_DEBUG=y
> CONFIG_CFG80211_DEBUGFS=y
> CONFIG_MAC80211_DEBUGFS=y
> CONFIG_DEBUG_DEVRES=y
> CONFIG_DM_DEBUG=y
> CONFIG_FIREWIRE_OHCI_DEBUG=y
> CONFIG_MLX4_DEBUG=y
> CONFIG_LIBERTAS_DEBUG=y
> CONFIG_ATH5K_DEBUG=y
> CONFIG_IWLWIFI_DEBUG=y
> CONFIG_IWLWIFI_DEBUGFS=y
> CONFIG_RT2X00_LIB_DEBUGFS=y
> CONFIG_SND_DEBUG=y
> CONFIG_SND_PCM_XRUN_DEBUG=y
> CONFIG_INFINIBAND_MTHCA_DEBUG=y
> CONFIG_INFINIBAND_IPOIB_DEBUG=y
> CONFIG_INFINIBAND_IPOIB_DEBUG_DATA=y
> CONFIG_JBD2_DEBUG=y
> CONFIG_DLM_DEBUG=y
> CONFIG_DEBUG_FS=y
> CONFIG_DEBUG_KERNEL=y
> CONFIG_DEBUG_SHIRQ=y
> CONFIG_SCHED_DEBUG=y
> CONFIG_DEBUG_OBJECTS=y
> CONFIG_DEBUG_OBJECTS_FREE=y
> CONFIG_DEBUG_OBJECTS_TIMERS=y
> CONFIG_DEBUG_OBJECTS_ENABLE_DEFAULT=1
> CONFIG_SLUB_DEBUG_ON=y
> CONFIG_DEBUG_RT_MUTEXES=y
> CONFIG_DEBUG_PI_LIST=y
> CONFIG_DEBUG_SPINLOCK=y
> CONFIG_DEBUG_MUTEXES=y
> CONFIG_DEBUG_LOCK_ALLOC=y
> CONFIG_DEBUG_SPINLOCK_SLEEP=y
> CONFIG_DEBUG_BUGVERBOSE=y
> CONFIG_DEBUG_INFO=y
> CONFIG_DEBUG_VM=y
> CONFIG_DEBUG_WRITECOUNT=y
> CONFIG_DEBUG_MEMORY_INIT=y
> CONFIG_DEBUG_LIST=y
> CONFIG_DEBUG_SG=y
> CONFIG_DEBUG_NOTIFIERS=y
> CONFIG_FAULT_INJECTION_DEBUG_FS=y
> CONFIG_DYNAMIC_DEBUG=y
> CONFIG_DMA_API_DEBUG=y
> CONFIG_DEBUG_STACKOVERFLOW=y
> CONFIG_DEBUG_STACK_USAGE=y
> CONFIG_DEBUG_RODATA=y
> CONFIG_DEBUG_RODATA_TEST=y
> CONFIG_DEBUG_NX_TEST=m
> CONFIG_DEBUG_BOOT_PARAMS=y
> CONFIG_KEYS_DEBUG_PROC_KEYS=y
>
> I realize a bunch of these are for hardware that has little or nothing
> to do with Xen.
>
> Thanks for any feedback.
>
> --
> Digimer
> E-Mail: digimer@alteeve.com
> AN!Whitepapers: http://alteeve.com
> Node Assassin: http://nodeassassin.org

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

On 11/19/2010 12:11 PM, Pasi Kärkkäinen wrote:
> On Fri, Nov 19, 2010 at 12:08:30PM -0500, Digimer wrote:
>> On 11/18/2010 03:39 PM, Pasi Kärkkäinen wrote:
>>> Note the kernel reference .config has debugging stuff enabled,
>>> so that will slow down dom0.
>>>
>>> -- Pasi
>>
>> With regard to this;
>>
>> I've been hoping to create a set of updated KVM vs. Xen benchmarks as
>> I've seen this asked for of late and existing data is>3 years old.
>>
>> I would like to get the kernel setup relatively similarly to how it will
>> be setup if/when an RPM is provided for RHEL 6.
>>
>> These are the DEBUG entries I found in .config from your tutorial. Which
>> are reasonable to set to n/m or just comment out? Did I miss anything
>> else I should change? Again, I'm not looking to optimize, just to get
>> closer to what the final generally available kernel will have.
>>
>
> Yeah, you should definitely disable the various DEBUG options
> for performance benchmarking.
>
> -- Pasi

Thanks, I'm compiling now. If it works, I'll post my patch for
review/critique. :P

--
Digimer
E-Mail: digimer@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin: http://nodeassassin.org

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

On Fri, Nov 19, 2010 at 01:04:55PM -0500, Digimer wrote:
> On 11/19/2010 12:11 PM, Pasi Kärkkäinen wrote:
>> On Fri, Nov 19, 2010 at 12:08:30PM -0500, Digimer wrote:
>>> On 11/18/2010 03:39 PM, Pasi Kärkkäinen wrote:
>>>> Note the kernel reference .config has debugging stuff enabled,
>>>> so that will slow down dom0.
>>>>
>>>> -- Pasi
>>>
>>> With regard to this;
>>>
>>> I've been hoping to create a set of updated KVM vs. Xen benchmarks as
>>> I've seen this asked for of late and existing data is>3 years old.
>>>
>>> I would like to get the kernel setup relatively similarly to how it will
>>> be setup if/when an RPM is provided for RHEL 6.
>>>
>>> These are the DEBUG entries I found in .config from your tutorial. Which
>>> are reasonable to set to n/m or just comment out? Did I miss anything
>>> else I should change? Again, I'm not looking to optimize, just to get
>>> closer to what the final generally available kernel will have.
>>>
>>
>> Yeah, you should definitely disable the various DEBUG options
>> for performance benchmarking.
>>
>> -- Pasi
>
> Thanks, I'm compiling now. If it works, I'll post my patch for
> review/critique. :P
>

Yep.

How/what are you thinking of benchmarking?

-- Pasi


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

On 11/19/2010 01:28 PM, Pasi Kärkkäinen wrote:
> Yep.
>
> How/what are you thinking of benchmarking?
>
> -- Pasi

My current plan is;
- Repeat all tests 3 times and average the results.
- All tests run inside of a VM, one set with only one VM, again
simultaneously on two VMs and then a final set with three VMs
simultaneously.
- Actual tests:
- bonnie++
- kernel compile timing
- network transfer of a large file from a common source
- migration timing on VM (live and frozen)

I'd love to hear suggestions for other tests as well. I'll be posting my
results here:

http://wiki.alteeve.com/index.php/Xen_vs._KVM_Benchmark_-_Nov._2010

It's pretty empty though just now though.

--
Digimer
E-Mail: digimer@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin: http://nodeassassin.org

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

On Fri, Nov 19, 2010 at 02:07:54PM -0500, Digimer wrote:
> On 11/19/2010 01:28 PM, Pasi Kärkkäinen wrote:
>> Yep.
>>
>> How/what are you thinking of benchmarking?
>>
>> -- Pasi
>
> My current plan is;
> - Repeat all tests 3 times and average the results.
> - All tests run inside of a VM, one set with only one VM, again
> simultaneously on two VMs and then a final set with three VMs
> simultaneously.
>

It would be nice if you benchmarked both Xen PV and HVM VMs:

- Xen PV 32bit VM
- Xen PV 64bit VM

- Xen HVM 32bit VM
- Xen HVM 64bit VM

- Xen HVM 32bit VM (with PV-on-HVM drivers)
- Xen HVM 64bit VM (with PV-on-HVM drivers)


-- Pasi

> - Actual tests:
> - bonnie++
> - kernel compile timing
> - network transfer of a large file from a common source
> - migration timing on VM (live and frozen)
>
> I'd love to hear suggestions for other tests as well. I'll be posting my
> results here:
>
> http://wiki.alteeve.com/index.php/Xen_vs._KVM_Benchmark_-_Nov._2010
>
> It's pretty empty though just now though.
>
> --
> Digimer
> E-Mail: digimer@alteeve.com
> AN!Whitepapers: http://alteeve.com
> Node Assassin: http://nodeassassin.org

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

On Fri, Nov 19, 2010 at 02:07:54PM -0500, Digimer wrote:
> On 11/19/2010 01:28 PM, Pasi Kärkkäinen wrote:
> >Yep.
> >
> >How/what are you thinking of benchmarking?
> >
> >-- Pasi
>
> My current plan is;
> - Repeat all tests 3 times and average the results.
> - All tests run inside of a VM, one set with only one VM, again
> simultaneously on two VMs and then a final set with three VMs
> simultaneously.
> - Actual tests:
> - bonnie++

also do fio and use the iometer example.

> - kernel compile timing
> - network transfer of a large file from a common source
> - migration timing on VM (live and frozen)
>
> I'd love to hear suggestions for other tests as well. I'll be

This would be 2.6.32 kernel on both sides of equation?
> posting my results here:
>
> http://wiki.alteeve.com/index.php/Xen_vs._KVM_Benchmark_-_Nov._2010
>
> It's pretty empty though just now though.
>
> --
> Digimer
> E-Mail: digimer@alteeve.com
> AN!Whitepapers: http://alteeve.com
> Node Assassin: http://nodeassassin.org
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

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

On 11/22/2010 10:08 AM, Konrad Rzeszutek Wilk wrote:
>> My current plan is;
>> - Repeat all tests 3 times and average the results.
>> - All tests run inside of a VM, one set with only one VM, again
>> simultaneously on two VMs and then a final set with three VMs
>> simultaneously.
>> - Actual tests:
>> - bonnie++
>
> also do fio and use the iometer example.

I'll look into adding it to the tests.

>> - kernel compile timing
>> - network transfer of a large file from a common source
>> - migration timing on VM (live and frozen)
>>
>> I'd love to hear suggestions for other tests as well. I'll be
>
> This would be 2.6.32 kernel on both sides of equation?

Yup.

--
Digimer
E-Mail: digimer@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin: http://nodeassassin.org

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

On Mon, Nov 22, 2010 at 10:08:27AM -0500, Konrad Rzeszutek Wilk wrote:
> On Fri, Nov 19, 2010 at 02:07:54PM -0500, Digimer wrote:
> > On 11/19/2010 01:28 PM, Pasi Kärkkäinen wrote:
> > >Yep.
> > >
> > >How/what are you thinking of benchmarking?
> > >
> > >-- Pasi
> >
> > My current plan is;
> > - Repeat all tests 3 times and average the results.
> > - All tests run inside of a VM, one set with only one VM, again
> > simultaneously on two VMs and then a final set with three VMs
> > simultaneously.

Try more too. As in more VCPUs than your machine has.

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

In meantime
yum install texi2html pciutils-devel
fails.
What causes failure

[root@el6 x86_64]# cd /root/src

[root@el6 src]# wget ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/13/SRPMS/qemu-0.12.5-1.fc13.src.rpm

[root@el6 src]# rpm -i qemu-0.12.5-1.fc13.src.rpm

[root@el6 src]# cd /root/rpmbuild/SPECS

[root@el6 SPECS]# rpmbuild -bb qemu.spec


Attempt to drop dependences doesn't help.

Boris.

On Tue, Nov 23, 2010 at 03:55:28AM -0800, Boris Derzhavets wrote:
> In meantime
> yum install texi2html pciutils-devel
> fails.
> What causes failure
>

You need to enable the Optional channel from RHN. It' mentioned in the tutorial..

-- Pasi

> [root@el6 x86_64]# cd /root/src
> [root@el6 src]# wget
> ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/13/SRPMS/qemu-0.12.5-1.fc13.src.rpm
> [root@el6 src]# rpm -i qemu-0.12.5-1.fc13.src.rpm
> [root@el6 src]# cd /root/rpmbuild/SPECS
> [root@el6 SPECS]# rpmbuild -bb qemu.spec
>
> Attempt to drop dependences doesn't help.
>
> Boris.

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

In meantime :-

[root@Server6RH SPECS]# rpmbuild -bb ./xen.spec
error: Failed build dependencies:
    texi2html is needed by xen-4.0.1-6.el6.x86_64
    dev86 is needed by xen-4.0.1-6.el6.x86_64
    pciutils-devel is needed by xen-4.0.1-6.el6.x86_64
    iasl is needed by xen-4.0.1-6.el6.x86_64


Boris.

It's just evaluation subscription and i was not given this option.
Moreover i cannot reconnect to RHN

Boris.

--- On Tue, 11/23/10, Pasi Kärkkäinen <pasik@iki.fi> wrote:

From: Pasi Kärkkäinen <pasik@iki.fi>
Subject: Re: [Xen-devel] Re: [Xen-users] [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6)
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Digimer" <linux@alteeve.com>, xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Date: Tuesday, November 23, 2010, 7:23 AM

On Tue, Nov 23, 2010 at 03:55:28AM -0800, Boris Derzhavets wrote:
> In meantime
> yum install texi2html pciutils-devel
> fails.
> What causes failure
>

You need to enable the Optional channel from RHN. It' mentioned in the tutorial..

-- Pasi

> [root@el6 x86_64]# cd /root/src
> [root@el6 src]# wget
> ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/updates/13/SRPMS/qemu-0.12.5-1.fc13.src.rpm
> [root@el6 src]# rpm -i qemu-0.12.5-1.fc13.src.rpm
> [root@el6 src]# cd /root/rpmbuild/SPECS
> [root@el6 SPECS]# rpmbuild -bb qemu.spec
>
> Attempt to drop dependences doesn't help.
>
> Boris.

If you're subscribed into Optional channel (and maybe some other channel
too) in RHN you should be able to download and install them using yum, i.e.

# yum install texi2html dev86 pciutils-devel iasl

command. After that you should be able to recompile. In RHEL-6
environment you can always try either to google for the package or,
better, use `yum install` command to install the dependencies required.

Michal

On 11/23/2010 01:24 PM, Boris Derzhavets wrote:
> In meantime :-
>
> [root@Server6RH SPECS]# rpmbuild -bb ./xen.spec
> error: Failed build dependencies:
> texi2html is needed by xen-4.0.1-6.el6.x86_64
> dev86 is needed by xen-4.0.1-6.el6.x86_64
> pciutils-devel is needed by xen-4.0.1-6.el6.x86_64
> iasl is needed by xen-4.0.1-6.el6.x86_64
>
>
> Boris.
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


--
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat


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

It seems to be impossible reconnect to RHN to subscribe to optional
channel. During registration (30 days evaluation account) i was not given any
option.

Boris.

--- On Tue, 11/23/10, Michal Novotny <minovotn@redhat.com> wrote:

From: Michal Novotny <minovotn@redhat.com>
Subject: Re: [Xen-devel] Re: [Xen-users] [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6) xen fails to build
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Pasi Kärkkäinen" <pasik@iki.fi>, "Digimer" <linux@alteeve.com>, xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Date: Tuesday, November 23, 2010, 7:35 AM

If you're subscribed into Optional channel (and maybe some other channel
too) in RHN you should be able to download and install them using yum, i.e.

# yum install texi2html dev86 pciutils-devel iasl

command. After that you should be able to recompile. In RHEL-6
environment you can always try either to google for the package or,
better, use `yum install` command to install the dependencies required.

Michal

On 11/23/2010 01:24 PM, Boris Derzhavets wrote:
> In meantime :-
>
> [root@Server6RH SPECS]# rpmbuild -bb ./xen.spec
> error: Failed build dependencies:
>     texi2html is needed by xen-4.0.1-6.el6.x86_64
>     dev86 is needed by xen-4.0.1-6.el6.x86_64
>     pciutils-devel is needed by xen-4.0.1-6.el6.x86_64
>     iasl is needed by xen-4.0.1-6.el6.x86_64
>
>
> Boris.
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


--
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat

I did subscription to Optinal Channel via login to RHN.

Thank you.

Boris

--- On Tue, 11/23/10, Michal Novotny <minovotn@redhat.com> wrote:

From: Michal Novotny <minovotn@redhat.com>
Subject: Re: [Xen-devel] Re: [Xen-users] [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6) xen fails to build
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: xen-devel@lists.xensource.com, "Digimer" <linux@alteeve.com>, xen-users@lists.xensource.com
Date: Tuesday, November 23, 2010, 7:35 AM

If you're subscribed into Optional channel (and maybe some other channel
too) in RHN you should be able to download and install them using yum, i.e.

# yum install texi2html dev86 pciutils-devel iasl

command. After that you should be able to recompile. In RHEL-6
environment you can always try either to google for the package or,
better, use `yum install` command to install the dependencies required.

Michal

On 11/23/2010 01:24 PM, Boris Derzhavets wrote:
> In meantime :-
>
> [root@Server6RH SPECS]# rpmbuild -bb ./xen.spec
> error: Failed build dependencies:
>     texi2html is needed by xen-4.0.1-6.el6.x86_64
>     dev86 is needed by xen-4.0.1-6.el6.x86_64
>     pciutils-devel is needed by xen-4.0.1-6.el6.x86_64
>     iasl is needed by xen-4.0.1-6.el6.x86_64
>
>
> Boris.
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


--
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat


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

I believe path to libvirt :-

ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/os/SRPMS/libvirt-0.8.1-27.el6.src.rpm

It doesn't match "Howto"

Boris.

--- On Tue, 11/23/10, Boris Derzhavets <bderzhavets@yahoo.com> wrote:

From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] Re: [Xen-users] [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6) xen fails to build
To: "Michal Novotny" <minovotn@redhat.com>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com, "Digimer" <linux@alteeve.com>
Date: Tuesday, November 23, 2010, 8:03 AM

I did subscription to Optinal Channel via login to RHN.

Thank you.

Boris

--- On Tue, 11/23/10, Michal Novotny <minovotn@redhat.com> wrote:

From: Michal Novotny <minovotn@redhat.com>
Subject: Re: [Xen-devel] Re: [Xen-users] [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6) xen fails to build
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: xen-devel@lists.xensource.com, "Digimer" <linux@alteeve.com>, xen-users@lists.xensource.com
Date: Tuesday, November 23, 2010, 7:35 AM

If you're subscribed into Optional channel (and maybe some other channel
too) in RHN you should be able to download and install them using yum, i.e.

# yum
install texi2html dev86 pciutils-devel iasl

command. After that you should be able to recompile. In RHEL-6
environment you can always try either to google for the package or,
better, use `yum install` command to install the dependencies required.

Michal

On 11/23/2010 01:24 PM, Boris Derzhavets wrote:
> In meantime :-
>
> [root@Server6RH SPECS]# rpmbuild -bb ./xen.spec
> error: Failed build dependencies:
>     texi2html is needed by xen-4.0.1-6.el6.x86_64
>     dev86 is needed by xen-4.0.1-6.el6.x86_64
>     pciutils-devel is needed by xen-4.0.1-6.el6.x86_64
>     iasl is needed by xen-4.0.1-6.el6.x86_64
>
>
> Boris.
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel


--
Michal Novotny<minovotn@redhat.com>, RHCE
Virtualization Team (xen userspace), Red Hat


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




-----Inline Attachment Follows-----

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

On 11/23/2010 09:20 AM, Boris Derzhavets wrote:
> I believe path to libvirt :-
>
> ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/os/SRPMS/libvirt-0.8.1-27.el6.src.rpm
>
> It doesn't match "Howto"
>
> Boris.

ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/os/SRPMS/libvirt-0.8.1-27.el6.src.rpm

Just checked, it's there. Red Hat did change the URL yesterday though.

--
Digimer
E-Mail: digimer@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin: http://nodeassassin.org

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

On Tue, Nov 23, 2010 at 06:20:52AM -0800, Boris Derzhavets wrote:
> I believe path to libvirt :-
>
> ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/os/SRPMS/libvirt-0.8.1-27.el6.src.rpm
>
> It doesn't match "Howto"
>

Hmm.. the URL has changed, it seems.. I'll fix it.

Thanks!

-- Pasi


> Boris.
>
> --- On Tue, 11/23/10, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
>
> From: Boris Derzhavets <bderzhavets@yahoo.com>
> Subject: Re: [Xen-devel] Re: [Xen-users] [HOWTO] Running Xen 4.0 host (dom0) with Redhat
> Enterprise Linux 6 (RHEL6) xen fails to build
> To: "Michal Novotny" <minovotn@redhat.com>
> Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com, "Digimer" <linux@alteeve.com>
> Date: Tuesday, November 23, 2010, 8:03 AM
>
> I did subscription to Optinal Channel via login to RHN.
>
> Thank you.
>
> Boris
>
> --- On Tue, 11/23/10, Michal Novotny <minovotn@redhat.com> wrote:
>
> From: Michal Novotny <minovotn@redhat.com>
> Subject: Re: [Xen-devel] Re: [Xen-users] [HOWTO] Running Xen 4.0 host (dom0) with Redhat
> Enterprise Linux 6 (RHEL6) xen fails to build
> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> Cc: xen-devel@lists.xensource.com, "Digimer" <linux@alteeve.com>,
> xen-users@lists.xensource.com
> Date: Tuesday, November 23, 2010, 7:35 AM
>
> If you're subscribed into Optional channel (and maybe some other channel
> too) in RHN you should be able to download and install them using yum, i.e.
>
> # yum install texi2html dev86 pciutils-devel iasl
>
> command. After that you should be able to recompile. In RHEL-6
> environment you can always try either to google for the package or,
> better, use `yum install` command to install the dependencies required.
>
> Michal
>
> On 11/23/2010 01:24 PM, Boris Derzhavets wrote:
> > In meantime :-
> >
> > [root@Server6RH SPECS]# rpmbuild -bb ./xen.spec
> > error: Failed build dependencies:
> > texi2html is needed by xen-4.0.1-6.el6.x86_64
> > dev86 is needed by xen-4.0.1-6.el6.x86_64
> > pciutils-devel is needed by xen-4.0.1-6.el6.x86_64
> > iasl is needed by xen-4.0.1-6.el6.x86_64
> >
> >
> > Boris.
> >
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > [1]http://lists.xensource.com/xen-devel
>
> --
> Michal Novotny<minovotn@redhat.com>, RHCE
> Virtualization Team (xen userspace), Red Hat
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> [2]http://lists.xensource.com/xen-devel
>
> -----Inline Attachment Follows-----
>
> _______________________________________________
> Xen-users mailing list
> [3]Xen-users@lists.xensource.com
> [4]http://lists.xensource.com/xen-users
>
> References
>
> Visible links
> 1. http://lists.xensource.com/xen-devel
> 2. http://lists.xensource.com/xen-devel
> 3. file:///mc/compose?to=Xen-users@lists.xensource.com
> 4. http://lists.xensource.com/xen-users

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


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

On Tue, Nov 23, 2010 at 04:45:25AM -0800, Boris Derzhavets wrote:
> It seems to be impossible reconnect to RHN to subscribe to optional
> channel. During registration (30 days evaluation account) i was not given
> any
> option.
>

RHN channel subscriptions are changed from the RHN website,
not from the RHEL6 server..

So maybe that's the problem..

-- Pasi

> Boris.
>
> --- On Tue, 11/23/10, Michal Novotny <minovotn@redhat.com> wrote:
>
> From: Michal Novotny <minovotn@redhat.com>
> Subject: Re: [Xen-devel] Re: [Xen-users] [HOWTO] Running Xen 4.0 host
> (dom0) with Redhat Enterprise Linux 6 (RHEL6) xen fails to build
> To: "Boris Derzhavets" <bderzhavets@yahoo.com>
> Cc: "Pasi Kärkkäinen" <pasik@iki.fi>, "Digimer" <linux@alteeve.com>,
> xen-devel@lists.xensource.com, xen-users@lists.xensource.com
> Date: Tuesday, November 23, 2010, 7:35 AM
>
> If you're subscribed into Optional channel (and maybe some other channel
> too) in RHN you should be able to download and install them using yum,
> i.e.
>
> # yum install texi2html dev86 pciutils-devel iasl
>
> command. After that you should be able to recompile. In RHEL-6
> environment you can always try either to google for the package or,
> better, use `yum install` command to install the dependencies required.
>
> Michal
>
> On 11/23/2010 01:24 PM, Boris Derzhavets wrote:
> > In meantime :-
> >
> > [root@Server6RH SPECS]# rpmbuild -bb ./xen.spec
> > error: Failed build dependencies:
> > texi2html is needed by xen-4.0.1-6.el6.x86_64
> > dev86 is needed by xen-4.0.1-6.el6.x86_64
> > pciutils-devel is needed by xen-4.0.1-6.el6.x86_64
> > iasl is needed by xen-4.0.1-6.el6.x86_64
> >
> >
> > Boris.
> >
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > [1]Xen-devel@lists.xensource.com
> > [2]http://lists.xensource.com/xen-devel
>
> --
> Michal Novotny<[3]minovotn@redhat.com>, RHCE
> Virtualization Team (xen userspace), Red Hat
>
> References
>
> Visible links
> 1. file:///mc/compose?to=Xen-devel@lists.xensource.com
> 2. http://lists.xensource.com/xen-devel
> 3. file:///mc/compose?to=minovotn@redhat.com

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

On Tue, Nov 23, 2010 at 09:36:27AM -0500, Digimer wrote:
> On 11/23/2010 09:20 AM, Boris Derzhavets wrote:
>> I believe path to libvirt :-
>>
>> ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/os/SRPMS/libvirt-0.8.1-27.el6.src.rpm
>>
>> It doesn't match "Howto"
>>
>> Boris.
>
> ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/os/SRPMS/libvirt-0.8.1-27.el6.src.rpm
>
> Just checked, it's there. Red Hat did change the URL yesterday though.
>

Yep, I just updated the tutorial to have the proper link.

-- Pasi


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

Thanks, Pasi.
I found out it about 7 hr ago and sent message to list.
"rhn_register" works just once and installs basic channel ( via server's session)
Afterwards one should login to rhn.redhat.com and change subscription
to "Optional"  inside account .

All your hackery works fine.
   I've also tried to rebuild Michael's xendom0  .32.25-172.src.rpm . It generates problem with kernel-firmware.rpm. I would not expect him to fix it , until CentOS 6.0 will be out.

Boris.
P.S. asciidoc dependency may be dropped during .32.25-172.src.rpm rebuild.

--- On Tue, 11/23/10, Pasi Kärkkäinen <pasik@iki.fi> wrote:

From: Pasi Kärkkäinen <pasik@iki.fi>
Subject: Re: [Xen-devel] Re: [Xen-users] [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6) xen fails to build
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Michal Novotny" <minovotn@redhat.com>, "Digimer" <linux@alteeve.com>, xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Date: Tuesday, November 23, 2010, 2:09 PM

On Tue, Nov 23, 2010 at 04:45:25AM -0800, Boris Derzhavets wrote:
>    It seems to be impossible reconnect to RHN to subscribe to optional
>    channel. During registration (30 days evaluation account) i was not given
>    any
>    option.
>

RHN channel subscriptions are changed from the RHN website,
not from the RHEL6 server..

So maybe that's the problem..

-- Pasi

>    Boris.
>
>    --- On Tue, 11/23/10, Michal Novotny <minovotn@redhat.com> wrote:
>
>      From: Michal Novotny <minovotn@redhat.com>
>      Subject: Re: [Xen-devel] Re: [Xen-users] [HOWTO] Running Xen 4.0 host
>      (dom0) with Redhat Enterprise Linux 6 (RHEL6) xen fails to build
>      To: "Boris Derzhavets" <bderzhavets@yahoo.com>
>      Cc: "Pasi Kärkkäinen" <pasik@iki.fi>, "Digimer" <linux@alteeve.com>,
>      xen-devel@lists.xensource.com, xen-users@lists.xensource.com
>      Date: Tuesday, November 23, 2010, 7:35 AM
>
>      If you're subscribed into Optional channel (and maybe some other channel
>      too) in RHN you should be able to download and install them using yum,
>      i.e.
>
>      # yum install texi2html dev86 pciutils-devel iasl
>
>      command. After that you should be able to recompile. In RHEL-6
>      environment you can always try either to google for the package or,
>      better, use `yum install` command to install the dependencies required.
>
>      Michal
>
>      On 11/23/2010 01:24 PM, Boris Derzhavets wrote:
>      > In meantime :-
>      >
>      > [root@Server6RH SPECS]# rpmbuild -bb ./xen.spec
>      > error: Failed build dependencies:
>      >     texi2html is needed by xen-4.0.1-6.el6.x86_64
>      >     dev86 is needed by xen-4.0.1-6.el6.x86_64
>      >     pciutils-devel is needed by xen-4.0.1-6.el6.x86_64
>      >     iasl is needed by xen-4.0.1-6.el6.x86_64
>      >
>      >
>      > Boris.
>      >
>      >
>      >
>      > _______________________________________________
>      > Xen-devel mailing list
>      > [1]Xen-devel@lists.xensource.com
>      > [2]http://lists.xensource.com/xen-devel
>
>      --
>      Michal Novotny<[3]minovotn@redhat.com>, RHCE
>      Virtualization Team (xen userspace), Red Hat
>
> References
>
>    Visible links
>    1. file:///mc/compose?to=Xen-devel@lists.xensource.com
>    2. http://lists.xensource.com/xen-devel
>    3. file:///mc/compose?to=minovotn@redhat.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@iki.fi> wrote:

From: Pasi Kärkkäinen <pasik@iki.fi>
Subject: [Xen-devel] Re: [Xen-users] [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6)
To: "Digimer" <linux@alteeve.com>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
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@lists.xensource.com
http://lists.xensource.com/xen-devel

Could it be considered as update for "HOWTO" ?

http://bderzhavets.wordpress.com/2010/11/29/rebuild-kernel-2-6-32-26-174-xendom0-fc12-src-rpm-on-rhel-server-6/

Boris.

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

From: Pasi Kärkkäinen <pasik@iki.fi>
Subject: [Xen-devel] Re: [Xen-users] [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6)
To: "Digimer" <linux@alteeve.com>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
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@lists.xensource.com
http://lists.xensource.com/xen-devel

On 11/29/2010 02:40 PM, Boris Derzhavets wrote:
> Could it be considered as update for "HOWTO" ?
>
> http://bderzhavets.wordpress.com/2010/11/29/rebuild-kernel-2-6-32-26-174-xendom0-fc12-src-rpm-on-rhel-server-6/
>
> Boris.

I ran through this tonight, and I did get it working and installed, so
thank you. :)

If I can make a couple suggestions?

1. Provide a downloadable patch file and and example showing how to use
patch for those who might be less familiar with it.

2. After compile and install, disable the epel repo as it triggers these
errors:

------------------------------------------------------------------------
[root@an-node03 x86_64]# yum update
Loaded plugins: refresh-packagekit, rhnplugin
epel | 3.7 kB 00:00
epel/primary_db | 3.4 MB 00:07
rhel-x86_64-server-6 | 1.8 kB 00:00
rhel-x86_64-server-6/primary | 1.6 MB 00:03
rhel-x86_64-server-6 3562/3562
rhel-x86_64-server-ha-6 | 1.8 kB 00:00
rhel-x86_64-server-ha-6/primary | 13 kB 00:00
rhel-x86_64-server-ha-6 35/35
rhel-x86_64-server-optional-6 | 1.6 kB 00:00
rhel-x86_64-server-optional-6/primary| 695 kB 00:01
rhel-x86_64-server-optional-6 2672/2672
Setting up Update Process
Resolving Dependencies
--> Running transaction check
--> Processing Dependency: pkgconfig(augeas) >= 0.5.0 for package:
netcf-devel-0.1.6-4.el6.x86_64
---> Package augeas-devel.x86_64 0:0.7.3-1.el5 set to be updated
--> Processing Dependency: augeas-libs = 0.7.2-3.el6 for package:
augeas-devel-0.7.2-3.el6.i686
---> Package augeas-libs.x86_64 0:0.7.3-1.el5 set to be updated
---> Package cvs.x86_64 0:1.11.23-11.el6_0.1 set to be updated
---> Package fontpackages-filesystem.noarch 0:1.44-1.el5.1 set to be updated
---> Package iwl6000-firmware.noarch 0:9.193.4.1-1.el5 set to be updated
---> Package libldb.x86_64 0:0.9.10-25.el5 set to be updated
---> Package libtalloc.x86_64 0:2.0.1-7.el5 set to be updated
---> Package libtdb.x86_64 0:1.2.1-4.el5 set to be updated
---> Package python-nose.noarch 0:0.11.3-2.el5 set to be updated
--> Processing Dependency: python(abi) = 2.4 for package:
python-nose-0.11.3-2.el5.noarch
---> Package python-paramiko.noarch 0:1.7.6-1.el5 set to be updated
--> Processing Dependency: python(abi) = 2.4 for package:
python-paramiko-1.7.6-1.el5.noarch
---> Package xorg-x11-drv-qxl.x86_64 0:0.0.12-2.1.el6_0.1 set to be updated
--> Running transaction check
---> Package augeas-devel.i686 0:0.7.2-3.el6 set to be updated
---> Package augeas-libs.i686 0:0.7.2-3.el6 set to be updated
--> Processing Dependency: libselinux.so.1 for package:
augeas-libs-0.7.2-3.el6.i686
---> Package python-nose.noarch 0:0.11.3-2.el5 set to be updated
--> Processing Dependency: python(abi) = 2.4 for package:
python-nose-0.11.3-2.el5.noarch
---> Package python-paramiko.noarch 0:1.7.6-1.el5 set to be updated
--> Processing Dependency: python(abi) = 2.4 for package:
python-paramiko-1.7.6-1.el5.noarch
--> Running transaction check
---> Package libselinux.i686 0:2.0.94-2.el6 set to be updated
---> Package python-nose.noarch 0:0.11.3-2.el5 set to be updated
--> Processing Dependency: python(abi) = 2.4 for package:
python-nose-0.11.3-2.el5.noarch
---> Package python-paramiko.noarch 0:1.7.6-1.el5 set to be updated
--> Processing Dependency: python(abi) = 2.4 for package:
python-paramiko-1.7.6-1.el5.noarch
--> Finished Dependency Resolution
Error: Package: python-nose-0.11.3-2.el5.noarch (epel)
Requires: python(abi) = 2.4
Installed: python-2.6.5-3.el6.x86_64 (@Red Hat Enterprise
Linux/6.0)
python(abi) = 2.6
Available: python26-2.6.5-5.el5.x86_64 (epel)
python(abi) = 2.6
Error: Package: python-paramiko-1.7.6-1.el5.noarch (epel)
Requires: python(abi) = 2.4
Installed: python-2.6.5-3.el6.x86_64 (@Red Hat Enterprise
Linux/6.0)
python(abi) = 2.6
Available: python26-2.6.5-5.el5.x86_64 (epel)
python(abi) = 2.6
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
------------------------------------------------------------------------

I had to change /etc/yum.repos.d/epel.repo to 'enabled=0' and then run
'yum clean all && yum update' to get yum running again.

These are small issues though, and I'd vote for a reference in Pasi's
tutorial as an option against compiling from source (though I'd leave
that option in place).

I would like to use this to add myoung's kernel as an option in pxdi, if
that is ok with you.

--
Digimer
E-Mail: digimer@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin: http://nodeassassin.org

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

> I would like to use this to add myoung's kernel as an option in pxdi, if that is ok with you.

What is pxdi ?

Boris.

--- On Mon, 11/29/10, Digimer <linux@alteeve.com> wrote:

From: Digimer <linux@alteeve.com>
Subject: Re: [Xen-devel] Re: [Xen-users] [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6)
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: "Pasi Kärkkäinen" <pasik@iki.fi>, xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Date: Monday, November 29, 2010, 10:50 PM

On 11/29/2010 02:40 PM, Boris Derzhavets wrote:
> Could it be considered as update for "HOWTO" ?
>
> http://bderzhavets.wordpress.com/2010/11/29/rebuild-kernel-2-6-32-26-174-xendom0-fc12-src-rpm-on-rhel-server-6/
>
> Boris.

I ran through this tonight, and I did get it working and installed, so thank you. :)

If I can make a couple suggestions?

1. Provide a downloadable patch file and and example showing how to use patch for those who might be less familiar with it.

2. After compile and install, disable the epel repo as it triggers these errors:

------------------------------------------------------------------------
[root@an-node03 x86_64]# yum update
Loaded plugins: refresh-packagekit, rhnplugin
epel                                 | 3.7 kB     00:00
epel/primary_db                      | 3.4 MB     00:07
rhel-x86_64-server-6                 | 1.8 kB     00:00
rhel-x86_64-server-6/primary         | 1.6 MB     00:03
rhel-x86_64-server-6                              3562/3562
rhel-x86_64-server-ha-6              | 1.8 kB     00:00
rhel-x86_64-server-ha-6/primary      |  13 kB     00:00
rhel-x86_64-server-ha-6                               35/35
rhel-x86_64-server-optional-6        | 1.6 kB     00:00
rhel-x86_64-server-optional-6/primary| 695 kB     00:01
rhel-x86_64-server-optional-6                     2672/2672
Setting up Update Process
Resolving Dependencies
--> Running transaction check
--> Processing Dependency: pkgconfig(augeas) >= 0.5.0 for package: netcf-devel-0.1.6-4.el6.x86_64
---> Package augeas-devel.x86_64 0:0.7.3-1.el5 set to be updated
--> Processing Dependency: augeas-libs = 0.7.2-3.el6 for package: augeas-devel-0.7.2-3.el6.i686
---> Package augeas-libs.x86_64 0:0.7.3-1.el5 set to be updated
---> Package cvs.x86_64 0:1.11.23-11.el6_0.1 set to be updated
---> Package fontpackages-filesystem.noarch 0:1.44-1.el5.1 set to be updated
---> Package iwl6000-firmware.noarch 0:9.193.4.1-1.el5 set to be updated
---> Package libldb.x86_64 0:0.9.10-25.el5 set to be updated
---> Package libtalloc.x86_64 0:2.0.1-7.el5 set to be updated
---> Package libtdb.x86_64 0:1.2.1-4.el5 set to be updated
---> Package python-nose.noarch 0:0.11.3-2.el5 set to be updated
--> Processing Dependency: python(abi) = 2.4 for package: python-nose-0.11.3-2.el5.noarch
---> Package python-paramiko.noarch 0:1.7.6-1.el5 set to be updated
--> Processing Dependency: python(abi) = 2.4 for package: python-paramiko-1.7.6-1.el5.noarch
---> Package xorg-x11-drv-qxl.x86_64 0:0.0.12-2.1.el6_0.1 set to be updated
--> Running transaction check
---> Package augeas-devel.i686 0:0.7.2-3.el6 set to be updated
---> Package augeas-libs.i686 0:0.7.2-3.el6 set to be updated
--> Processing Dependency: libselinux.so.1 for package: augeas-libs-0.7.2-3.el6.i686
---> Package python-nose.noarch 0:0.11.3-2.el5 set to be updated
--> Processing Dependency: python(abi) = 2.4 for package: python-nose-0.11.3-2.el5.noarch
---> Package python-paramiko.noarch 0:1.7.6-1.el5 set to be updated
--> Processing Dependency: python(abi) = 2.4 for package: python-paramiko-1.7.6-1.el5.noarch
--> Running transaction check
---> Package libselinux.i686 0:2.0.94-2.el6 set to be updated
---> Package python-nose.noarch 0:0.11.3-2.el5 set to be updated
--> Processing Dependency: python(abi) = 2.4 for package: python-nose-0.11.3-2.el5.noarch
---> Package python-paramiko.noarch 0:1.7.6-1.el5 set to be updated
--> Processing Dependency: python(abi) = 2.4 for package: python-paramiko-1.7.6-1.el5.noarch
--> Finished Dependency Resolution
Error: Package: python-nose-0.11.3-2.el5.noarch (epel)
           Requires: python(abi) = 2.4
           Installed: python-2.6.5-3.el6.x86_64 (@Red Hat Enterprise Linux/6.0)
               python(abi) = 2.6
           Available: python26-2.6.5-5.el5.x86_64 (epel)
               python(abi) = 2.6
Error: Package: python-paramiko-1.7.6-1.el5.noarch (epel)
           Requires: python(abi) = 2.4
           Installed: python-2.6.5-3.el6.x86_64 (@Red Hat Enterprise Linux/6.0)
               python(abi) = 2.6
           Available: python26-2.6.5-5.el5.x86_64 (epel)
               python(abi) = 2.6
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
------------------------------------------------------------------------

I had to change /etc/yum.repos.d/epel.repo to 'enabled=0' and then run 'yum clean all && yum update' to get yum running again.

These are small issues though, and I'd vote for a reference in Pasi's tutorial as an option against compiling from source (though I'd leave that option in place).

I would like to use this to add myoung's kernel as an option in pxdi, if that is ok with you.

-- Digimer
E-Mail: digimer@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org

On 11/30/2010 01:04 AM, Boris Derzhavets wrote:
> > I would like to use this to add myoung's kernel as an option in pxdi,
> if that is ok with you.
>
> What is pxdi ?
>
> Boris.

A script I wrote to automate Pasi's tutorial.

http://wiki.alteeve.com/index.php/Pxdi

--
Digimer
E-Mail: digimer@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin: http://nodeassassin.org

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

Sure,  I don't mind.

Boris.

--- On Tue, 11/30/10, Digimer <linux@alteeve.com> wrote:

From: Digimer <linux@alteeve.com>
Subject: Re: [Xen-devel] Re: [Xen-users] [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6)
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com, "Pasi Kärkkäinen" <pasik@iki.fi>
Date: Tuesday, November 30, 2010, 9:43 AM

On 11/30/2010 01:04 AM, Boris Derzhavets wrote:
>  > I would like to use this to add myoung's kernel as an option in pxdi,
> if that is ok with you.
>
> What is pxdi ?
>
> Boris.

A script I wrote to automate Pasi's tutorial.

http://wiki.alteeve.com/index.php/Pxdi

--
Digimer
E-Mail: digimer@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org

On 11/30/2010 09:45 AM, Boris Derzhavets wrote:
> Sure, I don't mind.
>
> Boris.

Thanks, I will work on adding it in the next day or two. Thanks again
for the .spec trick!

--
Digimer
E-Mail: digimer@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin: http://nodeassassin.org

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

On Mon, Nov 29, 2010 at 11:40:35AM -0800, Boris Derzhavets wrote:
> Could it be considered as update for "HOWTO" ?
>
> http://bderzhavets.wordpress.com/2010/11/29/rebuild-kernel-2-6-32-26-174-xendom0-fc12-src-rpm-on-rhel-server-6/
>

I just added the link to your tutorial! Thanks.

-- Pasi


> Boris.
>
> --- On Thu, 11/18/10, Pasi Kärkkäinen <pasik@iki.fi> wrote:
>
> From: Pasi Kärkkäinen <pasik@iki.fi>
> Subject: [Xen-devel] Re: [Xen-users] [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6
> (RHEL6)
> To: "Digimer" <linux@alteeve.com>
> Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
> 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: [1]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
> [2]Xen-devel@lists.xensource.com
> [3]http://lists.xensource.com/xen-devel
>
> References
>
> Visible links
> 1. http://wiki.xen.org/xenwiki/RHEL6Xen4Tutorial
> 2. file:///mc/compose?to=Xen-devel@lists.xensource.com
> 3. http://lists.xensource.com/xen-devel

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

-------------------------------------------
RPMS setup with no hackery
-------------------------------------------
# rpmbuild -bb -with firmware kernel.spec ( original version)

All required rpms get built .

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
Marking kernel-2.6.32.26-174.xendom0.el6.x86_64.rpm as an update to kernel-2.6.32-71.7.1.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
Marking kernel-devel-2.6.32.26-174.xendom0.el6.x86_64.rpm as an update to kernel-devel-2.6.32-71.7.1.el6.x86_64
Examining kernel-firmware-2.6.32.26-174.xendom0.el6.x86_64.rpm: kernel-firmware-2.6.32.26-174.xendom0.el6.x86_64
Marking kernel-firmware-2.6.32.26-174.xendom0.el6.x86_64.rpm to be installed
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.7.1.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-firmware.x86_64 0:2.6.32.26-174.xendom0.el6 set to be updated
---> 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
 kernel-firmware    x86_64 2.6.32.26-174.xendom0.el6  /kernel-firmware-2.6.32.26-174.xendom0.el6.x86_64    2.2 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       5 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-debuginfo-common-x86_64-2.6.32.26-174.xendom0.el6.x86_64                           1/7
  Installing     : kernel-firmware-2.6.32.26-174.xendom0.el6.x86_64                                          2/7
  Installing     : kernel-debuginfo-2.6.32.26-174.xendom0.el6.x86_64                                         3/7
  Updating       : kernel-headers-2.6.32.26-174.xendom0.el6.x86_64                                           4/7
  Installing     : kernel-devel-2.6.32.26-174.xendom0.el6.x86_64                                             5/7
  Installing     : kernel-2.6.32.26-174.xendom0.el6.x86_64                                                   6/7
  Cleanup        : kernel-headers-2.6.32-71.7.1.el6.x86_64                                                   7/7

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                                                               
  kernel-firmware.x86_64 0:2.6.32.26-174.xendom0.el6                                                            

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

Complete!


Boris.

--- On Mon, 11/29/10, Digimer <linux@alteeve.com> wrote:

From: Digimer <linux@alteeve.com>
Subject: Re: [Xen-devel] Re: [Xen-users] [HOWTO] Running Xen 4.0 host (dom0) with Redhat Enterprise Linux 6 (RHEL6)
To: "Boris Derzhavets" <bderzhavets@yahoo.com>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Date: Monday, November 29, 2010, 10:50 PM

On 11/29/2010 02:40 PM, Boris Derzhavets wrote:
> Could it be considered as update for "HOWTO" ?
>
> http://bderzhavets.wordpress.com/2010/11/29/rebuild-kernel-2-6-32-26-174-xendom0-fc12-src-rpm-on-rhel-server-6/
>
> Boris.

I ran through this tonight, and I did get it working and installed, so thank you. :)

If I can make a couple suggestions?

1. Provide a downloadable patch file and and example showing how to use patch for those who might be less familiar with it.

2. After compile and install, disable the epel repo as it triggers these errors:

------------------------------------------------------------------------
[root@an-node03 x86_64]# yum update
Loaded plugins: refresh-packagekit, rhnplugin
epel                                 | 3.7 kB     00:00
epel/primary_db                      | 3.4 MB     00:07
rhel-x86_64-server-6                 | 1.8 kB     00:00
rhel-x86_64-server-6/primary         | 1.6 MB     00:03
rhel-x86_64-server-6                              3562/3562
rhel-x86_64-server-ha-6              | 1.8 kB     00:00
rhel-x86_64-server-ha-6/primary      |  13 kB     00:00
rhel-x86_64-server-ha-6                               35/35
rhel-x86_64-server-optional-6        | 1.6 kB     00:00
rhel-x86_64-server-optional-6/primary| 695 kB     00:01
rhel-x86_64-server-optional-6                     2672/2672
Setting up Update Process
Resolving Dependencies
--> Running transaction check
--> Processing Dependency: pkgconfig(augeas) >= 0.5.0 for package: netcf-devel-0.1.6-4.el6.x86_64
---> Package augeas-devel.x86_64 0:0.7.3-1.el5 set to be updated
--> Processing Dependency: augeas-libs = 0.7.2-3.el6 for package: augeas-devel-0.7.2-3.el6.i686
---> Package augeas-libs.x86_64 0:0.7.3-1.el5 set to be updated
---> Package cvs.x86_64 0:1.11.23-11.el6_0.1 set to be updated
---> Package fontpackages-filesystem.noarch 0:1.44-1.el5.1 set to be updated
---> Package iwl6000-firmware.noarch 0:9.193.4.1-1.el5 set to be updated
---> Package libldb.x86_64 0:0.9.10-25.el5 set to be updated
---> Package libtalloc.x86_64 0:2.0.1-7.el5 set to be updated
---> Package libtdb.x86_64 0:1.2.1-4.el5 set to be updated
---> Package python-nose.noarch 0:0.11.3-2.el5 set to be updated
--> Processing Dependency: python(abi) = 2.4 for package: python-nose-0.11.3-2.el5.noarch
---> Package python-paramiko.noarch 0:1.7.6-1.el5 set to be updated
--> Processing Dependency: python(abi) = 2.4 for package: python-paramiko-1.7.6-1.el5.noarch
---> Package xorg-x11-drv-qxl.x86_64 0:0.0.12-2.1.el6_0.1 set to be updated
--> Running transaction check
---> Package augeas-devel.i686 0:0.7.2-3.el6 set to be updated
---> Package augeas-libs.i686 0:0.7.2-3.el6 set to be updated
--> Processing Dependency: libselinux.so.1 for package: augeas-libs-0.7.2-3.el6.i686
---> Package python-nose.noarch 0:0.11.3-2.el5 set to be updated
--> Processing Dependency: python(abi) = 2.4 for package: python-nose-0.11.3-2.el5.noarch
---> Package python-paramiko.noarch 0:1.7.6-1.el5 set to be updated
--> Processing Dependency: python(abi) = 2.4 for package: python-paramiko-1.7.6-1.el5.noarch
--> Running transaction check
---> Package libselinux.i686 0:2.0.94-2.el6 set to be updated
---> Package python-nose.noarch 0:0.11.3-2.el5 set to be updated
--> Processing Dependency: python(abi) = 2.4 for package: python-nose-0.11.3-2.el5.noarch
---> Package python-paramiko.noarch 0:1.7.6-1.el5 set to be updated
--> Processing Dependency: python(abi) = 2.4 for package: python-paramiko-1.7.6-1.el5.noarch
--> Finished Dependency Resolution
Error: Package: python-nose-0.11.3-2.el5.noarch (epel)
           Requires: python(abi) = 2.4
           Installed: python-2.6.5-3.el6.x86_64 (@Red Hat Enterprise Linux/6.0)
               python(abi) = 2.6
           Available: python26-2.6.5-5.el5.x86_64 (epel)
               python(abi) = 2.6
Error: Package: python-paramiko-1.7.6-1.el5.noarch (epel)
           Requires: python(abi) = 2.4
           Installed: python-2.6.5-3.el6.x86_64 (@Red Hat Enterprise Linux/6.0)
               python(abi) = 2.6
           Available: python26-2.6.5-5.el5.x86_64 (epel)
               python(abi) = 2.6
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
------------------------------------------------------------------------

I had to change /etc/yum.repos.d/epel.repo to 'enabled=0' and then run 'yum clean all && yum update' to get yum running again.

These are small issues though, and I'd vote for a reference in Pasi's tutorial as an option against compiling from source (though I'd leave that option in place).

I would like to use this to add myoung's kernel as an option in pxdi, if that is ok with you.

-- Digimer
E-Mail: digimer@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org

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

Thanks Digimer for this respons.

I've booted in non xen environement. And the xencapstest PASS now

Many Thanks

Olivier

--
View this message in context: http://xen.1045712.n5.nabble.com/HOWTO-Running-Xen-4-0-host-dom0-with-Redhat-Enterprise-Linux-6-RHEL6-tp3271407p5006651.html
Sent from the Xen - Dev mailing list archive at Nabble.com.