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