none
RemoteFX locking up VM's on boot RRS feed

  • Question

  • Here's the host system:

    Xeon E3-1220 v2 SLAT enabled.

    32Gig of ram.

    Adaptec 7805Q raid controller

    Nvidia 1060.

    Testing in order:

    Windows 10 and Win2k16 Generation 1 VM's.  Setup with RemoteFX added.  Tried to boot off of DVD image to install the OS.  Locked up at 10% with error 32788.  I then installed without RemoteFX added and the installs went fine.  Added RemoteFX after shutting them down.  Went to restart them, issue; locked up at 10% on startup with error 32788.

    Did this with Generation 2 VM's.  Same exact steps, same exact results.

    What am I doing wrong?

    Friday, August 31, 2018 12:53 AM

All replies

  • Hi Michael,

    Have you tried looking Hyper-V VMMS and Worker events in event viewer?

    Can you share them here?

    Also, if you didn't find any config error in the VM hardware settings, a faulty or outdated driver can be the issue. Is your GFX driver up-to-date?
    • Edited by Darci Filho Friday, August 31, 2018 2:16 AM
    Friday, August 31, 2018 2:12 AM
  • Ok.  here it goes.  VMMS: It's too big for all, so I've got a little bit here.

    Level,Date and Time,Source,Event ID,Task Category
    Information,8/30/2018 6:01:33 PM,Microsoft-Windows-Hyper-V-VMMS,20407,None,The Virtual Machine Management Service started the listener for Virtual Machine migration connections using the following addresses:
    192.168.99.50
    fe80::5efe:192.168.99.50
    fe80::9:86ed:c4b5:ac3b
    fe80::9c67:dade:2f26:aa64
    fe80::5efe:192.168.99.51
    192.168.99.51.
    Information,8/30/2018 6:01:33 PM,Microsoft-Windows-Hyper-V-VMMS,20407,None,The Virtual Machine Management Service started the listener for Virtual Machine migration connections using the following addresses:
    192.168.99.50
    fe80::5efe:192.168.99.50
    fe80::9:86ed:c4b5:ac3b
    fe80::9c67:dade:2f26:aa64
    fe80::5efe:192.168.99.51
    192.168.99.51.
    Information,8/30/2018 6:01:33 PM,Microsoft-Windows-Hyper-V-VMMS,20407,None,The Virtual Machine Management Service started the listener for Virtual Machine migration connections using the following addresses:
    192.168.99.50
    fe80::5efe:192.168.99.50
    fe80::9:86ed:c4b5:ac3b
    fe80::9c67:dade:2f26:aa64
    fe80::5efe:192.168.99.51.
    Information,8/30/2018 6:01:31 PM,Microsoft-Windows-Hyper-V-VMMS,20407,None,The Virtual Machine Management Service started the listener for Virtual Machine migration connections using the following addresses:
    192.168.99.50
    fe80::5efe:192.168.99.50
    fe80::9:86ed:c4b5:ac3b
    fe80::9c67:dade:2f26:aa64.
    Information,8/30/2018 6:01:27 PM,Microsoft-Windows-Hyper-V-VMMS,20407,None,The Virtual Machine Management Service started the listener for Virtual Machine migration connections using the following addresses:
    192.168.99.50
    fe80::5efe:192.168.99.50
    fe80::9:86ed:c4b5:ac3b
    fe80::9c67:dade:2f26:aa64.
    Warning,8/30/2018 6:01:27 PM,Microsoft-Windows-Hyper-V-VMMS,20406,None,"The description for Event ID 20406 from source Microsoft-Windows-Hyper-V-VMMS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    %%2147952449
    0x80072741
    192.168.99.51
    The locale specific resource for the desired message is not present
    "
    Information,8/30/2018 6:01:27 PM,Microsoft-Windows-Hyper-V-VMMS,20407,None,The Virtual Machine Management Service started the listener for Virtual Machine migration connections using the following addresses:
    192.168.99.50
    fe80::5efe:192.168.99.50
    fe80::9:86ed:c4b5:ac3b
    fe80::9c67:dade:2f26:aa64.
    Information,8/30/2018 6:00:59 PM,Microsoft-Windows-Hyper-V-VMMS,20407,None,The Virtual Machine Management Service started the listener for Virtual Machine migration connections using the following addresses:
    192.168.99.50
    fe80::5efe:192.168.99.50
    fe80::9:86ed:c4b5:ac3b.
    Warning,8/30/2018 6:00:59 PM,Microsoft-Windows-Hyper-V-VMMS,20406,None,"The description for Event ID 20406 from source Microsoft-Windows-Hyper-V-VMMS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    %%2147952449
    0x80072741
    fe80::5efe:192.168.99.51
    The locale specific resource for the desired message is not present
    "
    Warning,8/30/2018 6:00:59 PM,Microsoft-Windows-Hyper-V-VMMS,20406,None,"The description for Event ID 20406 from source Microsoft-Windows-Hyper-V-VMMS cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    %%2147952449
    0x80072741
    192.168.99.51
    The locale specific resource for the desired message is not present
    "
    Information,8/30/2018 5:49:18 PM,Microsoft-Windows-Hyper-V-VMMS,13003,None,The virtual machine 'Win2k16 Test' was deleted. (Virtual machine ID 87971A67-EE36-4944-901E-53A74D10ED5A)
    Error,8/30/2018 5:49:05 PM,Microsoft-Windows-Hyper-V-VMMS,32613,None,"The Virtual Machine Management Service could not start the RemoteFX Manager process to enable RemoteFX for the virtual machine Win2k16 Test. Affected virtual machine id is 87971A67-EE36-4944-901E-53A74D10ED5A. Try restarting the Virtual Machine Management Service. Error message: An attempt was made to reference a token that does not exist.
    Status Code: 20."

    Friday, August 31, 2018 2:37 AM
  • A little bit of Worker:

    Level,Date and Time,Source,Event ID,Task Category
    Error,8/30/2018 5:49:05 PM,Microsoft-Windows-Hyper-V-Worker,12030,None,'Win2k16 Test' failed to start. (Virtual machine ID 87971A67-EE36-4944-901E-53A74D10ED5A)
    Information,8/30/2018 5:49:05 PM,Microsoft-Windows-Hyper-V-SynthNic,12598,None,'Win2k16 Test' Network Adapter (87971a67-ee36-4944-901e-53a74d10ed5a--db55ada6-b897-4706-9dcd-a1e0f450b188) Disconnected from virtual network. (Virtual Machine ID 87971A67-EE36-4944-901E-53A74D10ED5A)
    Error,8/30/2018 5:49:05 PM,Microsoft-Windows-Hyper-V-Worker,12010,None,"The description for Event ID 12010 from source Microsoft-Windows-Hyper-V-Worker cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    Win2k16 Test
    87971A67-EE36-4944-901E-53A74D10ED5A
    Synthetic 3D Display Controller
    %%2147943850
    0x800705AA
    113560EA-48CD-4BD1-8828-FCEC44E2B5D5
    The locale specific resource for the desired message is not present
    "
    Error,8/30/2018 5:49:05 PM,Microsoft-Windows-VStack-Synth3dVideo,12018,None,'Win2k16 Test'Synthetic 3D Display Controller: Failed to Power on with Error 'The virtual machine cannot be started because a worker session cannot be created.'. (Virtual machine ID 87971A67-EE36-4944-901E-53A74D10ED5A)
    Information,8/30/2018 5:47:01 PM,Microsoft-Windows-Hyper-V-SynthNic,12582,None,'Win2k16 Test' Network Adapter (DB55ADA6-B897-4706-9DCD-A1E0F450B188) started successfully. (Virtual Machine ID 87971A67-EE36-4944-901E-53A74D10ED5A)

    Friday, August 31, 2018 2:38 AM
  • Oh.  The video driver is up to date.  Checked it this morning.
    Friday, August 31, 2018 2:38 AM
  • I would check if the device is compatible for device pass through.

    Does the GPU vendor state anything about it?

    Windows Server Catalog certifies the GPU card if that's the case, but I didn't find anything specific to RemoteFX or Desktop Virtualization.

    You can try "tuning" your VM before booting it up.

    https://blogs.technet.microsoft.com/virtualization/2015/11/23/discrete-device-assignment-gpus/

    Friday, August 31, 2018 3:59 AM
  • I'm trying to avoid pass thru for multiple user configuration.  Thus RemoteFX was the attractive solution.

    Friday, August 31, 2018 4:55 AM
  • Hi Michael,

    How are things going on? Was your issue resolved now?

    Please feel free to let us know if you need further assistance.

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com


    Saturday, September 1, 2018 4:32 AM
    Moderator
  • Not as of yet.  But, judging by this link; https://docs.microsoft.com/en-us/windows-server/get-started/windows-server-1803-removed-features ; It looks like RemoteFX is being deprecated.

    So, I'm thinking about waiting until Windows Server 2019 to see what the replacement for it is.  Hopefully, that'll be the fix.

    This is a lab box.  None of my clients (I'm also an independent contractor) have faced this yet.  So, it's not mission critical.  But I'd sure like to solve it.

    I won't be able to get to this again until Tuesday.  I'm taking the 3 day weekend.

    Thanks.

    -Michael.

    Saturday, September 1, 2018 5:21 AM
  • Hi,

    Thanks for your update.

    I'll follow up and stand by with you. If any update, I'll post to you as soon as possible.

    Your technical and effort are very appreciated.

    Have a nice weekend!

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Monday, September 3, 2018 10:02 AM
    Moderator
  • Thanks.

    If I get a chance to work on it again soon, I will and post any results here.

    Monday, September 3, 2018 8:46 PM
  • Hi,

    How are things going on?

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Sunday, September 9, 2018 7:16 AM
    Moderator
  • Hi Michael.

    Going ok.  

    I haven't had time to work on this.  Probably won't for a while.  

    Go ahead and close this.  I'm just going to wait for Windows Server 2019 and whatever the RemoteFX replacement is that comes with it.

    Monday, September 10, 2018 10:24 PM
  • Hi Michael😊,

    Appreciate your feedback. And I'll also research the issue, if I figure out more different solution, I will share with you either.

    Anyway thanks for your sharing and support.

    Nice day!

    Best regards,

    Michael


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com


    Tuesday, September 11, 2018 10:01 AM
    Moderator
  • Thanks Michael. 

    If I get to work on it, I'll post any findings here.

    Tuesday, September 11, 2018 4:57 PM