[Environments reliability] Hyper-V Configuration error: Unable to perform the requested operation

[bbonaby]

Dev Home version

No response

Windows build number

No response

Other software

No response

Steps to reproduce the bug

Attempt to configure a Win 10/11 Hyper-V VM

Expected result

User is able to configure Hyper-V Win 10/11 VM. Or receives better error messaging.

Actual result

The user receives the display error: "Unable to perform the requested operation. Check the Dev Home Hyper-V Extension's log file: for more information".

The diagnosticText simply states: “Exception of type HyperVExtension.HostGuestCommunication”

looking at the configuration code this one may likely be due to the extension not being able to start the VM. We'll need to update the error messaging since all the other operations e.g shutting down, terminating, pausing all have the same error message if something unexpected occurs.

Included System Information

No response

Included Extensions Information

No response

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• Hyper-V in environments throwing error (#3351), similarity score: 0.78

Closed similar issues:

• Hyper-V is confusing (#2745), similarity score: 0.78
• [Environments] [HyperV] Error code when you don't have VMP installed isn't specific (#2766), similarity score: 0.76

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[sshilov7]

There is diagnostic text in the event saying, "Exception of type 'HyperVExtension.HostGuestCommunication.HResultException' was thrown.". That exception is used when processing results or progress from the guest OS. It's not clear how that message gets into the event if the error is coming from Start VM operation.

[sshilov7]

A repro that simulates this error: Create VM that asks for a lot of memory so it can't be started. Try to configure it.
This error happens when something goes wrong with Hyper-V manager or PowerShell runspace used to send command to Hyper-V manager. We'll get more data in future telemetry.
This is no nesassaraly Dev Home's bug, but we might be able to mitigate some of the issues.