MigrationQemu0.8.2: Difference between revisions

From KVM
No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 23: Line 23:


=== Example/ HOWTO: ===
=== Example/ HOWTO: ===
A is the source host, B is the destination host:  
A is the source host, B is the destination host:
1. Start the VM on B with the exact same parameters as the VM on A, in stopped mode (-S)  
1. Start the VM on B with the exact same parameters as the VM on A, in stopped mode (-S)
 
2. Establish Connection (either A or B can listen/connect):  
2. Establish Connection (either A or B can listen/connect):  


Line 41: Line 43:
* Finish Interface implementation.  
* Finish Interface implementation.  
* 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.
__NOTOC__

Latest revision as of 07:47, 4 February 2009

KVM: migrating a VM on Qemu-0.8.2

Interface:

  • Connection Establishment
migration listen  [local_host:port [remote_host:port]] -- listen on a port
migration connect [local_host:port [remote_host:port]] -- connect to a port
migration getfd fd (socket) -- get established connection (not implemented yet)
  • Management
migration start online/offline
migration cancel

Once started, offline migration can not be canceled.

  • Status
migration status
  • Migration Parameters (not implemented yet)
migration set rate min max offline -- set bandwidth control parameters (min, max, offline)
migration set total_time seconds -- set migration total_time (seconds)
migration show -- show migration parameters
  • Help
migration help

Example/ HOWTO:

A is the source host, B is the destination host:

1. Start the VM on B with the exact same parameters as the VM on A, in stopped mode (-S)

2. Establish Connection (either A or B can listen/connect):

B: migration listen  BIP:port  [AIP:port] (e.g. migration listen 0:4444)
A: migration connect AIP:port   BIP:port  (e.g. migration connect 0:4445 192.168.1.15:4444)

3. Start the migration (always on the source host):

A: migration start offline

4. Check the status (on either host):

migration status

Problems/Todo:

  • handle migration completion better (especially when network problems occur).
  • Online Migration.
  • Finish Interface implementation.
  • Migration does not work while CPU real-mode/protected mode are still changing.