Hi all, I am installing Xen on a dell PowerEdge 1950 box, which has two NICs and 8 cores. After I finished install Xen, I can only see xenbr1 in "ifconfig -a" and "brctl show". Where is the xenbr0? it is suppose to be the first one. The machine is one of the nodes in a cluster. eth0 is configured with a public address which connects to the dept. network. eth1 is the NIC for the private address connects to the master node. It seems that Xen only bridges on eth1. I have experience installing Xen on a box with single NIC, everything was fine. Any idea? Jia. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
did you try ifconfig xenbr0 up ? On Wed, Jul 30, 2008 at 3:40 PM, Jia Rao <rickenrao@gmail.com> wrote:> Hi all, > > I am installing Xen on a dell PowerEdge 1950 box, which has two NICs and 8 > cores. > > After I finished install Xen, I can only see xenbr1 in "ifconfig -a" and > "brctl show". > > Where is the xenbr0? it is suppose to be the first one. > > The machine is one of the nodes in a cluster. eth0 is configured with a > public address which connects to the dept. network. eth1 is the NIC for the > private address connects to the master node. It seems that Xen only bridges > on eth1. > > I have experience installing Xen on a box with single NIC, everything was > fine. > > Any idea? > > Jia. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Fangfei Zhou ---------------------------------------------------- I have a dream, fly to the sky _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Jul 30, 2008 at 3:40 PM, Jia Rao <rickenrao@gmail.com> wrote:> Hi all, > > I am installing Xen on a dell PowerEdge 1950 box, which has two NICs and 8 > cores. > > After I finished install Xen, I can only see xenbr1 in "ifconfig -a" and > "brctl show". > > Where is the xenbr0? it is suppose to be the first one. > > The machine is one of the nodes in a cluster. eth0 is configured with a > public address which connects to the dept. network. eth1 is the NIC for the > private address connects to the master node. It seems that Xen only bridges > on eth1. >This is most likely to do with how the xen network bridge script detects to default device. Check your default route, most likely it is set to eth1. you should be able to understand this better by taking a look at /etc/xen/scripts/network-bridge, in particular look for the line that is something like "ip route list | awk ..."> I have experience installing Xen on a box with single NIC, everything was > fine. >If you need both xenbr0 and xenbr1, the most reliable way to do this is to use a multiple network interfaces network script These instructions linked here have (minor) errors, but should give you a start. http://www.centos.org/docs/5/html/5.1/Virtualization_Guide/ch-virt-bridge-errors.html In particular, watch out for the space between the # and ! in the script The copying of the network-script to network-script.xen is unnecessary Also, in one place it says uncomment when it should say comment Cheers, Todd> Any idea? > > Jia. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Todd Deshane http://todddeshane.net check out our book: http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, The problem was fixed by updating the broadcom Gigabyte NIC driver. It is a known problem of Xen and Dell PowerEdge servers with Broadcom NICs. You guys can search "xen poweredge" to see what is the problem. Thanks for replying Jia. On Wed, Jul 30, 2008 at 11:26 PM, Todd Deshane <deshantm@gmail.com> wrote:> On Wed, Jul 30, 2008 at 3:40 PM, Jia Rao <rickenrao@gmail.com> wrote: > > Hi all, > > > > I am installing Xen on a dell PowerEdge 1950 box, which has two NICs and > 8 > > cores. > > > > After I finished install Xen, I can only see xenbr1 in "ifconfig -a" and > > "brctl show". > > > > Where is the xenbr0? it is suppose to be the first one. > > > > The machine is one of the nodes in a cluster. eth0 is configured with a > > public address which connects to the dept. network. eth1 is the NIC for > the > > private address connects to the master node. It seems that Xen only > bridges > > on eth1. > > > > This is most likely to do with how the xen network bridge script detects to > default device. > > Check your default route, most likely it is set to eth1. > > you should be able to understand this better by taking a look at > /etc/xen/scripts/network-bridge, in particular look for the line that > is something like "ip route list | awk ..." > > > > I have experience installing Xen on a box with single NIC, everything was > > fine. > > > > If you need both xenbr0 and xenbr1, the most reliable way to do this is > to use a multiple network interfaces network script > > These instructions linked here have (minor) errors, but should give you a > start. > > http://www.centos.org/docs/5/html/5.1/Virtualization_Guide/ch-virt-bridge-errors.html > > In particular, watch out for the space between the # and ! in the script > > The copying of the network-script to network-script.xen is unnecessary > > Also, in one place it says uncomment when it should say comment > > Cheers, > Todd > > > Any idea? > > > > Jia. > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > > > > -- > Todd Deshane > http://todddeshane.net > check out our book: http://runningxen.com >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Jul 30, 2008 at 11:48 PM, Jia Rao <rickenrao@gmail.com> wrote:> Hi, > The problem was fixed by updating the broadcom Gigabyte NIC driver. It is a > known problem of Xen and Dell PowerEdge servers with Broadcom NICs. > You guys can search "xen poweredge" to see what is the problem. >Are you referring to the firmware upgrade mentioned here: http://mywiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround Or is it simply a driver issue? When did you get your Poweredge 1950? Maybe the issue was fixed in the Poweredge 1950 III? Cheers, Todd> Thanks for replying > Jia. >-- Todd Deshane http://todddeshane.net check out our book: http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
We got the PowerEdge III Boxes a month ago. http://mywiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround is the solution I found. However I did not have any CD with me, so I tried to upgrade the NIC driver first as indicated by the following link in Citrix forum http://forums.citrix.com/thread.jspa?threadID=151786&tstart=0 I worked for me, but some guys in Citrix forum said it still has some problems after one week running. I am still testing it, and let you know if it solves the problem or just hides it. Cheers, Jia On Thu, Jul 31, 2008 at 12:04 AM, Todd Deshane <deshantm@gmail.com> wrote:> On Wed, Jul 30, 2008 at 11:48 PM, Jia Rao <rickenrao@gmail.com> wrote: > > Hi, > > The problem was fixed by updating the broadcom Gigabyte NIC driver. It is > a > > known problem of Xen and Dell PowerEdge servers with Broadcom NICs. > > You guys can search "xen poweredge" to see what is the problem. > > > > Are you referring to the firmware upgrade mentioned here: > http://mywiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround > > Or is it simply a driver issue? > > When did you get your Poweredge 1950? > > Maybe the issue was fixed in the Poweredge 1950 III? > > Cheers, > Todd > > > Thanks for replying > > Jia. > > > > -- > Todd Deshane > http://todddeshane.net > check out our book: http://runningxen.com >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Jul 31, 2008 at 10:04 AM, Jia Rao <rickenrao@gmail.com> wrote:> We got the PowerEdge III Boxes a month ago. > http://mywiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround is the > solution I found. However I did not have any CD with me, so I tried to > upgrade the NIC driver first as indicated by the following link in Citrix > forum > http://forums.citrix.com/thread.jspa?threadID=151786&tstart=0 > > I worked for me, but some guys in Citrix forum said it still has some > problems after one week running. >What version of Xen and distro are you running? -- Todd Deshane http://todddeshane.net check out our book: http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I am running Xen 3.1 compiled from source and REHL 4.5 shipped with Dell PowerEdge 1950 III. On Thu, Jul 31, 2008 at 12:01 PM, Todd Deshane <deshantm@gmail.com> wrote:> On Thu, Jul 31, 2008 at 10:04 AM, Jia Rao <rickenrao@gmail.com> wrote: > > We got the PowerEdge III Boxes a month ago. > > http://mywiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround is > the > > solution I found. However I did not have any CD with me, so I tried to > > upgrade the NIC driver first as indicated by the following link in Citrix > > forum > > http://forums.citrix.com/thread.jspa?threadID=151786&tstart=0 > > > > I worked for me, but some guys in Citrix forum said it still has some > > problems after one week running. > > > > What version of Xen and distro are you running? > > > -- > Todd Deshane > http://todddeshane.net > check out our book: http://runningxen.com >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Unfortunately, the eth0 starts to fail sometimes when xend is started (better than the previous NIC driver, with previous one, eth0 fails even without starting xend, and I can not see xenbr0). Right now, there are xenbr0 and xenbr1 in ifconfig -a. I am trying to disable the management firmware in the NIC now... Jia. On Thu, Jul 31, 2008 at 12:28 PM, Jia Rao <rickenrao@gmail.com> wrote:> I am running Xen 3.1 compiled from source and REHL 4.5 shipped with Dell > PowerEdge 1950 III. > > > > > On Thu, Jul 31, 2008 at 12:01 PM, Todd Deshane <deshantm@gmail.com> wrote: > >> On Thu, Jul 31, 2008 at 10:04 AM, Jia Rao <rickenrao@gmail.com> wrote: >> > We got the PowerEdge III Boxes a month ago. >> > http://mywiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround is >> the >> > solution I found. However I did not have any CD with me, so I tried to >> > upgrade the NIC driver first as indicated by the following link in >> Citrix >> > forum >> > http://forums.citrix.com/thread.jspa?threadID=151786&tstart=0 >> > >> > I worked for me, but some guys in Citrix forum said it still has some >> > problems after one week running. >> > >> >> What version of Xen and distro are you running? >> >> >> -- >> Todd Deshane >> http://todddeshane.net >> check out our book: http://runningxen.com >> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Jul 31, 2008 at 4:15 PM, Jia Rao <rickenrao@gmail.com> wrote:> Unfortunately, the eth0 starts to fail sometimes when xend is started > (better than the previous NIC driver, with previous one, eth0 fails even > without starting xend, and I can not see xenbr0). Right now, there are > xenbr0 and xenbr1 in ifconfig -a. >Have you looked closer at my original assessment? I believe that xen should only create one bridge by default and that if you want more created you need a multi bridge script. Cheers, Todd> I am trying to disable the management firmware in the NIC now... > > Jia. > > On Thu, Jul 31, 2008 at 12:28 PM, Jia Rao <rickenrao@gmail.com> wrote: >> >> I am running Xen 3.1 compiled from source and REHL 4.5 shipped with Dell >> PowerEdge 1950 III. >> >> >> >> On Thu, Jul 31, 2008 at 12:01 PM, Todd Deshane <deshantm@gmail.com> wrote: >>> >>> On Thu, Jul 31, 2008 at 10:04 AM, Jia Rao <rickenrao@gmail.com> wrote: >>> > We got the PowerEdge III Boxes a month ago. >>> > http://mywiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround is >>> > the >>> > solution I found. However I did not have any CD with me, so I tried to >>> > upgrade the NIC driver first as indicated by the following link in >>> > Citrix >>> > forum >>> > http://forums.citrix.com/thread.jspa?threadID=151786&tstart=0 >>> > >>> > I worked for me, but some guys in Citrix forum said it still has some >>> > problems after one week running. >>> > >>> >>> What version of Xen and distro are you running? >>> >>> >>> -- >>> Todd Deshane >>> http://todddeshane.net >>> check out our book: http://runningxen.com >> > >-- Todd Deshane http://todddeshane.net check out our book: http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
If you''re running a Dell PowerEdge you have a Broadcom ethernet Adapter, right? Are you using the bnx2 module? I had the same issues using debian. There is a bug in this driver, that freezes the driver when used with xen. The newest version which you can download from broadcom fixes this. What version of bnx2 do you have? Might this perhaps be your problem? Cheers, Alex Jia Rao schrieb:> Unfortunately, the eth0 starts to fail sometimes when xend is started > (better than the previous NIC driver, with previous one, eth0 fails > even without starting xend, and I can not see xenbr0). Right now, > there are xenbr0 and xenbr1 in ifconfig -a. > > I am trying to disable the management firmware in the NIC now... > > Jia. > > On Thu, Jul 31, 2008 at 12:28 PM, Jia Rao <rickenrao@gmail.com > <mailto:rickenrao@gmail.com>> wrote: > > I am running Xen 3.1 compiled from source and REHL 4.5 shipped > with Dell PowerEdge 1950 III. > > > > > On Thu, Jul 31, 2008 at 12:01 PM, Todd Deshane <deshantm@gmail.com > <mailto:deshantm@gmail.com>> wrote: > > On Thu, Jul 31, 2008 at 10:04 AM, Jia Rao <rickenrao@gmail.com > <mailto:rickenrao@gmail.com>> wrote: > > We got the PowerEdge III Boxes a month ago. > > > http://mywiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround > is the > > solution I found. However I did not have any CD with me, so > I tried to > > upgrade the NIC driver first as indicated by the following > link in Citrix > > forum > > > http://forums.citrix.com/thread.jspa?threadID=151786&tstart=0 > <http://forums.citrix.com/thread.jspa?threadID=151786&tstart=0> > > > > I worked for me, but some guys in Citrix forum said it still > has some > > problems after one week running. > > > > What version of Xen and distro are you running? > > > -- > Todd Deshane > http://todddeshane.net > check out our book: http://runningxen.com > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > > __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 3315 (20080731) __________ > > E-Mail wurde geprüft mit ESET NOD32 Antivirus. > > http://www.eset.com >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Jul 31, 2008 at 4:26 PM, Alexander Hoßdorf <xen-users@hossdorf.eu> wrote:> If you''re running a Dell PowerEdge you have a Broadcom ethernet Adapter, > right? > Are you using the bnx2 module? > > I had the same issues using debian. > There is a bug in this driver, that freezes the driver when used with xen.What is a use case that makes it freeze? Could it be specific to 32bit? I''ve haven''t (yet) seem any problems on 64 bit. We are using the drivers that come with 2.6.18-92.1.6.el5xen + CentOS 5.2 Cheers, Todd> The newest version which you can download from broadcom fixes this. > > What version of bnx2 do you have? > > Might this perhaps be your problem? > > Cheers, > Alex > > > > Jia Rao schrieb: >> >> Unfortunately, the eth0 starts to fail sometimes when xend is started >> (better than the previous NIC driver, with previous one, eth0 fails even >> without starting xend, and I can not see xenbr0). Right now, there are >> xenbr0 and xenbr1 in ifconfig -a. >> >> I am trying to disable the management firmware in the NIC now... >> >> Jia. >> >> On Thu, Jul 31, 2008 at 12:28 PM, Jia Rao <rickenrao@gmail.com >> <mailto:rickenrao@gmail.com>> wrote: >> >> I am running Xen 3.1 compiled from source and REHL 4.5 shipped >> with Dell PowerEdge 1950 III. >> >> >> >> >> On Thu, Jul 31, 2008 at 12:01 PM, Todd Deshane <deshantm@gmail.com >> <mailto:deshantm@gmail.com>> wrote: >> >> On Thu, Jul 31, 2008 at 10:04 AM, Jia Rao <rickenrao@gmail.com >> <mailto:rickenrao@gmail.com>> wrote: >> > We got the PowerEdge III Boxes a month ago. >> > >> >> http://mywiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround >> is the >> > solution I found. However I did not have any CD with me, so >> I tried to >> > upgrade the NIC driver first as indicated by the following >> link in Citrix >> > forum >> > >> http://forums.citrix.com/thread.jspa?threadID=151786&tstart=0 >> <http://forums.citrix.com/thread.jspa?threadID=151786&tstart=0> >> > >> > I worked for me, but some guys in Citrix forum said it still >> has some >> > problems after one week running. >> > >> >> What version of Xen and distro are you running? >> >> >> -- >> Todd Deshane >> http://todddeshane.net >> check out our book: http://runningxen.com >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> >> __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version >> 3315 (20080731) __________ >> >> E-Mail wurde geprüft mit ESET NOD32 Antivirus. >> >> http://www.eset.com >> > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- Todd Deshane http://todddeshane.net check out our book: http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
The new driver I have installed is 1.7.1c which is the newest. The other info: Xen: 3.1 Kernel: 2.6.18 OS: RHEL 4.5 x86_64 Jia. On Thu, Jul 31, 2008 at 4:26 PM, Alexander Hoßdorf <xen-users@hossdorf.eu>wrote:> If you''re running a Dell PowerEdge you have a Broadcom ethernet Adapter, > right? > Are you using the bnx2 module? > > I had the same issues using debian. > There is a bug in this driver, that freezes the driver when used with xen. > The newest version which you can download from broadcom fixes this. > > What version of bnx2 do you have? > > Might this perhaps be your problem? > > Cheers, > Alex > > > > Jia Rao schrieb: > >> Unfortunately, the eth0 starts to fail sometimes when xend is started >> (better than the previous NIC driver, with previous one, eth0 fails even >> without starting xend, and I can not see xenbr0). Right now, there are >> xenbr0 and xenbr1 in ifconfig -a. >> >> I am trying to disable the management firmware in the NIC now... >> >> Jia. >> >> On Thu, Jul 31, 2008 at 12:28 PM, Jia Rao <rickenrao@gmail.com <mailto: >> rickenrao@gmail.com>> wrote: >> >> I am running Xen 3.1 compiled from source and REHL 4.5 shipped >> with Dell PowerEdge 1950 III. >> >> >> >> >> On Thu, Jul 31, 2008 at 12:01 PM, Todd Deshane <deshantm@gmail.com >> <mailto:deshantm@gmail.com>> wrote: >> >> On Thu, Jul 31, 2008 at 10:04 AM, Jia Rao <rickenrao@gmail.com >> <mailto:rickenrao@gmail.com>> wrote: >> > We got the PowerEdge III Boxes a month ago. >> > >> >> http://mywiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround >> is the >> > solution I found. However I did not have any CD with me, so >> I tried to >> > upgrade the NIC driver first as indicated by the following >> link in Citrix >> > forum >> > >> http://forums.citrix.com/thread.jspa?threadID=151786&tstart=0 >> <http://forums.citrix.com/thread.jspa?threadID=151786&tstart=0> >> > >> > I worked for me, but some guys in Citrix forum said it still >> has some >> > problems after one week running. >> > >> >> What version of Xen and distro are you running? >> >> >> -- >> Todd Deshane >> http://todddeshane.net >> check out our book: http://runningxen.com >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >> >> __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version >> 3315 (20080731) __________ >> >> E-Mail wurde geprüft mit ESET NOD32 Antivirus. >> >> http://www.eset.com >> >> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
In my case I only had to start xend. Then there was no more ethernet connectivity and xen bridges did not come up. And yes, it was a 32 bit system. I had downloaded the bnx2 drivers from broadcom and compiled them from source. I don''t know the version exactly any more, but I can say version 1.6.9 works well for me. I think downloading the latest driver and then building it from source ois the safest way?! Cheers, Alex Todd Deshane schrieb:> On Thu, Jul 31, 2008 at 4:26 PM, Alexander Hoßdorf > <xen-users@hossdorf.eu> wrote: > >> If you''re running a Dell PowerEdge you have a Broadcom ethernet Adapter, >> right? >> Are you using the bnx2 module? >> >> I had the same issues using debian. >> There is a bug in this driver, that freezes the driver when used with xen. >> > > What is a use case that makes it freeze? > > Could it be specific to 32bit? > > I''ve haven''t (yet) seem any problems on 64 bit. > > We are using the drivers that come with 2.6.18-92.1.6.el5xen + CentOS 5.2 > > Cheers, > Todd > > > > >> The newest version which you can download from broadcom fixes this. >> >> What version of bnx2 do you have? >> >> Might this perhaps be your problem? >> >> Cheers, >> Alex >> >> >> >> Jia Rao schrieb: >> >>> Unfortunately, the eth0 starts to fail sometimes when xend is started >>> (better than the previous NIC driver, with previous one, eth0 fails even >>> without starting xend, and I can not see xenbr0). Right now, there are >>> xenbr0 and xenbr1 in ifconfig -a. >>> >>> I am trying to disable the management firmware in the NIC now... >>> >>> Jia. >>> >>> On Thu, Jul 31, 2008 at 12:28 PM, Jia Rao <rickenrao@gmail.com >>> <mailto:rickenrao@gmail.com>> wrote: >>> >>> I am running Xen 3.1 compiled from source and REHL 4.5 shipped >>> with Dell PowerEdge 1950 III. >>> >>> >>> >>> >>> On Thu, Jul 31, 2008 at 12:01 PM, Todd Deshane <deshantm@gmail.com >>> <mailto:deshantm@gmail.com>> wrote: >>> >>> On Thu, Jul 31, 2008 at 10:04 AM, Jia Rao <rickenrao@gmail.com >>> <mailto:rickenrao@gmail.com>> wrote: >>> > We got the PowerEdge III Boxes a month ago. >>> > >>> >>> http://mywiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround >>> is the >>> > solution I found. However I did not have any CD with me, so >>> I tried to >>> > upgrade the NIC driver first as indicated by the following >>> link in Citrix >>> > forum >>> > >>> http://forums.citrix.com/thread.jspa?threadID=151786&tstart=0 >>> <http://forums.citrix.com/thread.jspa?threadID=151786&tstart=0> >>> > >>> > I worked for me, but some guys in Citrix forum said it still >>> has some >>> > problems after one week running. >>> > >>> >>> What version of Xen and distro are you running? >>> >>> >>> -- >>> Todd Deshane >>> http://todddeshane.net >>> check out our book: http://runningxen.com >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com >>> http://lists.xensource.com/xen-users >>> >>> >>> __________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version >>> 3315 (20080731) __________ >>> >>> E-Mail wurde geprüft mit ESET NOD32 Antivirus. >>> >>> http://www.eset.com >>> >>> >> _______________________________________________ >> 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
Have you compiled it from source? Silly question ;-) You have to, if you build xen from source. Cheers, Alex Jia Rao schrieb:> The new driver I have installed is 1.7.1c which is the newest. > The other info: > Xen: 3.1 > Kernel: 2.6.18 > OS: RHEL 4.5 x86_64 > > Jia. > > On Thu, Jul 31, 2008 at 4:26 PM, Alexander Hoßdorf > <xen-users@hossdorf.eu> wrote: > > If you''re running a Dell PowerEdge you have a Broadcom ethernet > Adapter, right? > Are you using the bnx2 module? > > I had the same issues using debian. > There is a bug in this driver, that freezes the driver when used > with xen. > The newest version which you can download from broadcom fixes this. > > What version of bnx2 do you have? > > Might this perhaps be your problem? > > Cheers, > Alex > > > > Jia Rao schrieb: > > Unfortunately, the eth0 starts to fail sometimes when xend is > started (better than the previous NIC driver, with previous > one, eth0 fails even without starting xend, and I can not see > xenbr0). Right now, there are xenbr0 and xenbr1 in ifconfig -a. > > I am trying to disable the management firmware in the NIC now... > > Jia. > > On Thu, Jul 31, 2008 at 12:28 PM, Jia Rao <rickenrao@gmail.com > <mailto:rickenrao@gmail.com> <mailto:rickenrao@gmail.com > <mailto:rickenrao@gmail.com>>> wrote: > > I am running Xen 3.1 compiled from source and REHL 4.5 shipped > with Dell PowerEdge 1950 III. > > > > > On Thu, Jul 31, 2008 at 12:01 PM, Todd Deshane > <deshantm@gmail.com <mailto:deshantm@gmail.com> > <mailto:deshantm@gmail.com <mailto:deshantm@gmail.com>>> wrote: > > On Thu, Jul 31, 2008 at 10:04 AM, Jia Rao > <rickenrao@gmail.com <mailto:rickenrao@gmail.com> > <mailto:rickenrao@gmail.com > <mailto:rickenrao@gmail.com>>> wrote: > > We got the PowerEdge III Boxes a month ago. > > > > http://mywiki.ncsa.uiuc.edu/wiki/Dell_PE1950_NIC_Firmware_Workaround > is the > > solution I found. However I did not have any CD with > me, so > I tried to > > upgrade the NIC driver first as indicated by the > following > link in Citrix > > forum > > > > http://forums.citrix.com/thread.jspa?threadID=151786&tstart=0 > <http://forums.citrix.com/thread.jspa?threadID=151786&tstart=0> > > <http://forums.citrix.com/thread.jspa?threadID=151786&tstart=0 > <http://forums.citrix.com/thread.jspa?threadID=151786&tstart=0>> > > > > I worked for me, but some guys in Citrix forum said > it still > has some > > problems after one week running. > > > > What version of Xen and distro are you running? > > > -- > Todd Deshane > http://todddeshane.net > check out our book: http://runningxen.com > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > <mailto:Xen-users@lists.xensource.com> > http://lists.xensource.com/xen-users > > > __________ Hinweis von ESET NOD32 Antivirus, > Signaturdatenbank-Version 3315 (20080731) __________ > > E-Mail wurde geprüft mit ESET NOD32 Antivirus. > > http://www.eset.com > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users