Changes

Jump to: navigation, search

Migrating Xen domainU Guests Between Host Systems

1,040 bytes added, 15:36, 12 June 2008
Checking the Xen Log
After a short period of time the guest domain will no longer appear on the list of guests on the source host and will now be running on the target host.
== Checking the Xen Log for Migration Errors ==
The migration from a user's perspective is a silent process. This can make tracking down problems since a failed migration will not report anything on the command-line. If problems are encountered during the migration the first place to look for information is the Xen log file which can be viewed by running the ''xm log'' command. The following shows partial output from a successful live migration:
</pre>
If the migration fails the log output will likely differ in some significant way from the above log output. A common cause for the migration failing is the result of there being insufficient memory on the target system to accommodate the guest domain.In this situation the Xen log file will likely contain output similar to the following: <pre>[2008-06-12 10:53:48 xend 2414] DEBUG (balloon:133) Balloon: 31656 KiB free; 0 to scrub; need 524288; retries: 20.[2008-06-12 10:54:10 xend.XendDomainInfo 2414] DEBUG (XendDomainInfo:1557) XendDomainInfo.destroy: domid=4[2008-06-12 10:54:10 xend.XendDomainInfo 2414] DEBUG (XendDomainInfo:1566) XendDomainInfo.destroyDomain(4)[2008-06-12 10:54:10 xend 2414] ERROR (XendDomain:268) Restore failedTraceback (most recent call last): File "/usr/lib/python2.4/site-packages/xen/xend/XendDomain.py", line 263, in domain_restore_fd return XendCheckpoint.restore(self, fd) File "/usr/lib/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 207, in restore balloon.free(memory + shadow) File "/usr/lib/python2.4/site-packages/xen/xend/balloon.py", line 166, in free raise VmError(VmError: I need 524288 KiB, but dom0_min_mem is 262144 and shrinking to 262144 KiB would leave only 248744 KiB free.</pre>
1,798
edits

Navigation menu