pv_ops with xen-3.3

pv_ops with xen-3.3

[jonr]

I would like to try and test out the 2.6.29-rc4 kernel and see if I
can't get Xen-3.3-1 booting. I have patched the 2.6.28 kernel and have
a 2.6.29-rc4 kernel. I have configured the kernel to use xen by
following http://wiki.xensource.com/xenwiki/XenParavirtOps.

Now I have the kernel configured and built but am not quite sure how
to use this kernel with xen-3.3. When I downloaded the latest xen and
ran 'make world' it downloaded the 2.6.18 kernel and is building xen
against that. How do I make xen build against my kernel or do I even
need to?

Once xen-3.3 is done building do I just substitute my 2.6.29-rc4
kernel in the grub menu.conf or am I missing something?

Thanks for any help,

Jon

Re: pv_ops with xen-3.3

[Mark Williamson]

Hi there Jon,

The Xen build process builds a XenLinux using patches in the Xen repository, 
which are based on 2.6.18.  This includes full support of all features under 
both dom0 and domU.

The mainline Linux kernel has included - for some time - support for running 
as a Xen domU through its pv_ops infrastructure.  This support has been 
getting full-featured and AFAIK most or all domU functions are now available 
using appropriately-built kernel.org kernels.

Support for running as dom0 requires a kernel to support additional features 
on top of the standard domU featureset.  Mainline Linux has not had these in 
any releases - and as far as I can tell the full dom0 functionality hasn't 
been merged into 2.6.29.  I could be wrong about this though, the Xen wiki 
states 2.6.29 as a merge goal; if it's not in that release I'd imagine it'd be 
in the next one.

So, in summary:

If you want to run a kernel.org kernel as a domU then any recent release will 
do.

If you want to run a kernel.org kernel as a dom0 using pv_ops dom0 support 
then you may need to seek out and apply additional patches.

If you want to get a kernel.org kernel to run on dom0 out-of-the-box then you 
may need to wait for the next release.

You need to get a dom0 kernel from somewhere, so if you're not bothered about 
using the latest-and-greatest from kernel.org you can use the one built with 
Xen.

Does that make sense?

The upstream merge of Xen functionality into kernel.org has taken years longer 
than originally anticipated, however the good news is that Jeremy Fitzhardinge 
has been doing a tremendous job of leading the effort and getting progressively 
more stuff in a state that is acceptable to the upstream community.  Hopefully 
in the future kernel.org Linux will have full out-of-the-box support for Xen 
and the 2.6.18-based fork will no longer be needed at all.

Cheers,
Mark

On Tuesday 10 February 2009 16:55:48 jonr@destar.net wrote:
> I would like to try and test out the 2.6.29-rc4 kernel and see if I
> can't get Xen-3.3-1 booting. I have patched the 2.6.28 kernel and have
> a 2.6.29-rc4 kernel. I have configured the kernel to use xen by
> following http://wiki.xensource.com/xenwiki/XenParavirtOps.
>
> Now I have the kernel configured and built but am not quite sure how
> to use this kernel with xen-3.3. When I downloaded the latest xen and
> ran 'make world' it downloaded the 2.6.18 kernel and is building xen
> against that. How do I make xen build against my kernel or do I even
> need to?
>
> Once xen-3.3 is done building do I just substitute my 2.6.29-rc4
> kernel in the grub menu.conf or am I missing something?
>
> Thanks for any help,
>
> Jon
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: pv_ops with xen-3.3

[jonr]

Thanks for the run down Mark. During the 'make menuconfig' I saw an  
option for dom0 support for the kernel, so i was under the impression  
that support was there. I was just wanting to play around with it and  
see what happens. :)

OK, this may sound stupid but I gotta ask. :)

If support for dom0 does make it into mainline kernel will there be a  
need to download xen versions any longer? Will Xen still need to be  
built against a kernel that already has support for it inside the  
kernel? If not, how would I tell what version of Xen I am using.

Like I said, that may sound stupid but had to ask.

Jon

Quoting Mark Williamson <mark.williamson@cl.cam.ac.uk>:

> Hi there Jon,
>
> The Xen build process builds a XenLinux using patches in the Xen repository,
> which are based on 2.6.18.  This includes full support of all features under
> both dom0 and domU.
>
> The mainline Linux kernel has included - for some time - support for running
> as a Xen domU through its pv_ops infrastructure.  This support has been
> getting full-featured and AFAIK most or all domU functions are now available
> using appropriately-built kernel.org kernels.
>
> Support for running as dom0 requires a kernel to support additional features
> on top of the standard domU featureset.  Mainline Linux has not had these in
> any releases - and as far as I can tell the full dom0 functionality hasn't
> been merged into 2.6.29.  I could be wrong about this though, the Xen wiki
> states 2.6.29 as a merge goal; if it's not in that release I'd   
> imagine it'd be
> in the next one.
>
> So, in summary:
>
> If you want to run a kernel.org kernel as a domU then any recent release will
> do.
>
> If you want to run a kernel.org kernel as a dom0 using pv_ops dom0 support
> then you may need to seek out and apply additional patches.
>
> If you want to get a kernel.org kernel to run on dom0 out-of-the-box then you
> may need to wait for the next release.
>
> You need to get a dom0 kernel from somewhere, so if you're not bothered about
> using the latest-and-greatest from kernel.org you can use the one built with
> Xen.
>
> Does that make sense?
>
> The upstream merge of Xen functionality into kernel.org has taken   
> years longer
> than originally anticipated, however the good news is that Jeremy   
> Fitzhardinge
> has been doing a tremendous job of leading the effort and getting   
> progressively
> more stuff in a state that is acceptable to the upstream community.   
>  Hopefully
> in the future kernel.org Linux will have full out-of-the-box support for Xen
> and the 2.6.18-based fork will no longer be needed at all.
>
> Cheers,
> Mark
>
> On Tuesday 10 February 2009 16:55:48 jonr@destar.net wrote:
>> I would like to try and test out the 2.6.29-rc4 kernel and see if I
>> can't get Xen-3.3-1 booting. I have patched the 2.6.28 kernel and have
>> a 2.6.29-rc4 kernel. I have configured the kernel to use xen by
>> following http://wiki.xensource.com/xenwiki/XenParavirtOps.
>>
>> Now I have the kernel configured and built but am not quite sure how
>> to use this kernel with xen-3.3. When I downloaded the latest xen and
>> ran 'make world' it downloaded the 2.6.18 kernel and is building xen
>> against that. How do I make xen build against my kernel or do I even
>> need to?
>>
>> Once xen-3.3 is done building do I just substitute my 2.6.29-rc4
>> kernel in the grub menu.conf or am I missing something?
>>
>> Thanks for any help,
>>
>> Jon
>>
>>
>>
>>
>> _______________________________________________
>> 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
>

Re: pv_ops with xen-3.3

[Keir Fraser]

On 10/02/2009 17:26, "jonr@destar.net" <jonr@destar.net> wrote:

> If support for dom0 does make it into mainline kernel will there be a
> need to download xen versions any longer? Will Xen still need to be
> built against a kernel that already has support for it inside the
> kernel? If not, how would I tell what version of Xen I am using.

The kernel won't contain the hypervisor itself, so you'll need to download
Xen separately. But then you'll be able to run an unpatched mainline kernel
on top of it as dom0 or domU.

 -- Keir

Re: pv_ops with xen-3.3

[jonr]

Keir, Boris and Mark,

Thanks for the responses, that signing up on the devel list was a coup! :)

Jon

Re: pv_ops with xen-3.3

[jonr]

My thank you email didn't quite express my gratitude to you three for  
replying back to my question. Thank you all for taking the time to  
spell it out for me and clear up the confusion I was running into  
yesterday as I tried to stumble along and figure this out.

I very much appreciate the time you took to help clarify things for me,

Thanks again,

Jon

Quoting jonr@destar.net:

> Keir, Boris and Mark,
>
> Thanks for the responses, that signing up on the devel list was a coup! :)
>
> Jon
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: pv_ops with xen-3.3

[Mark Williamson]

On Tuesday 10 February 2009 17:26:35 jonr@destar.net wrote:
> Thanks for the run down Mark. During the 'make menuconfig' I saw an
> option for dom0 support for the kernel, so i was under the impression
> that support was there.

Heh, well maybe it is in that case!  I just took a quite look at lwn.net's 
merge summaries for the start of the 2.6.29 cycle (when most significant merges 
usually go in) but I suppose it could either have slipped under their radar or 
gone in later.  I haven't been following the detailed progress of the dom0 
pv_ops stuff for some time now so it's entirely possible I'm wrong.

> I was just wanting to play around with it and
> see what happens. :)

If it says it supports it then I think that's worth doing ;-)

