none
Issues with Windows Server 2003 R2 SP2 - SCVMM P2V. Integration Service are not installing. No Keyboard or Mouse response after conversion. RRS feed

  • Question

  • Issues with Windows Server 2003 R2 SP2 - VMM PV2. Integration Service are not installing properly. No Keyboard or Mouse response after conversion.

    Warning (13210)

    Timeout occurred while waiting for VM integration services to be installed on virtual machine VM01 residing on host HV01.

    Recommended Action

    Ensure that the version of the VM integration services binaries matches the version of the guest operating system in the virtual machine and then try the operation again.

    Warning (13222)

    An internal error occurred while Virtual Guest Services were being installed on virtual machine VM01 residing on host HV01.

    Recommended Action

    Try the operation again. If the same error occurs again, contact your support personnel for further help.

    Warning (458)

    The Virtual Machine Manager agent could not be removed from VM01.

    Recommended Action

    Uninstall the Virtual Machine Manager agent using Add or Remove Programs on VM01.

    Warning (416)

    Agent installation timed out while waiting on service VMMAgentInstaller on VM01.

    Recommended Action

    Ensure that the Windows Installer service is running on VM01 and try the operation again.



    Monday, January 21, 2013 1:09 PM

Answers

  • This is a single server 5 user environment.

     

    Physical Machine Configuration (PM):

    Dell PowerEdge SC440 Server

    1 Intel Xeon Processor

    4GB DDR2 RAM 667MHz

    1 RAID-1 73GB Volume containing Boot OS partition on Dell PERC 5/I Controller

    1 RAID-1 250GB Volume containing most data on IDE Controller

    Windows Server 2003 SP2

    SQL Server Workgroup 2005 (supporting a Financial Administration application)

    This server had hardware issues with its Dell PERC 5/i internal SAS controller.  The controller was replaced.

    This server is exhibiting issues with the i8042prt in Win2K3.  This port was disabled as it is not used.

     

    Hyper V Host Configuration (HV01):

    HP ProLiant ML 350p Gen8

    2 Intel E5-2650 Processors

    16GB RAM

    1 RAID 5 1TB Volume containing Boot OS partition and VM Files

    Windows Server Enterprise 2012 with Hyper V role

    1 Domain Controller VM Windows Server 2003 R2 SP2

    1 SCVMM 2012 Evaluation Version (for conversion purposes)

     

    Intention:

    • Convert PM into a VM (VM01) to be hosted on HV01

     

    Steps taken:

    • Updated the PM with the latest Windows Updates. (This causes some of the DCOMs of a SQL Server Financial Application installed on the server to loose there authentication credentials).
    • Used Disk2VHD 1.63 (prepare for VM) to create an image of the PM --> VM01.  This image started fine on the HV01, however, No keyboard or mouse response.
    • From Remote Desktop connected into the HV01, from the console of the HV01 connected into the console of the VM01, also same result.  Most probably the keyboard and mouse drivers are not working in the VM on Hyper-V.
    • Using a trail copy of SCVMM 2012 to convert the PM (based on recommendation that it is the best tool for this purpose).  This resulted in the same issue with the keyboard and the mouse.  The conversion completes with information: Issues with installing Integration Services.  See above SCVMM log.
    • Installed Integration Services through SCVMM by right clicking on the VM01 and selecting this option.  Integration Services installation completed successfully.  Still no keyboard or mouse responding after reboot of the VM01.
    • Mounted the vmguest.iso and installed the Integration Services directly on the PM.  Then did a SCVMM 2012 P2V.  Same results.  The SCVMM still tries to Install the Integration Services and times out.
    • Upgraded the PM to Windows Server 2003 R2 SP2 reapplied SP2 afterwards.  Uninstalled Integration Services from the PM.  Initiated a SCVMM P2V conversion.  Same results.  No access to the VM01 through the network either, thus no Remote Desktop possible.  Most likely issues with the keyboard and mouse drivers, most likely caused by an incompatible HAL, which will cause the keyboard and mouse devices not to be recognized properly and thus prevents the proper installation and/or working of their drivers.
    • Created a fresh image copy of the PM using Disk2VHD, mounted the VHD file, copied halaacpi.dll in C:\Windows\system32\" edited the boot.ini (in root the folder - C:\) to force the use of this HAL using the HAL="halaacpi.dll" switch as  implemented below.  This failed as well booting normally, again with no keyboard or mouse response.

    [boot loader]
    timeout=3
    default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows Server 2003, Enterprise Edition" /fastdetect /HAL=halaacpi.dll

     

    • Created a backup using Acronis True Image Echo Backup and Recovery for Windows 11.5 (Trail version) and restored it on a newly created virtual machine on HV01.  The keyboard worked.  The VM01 recognized some new hardware and request to restart.  After restart neither the keyboard nor the mouse worked.
    • Restore the bootable drive C: from backup image onto the same VM01, basically reverting to the previous state, where the keyboard worked.
    • Once VM01 booted, used the keyboard to check the hardware configurations.  The causes for the situation where identified.
    • Removed all software that could be hindering the Microsoft Hyper-V Integration Services from properly installing, e.g. Microsoft Hyper-V Integration Services (itself).
    • Installed Microsoft Hyper-V Integration Services again, the then it recognized that the HAL was not appropriate and suggested to upgrade it.  The upgrade completed successfully and after a reboot, the keyboard, mouse, network card, and display were identified and the proper drivers were loaded properly.
    • The migration of the PM to VM01 was completed successfully.

     

    Causes:

    • In this case for some reason neither Disk2VHD nor SCVMM were upgrading the HAL properly.
    • The HAL of the VM01 was configured with Advanced Configuration Programming Interface (ACPI) PC (Halacpi.dll), and Standard PC, instead of the ACPI Uniprocessor PC (Halaapci.dll) as indicated by Microsoft's support documents.  This causes the Microsoft Hyper-V Virtual Machine Bus, Microsoft Hyper-V S3 Cap, Microsoft Hyper-V Generation Counter to fail from loading.  Consequently, the keyboard, mouse, and network drivers will not work either.
    • There was an issue as well with the PS/2 mouse driver not loading properly.



    Wednesday, January 30, 2013 1:44 PM

