I have been running Hyper-V on a Server 2008 SuperMicro box for several months now, and because it was running so flawlessly, we recently decided to purchase a very expensive HP setup with 2 onboard NIC's and 2, 4 port Gig NIC's (among other specs).
We are also purchased an EMC SAN and will be moving our SQL database, file storage, etc. out to this new storage.
In building out the new HP, I have decided to use Server 2008 R2, as it recently became available to us. Durring this process we also threw SCVMM onto one of our servers and have succesfully ran through several P2V migrations.
Last Thursday, we ran a P2V on a server that was hosting Microsoft Dynamics CRM. The process went well, or so we thought, as we found this Monday our CRM randomly having issues serving reports. This is a side note to the actual question, but I did want to throw this out there as this is in need of attention too...
Besides the CRM issue, the problems that I am needing help with have seemed to just start after this last P2V... On Monday, I attempted to do a normal migration (V2V) using our SCVMM and moving a VM from 1 host to another. This failed, and failed again, and again. I have now tried different VM's, different directions between the hosts (Server A to Server B and Server B to Server A) and now have even thrown a 3rd test Hyper-V host at the mix and I am failing there too.
The errors are pretty much unhelpful, as it just states that the SCVMM is probably being rebooted??? The only things that I have found on this state that I should look to update my Hyper-V with a new patch, however 2 of the 3 servers already have this patch and wont take it. BTW, these 2 server that already have it are both Server 2008 R2, while the other is Server 2008 and will have this patch installed once I am able to reboot in a bit. It does not fail at the same % every time, as these are different per VM that I try and migrate, however it is always crashing SCVMM right after the copying process completes.
At this point, I had to get a VM moved over, so I decided to do it the old fashion way and export and import to the other server. Worked great.... Until today, where now I am getting an error when trying to import a machine, as I am getting an error of an invalid argument. From searching, the fix for this error is to open the .exp file and delete the GUID of the hard disk from the old server.... why this worked before, I dont know, however once doing this, I then get a different argument error.
Finally, these issues asside, I am trying to continue with preparing for the SAN implementation and was planning to come back to these as if nothing else, I could just copy over a .VHD and manually re-setup the machines... This brings me to the final issue (so far): I have teamed 4 of the 8 extra NIC's and named them Team-1. I then go into Virtual Network Manager and add them as an available external network adapater. These are attached to a VLan, however I am a little shaky with what needs to be done here, however I have tried both adding a VLan ID and not... in either case, I was initially getting an error that the NIC was already bound to another virtual network. I found this link:
http://nathanlasnoski.spaces.live.com/Blog/cns!F7A33F1F9EBD9237!455.entry which enabled me to at least create the network swithces whithin the Virtual Network Manager. Now,I go to the VM settings, add a network port, and choose Team-1. This all seems fine until I hit apply, at which point I get "Error Applying Network Adapter Changes Failed to add device 'Microsoft Synthetic Ethernet Port'." WHAT THE HECK!!! I have googled this as well and just cannot find anything to help me.
Any help on ANY of this would be much appriciated.