> OK, this may sound stupid but I gotta ask. :)
>
> If support for dom0 does make it into mainline kernel will there be a
> need to download xen versions any longer? Will Xen still need to be
> built against a kernel that already has support for it inside the
> kernel? If not, how would I tell what version of Xen I am using.
>
> Like I said, that may sound stupid but had to ask.

Not at all, it's a slightly complicated issue that's compounded by the fact 
that Xen and dom0 kernel versions *used* to need to be built together (that 
hasn't been the case for a while now).

Xen - the hypervisor - is it's own piece of software.  It's not built 
"against" Linux as-such - it's not like building a module, more like building 
a separate kernel.  It's self-contained.

To run a Xen-based system you need a dom0-aware kernel to control all the 
devices, etc.  This is booted initially and takes the role of the host system.  
The patches for dom0 awareness as more invasive to the kernel than the patches 
for domU functionality alone, so the domU patches got merged upstream whilst 
the dom0 patches have taken a bit longer.  In the meantime the 2.6.18 fork 
maintained alongside Xen has carried the dom0 functionality and various groups 
have forward-ported it to newer kernels for their particular distro.

There's a set of Xen tools that run in dom0's userspace, these do need to 
match the Xen version you're running AFAIK.  They poke information down into 
(and up out of) Xen using management APIs that dom0's kernel doesn't really 
care about.

Getting dom0 support upstream basically means that the Xen team shouldn't have 
to keep maintaining a fork of 2.6.18 (eventually, anyhow) to contain dom0 
functionality - you'd just build Xen + tools, build a dom0-aware kernel.org 
Linux and run with that.  This makes it easier for sysadmins and distros to 
build up-to-date dom0 kernels and reduces the amount of code the Xen team must 
maintain.

As a bonus, the pv_ops kernels are capable of booting paravirtual on Xen or 
natively on real hardware (or paravirt on VMware, or on lguest, or possibly 
KVM paravirt I think) - using the *same* kernel image.  So in future, if 
distros supply appropriately built kernels then you can run the same kernel 
build under Xen, native and anything else you want.  The pv_ops people have 
taken some care to minimise the performance hit incurred by this.

HTH,
Cheers,
Mark

> Jon
>
> Quoting Mark Williamson <mark.williamson@cl.cam.ac.uk>:
> > Hi there Jon,
> >
> > The Xen build process builds a XenLinux using patches in the Xen
> > repository, which are based on 2.6.18.  This includes full support of all
> > features under both dom0 and domU.
> >
> > The mainline Linux kernel has included - for some time - support for
> > running as a Xen domU through its pv_ops infrastructure.  This support
> > has been getting full-featured and AFAIK most or all domU functions are
> > now available using appropriately-built kernel.org kernels.
> >
> > Support for running as dom0 requires a kernel to support additional
> > features on top of the standard domU featureset.  Mainline Linux has not
> > had these in any releases - and as far as I can tell the full dom0
> > functionality hasn't been merged into 2.6.29.  I could be wrong about
> > this though, the Xen wiki states 2.6.29 as a merge goal; if it's not in
> > that release I'd
> > imagine it'd be
> > in the next one.
> >
> > So, in summary:
> >
> > If you want to run a kernel.org kernel as a domU then any recent release
> > will do.
> >
> > If you want to run a kernel.org kernel as a dom0 using pv_ops dom0
> > support then you may need to seek out and apply additional patches.
> >
> > If you want to get a kernel.org kernel to run on dom0 out-of-the-box then
> > you may need to wait for the next release.
> >
> > You need to get a dom0 kernel from somewhere, so if you're not bothered
> > about using the latest-and-greatest from kernel.org you can use the one
> > built with Xen.
> >
> > Does that make sense?
> >
> > The upstream merge of Xen functionality into kernel.org has taken
> > years longer
> > than originally anticipated, however the good news is that Jeremy
> > Fitzhardinge
> > has been doing a tremendous job of leading the effort and getting
> > progressively
> > more stuff in a state that is acceptable to the upstream community.
> >  Hopefully
> > in the future kernel.org Linux will have full out-of-the-box support for
> > Xen and the 2.6.18-based fork will no longer be needed at all.
> >
> > Cheers,
> > Mark
> >
> > On Tuesday 10 February 2009 16:55:48 jonr@destar.net wrote:
> >> I would like to try and test out the 2.6.29-rc4 kernel and see if I
> >> can't get Xen-3.3-1 booting. I have patched the 2.6.28 kernel and have
> >> a 2.6.29-rc4 kernel. I have configured the kernel to use xen by
> >> following http://wiki.xensource.com/xenwiki/XenParavirtOps.
> >>
> >> Now I have the kernel configured and built but am not quite sure how
> >> to use this kernel with xen-3.3. When I downloaded the latest xen and
> >> ran 'make world' it downloaded the 2.6.18 kernel and is building xen
> >> against that. How do I make xen build against my kernel or do I even
> >> need to?
> >>
> >> Once xen-3.3 is done building do I just substitute my 2.6.29-rc4
> >> kernel in the grub menu.conf or am I missing something?
> >>
> >> Thanks for any help,
> >>
> >> Jon
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> 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
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: pv_ops with xen-3.3

[Jeremy Fitzhardinge]

Mark Williamson wrote:
> On Tuesday 10 February 2009 17:26:35 jonr@destar.net wrote:
>   
>> Thanks for the run down Mark. During the 'make menuconfig' I saw an
>> option for dom0 support for the kernel, so i was under the impression
>> that support was there.
>>     
>
> Heh, well maybe it is in that case!  I just took a quite look at lwn.net's 
> merge summaries for the start of the 2.6.29 cycle (when most significant merges 
> usually go in) but I suppose it could either have slipped under their radar or 
> gone in later.  I haven't been following the detailed progress of the dom0 
> pv_ops stuff for some time now so it's entirely possible I'm wrong.
>   

He's patching the kernel up from the hg patch queue, so that will have 
pretty bleeding edge dom0 support in it.  I'm in the middle of migrating 
it all to git, still planning to get at least basic dom0 support into 
the next merge window.  And failing that, it should be easier for people 
to fetch a git tree than piece things together as they have to now.

    J

Re: pv_ops with xen-3.3

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 2477 bytes --]

