Bug 523446

Summary: KVM: e1000 networking issues on Windows 2003 (inbox driver)
Product: Red Hat Enterprise Linux 5 Reporter: Daniel Paikov <dpaikov>
Component: kvmAssignee: Tim Burke <tburke>
Status: CLOSED DUPLICATE QA Contact: Lawrence Lim <llim>
Severity: high Docs Contact:
Priority: high    
Version: 5.4.zCC: hateya, llim, rlerch, tools-bugs, virt-maint, yeylon, ykaul
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-17 08:29:32 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 Flags
tcpdump file none

Description Daniel Paikov 2009-09-15 14:42:56 UTC
Created attachment 361092 [details]
tcpdump file

Windows 2003 VM using e1000 NIC consistently fails to complete Windows Update because of a networking failure. The same host has no Windows Update problems when configured with a RTL NIC. No errors are seen in dmesg or in the stdio.dump file. I'm attaching the tcpdump file from the Windows Update session.

Comment 1 Yaniv Kaul 2009-09-15 14:52:32 UTC
(In reply to comment #0)
> Created an attachment (id=361092) [details]
> tcpdump file
> 
> Windows 2003 VM using e1000 NIC consistently fails to complete Windows Update
> because of a networking failure. The same host has no Windows Update problems
> when configured with a RTL NIC. No errors are seen in dmesg or in the
> stdio.dump file. I'm attaching the tcpdump file from the Windows Update
> session.  

It's just with the e1000 inbox driver, right?

Comment 2 Daniel Paikov 2009-09-15 14:58:31 UTC
Oops, that's right - the issue only reproduces with the default Windows 2003 e1000 driver, the latest e1000 driver from support.intel.com doesn't have this issue.

Comment 3 yeylon@redhat.com 2009-09-15 18:08:01 UTC
please add to RN that the driver must be updated!!!

Comment 5 Yaniv Kaul 2009-09-17 08:29:32 UTC

*** This bug has been marked as a duplicate of bug 510840 ***