Hello,

is this possible to make a P2V conversion using SCVMM 2012 to XenServer?

Regards

My setup first:

Server 1 : ESXi 4.1, using local disk storage only

Server 2 : Windows 2008 R2 Data Center 64bit, SP1 installed, Hyper-V Role Enabled. SCVMM Server & Console installed on here, server is on the domain. Local storage. Nothing fancy in either of these.

I want to move all the VM's from server 1 to server 2.

I was not able to register the ESXi server in SCVMM, I couldn't confirm if this could be done or not.

What I decided to do, was use SCVMM and do a P2V migration of each machine.

So, did the first machine (SQL1), confirmed VMWare Tools are NOT installed, launched the Live Migration wizard from SCVMM, pointed it at the SQL1 machine, stepped through, no issues everything worked perfectly. It's currently running on the new Server 2 right now.

Went to do the next machine (WEB1), confirmed VMWare Tools are NOT installed, launched the Live Migaration wizard again, pointed it at the WEB1 machine, stepped through, NO ERRORS were given, however once done and it booted up, I had no networking, and no pointer intergration. SCVMM indicates that the intergration services are installed, I also reinstalled them manually both from a shutdown state and also using the "CD", still no pointer intergration. For the Network card, it just doesn't even appear, in the device manager I don't even have a networking node, and in the network adapters list, it's completely blank no icons.

Both servers are Windows 2008 Standard Edition 64bit. The only major different between then, is SQL1 did NOT have SP1 installed before the migration. WEB1 does currently have SP1 installed BEFORE the migration.

Any help is appericated.

Edit : Some more information, on WEB1 (the not working server), all the Hyper-V services are running (5 of them). If am in the SCVMM console and I send a shutdown signal (right click->shutdown) I get the error message that I cannot shut it down because the Guest Services are not running or it is not supported. The number along with this shutdown message is 1735.

Edit 2 : Adding a new Network Adapter does work, so I can get the network working and moved to the new one, But the mouse is still not functional. I'd like to know either why way this didn't work.

Cross posted from here as recommended : http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/74ee0bcd-7fd1-4fa2-ab90-66ba71571000

As it says on the tin?

I have carried out a couple of successful V2V's from VMware > Hyper-V failover cluster with CSV using SCVMM 2008 R2 SP1successfully. I tried to carry out a V2V from a VMware VM that had 256GB virtual hard disks. This failed with an error 2606 and is apparantly fixed in the latest SCVMM hotfix rollup due to an issue with the available disk space on the system volume of the Hyper-V host that the VM is being migrated to:

http://support.microsoft.com/kb/2562466/en-us?sd=rss&spid=14555

My question is therefore:

How does this V2V migration occur?

Does SCVMM copy the VmWare VM files to the host, convert to vhd then copy to CSV?
Or does it copy the VmWare VM files to the SCVMM library, convert them to vhd then copy to CSV?
Or does it copy and convert directly to CSV (if so why would it require disk space on the system volume of the host?)?

In any case I have applied the SCVMM hotfix rollup but I am interested to understand the mechanism as I am unable to find any documentation on the process from the  MS knowledgebase. Thanks.

Microsoft Partner

I have a hyperv cluster windows 2008 r2 enterprise edition. I wanted to some P2V conversion so I installed the SCVMM 2008 R2 on another server which is a member of the same domain as the hyperv cluster. During a test P2V, the job fails with this error,

--------

VMM is unable to complete the requested file transfer. The connection to the HTTP server <server> could not be established.
 (Unknown error (0x80072ee2))

Recommended Action
Ensure that the HTTP service and/or the agent on the machine <server> are installed and running and that a firewall is not blocking HTTPS traffic

--------

When I choose to restart the job it says it cannot find the path X:\VmName . How do i resolve this error. The path is supposed to be the location where I wanted to place the VM during the failed P2V. I have checked the path and actually the X:\VmName folder does exist.  (The folder was created by the failed P2V Job) Why is it giving me not found error then?