The way it worked for me on Ubuntu Intrepid Server (x86_64)

First installed the most recent xen unstable:-

# cd /usr/src

# hg clone http://xenbits.xensource.com/xen-unstable.hg

# cd xen-unstable.hg

# make xen

# make install-xen

# make tools

# make install-tools

Compiled kernel supporting PV_OPS in Dom0 & INTEL AHCI (ICH(X)R)

# hg clone http://www.kernel.org/hg/linux-2.6

# cd linux-2.6/.hg

# hg clone http://xenbits.xensource.com/paravirt_ops/patches.hg patches

# cd ..

# ln -s .hg/patches . # for convenience

# hg update `cat patches/KERNEL_VERSION`

# hg qpush -a
# make menuconfig
# make
# make modules_install install 
# depmod 2.6.29-rc3-tip

# mkinitramfs -o /boot/initrd-2.6.29-rc3-tip.img 2.6.29-rc3-tip



Created grub entry :-



title Xen 3.4 / Ubuntu 8.10, kernel 2.6.29-tip

kernel /boot/xen-3.4.gz dom0_mem=1024M

module /boot/vmlinuz-2.6.29-rc3-tip root=/dev/sdb1 ro console=tty0 pci=nomsi

module /boot/initrd-2.6.29-rc3-tip.img

I was able to load 2.6.23-rc3 only under the most recent version of Xen Unstable Hypervisor. Xen 3.3.1 was unable to recognize kernel image:-
Printed "Not ELF format" to  console and hanged.

Details here:-

http://bderzhavets.wordpress.com/2009/02/07/attempt-of-install-xen-unstable-dom0-via-2629-rc3-pv_ops-enabled-kernel-on-intel-sataahci-box/

--- On Tue, 2/10/09, jonr@destar.net <jonr@destar.net> wrote:
From: jonr@destar.net <jonr@destar.net>
Subject: [Xen-devel] pv_ops with xen-3.3
To: xen-devel@lists.xensource.com
Date: Tuesday, February 10, 2009, 11:55 AM

I would like to try and test out the 2.6.29-rc4 kernel and see if I
can't get Xen-3.3-1 booting. I have patched the 2.6.28 kernel and have
a 2.6.29-rc4 kernel. I have configured the kernel to use xen by
following http://wiki.xensource.com/xenwiki/XenParavirtOps.

Now I have the kernel configured and built but am not quite sure how
to use this kernel with xen-3.3. When I downloaded the latest xen and
ran 'make world' it downloaded the 2.6.18 kernel and is building xen
against that. How do I make xen build against my kernel or do I even
need to?

