Migration - Revision history

Fghaas: /* Problems / Todo */ Mention limitations on nested guests, and add cross-reference to Nested Guests page

2018-02-08T17:40:21Z

Problems / Todo: Mention limitations on nested guests, and add cross-reference to Nested Guests page

← Older revision		Revision as of 13:40, 8 February 2018
Line 74:		Line 74:
	* handle migration completion better (especially when network problems occur).		* handle migration completion better (especially when network problems occur).
	* More informative status.		* More informative status.
	* Migration does not work while CPU real-mode/protected mode are still changing.		* Migration does not work while CPU real-mode/protected mode are still changing.
			* Migration does not work when running [[Nested Guests]]: if you are running a KVM guest that is itself running a KVM guest, migration of the unnested guest (including savevm/loadvm as described below) will result in undefined behavior.

	== savevm/loadvm to an external state file (using pseudo-migration) ==		== savevm/loadvm to an external state file (using pseudo-migration) ==

Bsd: anchor is not informative

2015-05-16T20:31:45Z

anchor is not informative

← Older revision		Revision as of 16:31, 16 May 2015
Line 31:		Line 31:
	* Open		* Open

	~~[[Anchor(1)]]~~ 1 These features are unique to KVM Live Migration as far as I know. If you know of other hypervisor that support any of them please update this page or let me (Uri) know.		1 These features are unique to KVM Live Migration as far as I know. If you know of other hypervisor that support any of them please update this page or let me (Uri) know.

	== User Interface ==		== User Interface ==

Uril: replace '-incoming stdio' with '-incoming "exec:cat" + cleanup (mainly whitespace)

2009-06-09T16:41:54Z

replace '-incoming stdio' with '-incoming "exec:cat" + cleanup (mainly whitespace)

← Older revision		Revision as of 12:41, 9 June 2009
Line 55:		Line 55:
	A is the source host, B is the destination host:		A is the source host, B is the destination host:
	===''TCP'' example:===		===''TCP'' example:===
	1. Start the VM on B with the exact same parameters as the VM on A, in migration-listen mode (-incoming tcp:0:4444 (or other PORT))		1. Start the VM on B with the exact same parameters as the VM on A, in migration-listen mode:
	2. Start the migration (always on the source host):		B: <qemu-command-line> -incoming tcp:0:4444 (or other PORT))
	A: migrate -d tcp:B:4444 (or other PORT)		2. Start the migration (always on the source host):
	3. Check the status (on A only):		A: migrate -d tcp:B:4444 (or other PORT)
	info migrate		3. Check the status (on A only):
			A: (qemu) info migrate

	===''Offline'' example:===		===''Offline'' example:===
Line 85:		Line 86:

	** Load		** Load
	gzip -c -d STATEFILE.gz \| <qemu-command-line> -incoming ~~stdio~~		gzip -c -d STATEFILE.gz \| <qemu-command-line> -incoming "exec: cat" or
			<qemu-command-line> -incoming "exec: gzip -c -d STATEFILE.gz"
	* Save VM State into an encrypted file (assumes KEY has already been generated)		* Save VM State into an encrypted file (assumes KEY has already been generated)
	** Save		** Save
	stop		stop
	migrate_set_speed 4095m		migrate_set_speed 4095m
	migrate "exec:gpg -q -e -r KEY -o STATFILE.gpg"		migrate "exec:gpg -q -e -r KEY -o STATFILE.gpg"

	* Load VM state from an encrypted file		* Load VM state from an encrypted file
	gpg -q -d -r KEY STATEFILE.gpg \| <qemu-command-line> -incoming ~~stdio~~		gpg -q -d -r KEY STATEFILE.gpg \| <qemu-command-line> -incoming "exec:cat"

	== more exec: options ==		== more exec: options ==
Line 103:		Line 105:

	** on host B		** on host B
	nc -l 4444 \| gpg -q -d -r KEY \| <qemu-command-line> -incoming ~~stdio~~		nc -l 4444 \| gpg -q -d -r KEY \| <qemu-command-line> -incoming "exec:cat"

	== Algorithm (the short version) ==		== Algorithm (the short version) ==

Themel: Removed file:// migration reference - no longer in current kvm.

2009-05-26T08:33:09Z

Removed file:// migration reference - no longer in current kvm.

← Older revision		Revision as of 04:33, 26 May 2009
Line 76:		Line 76:

	== savevm/loadvm to an external state file (using pseudo-migration) ==		== savevm/loadvm to an external state file (using pseudo-migration) ==
	* let the state file be /saved_images/VM.STATE
	* savevm (qemu monitor):
	~~stop~~
	~~migrate file:///saved_images/VM.STATE~~
	* loadvm (qemu command line and qemu monitor):
	~~<qemu-command-line> -incoming file:///saved_images/VM.STATE~~
	~~cont~~

	~~== more exec: options ==~~
	* To be supported directly by Migration Protocols, but until then...		* To be supported directly by Migration Protocols, but until then...
	* Save VM state into a compressed file		* Save VM state into a compressed file
Line 102:		Line 94:
	* Load VM state from an encrypted file		* Load VM state from an encrypted file
	gpg -q -d -r KEY STATEFILE.gpg \| <qemu-command-line> -incoming stdio		gpg -q -d -r KEY STATEFILE.gpg \| <qemu-command-line> -incoming stdio

			== more exec: options ==

	* Send encrypted VM state from host A to host B (Note: ssh is probably better, this is just for show)		* Send encrypted VM state from host A to host B (Note: ssh is probably better, this is just for show)

