You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/dedicated-hosts.md
+19-2Lines changed: 19 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,14 +82,14 @@ When creating a new host group, make sure the setting for automatic VM placement
82
82
83
83
Host groups that are enabled for automatic placement don't require all the VMs to be automatically placed. You'll still be able to explicitly pick a host, even when automatic placement is selected for the host group.
84
84
85
-
### Limitations
85
+
### Automatic placement limitations
86
86
87
87
Known issues and limitations when using automatic VM placement:
88
88
89
89
- You won't be able to redeploy your VM.
90
90
- You won't be able to use DCv2, Lsv2, NVasv4, NVsv3, Msv2, or M-series VMs with dedicated hosts.
91
91
92
-
## Host Service Healing
92
+
## Host service healing
93
93
94
94
In case of any failure relating to the underlying node, network connectivity or software issues can push the host and VMs on the host to a non-healthy state causing disruption and downtime to your workloads. The default action is for Azure to automatically service heal the impacted host to a healthy node and move all VMs to the healthy host. Once the VMs are service healed and restarted the impacted host will be deallocated. During the service healing process the host and VMs would become unavailable incurring a slight downtime.
95
95
@@ -200,6 +200,22 @@ Azure monitors and manages the health status of your hosts. The following states
200
200
| Host Pending Deallocate | Azure can’t restore the host back to a healthy state and ask you to redeploy your virtual machines out of this host. If `autoReplaceOnFailure` is enabled, your virtual machines are *service healed* to healthy hardware. Otherwise, your virtual machine may be running on a host that is about to fail.|
201
201
| Host Deallocated| All virtual machines have been removed from the host. You're no longer being charged for this host since the hardware was taken out of rotation. |
202
202
203
+
## Frequently Asked Questions
204
+
205
+
**Q**. What happens to my dedicated host in case of a live migration?
206
+
207
+
**A**. As of today, Azure dedicated hosts do not live migration and in case of a hardware failure, we service heal the host to a different node.
208
+
209
+
210
+
**Q**. Can I run VMs from multiple VM families on the same dedicated host?
211
+
212
+
**A**. No, you would be able to run only VMs as the same family as the underlying dedicated host. For e.g., a Dsv3-Type4 host will only support VMs of Dsv3 VM family.
213
+
214
+
215
+
**Q**. Would I be able to run different VM sizes on a single dedicated host?
216
+
217
+
**A**. Yes, you can run multiple sizes of VMs on the same dedicated host as long as the all the VMs belong to the same family as the underlying dedicated host and there is enough capacity on the host to support the VMs sizes. For e.g., on a Dsv3-Type4 host you could run D2sv3, D8sv3, D16sv3 VMs at the same time.
218
+
203
219
## Next steps
204
220
205
221
- To deploy a dedicated host, see [Deploy VMs and scale sets to dedicated hosts](./dedicated-hosts-how-to.md).
@@ -209,3 +225,4 @@ Azure monitors and manages the health status of your hosts. The following states
209
225
- You can also save on costs with a [Reserved Instance of Azure Dedicated Hosts](prepay-dedicated-hosts-reserved-instances.md).
0 commit comments