Hello, For the past year I have been trying to debug a problem with my Xen setup that involves a passthrough PCI card. If there was too much network traffic (where too much, could be around 5 Mbps) the network would freeze and I would loose all my connectivity. Initially I had the dom0 on Ubuntu 8.04 and things were terrible then. If I reached this state, the OS would have something in Ininturrptible I/O and I couldn''t gracefully shut down, creating the possibility of breaking havoc on my software RAID. Since I moved the dom0 to Centos 5.3 using the latest stable Xen, the problem has abated but still happens on rare occasions; at least the system is responsive and I restart all the domUs and have the network come back. It happened recently again I think I have found something that could be interesting in the Kernel Log (Posted at the end of the email). The card in question uses the tg3 driver and requires it to be setup in PCI permissive mode. As you will see, the first line of my paste below says ''ACPI: PCI interrupt for device 0000:04:00.0 disabled'' and then the netback fails. Any ideas of what is going on or what could I do so I can reduce the likelihood of this happening again even more? Thanks, Pepe ACPI: PCI interrupt for device 0000:04:00.0 disabled eth0: port 2(vif2.0) entering disabled state device vif2.0 left promiscuous mode eth0: port 2(vif2.0) entering disabled state #### netback grant fails < snip > #### netback grant fails eth0: port 4(vif4.0) entering disabled state device vif4.0 left promiscuous mode eth0: port 4(vif4.0) entering disabled state eth0: port 3(vif3.0) entering disabled state device vif3.0 left promiscuous mode eth0: port 3(vif3.0) entering disabled state _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
sorry I forget to reply to mailing list
my original is REHL 2.6.18-128.1.1.el5 64bit. I compiled xen ''s kernel
with source that came with Xen 3.4.0.
So I need to download my original kernel source code and compile it with
Xen,right?
thx,gra
--- On Thu, 7/23/09, Mike Lovell <mike@dev-zero.net> wrote:
From: Mike Lovell <mike@dev-zero.net>
Subject: Re: [Xen-users] network problem after boot Xen
To: "Gra zeus" <gra_zeus@yahoo.com>
Date: Thursday, July 23, 2009, 8:58 AM
Most likely, it is a problem where the dom0 kernel does not have the drivers for
your network interface. I don''t know what you use. But my guess would
be that if you were to do an lsmod you will not see a module for your interface.
You can try to modprobe the module. If that doesn''t work though, you
might need to recompile your kernel, compile the network drivers against your
kernel, or get a new kernel from your distribution. I probably should point out
that the kernel you boot when not using xen and the kernel you boot when you are
using xen might not be the same. Hence the different response from the different
boot processes.
mike
Gra zeus wrote:hello,
WHen i boot up the machine i found this line"Bringing up interface
eth0: Device eth0 does not seem to be present, delaying initialization"
i did `ls /sys/class/net/` and i found "lo" and "sit0". so
i bring up sit0 but it didn''t seem to work as eth0, I still couldn;t
access internet or local network.
this is ifconfig of sit0 after i start it up
sit0 Link encap:IPv6-in-IPv4 inet6 addr: ::127.0.0.1/96
Scope:Unknown UP RUNNING NOARP MTU:1480 Metric:1 RX
packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0
dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX
bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Is this something wrong with my Xen kernel and Xen ramdisk?
thx,gra
--- On Wed, 7/22/09, Mike Lovell <mike@dev-zero.net> wrote:
From: Mike Lovell <mike@dev-zero.net>
Subject: Re: [Xen-users] network problem after boot Xen
To: "Gra zeus" <gra_zeus@yahoo.com>
Cc: xen-users@lists.xensource.com
Date: Wednesday, July 22, 2009, 4:00 PM
Gra zeus wrote:Hello,
I installed Xen 3.4.0 yesterday and managed to boot it up. When I boot my
machine with xen kernel I can''t find my eth0. I tried ifconfig but it
return only loopback interface.Anyone experienced this before? Do I need to
install something to get network card to work?
///////////// when boot with Xen kernello Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128
Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX
packets:1334 errors:0 dropped:0 overruns:0 frame:0 TX packets:1334
errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0
RX bytes:87408 (85.3 KiB) TX bytes:87408 (85.3 KiB)
thx,gra
Do a `ls /sys/class/net/`. Does it show anything besides lo in that directory?
If not, then it is probably that the dom0 kernel you are booting does not have
the driver for the particular network card that you have. If there is something
besides lo, can you do an ifconfig on an interface named by what is listed there
and get networking up?
Hopefully that gives you some direction.
mike
-----Inline Attachment Follows-----
_______________________________________________
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
Hello, this might be a problem with interrupt sharing between virtual machines (including dom0). If an interrupt is assigned to more than one machine it can happen from time to time that one of the machines disables the interrupt. This causes other resources on this interrupt (and in other machines) to be disabled too. Have a look at /proc/interrupts in all of your machines to get to know if there are interrupts assigned to more than one. It''s nothing special if there are several resources sharing one interrupt, it''s just not good if this happens across machines. I had have had this problem with an usb controller sharing it''s interrupt with an onboard network controller and solved it by disabling the usb controller in the bios. So if you have an interrupt shared between machines, try to disabled some of the resources using it. I really don''t know if there are ways to reassign interrupts, but if they are "assigned" in hardware there is probably no way to do that. Excuse my (sometimes) poor English and potential wrong statements (if there are any). Greetings, leo> -----Ursprüngliche Nachricht----- > Von: xen-users-bounces@lists.xensource.com [mailto:xen-users- > bounces@lists.xensource.com] Im Auftrag von Pepe Barbe > Gesendet: Donnerstag, 23. Juli 2009 17:28 > An: xen-users@lists.xensource.com > Betreff: [Xen-users] Netback grant fails > > Hello, > > For the past year I have been trying to debug a problem with my Xen > setup that involves a passthrough PCI card. If there was too much > network traffic (where too much, could be around 5 Mbps) the network > would freeze and I would loose all my connectivity. > > Initially I had the dom0 on Ubuntu 8.04 and things were terrible then. > If I reached this state, the OS would have something in Ininturrptible > I/O and I couldn''t gracefully shut down, creating the possibility of > breaking havoc on my software RAID. Since I moved the dom0 to Centos > 5.3 using the latest stable Xen, the problem has abated but still > happens on rare occasions; at least the system is responsive and I > restart all the domUs and have the network come back. > > It happened recently again I think I have found something that could > be interesting in the Kernel Log (Posted at the end of the email). > > The card in question uses the tg3 driver and requires it to be setup > in PCI permissive mode. As you will see, the first line of my paste > below says ''ACPI: PCI interrupt for device 0000:04:00.0 disabled'' and > then the netback fails. > > Any ideas of what is going on or what could I do so I can reduce the > likelihood of this happening again even more? > > Thanks, > Pepe > > ACPI: PCI interrupt for device 0000:04:00.0 disabled > eth0: port 2(vif2.0) entering disabled state > device vif2.0 left promiscuous mode > eth0: port 2(vif2.0) entering disabled state > #### netback grant fails > > < snip > > > #### netback grant fails > eth0: port 4(vif4.0) entering disabled state > device vif4.0 left promiscuous mode > eth0: port 4(vif4.0) entering disabled state > eth0: port 3(vif3.0) entering disabled state > device vif3.0 left promiscuous mode > eth0: port 3(vif3.0) entering disabled state > > _______________________________________________ > 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