Bug 510840 - win23k/32bit failed to ping host when using windows e1000 inbox driver and vice versa.
Summary: win23k/32bit failed to ping host when using windows e1000 inbox driver and vi...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kvm
Version: 5.4
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Eduardo Habkost
QA Contact: Lawrence Lim
URL:
Whiteboard:
: 523446 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-11 12:40 UTC by Miya Chen
Modified: 2014-03-26 00:58 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-29 13:51:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
tcpdump file using "tcpdump -w tcpdump_e1000.pcap -s 1500" (120.12 KB, application/octet-stream)
2009-07-11 12:41 UTC, Miya Chen
no flags Details
ping from guest to host (28.83 KB, image/png)
2009-07-13 08:20 UTC, jiyang
no flags Details

Description Miya Chen 2009-07-11 12:40:50 UTC
Description of problem:


Version-Release number of selected component (if applicable):
kvm-83-87.el5

How reproducible:
100%

Steps to Reproduce:
1.start guest:
/usr/libexec/qemu-kvm -no-hpet -usbdevice tablet -rtc-td-hack -drive file=win23k-64.qcow2,if=ide -cpu qemu64,+sse2 -vnc :16 -net nic,vlan=0,macaddr=20:20:20:00:49:81,model=e1000 -net tap,vlan=0,script=/mnt/images/qemu-ifup -m 1G -smp 4
2.Issue 'ping $hostip' in cmd.

  
Actual results:
Guest failed to ping it's own host.(tcpdump will be attached)
Host failed to ping guest.
Guest can ping external network.

Expected results:


Additional info:
Tried in win28k, vista and 32bitwin23k with e1000, they do not have this problem.

Comment 1 Miya Chen 2009-07-11 12:41:24 UTC
Created attachment 351340 [details]
tcpdump file using "tcpdump -w tcpdump_e1000.pcap -s 1500"

Comment 2 Yaniv Kaul 2009-07-11 13:05:21 UTC
Try installing Intel's drivers, see if the problem persists.

Comment 3 jiyang 2009-07-13 08:19:49 UTC
Can not reproduce the issue:

CLI: 
 /usr/libexec/qemu-kvm -no-hpet -usbdevice tablet -rtc-td-hack -drive file=/data/images/win2003-64.qcow2,if=ide -cpu qemu64,+sse2 -net nic,vlan=0,macaddr=20:20:20:00:49:81,model=e1000 -net tap,vlan=0,script=/etc/qemu-ifup -m 1G -smp 4 -vnc :16

ping from host to guest :
[root@dhcp-66-70-78 images]# ping 10.66.70.108
PING 10.66.70.108 (10.66.70.108) 56(84) bytes of data.
64 bytes from 10.66.70.108: icmp_seq=1 ttl=128 time=0.607 ms
64 bytes from 10.66.70.108: icmp_seq=2 ttl=128 time=0.324 ms
64 bytes from 10.66.70.108: icmp_seq=3 ttl=128 time=0.257 ms

--- 10.66.70.108 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 0.257/0.396/0.607/0.151 ms
[root@dhcp-66-70-78 images]#

Comment 4 jiyang 2009-07-13 08:20:33 UTC
Created attachment 351440 [details]
ping from guest to host

Comment 5 Lawrence Lim 2009-07-13 18:16:10 UTC
Since jiyang cannot reproduce the bug, could u please retest on another machines?

Comment 9 Miya Chen 2009-08-12 10:39:44 UTC
Try in 83-105, this problem exits in guest of 32bitwin2003 when using windows build-in e1000 driver.

Steps to Reproduce:
1.start guest:
/usr/libexec/qemu-kvm -no-hpet -rtc-td-hack -drive file=win2003-32.raw,if=ide -cpu qemu64,+sse2 -m 16G -smp 8 -net nic,macaddr=20:20:20:00:00:11,model=e1000,vlan=2 -net tap,script=/etc/qemu-ifup,vlan=2 -vnc :11&
2.Issue 'ping $hostip' in cmd.


Actual results:
Guest failed to ping it's own host.(tcpdump will be attached)
Host failed to ping guest.
Guest can ping external network.

Addtional:
when using intel e1000 driver, this problem does exist.
64bitwin2003 does not have this problem.

Comment 10 Yaniv Kaul 2009-09-17 08:29:33 UTC
*** Bug 523446 has been marked as a duplicate of this bug. ***

Comment 11 Miya Chen 2009-09-22 04:30:57 UTC
(In reply to comment #9)
> Try in 83-105, this problem exits in guest of 32bitwin2003 when using windows
> build-in e1000 driver.
> 
> Steps to Reproduce:
> 1.start guest:
> /usr/libexec/qemu-kvm -no-hpet -rtc-td-hack -drive file=win2003-32.raw,if=ide
> -cpu qemu64,+sse2 -m 16G -smp 8 -net
> nic,macaddr=20:20:20:00:00:11,model=e1000,vlan=2 -net
> tap,script=/etc/qemu-ifup,vlan=2 -vnc :11&
> 2.Issue 'ping $hostip' in cmd.
> 
> 
> Actual results:
> Guest failed to ping it's own host.(tcpdump will be attached)
> Host failed to ping guest.
> Guest can ping external network.
> 
> Addtional:
> when using intel e1000 driver, this problem does exist.
> 64bitwin2003 does not have this problem.  

Change wrong additional info:
when using intel e1000 driver, this problem does not exist.

Comment 12 Christopher Curran 2009-10-22 04:42:07 UTC
Yaniv, 

In Bug 523446, comments #3 and #4 contradict each other. What should I write from the release note for this bug for the RHEV Hypervisor release?

Chris

Comment 13 Yaniv Kaul 2009-10-22 05:36:13 UTC
(In reply to comment #12)
> Yaniv, 
> 
> In Bug 523446, comments #3 and #4 contradict each other. What should I write
> from the release note for this bug for the RHEV Hypervisor release?
> 
> Chris  

Yes, I wouldn't write that we can use the drivers - not sure we can.

Comment 14 Christopher Curran 2009-10-22 06:40:30 UTC
I wrote:

The default e1000 network driver with Windows Server 2003 32 bit versions does not work. Use an alternative driver or an updated driver.

Does that summarize it and fit within the restriction?

Chris

Comment 15 Yaniv Kaul 2009-10-29 13:57:48 UTC
Chris, you (In reply to comment #14)
> I wrote:
> 
> The default e1000 network driver with Windows Server 2003 32 bit versions does
> not work. Use an alternative driver or an updated driver.

An alternate device. 

> 
> Does that summarize it and fit within the restriction?
> 
> Chris


Note You need to log in before you can comment on or make changes to this bug.