Re: Are there source codes for Xen-IB?

[Ian Campbell <Ian.Campbell@eu.citrix.com>]

On Wed, 2011-05-25 at 14:40 +0100, maus wrote:
> Hi,
> 
> I have a project which is make KVM use InfiniBand.
> However, since Xen can use InfiniBand through Xen-IB, I want to try to
> make Xen use InfiniBand first.
> Through that way, I think it may give me some idea about how to make
> KVM use InfiniBand.
> So, as you said, I just use "Updated defconfig to include infiniband
> driver as modules for dom0/domU" to do?
> And since I don't know how to I do first for Xen-IB, is there any
> tutorial for Xen-IB?
> Or does Xen build-in support IB currently?

I'm not sure what IB support you expect Xen to have over and above the
driver and utils support, which are functions of the dom0 kernel and
distro and not the hypervisor.

Have you got IB working on a native system? I expect that if you do that
then Xen or KVM will be able to make use of it basically for free, i.e.
configure a VIF on an IP-over-IB bridge or use a local IP-over-IB
address in dom0 for migration etc etc.

Ian.

> 
> Yi-Man
> 
> 
> 
> 2011/5/24 Ian Campbell <Ian.Campbell@eu.citrix.com>
>         Please do not top post.
>         
>         On Tue, 2011-05-24 at 11:07 +0100, maus wrote:
>         > Hi,
>         >
>         > There many file in
>          http://xenbits.xensource.com/ext/xen-smartio/ ,
>         > which should I use for Xen-IB?
>         > Use the following three?
>         > Updated defconfig to include infiniband driver as modules
>         for
>         > dom0/domU
>         > Updating drivers/infiniband to latest. Should shrink size of
>         > xen_ib.patch in
>         > Add support for Infiniband into Xen
>         
>         
>         Again, these changesets are >5 years old and have not been
>         looked at or
>         maintained since -- I am very sceptical that you will find
>         anything of
>         use on a modern Xen system in there.
>         
>         I expect that IB support in the kernels we currently use for
>         dom0 is
>         vastly improved over what was available in the 2.6.16 tree
>         referenced in
>         the above repository. Perhaps you don't even need anything
>         special
>         outside of what is available in the upstream dom0 kernel.
>         
>         Perhaps if you explain what you are actually trying to achieve
>         then
>         people will be able to better advise you?
>         
>         Ian.
>         
>         
>