During an AHV upgrade, an administrator finds that a critical VM was powered off rather than migrating to another host. Which scenario explains this behavior?
A.
No AHV hosts were able to be scheduled.
B.
The VM was on the same host as the acropolis leader.
C.
The VM OS hung during migration.
D.
The VM was marked as an agent VM.
Answer:
d
User Votes:
A 2 votes
50%
B 1 votes
50%
C
50%
D 4 votes
50%
Discussions
0/ 1000
nuta
3Â months ago
The behavior of a critical VM being powered off instead of migrating during an AHV upgrade can occur if the VM is on the same host as the Acropolis leader. In this case, the system prioritizes the stability of the cluster during the upgrade process, leading to a situation where the VM cannot be migrated to another host.
Additionally, if a VM is configured as an "agent VM," it is also designed to remain powered off during upgrades, further impacting VM availability during the process​
Want to join our community?
Please log in or signup in order to use this feature
The behavior of a critical VM being powered off instead of migrating during an AHV upgrade can occur if the VM is on the same host as the Acropolis leader. In this case, the system prioritizes the stability of the cluster during the upgrade process, leading to a situation where the VM cannot be migrated to another host.
Additionally, if a VM is configured as an "agent VM," it is also designed to remain powered off during upgrades, further impacting VM availability during the process​