GET-IT: TEAMS DAY | 1-Day Free Virtual Conference all about Teams. Here on Petri.com - 8/12/20 GET-IT: TEAMS DAY - 8/12/20

P2V failure: Warning (13210) Timeout occurred while waiting for VM integration servic

Home Forums Virtualization Microsoft Hyper-V Technology P2V failure: Warning (13210) Timeout occurred while waiting for VM integration servic

Viewing 1 post (of 1 total)
  • Author
    Posts
  • Avatar
    Taw_Jackson
    Member
    #139392

    Hi there

    Looking for some advice re SCVMM P2V.

    We have a Hyper-V box, and the first P2V went perfectly (our Forefront server) with no problems at all.

    However, I have tried to P2V our CRM server (sitting on Windows Server 2003 SP2) and it failed with the below errors:


    Warning (13210)
    Timeout occurred while waiting for VM integration services to be installed on virtual machine hostname residing on host hyper-v.domain.com.

    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 host residing on host hyper-v.domain.com.

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



    I’ve tried googling the errors and recommended actions but hven’t came up with anything useful yet.

    Are these common P2V issues?

    I have tried various things, such as:

    >selecting a single virtual processor when running the P2V wizard

    >adding in the P2VBITSTcpPort entry to the registry (tried ports 445 and 446)

    >tried creating the VM on a different disk array

    Nothing worked.

    I’m wondering if the issue could be with the scsi card on the target physical server.

    It is a LSI Logic PCI-X Ultra320 SCSI Host Adapter (Embedded).

    Could there be a clash between this device and Hyper-V/SCVMM?

    Have already posted a similar question on the Microsoft forums and although someone has been kind enough to offer support advice, the problem persists.

    If anyone has any knowledge on how to resolve this, it would be very much appreciated.

    Thanks

    Taw Jackson

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.