Server, Windows 2008, X64 with Hyper-V RC0

Guest Windows 2003, SP2, Integration Services, and fully patched.

When using the synthetic network adapter I get great speed to the virtual
guest, but almost nothing on the transmit side.

I can browse the internet but not use windows update. I can run speed tests
but all fail on the upload portion. I can map a drive and copy files from a
file server on our network, but not from the virtual guest to the same
mapped drive.

I have 2 Intel 1000 PT and 2 Intel 1000 EB cards in the host.

These are teamed into a quad LACP (802.11ad) team.

I am also running 2 tagged VLANS (no untagged vlans)

The results do not change if I disable 3 out of 4 of the team members.

The host server does not have any network problems.

I could really use some looking into this. For now I am going back to
the legacy adapter that works in both directions just 4-5 times slower.

As a test I have reduced the complexity.
single network adapter

Intel Pro 1000 EB With I/O Acceleration

Latest driver

No team

No VLANs

No teaming config on the switch

Same issue. Great speed with synthetic network but only to the guest. (15
seconds to copy a file to the guest, 180 minutes (estimated) to copy it
back, but typically it fails)

I have the same problem with Windows Update on hyper-v rc0 running server
2003 R2 X64.

I keep reloading the OS and still have the error.

"RSG" wrote:

> As a test I have reduced the complexity.
> single network adapter
>
> Intel Pro 1000 EB With I/O Acceleration
>
> Latest driver
>
> No team
>
> No VLANs
>
> No teaming config on the switch
>
> Same issue. Great speed with synthetic network but only to the guest. (15
> seconds to copy a file to the guest, 180 minutes (estimated) to copy it
> back, but typically it fails)
>
>
>

I think you will find that if you add a legacy virtual adapter you will be
able to get the windows update completed.

but you will still have problems with the synthetic one after all the
updates.

Let me know if you find anything different.


"Steve" <Steve@discussions.microsoft.com> wrote in message
news:1D8562AD-3C3D-4003-952B-6DA224D04AF0@microsoft.com...
>I have the same problem with Windows Update on hyper-v rc0 running server
> 2003 R2 X64.
>
> I keep reloading the OS and still have the error.
>
> "RSG" wrote:
>
>> As a test I have reduced the complexity.
>> single network adapter
>>
>> Intel Pro 1000 EB With I/O Acceleration
>>
>> Latest driver
>>
>> No team
>>
>> No VLANs
>>
>> No teaming config on the switch
>>
>> Same issue. Great speed with synthetic network but only to the guest. (15
>> seconds to copy a file to the guest, 180 minutes (estimated) to copy it
>> back, but typically it fails)
>>
>>
>>

Correct. I just found that out. However, the legacy network adapter only
works in 32-bit guests because there is not 64-bit driver for 2003 64-bit.

This appears to be a bug in RC0. Hopefully there will be a fix shortly.

"RSG" wrote:

> I think you will find that if you add a legacy virtual adapter you will be
> able to get the windows update completed.
>
> but you will still have problems with the synthetic one after all the
> updates.
>
> Let me know if you find anything different.
>
>
> "Steve" <Steve@discussions.microsoft.com> wrote in message
> news:1D8562AD-3C3D-4003-952B-6DA224D04AF0@microsoft.com...
> >I have the same problem with Windows Update on hyper-v rc0 running server
> > 2003 R2 X64.
> >
> > I keep reloading the OS and still have the error.
> >
> > "RSG" wrote:
> >
> >> As a test I have reduced the complexity.
> >> single network adapter
> >>
> >> Intel Pro 1000 EB With I/O Acceleration
> >>
> >> Latest driver
> >>
> >> No team
> >>
> >> No VLANs
> >>
> >> No teaming config on the switch
> >>
> >> Same issue. Great speed with synthetic network but only to the guest. (15
> >> seconds to copy a file to the guest, 180 minutes (estimated) to copy it
> >> back, but typically it fails)
> >>
> >>
> >>
>
>
>

Of course.
Although I am only using 32 bit guests right now, the speed out of the vm
bus adapter is sooo much better, is only it worked.


"Steve" <Steve@discussions.microsoft.com> wrote in message
news:80A9A2C2-8DDE-463B-8B5C-43582F11CBE1@microsoft.com...
> Correct. I just found that out. However, the legacy network adapter only
> works in 32-bit guests because there is not 64-bit driver for 2003 64-bit.
>
> This appears to be a bug in RC0. Hopefully there will be a fix shortly.
>
> "RSG" wrote:
>
>> I think you will find that if you add a legacy virtual adapter you will
>> be
>> able to get the windows update completed.
>>
>> but you will still have problems with the synthetic one after all the
>> updates.
>>
>> Let me know if you find anything different.
>>
>>
>> "Steve" <Steve@discussions.microsoft.com> wrote in message
>> news:1D8562AD-3C3D-4003-952B-6DA224D04AF0@microsoft.com...
>> >I have the same problem with Windows Update on hyper-v rc0 running
>> >server
>> > 2003 R2 X64.
>> >
>> > I keep reloading the OS and still have the error.
>> >
>> > "RSG" wrote:
>> >
>> >> As a test I have reduced the complexity.
>> >> single network adapter
>> >>
>> >> Intel Pro 1000 EB With I/O Acceleration
>> >>
>> >> Latest driver
>> >>
>> >> No team
>> >>
>> >> No VLANs
>> >>
>> >> No teaming config on the switch
>> >>
>> >> Same issue. Great speed with synthetic network but only to the guest.
>> >> (15
>> >> seconds to copy a file to the guest, 180 minutes (estimated) to copy
>> >> it
>> >> back, but typically it fails)
>> >>
>> >>
>> >>
>>
>>
>>