I thought that maybe VMM does not want the folder as it maybe trying to create it as the first job did, so I went to the storage path and tried to delete the folder but I got the error that it cannot delete because it is in use by VMM.

So two questions, First how do I resolve this 2nd error? so I can restart the job or run from scratch.

Second question, how do I resolve the original error?

As to the original error let me add that SCVMM was installed on an exchange server where the defualt website is in use by exchange.

I'm trying to convert a VM in ESXi to a VM in Hyper-V. I've tried a Hyper-V 2008 R2 and 2012 host and I get the same error. When I try the migration I get this error:

Error (2940)
VMM is unable to complete the requested file transfer. The connection to the HTTP server esxi01.hyrule.local could not be established.
Unknown error (0x80072ee2)

Recommended Action
Ensure that the HTTP service and/or the agent on the machine esxi01.hyrule.local are installed and running and that a firewall is not blocking HTTP/HTTPS traffic on the configured port.

Vincent Sprague

I have new "everything"...new physical host server, new SCVMM 2008 install.  I'm trying to P2V a 2003 Std server that's a workgroup server.  It's not on the domain.  The VM host is a DC.

I can't P2V the workgroup server.  I get the 2904 error about HTTPS running, etc.

I believe the SCVMM host is setup correctly because when I tried to P2V the old DC, it began to work, began to copy the HDs and failed at about 58% with the same HTTPS error.

On the workgroup server, it never even tries to copy the HD.  It fails out at 40%.

What am I doing wrong?  Can I P2V the workgroup server?  Is it failing because it's not on the domain?

Thanks

Cliff

Hi,

Here is my situation, I'm doing a P2V conversion and the process fails during "'Make operating system virtualizable" phase.

I am running SCVMM 2008 R2 SP1, converting a physical machine with Windows Server 2003 R2 64 bits on a different Hyper-V host as the VMM Server that has running Windows Server 2008.

What I realized is that the VHD were created but the VM was not configured (if I open settings dialogue the IDE controllers are empty with no drives). So i cut the process and I tried to add the VHD to the VM Settings but when I try to start the machine it reported an error saying that another process was using the file (is like the VHD was mounted by a process). So then I restarted a service called "Hyper-V Image something..." and then I could start the machine, but then a BSOD happens with error number 0x0000007B.

I read that in some case if the source machine was using scsi drives (my case) but the target vm machine use IDE drives, that BSOD happens but I knew that SCVMM have to take care about that.

I found several issues in internet about similar behavior, but in order to understand and to find a clue, what are the exact steps involved in the P2V process?

What i really know is that SCVMM host machine, physical source machine and the target hyper-v host machine do not have all software updates. But could it be something that was fixed by an update? and wiche update is involved?

thanks

Hi

I received the following error when trying to P2V SBS 2003 SP2 using SCVMM R2:

An internal error has occurred trying to contact an agent on the 192.168.1.10 server.
Ensure the agent is installed and running. Ensure the WS-Management service is installed and running, then restart the agent.
ID: 2912
Details: More data is available (0x800700EA)

I P2V'd a XP server without any issues on the same domain and LAN. Following the following advice:

http://blogs.technet.com/b/jonjor/archive/2010/09/07/p2v-and-other-jobs-fail-with-error-2912-0x8007xxxx.aspx

How do I determine if the WS-Management service is installed? And which version do I download to install?

Any help is greatly appreciated.

d

I am trying to P2V a Windows 2000 SP4 server and keep getting the error below. I have copied DRIVER.CAB & dc21x4.sys & to our VMM server and ran the Add-Patch cmdlet and VMM shows successful on the add, but will get this error. Any help?

Error (13257):
Virtual Machine Manager server is unable to convert %SERVERNAME% because required files are missing.

