Error (3101) VMM failed to mount VHD file with online P2V using VMM 2008

All replies

• 

  

  1

  Sign in to vote

  Hi Frenzied,

  here are my answers :

  1 ) probably there is an already mounted vhd on the hyper-v host. try unmounting that.

  if there is no vhd, you can try rebooting your hyper-v host.

  After rebooting or unmounting do not start from scratch, just restart the failed p2v task, it will continue from where it left so you wont have to wait for the disk copy.

  If you continue seeing mount timeout, do the folloving workaround :

          1) go to the properties of the w2k3 vm through hyper-v console (as you did for xp VM)

          2) manually attach the vhds that are copied by p2v to the vm (they should be in the same folder as the vm)

   

  2) cd rom is added to the VM at the end of p2v operation. integration services installation is the last step of p2v operations.

  3) remove and add the host from SCVMM console. in that case all VM s on that host will get rediscovered in healty status.

  ---

  Thanks, Caglar --Posting is provided "AS IS" with no warranties, and confers no rights.

  • Proposed as answer by Caglar Pir [MSFT] Wednesday, January 28, 2009 12:32 AM
  • Marked as answer by Carmen SummersMicrosoft employee Tuesday, March 24, 2009 6:11 AM

  Wednesday, January 28, 2009 12:30 AM
• 

  

  0

  Sign in to vote

  Good news but there's still an issue...

  My second sequence of events plays out like this:

  1. Deleted the failed P2V from both the SCVMM and Hyper-V servers (I had mucked up the virtual so I had to start all over again)
  2. Rebooted the Hyper-V server
  3. Removed the host Hyper-V server from SCVMM and added it back in (it did clear up the failed status of a prior P2V that I resolved manually so thanks for this answer)
  4. Started the P2V migration
  5. Received a failure message in SCVMM in step 1.4.1, however 1.4.1.1 and 1.4.1.2 completed successfully.
  6. Logged into the Hyper-V server and reviewed the VM settings. This time the VHD files were attached and the DVD drive was there! Based on everything looking OK in the settings I decided to start the VM
  7. Started the VM and it booted into Server 2003 just fine. I logged into the VM, restored my services using msconfig and rebooted
  8. Logged in again and started the installation of the integrated tools. It said the integrated tools were already installed! I verified that they were in device manager.
  9. Last I reviewed the VM's log files and everything looked fine.

  This begin said, it seems that the P2V ran to completion as far as the VM is concerned. It obviously didn't clean off the P2V agent on the source but that's not a big deal.

  Why is SCVMM still giving me a failure? Are there some logs somewhere that I can check to to find out?

  Thanks

  Wednesday, January 28, 2009 4:24 PM
• 

  

  0

  Sign in to vote

  anyone?

  Monday, February 2, 2009 4:45 PM
• 

  

  0

  Sign in to vote

  what is the failure?
  probably it is a "warning"

  ---

  Thanks, Caglar --Posting is provided "AS IS" with no warranties, and confers no rights.

  Monday, February 9, 2009 5:57 PM
