Xen users - Feb 2006 - Xen 3.0 and Gentoo: basic network issues

Hi all
  I just joined the mailing list becuase I''ve run into a problem that
I''ve
found absolutely no solution for and that no one else seems to have ever had
either. I''m running Gentoo with a 2.6.15 kernel on an IBM x306 and I
installed Xen 3.0 from the portage tree.
  Now I was able to configure and compile a dom0 and domU kernel, boot into
Xen using the dom0 kernel and start a vm using the domU kernel.
  My issue is that I have no network connection whatsoever. I have two
ethernet ports built into the server that are Intel pro/1000 Gigabit ports.
When I boot to the normal Gentoo kernel, they both work fine I can set IP
addresses and get a connection, I can run dhcp and get a connection, etc.
However, under the Xen kernel, they refuse to work. Now I''ve tried
disabling
starting xend on startup just to see before any bridging and virtual
interface stuff got set if the ports work, but they still don''t.
I''ve also
tried just about anything else that might even be remotely related.
  I''m not sure what kind of outputs would be helpful in solving this
problem, so just let me know what kind of information is needed and
I''ll
post it up as soon as I get a chance.

  Thanks in advance for any assistance.


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

Em Ter, 2006-02-07 às 10:45 -0500, Nathan Tibbetts
escreveu:
>   My issue is that I have no network connection whatsoever. I have two
> ethernet ports built into the server that are Intel pro/1000 Gigabit
> ports. When I boot to the normal Gentoo kernel, they both work fine I
> can set IP addresses and get a connection, I can run dhcp and get a
> connection, etc. However, under the Xen kernel, they refuse to work.
> Now I''ve tried disabling starting xend on startup just to see
before
> any bridging and virtual interface stuff got set if the ports work,
> but they still don''t. I''ve also tried just about anything
else that
> might even be remotely related.
Hi,

I''m getting the same error at one of my servers running Xen-3.0.

I resolved this issue erasing the machine bios by jumper. I know it''s
weird but did worke for me.

I hope that when I upgrade to Xen-3.0.1 this doesn''t happen more.

--
 
Lucas de Souza Santos - 7F8050A6 @ http://subkeys.pgp.net


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

On Tuesday 07 February 2006 16:45, Nathan Tibbetts
wrote:
> Hi all
>   I just joined the mailing list becuase I''ve run into a problem
that I''ve
> found absolutely no solution for and that no one else seems to have ever
> had either. I''m running Gentoo with a 2.6.15 kernel on an IBM x306
and I
> installed Xen 3.0 from the portage tree.
>   Now I was able to configure and compile a dom0 and domU kernel, boot into
> Xen using the dom0 kernel and start a vm using the domU kernel.
>   My issue is that I have no network connection whatsoever. I have two
> ethernet ports built into the server that are Intel pro/1000 Gigabit ports.
> When I boot to the normal Gentoo kernel, they both work fine I can set IP
> addresses and get a connection, I can run dhcp and get a connection, etc.
> However, under the Xen kernel, they refuse to work. Now I''ve tried
> disabling starting xend on startup just to see before any bridging and
> virtual interface stuff got set if the ports work, but they still
don''t.
> I''ve also tried just about anything else that might even be
remotely
> related. I''m not sure what kind of outputs would be helpful in
solving this
> problem, so just let me know what kind of information is needed and
I''ll
> post it up as soon as I get a chance.
>
>   Thanks in advance for any assistance.
Obvious things first:
does your xen0 kernel have the network drivers for eepro1000, as module or 
statically?

do they show up in "ifconfig -a", "lsmod",
"lspci"?

also, you''ll most likely need to set RC_NET_STRICT_CHECKING to
"lo" or "no"
in /etc/conf.d/rc, otherwise /etc/init.d/xend start might deadlock.

/Ernst

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

The appropriate e1000 drivers are comiled into the kernel, not as modules.
Also they do show up under ifconfig and lspci, and of course the drivers
wouldn''t show up under lsmod since I compiled them into the kernel. And
RC_NET_STRICT_CHECKING is already set to "no" in my /etc/conf.d/rc
file.
  I''m able to manipulate the ethernet ports as far as giving them IP
addresses and such, it''s just that when I try even just a simple
connection
between two computers and manually set both IP addresses, I can''t make
any
kind of connection, as far as Xen is concerned nobody is at the other end.

I''ll have to try reseting the BIOS as suggested, though I
don''t see how
that''ll work since the ports work perfectly fine when I reboot into
Gentoo

Thanks for the responses so far


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

Hi
>   The appropriate e1000 drivers are comiled into the kernel, not as 
> modules. Also they do show up under ifconfig and lspci, and of course 
> the drivers wouldn''t show up under lsmod since I compiled them
into
> the kernel. And RC_NET_STRICT_CHECKING is already set to "no" in
my
> /etc/conf.d/rc file.
>   I''m able to manipulate the ethernet ports as far as giving them
IP
> addresses and such, it''s just that when I try even just a simple 
> connection between two computers and manually set both IP addresses, I 
> can''t make any kind of connection, as far as Xen is concerned
nobody
> is at the other end.

I found the Howto was a bit iffy here.  The howto suggests not starting 
/etc/init.d/net.eth0 - however, when I start /etc/init.d/xend then 
although the xen networking stuff comes up, no eth0 comes up... I am not 
clear if it was supposed to or not, but having both /etc/init.d/eth0 
starting as well seems to give me eth0 back again and ability to talk to 
the Dom0 again...  Can anyone please clarify whether xend is supposed to 
bring up eth0 on it''s own please?

Also note that RC_NET_STRICT_CHECKING defaults to "no", but you need
to
set it to "lo" - re-read the previous post!  The reason seems to be
that
otherwise xend comes up before net.lo which causes problems...

Finally, I have a Dom0 kernel running, but my DomU is failing to come up 
every time with random errors.  Would you please be kind enough to send 
me (offlist) your .config files for both of your kernels?  I suspect 
that perhaps I have some missing bit of hardware...  The only other 
thing is that I compiled both kernels with a hardened gcc and possibly 
that is causing problems...

Ed W

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