All replies

  • Can you try to install the integration services through Hyper-V Manager and see how it goes?

    Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

    Monday, January 28, 2013 1:32 PM
    Moderator
  • Dear Kristian,

    Thanks for your response.

    We have tried that with no change.  I will post the details of the path are taking and where we are shortly.

    Angelo.

    Tuesday, January 29, 2013 2:51 PM
  • This is a single server 5 user environment.

     

    Physical Machine Configuration (PM):

    Dell PowerEdge SC440 Server

    1 Intel Xeon Processor

    4GB DDR2 RAM 667MHz

    1 RAID-1 73GB Volume containing Boot OS partition on Dell PERC 5/I Controller

    1 RAID-1 250GB Volume containing most data on IDE Controller

    Windows Server 2003 SP2

    SQL Server Workgroup 2005 (supporting a Financial Administration application)

    This server had hardware issues with its Dell PERC 5/i internal SAS controller.  The controller was replaced.

    This server is exhibiting issues with the i8042prt in Win2K3.  This port was disabled as it is not used.

     

    Hyper V Host Configuration (HV01):

    HP ProLiant ML 350p Gen8

    2 Intel E5-2650 Processors

    16GB RAM

    1 RAID 5 1TB Volume containing Boot OS partition and VM Files

    Windows Server Enterprise 2012 with Hyper V role

    1 Domain Controller VM Windows Server 2003 R2 SP2

    1 SCVMM 2012 Evaluation Version (for conversion purposes)

     

    Intention:

    • Convert PM into a VM (VM01) to be hosted on HV01

     

    Steps taken:

    • Updated the PM with the latest Windows Updates. (This causes some of the DCOMs of a SQL Server Financial Application installed on the server to loose there authentication credentials).
    • Used Disk2VHD 1.63 (prepare for VM) to create an image of the PM --> VM01.  This image started fine on the HV01, however, No keyboard or mouse response.
    • From Remote Desktop connected into the HV01, from the console of the HV01 connected into the console of the VM01, also same result.  Most probably the keyboard and mouse drivers are not working in the VM on Hyper-V.
    • Using a trail copy of SCVMM 2012 to convert the PM (based on recommendation that it is the best tool for this purpose).  This resulted in the same issue with the keyboard and the mouse.  The conversion completes with information: Issues with installing Integration Services.  See above SCVMM log.
    • Installed Integration Services through SCVMM by right clicking on the VM01 and selecting this option.  Integration Services installation completed successfully.  Still no keyboard or mouse responding after reboot of the VM01.
    • Mounted the vmguest.iso and installed the Integration Services directly on the PM.  Then did a SCVMM 2012 P2V.  Same results.  The SCVMM still tries to Install the Integration Services and times out.
    • Upgraded the PM to Windows Server 2003 R2 SP2 reapplied SP2 afterwards.  Uninstalled Integration Services from the PM.  Initiated a SCVMM P2V conversion.  Same results.  No access to the VM01 through the network either, thus no Remote Desktop possible.  Most likely issues with the keyboard and mouse drivers, most likely caused by an incompatible HAL, which will cause the keyboard and mouse devices not to be recognized properly and thus prevents the proper installation and/or working of their drivers.
    • Created a fresh image copy of the PM using Disk2VHD, mounted the VHD file, copied halaacpi.dll in C:\Windows\system32\" edited the boot.ini (in root the folder - C:\) to force the use of this HAL using the HAL="halaacpi.dll" switch as  implemented below.  This failed as well booting normally, again with no keyboard or mouse response.

    [boot loader]
    timeout=3
    default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows Server 2003, Enterprise Edition" /fastdetect /HAL=halaacpi.dll

     

    • Created a backup using Acronis True Image Echo Backup and Recovery for Windows 11.5 (Trail version) and restored it on a newly created virtual machine on HV01.  The keyboard worked.  The VM01 recognized some new hardware and request to restart.  After restart neither the keyboard nor the mouse worked.
    • Restore the bootable drive C: from backup image onto the same VM01, basically reverting to the previous state, where the keyboard worked.
    • Once VM01 booted, used the keyboard to check the hardware configurations.  The causes for the situation where identified.
    • Removed all software that could be hindering the Microsoft Hyper-V Integration Services from properly installing, e.g. Microsoft Hyper-V Integration Services (itself).
    • Installed Microsoft Hyper-V Integration Services again, the then it recognized that the HAL was not appropriate and suggested to upgrade it.  The upgrade completed successfully and after a reboot, the keyboard, mouse, network card, and display were identified and the proper drivers were loaded properly.
    • The migration of the PM to VM01 was completed successfully.

     

    Causes:

    • In this case for some reason neither Disk2VHD nor SCVMM were upgrading the HAL properly.
    • The HAL of the VM01 was configured with Advanced Configuration Programming Interface (ACPI) PC (Halacpi.dll), and Standard PC, instead of the ACPI Uniprocessor PC (Halaapci.dll) as indicated by Microsoft's support documents.  This causes the Microsoft Hyper-V Virtual Machine Bus, Microsoft Hyper-V S3 Cap, Microsoft Hyper-V Generation Counter to fail from loading.  Consequently, the keyboard, mouse, and network drivers will not work either.
    • There was an issue as well with the PS/2 mouse driver not loading properly.



    Wednesday, January 30, 2013 1:44 PM
  • Hello. In our case after convert P2V we deleted antivirus program (officescan) from converted VM and only after that we succesfuly install Guest integration services.

    From Russia with love :D

    Sunday, November 22, 2015 3:32 AM