• 

  

  0

  Sign in to vote

  I get these:
  
  

  Error (3101)

  VMM failed to mount VHD file <filename>.vhd on the <servername> server. A timeout occurred.
  
  or these:
  
  Error (2916)

  VMM is unable to complete the request. The connection to the agent <servername> was lost.
  
  If I reboot the Hyper-V server and then start the P2v all over again (if I try to resume it doesn't respond) I can get rid of ther 3101 error but I don't like having to restart my Hyper-V server to get it to work. Error 2916 shows up when the process is trying to remove the agent from the source machine. The agent removal process of the P2V migration has not worked for me yet. This isn't a huge deal but it does make me have to remove and add the host Hyper-V server again so that the failure status goes away.

  Tuesday, February 10, 2009 3:28 PM
• 

  

  0

  Sign in to vote

  Normally you dont have to reboot your hyper-v server. this is an exceptional case.
  
  
  P2v agent removal error should not mark the task failed, it should be just a warning.
  
  if it fails the task then it is a different issue. Please collect SCVMM Server traces.
            http://blogs.technet.com/chengw/archive/2008/05/08/how-to-collect-scvmm-traces.aspx

  ---

  Thanks, Caglar --Posting is provided "AS IS" with no warranties, and confers no rights.

  Thursday, February 12, 2009 12:06 AM
• 

  

  0

  Sign in to vote

  I'm receiving the same error message on every online P2V I have tried. The series of events is as follows:

  1. Prep the client for p2v (disable a/v, etc. and reboot)
  2. Start the P2V using SC VMM 2008
  3. The P2V process copies the local disk using the network to the Hyper-V server I have chosen as the target, then when VMM 2008 tries to mount the VHD I receive this (computer name, volume and hyper-v server name have been removed):

  Error (3101)

  VMM failed to mount VHD file D:\HyperV\<computername>\<volume>.vhd on the <hyper-v> server. A timeout occurred.

  (Internal error code: 0x80990C1D)

  Recommended Action

   

  Check Device Manager/System Devices to make sure that Microsoft Virtual Server Storage Bus is installed and functional. If it is not, install VHDMount component of Virtual Server. Restart Virtual Disk Service, and then try the operation again.

   

  I've run the P2V on both a Server 2003 R2 SP2 installation as well as a Windows XP SP2 installation. Both exhibit the same problem. The target Hyper-V server is not clustered. On the Win XP I can do the following:

  1. Manually mount the VHD within Hyper-V (not using SC VMM 2008 - it will only give me the option to delete or view networking on the VM since it is in a failed state.
  2. Manually add a CD-ROM
  3. Start the VM and it boots into XP ok
  4. Enable all services/programs disabled during the prep
  5. Install integration tools

  And the XP VM is up and running fine. I haven't been able to boot into Server 2003 once I P2V it but I'll dig into that a little later.

  So here are my questions:

  1. Why am I receiving Error (3101) and what do I need to do to make my P2V's run to completion?
  2. When does the CD-ROM unit get added to the VM (or does it at all) during the P2V process and do the integration services automatically get installed as part of the P2V process?
  3. Since I have manually finished the P2V (in the case of the XP machine) how do I get SC VMM 2008 to show a running status instead of a P2V conversion failed status?

  Thanks for any help!

  
  Exact same issue here but... after mounting the VHD manually from Hyper V Manager, I get starting the VM I get blue screen of death. "WINDOWS HAS BEEN SHUT DOWN TO PREVENT DAMAGE TO YOUR COMPUTER. Stop: 0x0000007b
  
  Has anyone seen this error on a manually mounted VHD? I have now experienced it on two P2V attempts on different machines.

  • Edited by VirtualizeMe Friday, November 20, 2009 4:44 AM addition

  Thursday, November 19, 2009 1:59 PM
• 

  

  0

  Sign in to vote

  Solved this problem!
  
  As explained above, I was attempting this P2V for an XP source machine from HostA 2008 ServerR2 Using SCVMM to HostB HyperV2008 Server Core. After finally getting the VHD file attached to the VM by manually attaching it in Hyper V Manager, I ended up with Blue Screen.
  
  The solution that worked for me was to perform the P2V From Host A to HostA. So instead of using SCVMM to direct the P2V files to a better qualified Hyper V Host, I directed it to the local Hyper V running on the 2008 Server R2. Worked perfectly and no errors on starting the VM.
  
  Now I have a new problem that I will post in the appropriate forum. I still want this VM on the better Hyper V Host so I am trying to use SCVMM to clone this to HostB but I am now getting an error 2912 indicating Internal error (ther resource loader failed to find MUI file (0x80073AFC). The saga continues...

  • Proposed as answer by VirtualizeMe Monday, November 23, 2009 5:38 PM

  Monday, November 23, 2009 5:37 PM