Mangoo: how to disable NX

2009-03-24T13:56:46Z

how to disable NX

← Older revision		Revision as of 09:56, 24 March 2009
Line 9:		Line 9:
	You can migrate a guest between an AMD host to an Intel host and back. Naturally, a 64-bit guest can only be migrated to a 64-bit host, but a 32-bit guest can be migrated at will.		You can migrate a guest between an AMD host to an Intel host and back. Naturally, a 64-bit guest can only be migrated to a 64-bit host, but a 32-bit guest can be migrated at will.

	There are some older Intel processors which don't support NX (or XD), which may cause problems in a cluster which includes NX-supporting hosts. ~~We may add~~ a ~~feature to hide NX if this proves to be~~ a ~~problem in actual deployments.~~		There are some older Intel processors which don't support NX (or XD), which may cause problems in a cluster which includes NX-supporting hosts. To disable NX for a given guest, start it with such a parameter: -cpu qemu64,-nx

	== Requirements ==		== Requirements ==

Jeremy.perry@redhat.com at 14:16, 11 March 2009

2009-03-11T14:16:30Z

← Older revision		Revision as of 10:16, 11 March 2009
Line 1:		Line 1:
			=Migration=

	== Introduction ==		== Introduction ==
	KVM currently supports savevm/loadvm and offline or live migration		KVM currently supports savevm/loadvm and offline or live migration

WikiSysop: /* more exec: options */

2009-02-04T10:47:23Z

more exec: options

← Older revision		Revision as of 06:47, 4 February 2009
Line 101:		Line 101:
	gpg -q -d -r KEY STATEFILE.gpg \| <qemu-command-line> -incoming stdio		gpg -q -d -r KEY STATEFILE.gpg \| <qemu-command-line> -incoming stdio
	* Send encrypted VM state from host A to host B (Note: ssh is probably better, this is just for show)		* Send encrypted VM state from host A to host B (Note: ssh is probably better, this is just for show)

	** on host A		** on host A
	migrate "exec:gpg -q -e -r KEY \| nc B 4444"		migrate "exec:gpg -q -e -r KEY \| nc B 4444"

	** on host B		** on host B
	nc -l 4444 \| gpg -q -d -r KEY \| <qemu-command-line> -incoming stdio		nc -l 4444 \| gpg -q -d -r KEY \| <qemu-command-line> -incoming stdio

WikiSysop: /* more exec: options */

2009-02-04T10:46:44Z

more exec: options

← Older revision		Revision as of 06:46, 4 February 2009
Line 85:		Line 85:
	* To be supported directly by Migration Protocols, but until then...		* To be supported directly by Migration Protocols, but until then...
	* Save VM state into a compressed file		* Save VM state into a compressed file
	* Save		** Save
	stop		stop
	migrate_set_speed 4095m		migrate_set_speed 4095m
	migrate "exec:gzip -c > STATEFILE.gz"		migrate "exec:gzip -c > STATEFILE.gz"

	* Load		** Load
	gzip -c -d STATEFILE.gz \| <qemu-command-line> -incoming stdio		gzip -c -d STATEFILE.gz \| <qemu-command-line> -incoming stdio
	* Save VM State into an encrypted file (assumes KEY has already been generated)		* Save VM State into an encrypted file (assumes KEY has already been generated)

WikiSysop: /* more exec: options */

2009-02-04T10:46:14Z

more exec: options

← Older revision		Revision as of 06:46, 4 February 2009
Line 93:		Line 93:
	gzip -c -d STATEFILE.gz \| <qemu-command-line> -incoming stdio		gzip -c -d STATEFILE.gz \| <qemu-command-line> -incoming stdio
	* Save VM State into an encrypted file (assumes KEY has already been generated)		* Save VM State into an encrypted file (assumes KEY has already been generated)
	* Save		** Save
	stop		stop
	migrate_set_speed 4095m		migrate_set_speed 4095m
Line 101:		Line 101:
	gpg -q -d -r KEY STATEFILE.gpg \| <qemu-command-line> -incoming stdio		gpg -q -d -r KEY STATEFILE.gpg \| <qemu-command-line> -incoming stdio
	* Send encrypted VM state from host A to host B (Note: ssh is probably better, this is just for show)		* Send encrypted VM state from host A to host B (Note: ssh is probably better, this is just for show)
	* on host A		** on host A
	migrate "exec:gpg -q -e -r KEY \| nc B 4444"		migrate "exec:gpg -q -e -r KEY \| nc B 4444"
	* on host B		** on host B
	nc -l 4444 \| gpg -q -d -r KEY \| <qemu-command-line> -incoming stdio		nc -l 4444 \| gpg -q -d -r KEY \| <qemu-command-line> -incoming stdio

WikiSysop: /* Algorithm (the short version) */

2009-02-04T10:45:30Z

Algorithm (the short version)

← Older revision		Revision as of 06:45, 4 February 2009
Line 121:		Line 121:
	5. Continue the guest		5. Continue the guest
	* On destination upon success		* On destination upon success
	*+ Broadcast "I'm over here" Ethernet packet to announce new location of NIC(s).		** Broadcast "I'm over here" Ethernet packet to announce new location of NIC(s).
	* On source upon failure (with one exception).		* On source upon failure (with one exception).


	Instructions for kvm-13 and below: [[MigrationQemu0.8.2]].		Instructions for kvm-13 and below: [[MigrationQemu0.8.2]].