Hello, @PDA !
Edit: We have an update reported by @MBannon:
I opened a case with Support and the response back was it is a bug in canonical 6.2 kernel which impacts the Platform ID field passed to Hyper-V during VM startup. This field is used by the host to determine VM health status. The Canonical team is working on a fix and is expected to be available in the coming weeks.
Thank you for reporting this. We are currently collecting information and working with the Virtual Machine product group to determine the cause of this issue. I'm starting this answer to track information that is starting to get lost in the comments.
Why is my VM status showing Unavailable (Customer Initiated)
?
There have been multiple reports of this behavior and we are gathering more information as we track and resolve the issue. Here is what has been reported:
- 11/1 - As reported by @MBannon: "...it is a bug in canonical 6.2 kernel which impacts the Platform ID field passed to Hyper-V during VM startup. This field is used by the host to determine VM health status. The Canonical team is working on a fix and is expected to be available in the coming weeks."
- 10/16 - We have had a few people reach out to us and an internal team is investigating the affected resources. Please continue to email us as described in the 9/14 update below if you run into this.
- 9/14 - The most recent update from the virtual machine team is that this will require additional investigation based on your subscription and resources. Please email the following to AzCommunity@microsoft.com and we'll get back to you promptly:
- Subject: "Attn: kobulloc - VM status Unavailable (Customer Initiated)"
- Email body: Your Subscription ID
- Email body: A link to this thread so we can validate and expedite the request
- Email body: Your Subscription ID
- Subject: "Attn: kobulloc - VM status Unavailable (Customer Initiated)"
- 9/6 - (Update: We are still receiving reports of this behavior. Thank you for your reports!)
An initial investigation suggests that this was related to a small outage as there have not been additional reports. If you are still encountering this issue, please Start/Stop the VM and let us know in the comments if it persists. - 8/31 - The Virtual Machine is actively working on this issue.
- A VM restart (of the OS) has been reported to resolve the issue (@Ketan Siddhapura) however Stop/Start has been reported as not resolving the issue (@PDA)
- Ubuntu (22.04) and Windows Server (2019/2012) have been reported as affected
- In many reports, the VM still functions as expected
- This may be caused by an OS reboot or an automatic update (@Valerio Maglietta - Eusoft) or a stop command on the console (@celsmk).