Skip to content

Commit 99efba7

Browse files
authored
Update scheduled-events.md
Adding a limitation for GPU VMs
1 parent 19cbe61 commit 99efba7

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/virtual-machines/windows/scheduled-events.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -58,11 +58,13 @@ Scheduled events are delivered to and can be acknowledged by:
5858
- All the VMs in an availability set.
5959
- All the VMs in a scale set placement group.
6060

61-
> [!NOTE]
62-
> Scheduled Events for all virtual machines (VMs) in an entire Availability Set or a Placement Group for a Virtual Machine Scale Set are delivered to all other VMs in the same group or set regardless of Availability Zone usage.
61+
Scheduled Events for all virtual machines (VMs) in an entire Availability Set or a Placement Group for a Virtual Machine Scale Set are delivered to all other VMs in the same group or set regardless of Availability Zone usage.
6362

6463
As a result, check the `Resources` field in the event to identify which VMs are affected.
6564

65+
> [!NOTE]
66+
> GPU accelerated Virtual Machines in a scale set using 1 fault domain (FD = 1) will only receive scheduled events for the impacted resource. Events will not be broadcasted to all VMs in the same placement group.
67+
6668
### Endpoint discovery
6769
For VNET enabled VMs, Metadata Service is available from a static nonroutable IP, `169.254.169.254`. The full endpoint for the latest version of Scheduled Events is:
6870

0 commit comments

Comments
 (0)