Once xen-3.3 is done building do I just substitute my 2.6.29-rc4
kernel in the grub menu.conf or am I missing something?

Thanks for any help,

Jon




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



      

[-- Attachment #1.2: Type: text/html, Size: 2926 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: pv_ops with xen-3.3

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 3669 bytes --]

  I was able successfully installed and ran Ubuntu Intrepid Server PV DomU
and F10 PV DomU (both 64-bit) at mentioned Xen Unstable Dom0s.
One network issue came up on two boxes have been tested:-
1. C2D E8400,8 GB RAM , ASUS P5K Premium/WIFI, 2x250 GB SATA drives
2. C2D E6600,4 GB RAM, ASUS  P5B Deluxe, 2x160 GB SATA drives.
  Per "dmesg" report:-
South bridges ICH8R ,ICH9R (AHCI Bios Setup for both) have been
detected by the most recent version of 2.6.29-rc3 with no problems 
as well as SATA drives parameters. NCQ depth set to (31/32) .
  However , only Matvell Yukon 8056 was able to function as xen bridge
supporting LAN&WAN communications for Dom0.
   RTL 8110SC (first board) and RTL 8169 (plugged into second board)
failed to function as required

--- On Tue, 2/10/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] pv_ops with xen-3.3
To: xen-devel@lists.xensource.com, jonr@destar.net
Date: Tuesday, February 10, 2009, 12:52 PM

The way it worked for me on Ubuntu Intrepid Server (x86_64)

First installed the most recent xen unstable:-

# cd /usr/src

# hg clone http://xenbits.xensource.com/xen-unstable.hg

# cd xen-unstable.hg

# make xen

# make install-xen

# make tools

# make install-tools

Compiled kernel supporting PV_OPS in Dom0 & INTEL AHCI (ICH(X)R)

# hg clone http://www.kernel.org/hg/linux-2.6

# cd linux-2.6/.hg

# hg clone http://xenbits.xensource.com/paravirt_ops/patches.hg patches

# cd ..

# ln -s .hg/patches . # for convenience

# hg update `cat patches/KERNEL_VERSION`

# hg qpush -a
# make menuconfig
# make
# make modules_install install 
# depmod 2.6.29-rc3-tip

# mkinitramfs -o /boot/initrd-2.6.29-rc3-tip.img 2.6.29-rc3-tip



Created grub entry :-



title Xen 3.4 / Ubuntu 8.10, kernel 2.6.29-tip

kernel /boot/xen-3.4.gz dom0_mem=1024M

module /boot/vmlinuz-2.6.29-rc3-tip root=/dev/sdb1 ro console=tty0 pci=nomsi

module /boot/initrd-2.6.29-rc3-tip.img

I was able to load 2.6.23-rc3 only under the most recent version of Xen Unstable Hypervisor. Xen 3.3.1 was unable to recognize kernel image:-
Printed "Not ELF format" to  console and hanged.

Details here:-

http://bderzhavets.wordpress.com/2009/02/07/attempt-of-install-xen-unstable-dom0-via-2629-rc3-pv_ops-enabled-kernel-on-intel-sataahci-box/

--- On Tue, 2/10/09, jonr@destar.net <jonr@destar.net> wrote:
From: jonr@destar.net <jonr@destar.net>
Subject: [Xen-devel] pv_ops with xen-3.3
To: xen-devel@lists.xensource.com
Date: Tuesday, February 10, 2009, 11:55 AM

I would like to try and test out the 2.6.29-rc4 kernel and see if I
can't get Xen-3.3-1 booting. I have patched the 2.6.28 kernel and have
a 2.6.29-rc4 kernel. I have
 configured the kernel to use xen by
following http://wiki.xensource.com/xenwiki/XenParavirtOps.

Now I have the kernel configured and built but am not quite sure how
to use this kernel with xen-3.3. When I downloaded the latest xen and
ran 'make world' it downloaded the 2.6.18 kernel and is building xen
against that. How do I make xen build against my kernel or do I even
need to?

Once xen-3.3 is done building do I just substitute my 2.6.29-rc4
kernel in the grub menu.conf or am I missing something?

Thanks for any help,

Jon




_______________________________________________
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



      

[-- Attachment #1.2: Type: text/html, Size: 4700 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Install OpenSuse 11.1 PV DomU via VFB at Xen Unstable Dom0 (2.6.29-rc3)

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 4408 bytes --]

