Hi. I am trying to setup my firewall in DomU. However, I have got a little problem. My pon dsl-provider exits with following message. Nov 18 09:44:40 alsfw01 pppd[1723]: Plugin rp-pppoe.so loaded. Nov 18 09:44:40 alsfw01 pppd[1723]: Linux kernel does not support PPPoE -- are you running 2.4.x? Nov 18 09:44:40 alsfw01 pppd[1723]: Exit. I am running xen out of the box on Debian Stable. My pppoeconf configured everything and found the the interface with pppoe. I also believe that modules are actually loaded: pppoe 23296 0 pppox 8592 1 pppoe ppp_generic 34080 2 pppoe,pppox slhc 11392 1 ppp_generic Would you have idea where I have problem? Jiri _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
kanour-xen wrote:> Hi. > > I am trying to setup my firewall in DomU. However, I have got a little > problem. My *pon dsl-provider *exits with following message. > > Nov 18 09:44:40 alsfw01 pppd[1723]: Plugin rp-pppoe.so loaded. > Nov 18 09:44:40 alsfw01 pppd[1723]: Linux kernel does not support > PPPoE -- are you running 2.4.x? > Nov 18 09:44:40 alsfw01 pppd[1723]: Exit. > > I am running xen out of the box on Debian Stable. My *pppoeconf > *configured everything and found the the interface with pppoe. > I also believe that modules are actually loaded: > > pppoe 23296 0 > pppox 8592 1 pppoe > ppp_generic 34080 2 pppoe,pppox > slhc 11392 1 ppp_generic > > Would you have idea where I have problem? > > Jiri > > > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-usersOk, I am here again. I cannot figure it out. Here are some additional info if someone would want to help. Network setup in Dom0: Separate bridges for each card in /etc/xen/scrips/my-network-bridge $XENDIR/network-bridge "$@" netdev=eth0 bridge=xenbr0 vifnum=0 $XENDIR/network-bridge "$@" netdev=eth1 bridge=xenbr1 vifnum=1 $XENDIR/network-bridge "$@" netdev=eth2 bridge=xenbr2 vifnum=2 I can ping the ADSL modem from DomU, so the network card is working. However, when I try to establish the connection, it fails with the message above. Any suggestions? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christian Lyra wrote:>>> I am trying to setup my firewall in DomU. However, I have got a little >>> problem. My *pon dsl-provider *exits with following message. >>> >>> Nov 18 09:44:40 alsfw01 pppd[1723]: Plugin rp-pppoe.so loaded. >>> Nov 18 09:44:40 alsfw01 pppd[1723]: Linux kernel does not support >>> PPPoE -- are you running 2.4.x? >>> Nov 18 09:44:40 alsfw01 pppd[1723]: Exit. > > > My firewall is a domU too, but it has control of the interface > connected to the internet, and pppoe works just fine. never tried to > do this with a bridge... > >>> I am running xen out of the box on Debian Stable. My *pppoeconf >>> *configured everything and found the the interface with pppoe. >>> I also believe that modules are actually loaded: >>> >>> pppoe 23296 0 >>> pppox 8592 1 pppoe >>> ppp_generic 34080 2 pppoe,pppox >>> slhc 11392 1 ppp_generic >>> >>> Would you have idea where I have problem? >>> >>> Jiri >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com >>> http://lists.xensource.com/xen-users >> Ok, I am here again. I cannot figure it out. Here are some additional >> info if someone would want to help. >> >> Network setup in Dom0: >> Separate bridges for each card in /etc/xen/scrips/my-network-bridge >> $XENDIR/network-bridge "$@" netdev=eth0 bridge=xenbr0 vifnum=0 >> $XENDIR/network-bridge "$@" netdev=eth1 bridge=xenbr1 vifnum=1 >> $XENDIR/network-bridge "$@" netdev=eth2 bridge=xenbr2 vifnum=2 >> >> I can ping the ADSL modem from DomU, so the network card is working. >> However, when I try to establish the connection, it fails with the >> message above. >> >> Any suggestions? >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > > >What do you mean by domU has control over the interface? Jiri _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
>>> I am trying to setup my firewall in DomU. However, I have got a > >>> little problem. My *pon dsl-provider *exits with following > >>> message.> > My firewall is a domU too, but it has control of the interface > > connected to the internet, and pppoe works just fine. never tried > > to do this with a bridge... > >> What do you mean by domU has control over the interface?I "hide" the interface from dom0 with pciback.hide=(xx:xx.x) in grub and present it to domU with pci = [ ''xx:xx.x'' ]. So the domU has control of the real pci device. -- Christian Lyra POP-PR - RNP http://lyra.soueu.com.br Grand Master Turing once dreamed that he was a machine. When he awoke he exclaimed: ``I don''t know whether I am Turing dreaming that I am a machine, or a machine dreaming that I am Turing!'''' The Tao Of Programing _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christian Lyra wrote:>>>> I am trying to setup my firewall in DomU. However, I have got a >> >>> little problem. My *pon dsl-provider *exits with following >> >>> message. > >> > My firewall is a domU too, but it has control of the interface >> > connected to the internet, and pppoe works just fine. never tried >> > to do this with a bridge... >> > > >> What do you mean by domU has control over the interface? > > I "hide" the interface from dom0 with pciback.hide=(xx:xx.x) in grub and > present it to domU with pci = [ ''xx:xx.x'' ]. So the domU has control of > the real pci device. > >I tried that already, but when I included pciback.hide=(xx:xx.x) in grub the card was still present. So, I then unbound it from /sys/... I included pci =[..... and started domU. It was still the same. At this moment I don''t know what to do, but I will try to reinstall everything and try one more time with Debian Etch xen binary packages. At this moment I am using Debian Lenny with binary xen from XenSource. I am just wondering why the hiding with pciback.hide does not work for me? Jiri _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
kanour-xen wrote:> Christian Lyra wrote: >>>>> I am trying to setup my firewall in DomU. However, I have got a >>> >>> little problem. My *pon dsl-provider *exits with following >>> >>> message. >> >>> > My firewall is a domU too, but it has control of the interface >>> > connected to the internet, and pppoe works just fine. never tried >>> > to do this with a bridge... >>> > >> >>> What do you mean by domU has control over the interface? >> >> I "hide" the interface from dom0 with pciback.hide=(xx:xx.x) in grub >> and present it to domU with pci = [ ''xx:xx.x'' ]. So the domU has >> control of the real pci device. >> >> > > I tried that already, but when I included pciback.hide=(xx:xx.x) in grub > the card was still present. So, I then unbound it from /sys/... > I included pci =[..... and started domU. It was still the same. > > At this moment I don''t know what to do, but I will try to reinstall > everything and try one more time with Debian Etch xen binary packages. > > At this moment I am using Debian Lenny with binary xen from XenSource. > > I am just wondering why the hiding with pciback.hide does not work for me? > > Jiri > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >So, I did reinstall everything to Debian Etch. I am running xen from debian packages. But I just cannot make the pppoe work. Please help!!! I did hide the pci device on the boot. I checked that the driver (e1000) is not loaded in Dom0. I included pci statement in DomU config file. I checked that the devide was recognised and driver was loaded in DomU. I have it all on HP DL145 G2 server. There is AMD dual core processor, 2GB ram, 2x Broadcom network card and I added Intel PCI card in the raiser board (PCI-X). pppoeconf will discover pppoe on eth2 (intel 1G card) but when it tries to establish the connection. it fails with: Nov 18 09:44:40 alsfw01 pppd[1723]: Plugin rp-pppoe.so loaded. Nov 18 09:44:40 alsfw01 pppd[1723]: Linux kernel does not support PPPoE -- are you running 2.4.x? Could anyone help me to troubleshoot it. skype: linuxgo Jiri _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Here''s what I ''can'' tell you. My previous setup used Debian Etch as the dom0, pciback to pass a nic to a domU, and Smoothwall 3.0 firewall distro as the domU. I used the Xen provided Redhat kernel package for the domU, since Smoothwall is a fork from old Redhat, and copied the modules from it into the domU. It just worked. Then, I just recently dist-upgrade''d to Lenny, and installing the Xen 3.1 hypervisor, staying with the existing 3.04 kernels (2.6.18-5-xen-686), and it still works. I suspect your problems lie strictly with pppoe and not Xen, you might want to try hitting up the Roaring Pengiun forums (do they have a list?) and see what they can tell you. Of course, I''m no guru, I just pretend to know what I''m doing, so take my advice/info with a grain of salt. -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of kanour-xen Sent: November 21, 2007 7:37 AM To: Christian Lyra Cc: xen-users@lists.xensource.com Subject: Re: [Xen-users] PPPoE in DomU exits with error kanour-xen wrote:> Christian Lyra wrote: >>>>> I am trying to setup my firewall in DomU. However, I have got a >>> >>> little problem. My *pon dsl-provider *exits with following >>> >>> message. >> >>> > My firewall is a domU too, but it has control of the interface >>> > connected to the internet, and pppoe works just fine. never tried >>> > to do this with a bridge... >>> > >> >>> What do you mean by domU has control over the interface? >> >> I "hide" the interface from dom0 with pciback.hide=(xx:xx.x) in grub >> and present it to domU with pci = [ ''xx:xx.x'' ]. So the domU has >> control of the real pci device. >> >> > > I tried that already, but when I included pciback.hide=(xx:xx.x) in grub > the card was still present. So, I then unbound it from /sys/... > I included pci =[..... and started domU. It was still the same. > > At this moment I don''t know what to do, but I will try to reinstall > everything and try one more time with Debian Etch xen binary packages. > > At this moment I am using Debian Lenny with binary xen from XenSource. > > I am just wondering why the hiding with pciback.hide does not work for me? > > Jiri > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >So, I did reinstall everything to Debian Etch. I am running xen from debian packages. But I just cannot make the pppoe work. Please help!!! I did hide the pci device on the boot. I checked that the driver (e1000) is not loaded in Dom0. I included pci statement in DomU config file. I checked that the devide was recognised and driver was loaded in DomU. I have it all on HP DL145 G2 server. There is AMD dual core processor, 2GB ram, 2x Broadcom network card and I added Intel PCI card in the raiser board (PCI-X). pppoeconf will discover pppoe on eth2 (intel 1G card) but when it tries to establish the connection. it fails with: Nov 18 09:44:40 alsfw01 pppd[1723]: Plugin rp-pppoe.so loaded. Nov 18 09:44:40 alsfw01 pppd[1723]: Linux kernel does not support PPPoE -- are you running 2.4.x? Could anyone help me to troubleshoot it. skype: linuxgo Jiri _______________________________________________ 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
[STD]Ein wrote:> Here''s what I ''can'' tell you. > > My previous setup used Debian Etch as the dom0, pciback to pass a nic to a > domU, and Smoothwall 3.0 firewall distro as the domU. I used the Xen > provided Redhat kernel package for the domU, since Smoothwall is a fork from > old Redhat, and copied the modules from it into the domU. > > It just worked. Then, I just recently dist-upgrade''d to Lenny, and > installing the Xen 3.1 hypervisor, staying with the existing 3.04 kernels > (2.6.18-5-xen-686), and it still works. > > I suspect your problems lie strictly with pppoe and not Xen, you might want > to try hitting up the Roaring Pengiun forums (do they have a list?) and see > what they can tell you. Of course, I''m no guru, I just pretend to know what > I''m doing, so take my advice/info with a grain of salt. > > -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of kanour-xen > Sent: November 21, 2007 7:37 AM > To: Christian Lyra > Cc: xen-users@lists.xensource.com > Subject: Re: [Xen-users] PPPoE in DomU exits with error > > kanour-xen wrote: >> Christian Lyra wrote: >>>>>> I am trying to setup my firewall in DomU. However, I have got a >>>> >>> little problem. My *pon dsl-provider *exits with following >>>> >>> message. >>>> > My firewall is a domU too, but it has control of the interface >>>> > connected to the internet, and pppoe works just fine. never tried >>>> > to do this with a bridge... >>>> > >>>> What do you mean by domU has control over the interface? >>> I "hide" the interface from dom0 with pciback.hide=(xx:xx.x) in grub >>> and present it to domU with pci = [ ''xx:xx.x'' ]. So the domU has >>> control of the real pci device. >>> >>> >> I tried that already, but when I included pciback.hide=(xx:xx.x) in grub >> the card was still present. So, I then unbound it from /sys/... >> I included pci =[..... and started domU. It was still the same. >> >> At this moment I don''t know what to do, but I will try to reinstall >> everything and try one more time with Debian Etch xen binary packages. >> >> At this moment I am using Debian Lenny with binary xen from XenSource. >> >> I am just wondering why the hiding with pciback.hide does not work for me? >> >> Jiri >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > > So, I did reinstall everything to Debian Etch. I am running xen from > debian packages. But I just cannot make the pppoe work. > > Please help!!! > > I did hide the pci device on the boot. I checked that the driver (e1000) > is not loaded in Dom0. > I included pci statement in DomU config file. I checked that the devide > was recognised and driver was loaded in DomU. > > I have it all on HP DL145 G2 server. There is AMD dual core processor, > 2GB ram, 2x Broadcom network card and I added Intel PCI card in the > raiser board (PCI-X). > > pppoeconf will discover pppoe on eth2 (intel 1G card) but when it tries > to establish the connection. it fails with: > > Nov 18 09:44:40 alsfw01 pppd[1723]: Plugin rp-pppoe.so loaded. > Nov 18 09:44:40 alsfw01 pppd[1723]: Linux kernel does not support > PPPoE -- are you running 2.4.x? > > Could anyone help me to troubleshoot it. > skype: linuxgo > > Jiri > > _______________________________________________ > 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 >Hi. Thanks very much for info.I am still working on it because I just cannot figure it out. In dom0 pppoe is working fine. In domU it is not working. Same kernel for both. Same automatic setup through pppoeconf. I just don''t know... Jiri _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
kanour-xen wrote:> [STD]Ein wrote: >> Here''s what I ''can'' tell you. >> >> My previous setup used Debian Etch as the dom0, pciback to pass a nic >> to a >> domU, and Smoothwall 3.0 firewall distro as the domU. I used the Xen >> provided Redhat kernel package for the domU, since Smoothwall is a >> fork from >> old Redhat, and copied the modules from it into the domU. >> >> It just worked. Then, I just recently dist-upgrade''d to Lenny, and >> installing the Xen 3.1 hypervisor, staying with the existing 3.04 kernels >> (2.6.18-5-xen-686), and it still works. >> >> I suspect your problems lie strictly with pppoe and not Xen, you might >> want >> to try hitting up the Roaring Pengiun forums (do they have a list?) >> and see >> what they can tell you. Of course, I''m no guru, I just pretend to >> know what >> I''m doing, so take my advice/info with a grain of salt. >> >> -----Original Message----- >> From: xen-users-bounces@lists.xensource.com >> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of kanour-xen >> Sent: November 21, 2007 7:37 AM >> To: Christian Lyra >> Cc: xen-users@lists.xensource.com >> Subject: Re: [Xen-users] PPPoE in DomU exits with error >> >> kanour-xen wrote: >>> Christian Lyra wrote: >>>>>>> I am trying to setup my firewall in DomU. However, I have got a >>>>> >>> little problem. My *pon dsl-provider *exits with following >>>>> >>> message. >>>>> > My firewall is a domU too, but it has control of the interface >>>>> > connected to the internet, and pppoe works just fine. never tried >>>>> > to do this with a bridge... >>>>> > >>>>> What do you mean by domU has control over the interface? >>>> I "hide" the interface from dom0 with pciback.hide=(xx:xx.x) in grub >>>> and present it to domU with pci = [ ''xx:xx.x'' ]. So the domU has >>>> control of the real pci device. >>>> >>>> >>> I tried that already, but when I included pciback.hide=(xx:xx.x) in >>> grub the card was still present. So, I then unbound it from /sys/... >>> I included pci =[..... and started domU. It was still the same. >>> >>> At this moment I don''t know what to do, but I will try to reinstall >>> everything and try one more time with Debian Etch xen binary packages. >>> >>> At this moment I am using Debian Lenny with binary xen from XenSource. >>> >>> I am just wondering why the hiding with pciback.hide does not work >>> for me? >>> >>> Jiri >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com >>> http://lists.xensource.com/xen-users >>> >> >> So, I did reinstall everything to Debian Etch. I am running xen from >> debian packages. But I just cannot make the pppoe work. >> >> Please help!!! >> >> I did hide the pci device on the boot. I checked that the driver >> (e1000) is not loaded in Dom0. >> I included pci statement in DomU config file. I checked that the >> devide was recognised and driver was loaded in DomU. >> >> I have it all on HP DL145 G2 server. There is AMD dual core processor, >> 2GB ram, 2x Broadcom network card and I added Intel PCI card in the >> raiser board (PCI-X). >> >> pppoeconf will discover pppoe on eth2 (intel 1G card) but when it >> tries to establish the connection. it fails with: >> >> Nov 18 09:44:40 alsfw01 pppd[1723]: Plugin rp-pppoe.so loaded. >> Nov 18 09:44:40 alsfw01 pppd[1723]: Linux kernel does not support >> PPPoE -- are you running 2.4.x? >> >> Could anyone help me to troubleshoot it. >> skype: linuxgo >> >> Jiri >> >> _______________________________________________ >> 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 >> > > Hi. > > Thanks very much for info.I am still working on it because I just cannot > figure it out. In dom0 pppoe is working fine. In domU it is not working. > Same kernel for both. Same automatic setup through pppoeconf. > > I just don''t know... > > Jiri > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >I am wondering if the problem could be amd64 kernels? Jiri _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christian Lyra wrote:> hi > > > Thanks very much for info.I am still working on it because I just cannot >>> figure it out. In dom0 pppoe is working fine. In domU it is not working. >>> Same kernel for both. Same automatic setup through pppoeconf. >>> >> I am wondering if the problem could be amd64 kernels? >> > > > i dont know what to say... but I´m sure that this is not amd64 > related, or at least shouldnt be because my setup IS amd64! but I´m > using a compiled xen 3.1, not the distro package/kernel. Anyway... I > just remember about something very dumb... but doesnt hurt to ask. I > assume that you are using the same kernel on dom0 and on domU right? > did you had copy the /lib/modules/<kernel> from dom0 to domU? as pppoe > is a module, and need to be loaded on domU! on my "firewall" domU I > have: > > fwx:~# lsmod > ... > pppoe 19968 2 > pppox 6672 1 pppoe > ppp_generic 34208 6 pppoe,pppox > slhc 10112 1 ppp_generic > >Hi Christian. I used xen-tools to create image, so the modules are there. Just to make sure, I just deleted them and copy them over from dom0. It is still the same.I believe that this is related to the hardware. This is real server HP 145 DL2 with PCI-X and I am starting to believe that the PCI-X with AMD chipset is the problem. I am wondering how come it does work from dom0 and not from domU. Could you copy me some info from your machine? ethtool [interface where you run pppoe] here is my interface: alsfw01:~# ethtool -i eth2 driver: e1000 version: 7.1.9-k4-NAPI firmware-version: N/A bus-info: 0000:00:01.0 alsfw01:~# ethtool eth2 Settings for eth2: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: umbg Wake-on: g Current message level: 0x00000007 (7) Link detected: yes Thanks. (I would need some xen guru for this) Where they are??? Jiri _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christian Lyra wrote:>> I used xen-tools to create image, so the modules are there. Just to >> make sure, I just deleted them and copy them over from dom0. It is >> still the same.I believe that this is related to the hardware. This >> is real server HP 145 DL2 with PCI-X and I am starting to believe >> that the PCI-X with AMD chipset is the problem. >> >> I am wondering how come it does work from dom0 and not from domU. >> >> Could you copy me some info from your machine? >> ethtool [interface where you run pppoe] >> >> here is my interface: >> >> alsfw01:~# ethtool -i eth2 >> driver: e1000 >> version: 7.1.9-k4-NAPI >> firmware-version: N/A >> bus-info: 0000:00:01.0 >> >> alsfw01:~# ethtool eth2 >> Settings for eth2: >> Supported ports: [ TP ] >> Supported link modes: 10baseT/Half 10baseT/Full >> 100baseT/Half 100baseT/Full >> 1000baseT/Full >> Supports auto-negotiation: Yes >> Advertised link modes: 10baseT/Half 10baseT/Full >> 100baseT/Half 100baseT/Full >> 1000baseT/Full >> Advertised auto-negotiation: Yes >> Speed: 1000Mb/s >> Duplex: Full >> Port: Twisted Pair >> PHYAD: 0 >> Transceiver: internal >> Auto-negotiation: on >> Supports Wake-on: umbg >> Wake-on: g >> Current message level: 0x00000007 (7) >> Link detected: yes >> >> Thanks. (I would need some xen guru for this) Where they are??? > > fwx:/home/lyra# ethtool internet > Settings for internet: > Supported ports: [ TP MII ] > Supported link modes: 10baseT/Half 10baseT/Full > 100baseT/Half 100baseT/Full > Supports auto-negotiation: Yes > Advertised link modes: 10baseT/Half 10baseT/Full > 100baseT/Half 100baseT/Full > Advertised auto-negotiation: Yes > Speed: 100Mb/s > Duplex: Full > Port: MII > PHYAD: 32 > Transceiver: internal > Auto-negotiation: on > Supports Wake-on: pumbg > Wake-on: d > Current message level: 0x00000007 (7) > Link detected: yes > > fwx:/home/lyra# ethtool -i internet > driver: 8139too > version: 0.9.27 > firmware-version: > bus-info: 0000:01:08.0 > > > > >Hi Christian. I am assuming that your interface info was from DomU. I actually compared few machines and all real (hw - not xen created) interfaces have PHYD [some number]. I mean in dom0 and other non xen machines. But in my case there is number zero (0) in DomU on physical interface parsed through pci backend. The problem is that I don''t know what it means :-). Maybe there should be some number and this indicates that it works as hardware interface. Another question, do you run udev or hotplug on DomU? I don''t. Jiri _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christian Lyra wrote:>> > >> > fwx:/home/lyra# ethtool -i internet >> > driver: 8139too >> > version: 0.9.27 >> > firmware-version: >> > bus-info: 0000:01:08.0 >> >> I am assuming that your interface info was from DomU. I actually >> compared few machines and all real (hw - not xen created) interfaces >> have PHYD [some number]. I mean in dom0 and other non xen machines. > > Oh... yes... real hardware on domU (pciback). > >> The problem is that I don''t know what it means :-). Maybe there >> should be some number and this indicates that it works as hardware >> interface. >> Another question, do you run udev or hotplug on DomU? I don''t. > > Yes. I do. From my z25_persistent-net.rules: > > > # Xen virtual device (8139too) > SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:e0:7d:d9:25:61", > NAME="internet" > > But i guess maybe you have a point about the pciex. But... as I > understand you got the interface running right? if you plug the > interface to your switch, it works? > >Yes the interface runs fine and it works. I can ping the ADSL modem no problem as other devices on the same subnet. Can you tell me one more thing in regards to bus-info above. Does the number there corresponds to lspci number of the same device in dom0? I have: Dom0 - 0000:86:01.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet Controller (rev 05) DomU alsfw01:~# ethtool -i eth2 > driver: e1000 > version: 7.1.9-k4-NAPI > firmware-version: N/A > bus-info: 0000:00:01.0 They don''t correspond to each other. Jiri _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
kanour-xen wrote:> Christian Lyra wrote: >>> > >>> > fwx:/home/lyra# ethtool -i internet >>> > driver: 8139too >>> > version: 0.9.27 >>> > firmware-version: >>> > bus-info: 0000:01:08.0 >>> >>> I am assuming that your interface info was from DomU. I actually >>> compared few machines and all real (hw - not xen created) interfaces >>> have PHYD [some number]. I mean in dom0 and other non xen machines. >> >> Oh... yes... real hardware on domU (pciback). >>> The problem is that I don''t know what it means :-). Maybe there >>> should be some number and this indicates that it works as hardware >>> interface. >>> Another question, do you run udev or hotplug on DomU? I don''t. >> >> Yes. I do. From my z25_persistent-net.rules: >> >> >> # Xen virtual device (8139too) >> SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:e0:7d:d9:25:61", >> NAME="internet" >> >> But i guess maybe you have a point about the pciex. But... as I >> understand you got the interface running right? if you plug the >> interface to your switch, it works? >> > > Yes the interface runs fine and it works. I can ping the ADSL modem no > problem as other devices on the same subnet. > > Can you tell me one more thing in regards to bus-info above. > Does the number there corresponds to lspci number of the same device in > dom0? > > I have: > Dom0 - 0000:86:01.0 Ethernet controller: Intel Corporation 82541PI > Gigabit Ethernet Controller (rev 05) > > DomU > alsfw01:~# ethtool -i eth2 > > driver: e1000 > > version: 7.1.9-k4-NAPI > > firmware-version: N/A > > bus-info: 0000:00:01.0 > > They don''t correspond to each other. > > Jiri > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >IT IS ALL GOOOOOOOODDDDDD !!!!!!!!!!! As soon as I installed UDEV it started to work. Thank you very much to all. 3 days of hard work for me and so stupid solution :-) Thanks one more time to Christian who provide me comparison to his system. jiri _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christian Lyra wrote:>> IT IS ALL GOOOOOOOODDDDDD !!!!!!!!!!! >> >> As soon as I installed UDEV it started to work. >> >> Thank you very much to all. 3 days of hard work for me and so stupid >> solution :-) >> >> Thanks one more time to Christian who provide me comparison to his >> system. > > hehehe. glad it work. No problem at all... you can contact me when you > need. > >I am not sure if my logic is right but it kind of make sense that udev have to run on domU in case we assign it physical hardware to it. I don''t do that normally, so I never needed udev in domU and I actually thought that udev suppose to NOT run in domU. I am not sure if there is some info about udev (run or not to run) in domU. Jiri _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users