Xen users - Sep 2009 - network (bridged) problem when using xen 3.4.x

Hello,

I''m running xen 3.4.1 with debian dom0 kernel 2.6.26-2-686 on debian
lenny.
With this configuration I don''t get a network connection to the
machine.
When running the normal debian kernel there isn''t such a problem.

The machine has two onboard intel gigabit interfaces which require the
e1000e driver.
I got the driver source from intel and compiled it (under both kernels). As
I already said,
it runs perfectly with the normal debian kernel. When running xen, it seems
as if the driver loads correctly
but there is no link detected.
The only error message I get is something like "--physdev-out is not
supported anymore" from iptables.
Everything, except that there is no link, is normal.

Has anyone experienced a similar problems? I can give more information
regarding my setup if its necessary.
Any help would be nice, because I''m kind of stuck.

Greetings
Leo



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

hi leo,
unfortunately seems to be a problem between debian lenny and xen .. i spent
two weeks to configure them in the properly way.
cpuld you post here your config file and the error .. i will try to help you

Mirco

2009/9/15 Leo Krüger <leo.krueger@tu-harburg.de>
> Hello,
>
> I''m running xen 3.4.1 with debian dom0 kernel 2.6.26-2-686 on
debian lenny.
> With this configuration I don''t get a network connection to the
machine.
> When running the normal debian kernel there isn''t such a problem.
>
> The machine has two onboard intel gigabit interfaces which require the
> e1000e driver.
> I got the driver source from intel and compiled it (under both kernels). As
> I already said,
> it runs perfectly with the normal debian kernel. When running xen, it seems
> as if the driver loads correctly
> but there is no link detected.
> The only error message I get is something like "--physdev-out is not
> supported anymore" from iptables.
> Everything, except that there is no link, is normal.
>
> Has anyone experienced a similar problems? I can give more information
> regarding my setup if its necessary.
> Any help would be nice, because I''m kind of stuck.
>
> Greetings
> Leo
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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

There finally is a solution:

Debian 2.6.26-2 xen kernel has some issues regarding msi(-x) interrupts and
xen 3.4.x.
When the kernel is booted with pci=nomsi the network connection works.


Thanks for your help mirco.

Does anyone know if there are great disadvantages in using legacy instead of
msi interrupts?

Greetings

Von: Mirco Santori [mailto:mirco.santori@gmail.com] 
Gesendet: Mittwoch, 16. September 2009 09:52
An: Leo Krüger
Cc: xen-users@lists.xensource.com
Betreff: Re: [Xen-users] network (bridged) problem when using xen 3.4.x

hi leo,

unfortunately seems to be a problem between debian lenny and xen .. i spent
two weeks to configure them in the properly way.
cpuld you post here your config file and the error .. i will try to help you

Mirco
2009/9/15 Leo Krüger <leo.krueger@tu-harburg.de>
Hello,

I''m running xen 3.4.1 with debian dom0 kernel 2.6.26-2-686 on debian
lenny.
With this configuration I don''t get a network connection to the
machine.
When running the normal debian kernel there isn''t such a problem.

The machine has two onboard intel gigabit interfaces which require the
e1000e driver.
I got the driver source from intel and compiled it (under both kernels). As
I already said,
it runs perfectly with the normal debian kernel. When running xen, it seems
as if the driver loads correctly
but there is no link detected.
The only error message I get is something like "--physdev-out is not
supported anymore" from iptables.
Everything, except that there is no link, is normal.

Has anyone experienced a similar problems? I can give more information
regarding my setup if its necessary.
Any help would be nice, because I''m kind of stuck.

Greetings
Leo



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



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

i didnt do anything :)
anyway .. nice to know about pci=nomsi

cheers

Mirco

2009/9/16 Leo Krüger <leo.krueger@tu-harburg.de>
> There finally is a solution:
>
> Debian 2.6.26-2 xen kernel has some issues regarding msi(-x) interrupts and
> xen 3.4.x.
> When the kernel is booted with pci=nomsi the network connection works.
>
>
> Thanks for your help mirco.
>
> Does anyone know if there are great disadvantages in using legacy instead
> of
> msi interrupts?
>
> Greetings
>
> Von: Mirco Santori [mailto:mirco.santori@gmail.com]
> Gesendet: Mittwoch, 16. September 2009 09:52
> An: Leo Krüger
> Cc: xen-users@lists.xensource.com
> Betreff: Re: [Xen-users] network (bridged) problem when using xen 3.4.x
>
> hi leo,
>
> unfortunately seems to be a problem between debian lenny and xen .. i spent
> two weeks to configure them in the properly way.
> cpuld you post here your config file and the error .. i will try to help
> you
>
> Mirco
> 2009/9/15 Leo Krüger <leo.krueger@tu-harburg.de>
> Hello,
>
> I''m running xen 3.4.1 with debian dom0 kernel 2.6.26-2-686 on
debian lenny.
> With this configuration I don''t get a network connection to the
machine.
> When running the normal debian kernel there isn''t such a problem.
>
> The machine has two onboard intel gigabit interfaces which require the
> e1000e driver.
> I got the driver source from intel and compiled it (under both kernels). As
> I already said,
> it runs perfectly with the normal debian kernel. When running xen, it seems
> as if the driver loads correctly
> but there is no link detected.
> The only error message I get is something like "--physdev-out is not
> supported anymore" from iptables.
> Everything, except that there is no link, is normal.
>
> Has anyone experienced a similar problems? I can give more information
> regarding my setup if its necessary.
> Any help would be nice, because I''m kind of stuck.
>
> Greetings
> Leo
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

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