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.
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vcenterhost.doc/GUID-B8F9F952-EEE7-4C23-A8F6-35E55232263F.html
0
0
A
0
0
A
0
0
This could be either A or B correct?
Technically the file would be copied to the destination host(B)
Then stored with the VM config file file(A)
Am I crazy for thinking that B actually answers the question more directly?
0
0
A
–nevermind up above, while a copy does happen, it’s not to the destination host, it’s to the datastore with config file
0
0
Username checks out.
0
1
You can configure ESXi 5.5 or later hosts to store virtual machine swap files with the virtual machine configuration file, or on a local swap file datastore specified for that host.
During a migration with 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. This activity can result in slower migrations with vMotion. If the destination host cannot access the specified swap file location, it stores the swap file with the virtual machine configuration file.
0
0
Actually the Question is incorrect and needs to be modified in:
What happens if the swap file *location* of a virtual machine is inaccessible to the destination host during a vMotion?
Then answer A apply
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vcenterhost.doc/GUID-B8F9F952-EEE7-4C23-A8F6-35E55232263F.html
Otherwise: if the SWAP *file* is not accessible then answer C should be valid. Because you can not store/create a SWAP file when you are unable to read/access it in the first place.
0
0
Option A)
https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vcenterhost.doc/GUID-B8F9F952-EEE7-4C23-A8F6-35E55232263F.html
During a migration with 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. This activity can result in slower migrations with vMotion. If the destination host cannot access the specified swap file location, it stores the swap file with the virtual machine configuration file.
0
0
‘C’
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 by the hypervisor but evidently wouldn’t be available if vMotion without swap has been allowed… 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 VM 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).
1
0