Recommended Action:
Copy the file DRIVER.CAB to "C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\Patch Import" on the Virtual Machine Manager server, run the Add-Patch cmdlet to add the required files to the Virtual Machine Manager patch cache, and then try the operation again. The file DRIVER.CAB is located either at %WINDIR%\Driver Cache\i386 on %SERVERNAME%, or on the Microsoft Windows 2000 Server (ENU, i386) installation media.n/ If DRIVER.CAB is not available, locate dc21x4.sys (Version: 5.5.0.0) on the installation media, copy the file to "C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\Patch Import", and then run the Add-Patch cmdlet to add the required files to the Virtual Machine Manager patch cache.

Hi guys!

Required to convert a physical server into a virtual one. When installing p2v agent program reports an error ID: 417
The server programs and components p2v agent is not displayed. I tried to remove it's this way:
  $ Credential = Get-Credential 
  $ ComputerConfig = Get-SCComputerConfiguration | where {$ _.Name-eq "P2VSource01.Contoso.com"} 
  Remove-SCComputerConfiguration-ComputerConfiguration $ ComputerConfig-Credential $ Credential
after the last command we get an error:
Remove-SCComputerConfiguration: Unable to validate the argument for the parameter "ComputerConfiguration". The argument is NULL. Specify an argument that has no value NULL, then repeat the command.

Доброго дня!

Требуется конвертировать физический сервер в виртуальный. При установке агента p2v программы сообщает об ошибке: На компьютере установлен агент Virtual Machine Manager, который не отвечает или несовместим. Удалите существующий агент и повторите операцию.ИД: 417

На сервере в программах и компонентах p2v агент не отображается. Пробовал удалить его вот этим способом:

 $Credential = Get-Credential (указал админскую учетку)
 $ComputerConfig = Get-SCComputerConfiguration | where { $_.Name -eq "P2VSource01.Contoso.com" }  (указал имя компьютера с которого требуется удалить агента)
 Remove-SCComputerConfiguration -ComputerConfiguration $ComputerConfig -Credential $Credential

после выполнения последней команды получаем ошибку: 

We are getting the following issues while doing P2V Conversation

Agent installation failed copying C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\agents\I386\3.0.6019.0\msiInstaller.exe to \\machinename\ADMIN$\msiInstaller.exe.

ID: 415

Details: The network path was not found

Kris

We are looking to convert our windows 2003 terminal server to virtual machine for testing purposes.  Is there anything we need to be aware of before we convert this machine?  The only concern I have is there are so many users that use this machine and we have have a number of applications installed so I don't know how the conversion could take.

Hello,

I am trying to do a Physical to Virtual conversion using VMM 2008. 

Everytime try to install the VMM agent through the wizard, I get the following error:

"There is a virtual machine manager agent that is not responding or not compatiable on SERVERNAME.  Uninstall the existing agent and then try the operation again.  ID 417"

The thing is, this server it is trying to install it to, has never had an agent installed on it.

Both Machines are Windows Server 2008 Standard.

Can anyone assist me with this?

Hi all,

I've found pretty much every instance of this question being asked on the Internet, but the solutions haven't worked for me. So I'm reaching out with a question of my own in hopes of finding a solution. I'm trying to P2V my Windows Server 2003 SP2 (Small Business Edition, 32-bit) physical server to another computer running both Hyper-V Server 2008 R2 and SCVMM 2008 R2. After it copies the 40GB of data to the virtual machine, it fails on the step called "make operating system virtualizable". Here's the actual error:

Error (12700)
VMM cannot complete the Hyper-V operation on the [hyper-v] server because of the error: '[p2v'd server]' could not initialize. (Virtual machine ID A9F05152-7101-43CF-9964-E060873BC06A) (Unknown error (0x8000))

There are a number of suggestions on how to fix this, but they haven't worked for me. Here's what I've done so far::

• In the BIOS of the Hyper-V Server, enabled DEP and Virtualization. Then powered off and restarted.
• Downloaded all available updates to the Hyper-V server
• Ran bcdedit /set hypervisorlaunchtype auto on the Hyper-V server, then restarted
• Tested by making a small blank (no OS) virtual machine, which was successful

