Skip to content

Update troubleshoot-arc-enabled-vms.md #3618

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions azure-local/manage/troubleshoot-arc-enabled-vms.md
Original file line number Diff line number Diff line change
Expand Up @@ -128,6 +128,35 @@ If your environment fails to recognize Azure CLI after installing it, run the fo
}
```

## Live Migrations on Azure Local 23H2 May Fail Without Error

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change the title to: Live migrations on Azure Local 2311.2 and later could fail without error

After upgrading from Azure Local 22H2 to 23H2, or on a clean install of 23H2, you may encounter issues where VMs fail to live migrate in an Azure Local Cluster.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change to: After you upgrade to Azure Local 2311.2 or on a new deployment of 2311.2 or later, you could see issues where the Azure Local VMs fail to live migrate in an Azure Local instance.


**Issue:** Live migration attempts may fail silently — no error messages are logged.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add: Cause:

This problem is caused by a known issue in Azure Local 23H2 that manifests under specific system configurations.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change: This problem is caused by a known issue in Azure Local, version 2311.2 or later. This problem manifests under specific system configurations.


**Resolution:**

Run the following PowerShell script locally on one of the cluster nodes. This script will apply a registry fix on all nodes. After running it, reboot each node one at a time for the change to take effect.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change: Run the following PowerShell script locally on one of the Azure Local machines. This script applies a registry fix on all the machines of your Azure Local instance.

After you have run the script, reboot each machine one at a time for the change to take effect.


```PowerShell
Get-ClusterNode | ForEach-Object {
Invoke-Command -ComputerName $_.Name -ScriptBlock {
$RegPath = "HKLM:\System\CurrentControlSet\Services\Vid\Parameters"
$ValueName = "SkipSmallLocalAllocations"
$ValueData = 0

# Create the key if it doesn't exist
if (-Not (Test-Path $RegPath)) {
New-Item -Path $RegPath -Force | Out-Null
}

# Create or update the DWORD value
New-ItemProperty -Path $RegPath -Name $ValueName -Value $ValueData -PropertyType DWord -Force
}
}
```

## Next steps

Expand Down