Which happens if the swap file of a virtual machine is inaccessible to the destination host during a vMotion?
A.
The swap file is stored with the virtual machine configuration file.
B.
The swap file is copied to the destination host.
C.
The vMotion will fail.
D.
The swap file is replicated to a datastore accessible by both hosts.
A
3
0
A is correct.
During vMotion, if the swap file location on the destination host differs from the swap file location on the source host, the swap file is copied to the new location.
If the destination host cannot access the specified swap file location, it stores the swap file with the virtual machine configuration file.
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vcenterhost.doc/GUID-B8F9F952-EEE7-4C23-A8F6-35E55232263F.html
1
0
Correct: A
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vcenterhost.doc/GUID-B8F9F952-EEE7-4C23-A8F6-35E55232263F.html
1
0
‘C’ is correct for sure. If the swap file cannot be accessed by the destination host, vMotion cannot proceed. Swap contains inactive memory pages that have been moved from RAM onto disk as a temporary storage due to lack of RAM. At some point such content will be requested back the hypervisor but evidently wouldn’t be available had vMotion without swap been permitted… In ESX terms that’s Purple Screen of Death (PSOD) kind of situation…
The referenced quote from VMware documentation: “If the destination host cannot access the specified swap file **location**, it stores the swap file with the virtual machine configuration file.” – talks about inability to access a **new location** for the swap file, not the swap file itself. Such new location is alternative to the default one (default is where VM’s config and other files are stored) and can be chosen due to performance reasons (typically, because of lots of reads/writes from/to swap in case of insufficient RAM).
0
0