I'm not sure what to do! My Hyper-V host is a pretty new machine, i7 2600 with 8GB RAM. As I said, testing by making a new virtual machine worked fine, so I'm not sure what it is about my P2V transfer that's preventing VMM from making the operating system virtualizable. The system being P2V'd is a Dell PowerEdge 2950 Quad-core Xeon with 4GB RAM, and the volume being transferred is less than 50GB.

Many thanks if anyone can help me!

-Owen

Hi,

I have a new install of scvmm2012 , I have 2 hosts added to it , 1 hyper-v R2 and 1 esx.

I tried v2v (from esx to hyper-v) , but I got status failed after 1 hour of conversion .

It's error 1730 : The selected action could not be completed because the virtual machine is not in a state in which the action is valid. Recommended Action: Check the state of the virtual machine , and verify that the selected job can be run on a virtual machine in that state. 

I tried this with 2 virtual machines (1 in started state , and 1 in shutdown state)

Any help will be appreciated. Thank you.

-Mehdi

I have converted countless 2003 and 2008 servers in VMM, but just had the need for the migration of an older 2000 box that I cannot simply upgrade.  After running the P2V wizard and loading the PERC drivers into the import folder I started the migration.  It rebooted and, well I guess I had the incorrect drivers in the folder or something because the PE failed.  Now I get a disk read error hit CTRL ALT DEL to restart during the boot process.  In the VMM jobs console I get a 3133 error saying it did not connect and a warning 12246 that said no compatible drivers were found (might be an issue with this being an older Dell 2650 with no 7/WIN2008 Drivers being availible).  So now I cannot even boot into the original 2000 OS to get the migration back on path.

Any ideas on how to save this box and continue the migration.  I have a backup and can recover it from scratch, but that is a rediculous amount of work for this old server.

Installed a 10gig Dell Broadcom BCM57711 nic in our Dell R805 server. The server is Running Windows 2008 R2 SP1 Data Center in a 2 node (CSV), cluster shared volume configuration. We connect to our storage array via iSCSI initiator, we have SCVMM 2008 R2 running on another server to manage our Hyper-V vm's.

We started getting MSiSCSI event ID 113 after bringing the nic online with iSCSI. I also noticed that when I went into iSCSI initiator and ran a discovery portal and used my 10gig nic I got a TCP Transport error.

The fix was as follows;

1. Document current nic settings in properties tab for each nic.
2. Apply hotfix 2684681, and 2685007.
3. Apply the latest Broadcom nic drivers, then update the nic bios.
4. Install the Dell BACS nic configuration software.
5. Make sure no nics appear in the Storage Controller area of Device Manager, if present remove them.
6. Disable all offload and rss settings on the properties tab for each nic.
7. Using the Dell BACS disable iscsi support for all nics.
8. Disable Offloading in Windows OS with below netsh commands.
9. netsh      int tcp set global rss=disabled
10. netsh int tcp set global      netdma=disabled
11. netsh int tcp set global      chimney=disabled
12. netsh int tcp set global      autotuninglevel=disabled
13. netsh int tcp set global      congestionprovider=none
14. Edit registry, create Registry entry in the HKEY_Local_Machine, System, CurrentControlSet, Services, Tcpip, Parameters. Add Dword EnableTCPA and set it's value to 0.
15. Apply Service Pack 1 to SCVMM or KB2492980.
16. Reboot.
17. Once rebooted the iSCSI discovery portal wizard will not have any selection other than default in the advanced tab so you will not be able to select the 10gig which was creating the TCP Transport error. There appears to be no reason to be able to select the nic, and the default settings work fine.

Hi all

I have an urgent need to convert approx 15 vms from 3 ESXi hosts to Hyper-V on new hardware.  Is SCVMM the best way to accomplish this?  By "best way" I'm less concerned with downtime and speed as I am a trouble-free conversion. 

Assuming the SCVMM is the way to go, while we wait for 2012 to come out, can I just load up the eval appliance and run the conversion with it, even though I don't plan to use any other features in production or otherwise?  My primary concern to get through the conversion to Hyper-V so I can retire the ESXi servers.  I'll implement SCVMM 2012 later.

Thanks!

Mark