Transferring large file across network to a virtual server machine locks network.
msnews.microsoft.com
a dead hit. The only problem is the thread is somewhat dangling and does
not answer the question definitively.
The problem: You start an instance of Server 2003 inside a Virtual Server
2005 service. Login (remote desktop) to the virtual PC (Server 2003) and
transfer a large file across the network (say, Windows Server SP1 @ 300MB).
After a while the network drops on the guest OS >AND< on the HOST server.
I have seen this happen in several environments consistently. The host OS
is always Windows Server 2003 SP1 and the guest OS is Windows Server 2003
SP0 and SP1. In all of these situations the nic is piggybacked to the real
nic on the host machine.
The thread I found suggested binding the virtual machine to a seperate nic.
Is this the solution and has anyone verified that it works. I do not
currently have the capacity to test it.
Thanks,
David
Jeroen van den Bos
It appears to be some kind of "traffic jam": whenever I attempt to copy
a large file to a VM its network connection just goes down, sometimes
even the host's as well. This has even happened when I tried to read
large amounts of data (~1GB) from a share directly on the host server.
JayDubb
problem for us. Our backup procedures had to be altered in ways we do not
like, because we couldn't transfer backup sets from VM to our backup array
without the network connection bombing out. We have a temporary band aid on
it, but it is not scalable, nor is it all that workable a solution.
We're limping along for now, hoping that SP1 will address this. If not, we
aren't going to have much choice but to abandon the VS/VM solutions we were
counting on using. Not being able to transfer large files is a HUGE
embarrassment for MS's VM program.
JANR
THere several posting adrsseing this matter.
In my cased some changes on the network adapter (host machine) solved this
problem totally.
Jan
"JayDubb" <j...@dubb.nowhere.org> schreef in bericht
news:42F4B195...@dubb.nowhere.org...
ke...@kmsi.net
posting them? Even if you aren't sure which made the difference, the
information could be useful.
/kenw
Ken Wallewein
K&M Systems Integration
Phone (403)274-7848
Fax (403)275-4535
ke...@kmsi.net
www.kmsi.net
Jan Radstaake
I'm at work now and found it:
I changed all "offload settings" on the NIC's to disabele of off, after
resetting and VS (and thus all VM's also) itself all problemens were
gone....
Jan
<ke...@kmsi.net> wrote in message
news:shjcf1dhj7duav738...@4ax.com...
Jan Radstaake
see also:
http://support.microsoft.com/default.aspx?scid=kb;en-us;888750
Jan
"Jan Radstaake" <j.rad...@pinkroccade.com> wrote in message
news:OMg3jTAn...@TK2MSFTNGP12.phx.gbl...
ke...@kmsi.net
>I'm at work now and found it:
>I changed all "offload settings" on the NIC's to disabele of off, after
>resetting and VS (and thus all VM's also) itself all problemens were
>gone....
>
>Jan
Fascinating. That implies that the offloading doesn't handle context
switches well. I've had Intel engineers recommend against using offloading
as well, saying that most modern PCs don't benefit from it. Sounds like
there's more to the story.
Jeroen van den Bos
TCP segmentation offloading, and now I could easily copy 3.5GB around
to/from the host. So this is actually the fix! (At least for me anyway)
David Wang [Msft]
several other people already...
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"JayDubb" <j...@dubb.nowhere.org> wrote in message
news:42F4B195...@dubb.nowhere.org...
JayDubb
>
> Does disabling TCP offloading help in your situation? Seems to help for
> several other people already...
We tried that after reading posts here about it. Unfortunately, it did not
work. For example, when transferring a file of 3 GB (nightly backup, we use
disk imaging) the transfer bombs out somewhere between 300MB and 1GB, or so.
Sometimes more, sometimes less.
VM --> Backup Array = Failure
VM --> VS HOST, then VS HOST --> Backup Array = Success
Neither of the NICs in the chassis (Intel SR1325TP1-E) can be dedicated solely
to the VM. We use one for the public network, the other for private
(management, backups) traffic.
The same NIC that bombs out on VM transfers, works just fine when the physical
host transfers large files across it. There are no errors recorded on the
switchport, and we have already swapped patch cables and switchports, so we
can safely assume the physical network is OK.