xen networking problem, no peth0 in ifconfig

Bug #145387 reported by Fastguy
4
Affects Status Importance Assigned to Milestone
xen-3.1 (Ubuntu)
Fix Released
Undecided
Chuck Short

Bug Description

After installing updates of 25/9/2007, my Ubuntu Gutsy test system doesn't have the peth0 interface anymore in the output of ifconfig -a and thus xen networking does not work. Xen configuration files seems to be OK.

System runs 2.6.22-12-xen Dom0 kernel with Xen 3.1 packages from repositories.

Here's the output of ifconfig -a when XEN is running:

===========

root@enterprise:/home/emre# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:18:F3:9D:6E:FC
          inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::218:f3ff:fe9d:6efc/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:5706 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6025 errors:0 dropped:0 overruns:0 carrier:1
          collisions:0 txqueuelen:1000
          RX bytes:3282620 (3.1 MB) TX bytes:1300213 (1.2 MB)

lo 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:262 errors:0 dropped:0 overruns:0 frame:0
          TX packets:262 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:14260 (13.9 KB) TX bytes:14260 (13.9 KB)

veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
          BROADCAST MULTICAST MTU:1500 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)

veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
          BROADCAST MULTICAST MTU:1500 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)

veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00
          BROADCAST MULTICAST MTU:1500 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)

veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00
          BROADCAST MULTICAST MTU:1500 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)

vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
          BROADCAST MULTICAST MTU:1500 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)

vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
          BROADCAST MULTICAST MTU:1500 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)

vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
          BROADCAST MULTICAST MTU:1500 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)

vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
          BROADCAST MULTICAST MTU:1500 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)

xenbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:67 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b) TX bytes:2420 (2.3 KB)

=========

Best regards,

Emre

Revision history for this message
Fastguy (erenoglu) wrote :

Dom0 network runs fine by the way...

Changed in xen-3.1:
assignee: nobody → zulcss
Revision history for this message
Fastguy (erenoglu) wrote :

The syslog xen related sections are attached...

It appears that the script is trying to use xenbr1, but it doesn't exist in the system. xenbr1 once existed when my Attansic L1 ethernet card didn't work reliably with xen, and I was using a USB ethernet. I don't use it anymore, but XEN is stuck with it somehow...

Emre

Revision history for this message
Fastguy (erenoglu) wrote :

I replugged my USB adapter and connected the ethernet to that, rebooted the system, and now it works.

The xen bridge is still xenbr0, but peth0 came back. Continues to work if I unplug now the USB and plug the cable back to the onboard controller. Won't survive a reboot though, peth0 dissapears if usb card is not there...

Emre

Revision history for this message
Todd Deshane (deshantm) wrote :

This sounds more like it might be a udev problem.

try moving /etc/udev/rules.d/70-persistent-net.rules
something like:

$ sudo mv /etc/udev/rules.d/70-persistent-net.rules /etc/udev/rules.d/70-persistent-net.rules.bak

And then reboot. udev will re-create this file based on the new setup.

Revision history for this message
Fastguy (erenoglu) wrote :

Hi Todd,

Thanks for the comment. Unfortunately, problem still persists even though I renamed the udev rule and rebooted.

I have the same ifconfig -a output as in my first post, networking doesn't work...

Maybe it's time to make a full-reinstall...

Best regards,

Emre

Revision history for this message
Jeff Anderson (jander99) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in xen-3.1 (Ubuntu):
status: New → Incomplete
Revision history for this message
Chuck Short (zulcss) wrote :

I think this has been fixed for a while now. Please re-open if I am wrong.

Changed in xen-3.1 (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.