Bug 258

Summary: [Qemu] All qemu targets fail to get network access
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: Jiajun Xu <jiajun.xu>
Component: meta-yoctoAssignee: Kevin Tian <kevin.tian>
Status: VERIFIED INVALID QA Contact:
Severity: critical    
Priority: High CC: kevin.tian, poky.bs.watcher, poky.watcher, richard.purdie, sgw
Version: 0.9   
Target Milestone: 0.9 M3   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Program Management Documentation change: ---

Description Jiajun Xu 2010-09-02 05:44:06 UTC
Testing Env:    
Host: Ubuntu 10.04 LTS
Kernel: 2.6.32-21-generic-pae
Poky gitinfo(used to build qemu-native):
e300aa048531a5a11c4c87848551e5541b5b3022 (git.pokylinux.org:poky-wr
+yocto-kernel-clean)
All images file from http://autobuilder.pokylinux.org/nightly/20100831-1/.


There is no network for all qemu targets after booting up. After booting, in qemu, we can see eth0 get IP address "192.168.7.2", but we can not connect to host address "192.168.7.1".

The tap0, tap1 seems setup correctly:
############
tap0      Link encap:Ethernet  HWaddr 06:56:5e:b9:7f:5b
          inet addr:192.168.7.1  Bcast:192.168.7.255  Mask:255.255.255.0
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:2510 errors:0 dropped:0 overruns:0 frame:0
          TX packets:165 errors:0 dropped:340 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:419120 (419.1 KB)  TX bytes:32718 (32.7 KB)

tap1      Link encap:Ethernet  HWaddr 56:81:d2:d9:cd:16
          inet addr:192.168.7.2  Bcast:192.168.7.255  Mask:255.255.255.0
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:22 errors:0 dropped:20 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:0 (0.0 B)  TX bytes:3566 (3.5 KB)
###########

Reproduce Steps:
1. Download qemu images from above URL
2. git clone poky tree and checkout the commit stated above
3. build qemu-native and related staffs
4. start qemu and check the network information by "ifconfig", ping "192.168.7.1", which is host's tap0 ip address, in qemu.
Comment 1 Kevin Tian 2010-09-02 20:18:46 UTC
I just built an incremental arm image with latest poky master. The network just works fine. I can ssh into the target image.

I took a quick look at git log. No fortune to find related commits.
Comment 2 Jiajun Xu 2010-09-03 06:41:50 UTC
(In reply to comment #1)
> I just built an incremental arm image with latest poky master. The network just
> works fine. I can ssh into the target image.
> I took a quick look at git log. No fortune to find related commits.

After I reboot my system, the issue disappear. I will try to find a reproducible way for the issue.
Comment 3 Jiajun Xu 2010-09-07 08:37:25 UTC
Since I can not reproduce the bug now, I mark the bug as INVALID here.