OpenSuse 11.1 PV DomU has been also successfully tested ( utilizing VFB for installation and runtime profile)  at Xen Unstable Dom0 (2.6.29-rc3).
Extracting phase for for Suse's images is noticeably slow versus same
install running at Xen 3.3.1 CentOS 5.2 Dom0 ( same hardware just
multibooting several Xen Dom0) 

--- On Tue, 2/10/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] pv_ops with xen-3.3
To: xen-devel@lists.xensource.com, jonr@destar.net
Date: Tuesday, February 10, 2009, 1:18 PM

  I was able successfully installed and ran Ubuntu Intrepid Server PV DomU
and F10 PV DomU (both 64-bit) at mentioned Xen Unstable Dom0s.
One network issue came up on two boxes have been tested:-
1. C2D E8400,8 GB RAM , ASUS P5K Premium/WIFI, 2x250 GB SATA drives
2. C2D E6600,4 GB RAM, ASUS  P5B Deluxe, 2x160 GB SATA drives.
  Per "dmesg" report:-
South bridges ICH8R ,ICH9R (AHCI Bios Setup for both) have been
detected by the most recent version of 2.6.29-rc3 with no problems 
as well as SATA drives parameters. NCQ depth set to (31/32) .
  However , only Matvell Yukon 8056 was able to function as xen bridge
supporting LAN&WAN communications for Dom0.
   RTL 8110SC (first board) and RTL 8169 (plugged into second board)
failed to function as required

--- On Tue, 2/10/09, Boris
 Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] pv_ops with xen-3.3
To: xen-devel@lists.xensource.com, jonr@destar.net
Date: Tuesday, February 10, 2009, 12:52 PM

The way it worked for me on Ubuntu Intrepid Server (x86_64)

First installed the most recent xen unstable:-

# cd /usr/src

# hg clone http://xenbits.xensource.com/xen-unstable.hg

# cd xen-unstable.hg

# make xen

# make install-xen

# make tools

# make install-tools

Compiled kernel supporting PV_OPS in Dom0 & INTEL AHCI (ICH(X)R)

# hg clone http://www.kernel.org/hg/linux-2.6

# cd linux-2.6/.hg

# hg clone http://xenbits.xensource.com/paravirt_ops/patches.hg patches

# cd ..

# ln -s .hg/patches . # for convenience

# hg update `cat patches/KERNEL_VERSION`

# hg qpush -a
# make menuconfig
# make
# make modules_install install 
# depmod 2.6.29-rc3-tip

# mkinitramfs -o /boot/initrd-2.6.29-rc3-tip.img 2.6.29-rc3-tip



Created grub entry :-



title Xen 3.4 / Ubuntu 8.10, kernel 2.6.29-tip

kernel /boot/xen-3.4.gz dom0_mem=1024M

module /boot/vmlinuz-2.6.29-rc3-tip root=/dev/sdb1 ro console=tty0 pci=nomsi

module /boot/initrd-2.6.29-rc3-tip.img

I was able to load 2.6.23-rc3 only under the most recent version of Xen Unstable Hypervisor. Xen 3.3.1 was unable to recognize kernel image:-
Printed "Not ELF format" to  console and hanged.

Details here:-

http://bderzhavets.wordpress.com/2009/02/07/attempt-of-install-xen-unstable-dom0-via-2629-rc3-pv_ops-enabled-kernel-on-intel-sataahci-box/

--- On Tue, 2/10/09, jonr@destar.net <jonr@destar.net> wrote:
From: jonr@destar.net <jonr@destar.net>
Subject: [Xen-devel] pv_ops with xen-3.3
To: xen-devel@lists.xensource.com
Date: Tuesday, February 10, 2009, 11:55 AM

I would like to try and test out the 2.6.29-rc4 kernel and see if I
can't get Xen-3.3-1 booting. I have patched the 2.6.28 kernel and have
a 2.6.29-rc4 kernel. I
 have
 configured the kernel to use xen by
following http://wiki.xensource.com/xenwiki/XenParavirtOps.

Now I have the kernel configured and built but am not quite sure how
to use this kernel with xen-3.3. When I downloaded the latest xen and
ran 'make world' it downloaded the 2.6.18 kernel and is building xen
against that. How do I make xen build against my kernel or do I even
need to?

Once xen-3.3 is done building do I just substitute my 2.6.29-rc4
kernel in the grub menu.conf or am I missing something?

