Bug 510840
| Summary: | win23k/32bit failed to ping host when using windows e1000 inbox driver and vice versa. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Miya Chen <michen> | ||||||
| Component: | kvm | Assignee: | Eduardo Habkost <ehabkost> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Lawrence Lim <llim> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 5.4 | CC: | ccurran, dpaikov, dyasny, jiyang, lihuang, ovirt-maint, tburke, tools-bugs, virt-maint, yeylon, ykaul | ||||||
| Target Milestone: | rc | Keywords: | Reopened | ||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-10-29 13:51:08 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Miya Chen
2009-07-11 12:40:50 UTC
Created attachment 351340 [details]
tcpdump file using "tcpdump -w tcpdump_e1000.pcap -s 1500"
Try installing Intel's drivers, see if the problem persists. 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]# Created attachment 351440 [details]
ping from guest to host
Since jiyang cannot reproduce the bug, could u please retest on another machines? 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. *** Bug 523446 has been marked as a duplicate of this bug. *** (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. 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 (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. 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 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 |