Some cross posting that s a bit

"
Can you try with the DisableTaskOffload functionality as noted on this page?



http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentry/94176.mspx?mfr=true"



When done on both guest and host things are working better for me. I have to
test more to see what the best options are.


"RSG" <scott_garrett@hotmail.com> wrote in message
news:OO0OWsOlIHA.5084@TK2MSFTNGP04.phx.gbl...
> Of course.
> Although I am only using 32 bit guests right now, the speed out of the vm
> bus adapter is sooo much better, is only it worked.
>
>
> "Steve" <Steve@discussions.microsoft.com> wrote in message
> news:80A9A2C2-8DDE-463B-8B5C-43582F11CBE1@microsoft.com...
>> Correct. I just found that out. However, the legacy network adapter only
>> works in 32-bit guests because there is not 64-bit driver for 2003
>> 64-bit.
>>
>> This appears to be a bug in RC0. Hopefully there will be a fix shortly.
>>
>> "RSG" wrote:
>>
>>> I think you will find that if you add a legacy virtual adapter you will
>>> be
>>> able to get the windows update completed.
>>>
>>> but you will still have problems with the synthetic one after all the
>>> updates.
>>>
>>> Let me know if you find anything different.
>>>
>>>
>>> "Steve" <Steve@discussions.microsoft.com> wrote in message
>>> news:1D8562AD-3C3D-4003-952B-6DA224D04AF0@microsoft.com...
>>> >I have the same problem with Windows Update on hyper-v rc0 running
>>> >server
>>> > 2003 R2 X64.
>>> >
>>> > I keep reloading the OS and still have the error.
>>> >
>>> > "RSG" wrote:
>>> >
>>> >> As a test I have reduced the complexity.
>>> >> single network adapter
>>> >>
>>> >> Intel Pro 1000 EB With I/O Acceleration
>>> >>
>>> >> Latest driver
>>> >>
>>> >> No team
>>> >>
>>> >> No VLANs
>>> >>
>>> >> No teaming config on the switch
>>> >>
>>> >> Same issue. Great speed with synthetic network but only to the guest.
>>> >> (15
>>> >> seconds to copy a file to the guest, 180 minutes (estimated) to copy
>>> >> it
>>> >> back, but typically it fails)
>>> >>
>>> >>
>>> >>
>>>
>>>
>>>
>
>

Yep that ed me too. WU on my guest works now. I did not yet try it on
the host.

Thanks, Steve

"RSG" wrote:

> Some cross posting that s a bit
>
> "
> Can you try with the DisableTaskOffload functionality as noted on this page?
>
>
>
> http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/regentry/94176.mspx?mfr=true"
>
>
>
> When done on both guest and host things are working better for me. I have to
> test more to see what the best options are.
>
>
> "RSG" <scott_garrett@hotmail.com> wrote in message
> news:OO0OWsOlIHA.5084@TK2MSFTNGP04.phx.gbl...
> > Of course.
> > Although I am only using 32 bit guests right now, the speed out of the vm
> > bus adapter is sooo much better, is only it worked.
> >
> >
> > "Steve" <Steve@discussions.microsoft.com> wrote in message
> > news:80A9A2C2-8DDE-463B-8B5C-43582F11CBE1@microsoft.com...
> >> Correct. I just found that out. However, the legacy network adapter only
> >> works in 32-bit guests because there is not 64-bit driver for 2003
> >> 64-bit.
> >>
> >> This appears to be a bug in RC0. Hopefully there will be a fix shortly.
> >>
> >> "RSG" wrote:
> >>
> >>> I think you will find that if you add a legacy virtual adapter you will
> >>> be
> >>> able to get the windows update completed.
> >>>
> >>> but you will still have problems with the synthetic one after all the
> >>> updates.
> >>>
> >>> Let me know if you find anything different.
> >>>
> >>>
> >>> "Steve" <Steve@discussions.microsoft.com> wrote in message
> >>> news:1D8562AD-3C3D-4003-952B-6DA224D04AF0@microsoft.com...
> >>> >I have the same problem with Windows Update on hyper-v rc0 running
> >>> >server
> >>> > 2003 R2 X64.
> >>> >
> >>> > I keep reloading the OS and still have the error.
> >>> >
> >>> > "RSG" wrote:
> >>> >
> >>> >> As a test I have reduced the complexity.
> >>> >> single network adapter
> >>> >>
> >>> >> Intel Pro 1000 EB With I/O Acceleration
> >>> >>
> >>> >> Latest driver
> >>> >>
> >>> >> No team
> >>> >>
> >>> >> No VLANs
> >>> >>
> >>> >> No teaming config on the switch
> >>> >>
> >>> >> Same issue. Great speed with synthetic network but only to the guest.
> >>> >> (15
> >>> >> seconds to copy a file to the guest, 180 minutes (estimated) to copy
> >>> >> it
> >>> >> back, but typically it fails)
> >>> >>
> >>> >>
> >>> >>
> >>>
> >>>
> >>>
> >
> >
>
>
>