Thanks for any help,

Jon




_______________________________________________
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



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



      

[-- Attachment #1.2: Type: text/html, Size: 5947 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: pv_ops with xen-3.3

[jonr]

Quoting Boris Derzhavets <bderzhavets@yahoo.com>:

> Compiled kernel supporting PV_OPS in Dom0 & INTEL AHCI (ICH(X)R)
>
> # hg clone http://www.kernel.org/hg/linux-2.6
>
> # cd linux-2.6/.hg
>
> # hg clone http://xenbits.xensource.com/paravirt_ops/patches.hg patches
>
> # cd ..
>
> # ln -s .hg/patches . # for convenience
>
> # hg update `cat patches/KERNEL_VERSION`
>
> # hg qpush -a

This last command does not work, is it supposed to be just 'hg push  
-a'? I had the same issue yesterday, when I issue that command I get  
what I pasted below, just showing basic commands.

root@null:/usr/src/xen-unstable.hg/linux-2.6# hg qpush -a
hg: unknown command 'qpush'
Mercurial Distributed SCM

basic commands:

  add        add the specified files on the next commit
  annotate   show changeset information per file line
  clone      make a copy of an existing repository
  commit     commit the specified files or all outstanding changes
  diff       diff repository (or selected files)
  export     dump the header and diffs for one or more changesets
  init       create a new repository in the given directory
  log        show revision history of entire repository or files
  merge      merge working directory with another revision
  parents    show the parents of the working dir or revision
  pull       pull changes from the specified source
  push       push changes to the specified destination
  remove     remove the specified files on the next commit
  serve      export the repository via HTTP
  status     show changed files in the working directory
  update     update working directory

use "hg help" for the full list of commands or "hg -v" for details

Re: pv_ops with xen-3.3

[Mark Williamson]

qpush is from the Mercurial Queues (mq) extension.  You need to install / 
enable that to get it to work.

qpush is a very different command to push - qpush actually means "Apply patches 
to the stack", qpush -a meaning "Apply all the patches to the stack".

Cheers,
Mark

On Tuesday 10 February 2009 21:01:28 jonr@destar.net wrote:
> Quoting Boris Derzhavets <bderzhavets@yahoo.com>:
> > Compiled kernel supporting PV_OPS in Dom0 & INTEL AHCI (ICH(X)R)
> >
> > # hg clone http://www.kernel.org/hg/linux-2.6
> >
> > # cd linux-2.6/.hg
> >
> > # hg clone http://xenbits.xensource.com/paravirt_ops/patches.hg patches
> >
> > # cd ..
> >
> > # ln -s .hg/patches . # for convenience
> >
> > # hg update `cat patches/KERNEL_VERSION`
> >
> > # hg qpush -a
>
> This last command does not work, is it supposed to be just 'hg push
> -a'? I had the same issue yesterday, when I issue that command I get
> what I pasted below, just showing basic commands.
>
> root@null:/usr/src/xen-unstable.hg/linux-2.6# hg qpush -a
> hg: unknown command 'qpush'
> Mercurial Distributed SCM
>
> basic commands:
>
>   add        add the specified files on the next commit
>   annotate   show changeset information per file line
>   clone      make a copy of an existing repository
>   commit     commit the specified files or all outstanding changes
>   diff       diff repository (or selected files)
>   export     dump the header and diffs for one or more changesets
>   init       create a new repository in the given directory
>   log        show revision history of entire repository or files
>   merge      merge working directory with another revision
>   parents    show the parents of the working dir or revision
>   pull       pull changes from the specified source
>   push       push changes to the specified destination
>   remove     remove the specified files on the next commit
>   serve      export the repository via HTTP
>   status     show changed files in the working directory
>   update     update working directory
>
> use "hg help" for the full list of commands or "hg -v" for details
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: pv_ops with xen-3.3

[jonr]

Quoting Mark Williamson <mark.williamson@cl.cam.ac.uk>:

> qpush is from the Mercurial Queues (mq) extension.  You need to install /
> enable that to get it to work.
>
> qpush is a very different command to push - qpush actually means   
> "Apply patches
> to the stack", qpush -a meaning "Apply all the patches to the stack".
>
> Cheers,
> Mark
That did the trick, thanks again Mark!

Re: pv_ops with xen-3.3

[Boris Derzhavets]

[-- Attachment #1.1: Type: text/plain, Size: 2909 bytes --]

http://wiki.xensource.com/xenwiki/XenParavirtOps
 
apt-get install mercurial +
 
(You may need to add this to your ~/.hgrc file: 
[extensions]
hgext.mq=
) 


--- On Tue, 2/10/09, Mark Williamson <mark.williamson@cl.cam.ac.uk> wrote:

From: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Subject: Re: [Xen-devel] pv_ops with xen-3.3
To: xen-devel@lists.xensource.com
Cc: jonr@destar.net
Date: Tuesday, February 10, 2009, 4:09 PM

qpush is from the Mercurial Queues (mq) extension.  You need to install / 
enable that to get it to work.

qpush is a very different command to push - qpush actually means "Apply
patches 
to the stack", qpush -a meaning "Apply all the patches to the
stack".

Cheers,
Mark

On Tuesday 10 February 2009 21:01:28 jonr@destar.net wrote:
> Quoting Boris Derzhavets <bderzhavets@yahoo.com>:
> > Compiled kernel supporting PV_OPS in Dom0 & INTEL AHCI (ICH(X)R)
> >
> > # hg clone http://www.kernel.org/hg/linux-2.6
> >
> > # cd linux-2.6/.hg
> >
> > # hg clone http://xenbits.xensource.com/paravirt_ops/patches.hg
patches
> >
> > # cd ..
> >
> > # ln -s .hg/patches . # for convenience
> >
> > # hg update `cat patches/KERNEL_VERSION`
> >
> > # hg qpush -a
>
> This last command does not work, is it supposed to be just 'hg push
> -a'? I had the same issue yesterday, when I issue that command I get
> what I pasted below, just showing basic commands.
>
> root@null:/usr/src/xen-unstable.hg/linux-2.6# hg qpush -a
> hg: unknown command 'qpush'
> Mercurial Distributed SCM
>
> basic commands:
>
>   add        add the specified files on the next commit
>   annotate   show changeset information per file line
>   clone      make a copy of an existing repository
>   commit     commit the specified files or all outstanding changes
>   diff       diff repository (or selected files)
>   export     dump the header and diffs for one or more changesets
>   init       create a new repository in the given directory
>   log        show revision history of entire repository or files
>   merge      merge working directory with another revision
>   parents    show the parents of the working dir or revision
>   pull       pull changes from the specified source
>   push       push changes to the specified destination
>   remove     remove the specified files on the next commit
>   serve      export the repository via HTTP
>   status     show changed files in the working directory
>   update     update working directory
>
> use "hg help" for the full list of commands or "hg -v"
for details
>
>
>
>
> _______________________________________________
> 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



      

[-- Attachment #1.2: Type: text/html, Size: 3779 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: pv_ops with xen-3.3

[jonr]

Quoting Boris Derzhavets <bderzhavets@yahoo.com>:

> http://wiki.xensource.com/xenwiki/XenParavirtOps
>  
> apt-get install mercurial +
>  
> (You may need to add this to your ~/.hgrc file:
> [extensions]
> hgext.mq=
> )

Thanks Boris,

  I am working with a source only machine so I don't have apt or yum  
or smart or any of the tools that would make this a lot easier. I had  
to install 'quilt' and link that to my /usr/lib/python2.5/ directory  
and add the .hgrc file for my user. After that, everything is moving  
along smoothly. I am building the kernel now.

Jon

Re: pv_ops with xen-3.3

[Jeremy Fitzhardinge]

jonr@destar.net wrote:
> Quoting Boris Derzhavets <bderzhavets@yahoo.com>:
>
>> Compiled kernel supporting PV_OPS in Dom0 & INTEL AHCI (ICH(X)R)
>>
>> # hg clone http://www.kernel.org/hg/linux-2.6
>>
>> # cd linux-2.6/.hg
>>
>> # hg clone http://xenbits.xensource.com/paravirt_ops/patches.hg patches
>>
>> # cd ..
>>
>> # ln -s .hg/patches . # for convenience
>>
>> # hg update `cat patches/KERNEL_VERSION`
>>
>> # hg qpush -a
>
> This last command does not work, is it supposed to be just 'hg push 
> -a'? I had the same issue yesterday, when I issue that command I get 
> what I pasted below, just showing basic commands.

You need to enable the "mq" extension.  It comes with mercurial, so its 
just a matter of creating ~/.hgrc with:

[extensions]
hgext.mq=


    J