I set up System Center Virtual Machine Manager some time ago. We barely use it, except to do conversions from VMWare to Hyper-V. When I initially set it up, it worked fine for this purpose. Now, when I try to do a V2V conversion, the job fails during the transfer of data over BITS; it says that the connection timed out. The source VM, destination, and SCVMM machine are all the same machine. I've looked at the event logs, and I see the URL that is trying to be accessed by BITS. I've popped that URL into my browser, and it doesn't work. I've tried packet captures, but the traffic never appears on any of the adapters since it is all loopback traffic. When I try the hostname of the URL in a manual telnet session to the SSL port, I get a connection, so I know something is listening. I checked the SSL cert bindings, and I beleive that a cert is bound. I don't get any errors in my browser regarding certs when I try. I did try trimming the URL up a bit, and I am getting 404 errors when I try the top level directory. However, SCVMM uses BITS for the transfer, not pure HTTP, so I may not be doing the right kind of test.
UPDATE: I tried it with a VMWare VM copied from a different server, it magically worked. So, somehow, SCVMM's ability to dish out the file is based on the file itself. I also tried to start the same said VM on a different machine, under VMWare Workstation, and it failed too. There is something very, very wrong here. It could have occured on the transfer to the SCVMM machine (I doubt it, I tried twice), or it could be something not right about VMWare Server.
Any help would be much appreciated! I've been banging my head on this for half of a week now.
Thanks!
J.Ja
Best Answer
As I understand BITS - it's a sort of low-priority service. If other network traffic on that machine (presumably, the existing VMs) are saturating that bandwidth, BITS would (working as intended) never get a chance.
Do you have the luxury of suspending the other VMs to see if the timeouts persist?