Status: New
Owner: ----
New issue 824 by [email protected]: Problem with xm migrate syntax
http://code.google.com/p/ganeti/issues/detail?id=824
What software version are you running? Please provide the output of "gnt-
cluster --version", "gnt-cluster version", and "hspace --version".
root@vm01:~# gnt-cluster --version
gnt-cluster (ganeti v2.10.3) 2.10.3
root@vm01:~# gnt-cluster version
Software version: 2.10.3
Internode protocol: 2100000
Configuration format: 2100000
OS api version: 20
Export interface: 0
VCS version: (ganeti) version v2.10.3
root@vm01:~# hspace --version
hspace (ganeti) version v2.10.3
compiled with ghc 7.4
running on linux x86_64
using ganeti build from:
http://ppa.launchpad.net/pkg-ganeti-devel/lts/ubuntu precise main
What distribution are you using?
Ubuntu 12.04.4 LTS
What steps will reproduce the problem?
1. gnt-instance add -t drbd -o debootstrap+default -s 4G instance1
This produces a running instance as expected....
2. gnt-instance list
Instance Hypervisor OS
Primary_node Status Memory
instance1.foobar.com xen-pvm debootstrap+default
vm02.foobar.com running 128M
3. gnt-instance migrate instance1
What is the expected output?
Expect that the machine would be migrated to vm01
What do you see instead?
Instance instance1 will be migrated. Note that migration might impact
the instance if anything goes wrong (e.g. due to bugs in the
hypervisor). Continue?
y/[n]/?: y
Sat May 10 12:42:54 2014 Migrating instance instance1.foobar.com
Sat May 10 12:42:54 2014 * checking disk consistency between source and
target
Sat May 10 12:42:54 2014 * switching node vm01.foobar.com to secondary mode
Sat May 10 12:42:55 2014 * changing into standalone mode
Sat May 10 12:42:55 2014 * changing disks into dual-master mode
Sat May 10 12:42:56 2014 * wait until resync is done
Sat May 10 12:42:56 2014 * preparing vm01.foobar.com to accept the instance
Sat May 10 12:42:57 2014 * migrating instance to vm01.foobar.com
Sat May 10 12:42:57 2014 Migration failed, aborting
Sat May 10 12:42:57 2014 * switching node vm01.foobar.com to secondary mode
Sat May 10 12:42:57 2014 * changing into standalone mode
Sat May 10 12:42:58 2014 * changing disks into single-master mode
Sat May 10 12:42:59 2014 * wait until resync is done
Failure: command execution error:
Could not migrate instance instance1.foobar.com: Failed to migrate
instance: Failed to migrate instance instance1.foobar.com: Usage: xm
migrate <Domain> <Host>
Migrate a domain to another machine.
Options:
-h, --help Print this help.
-l, --live Use live migration.
-p=portnum, --port=portnum
Use specified port for migration.
-n=nodenum, --node=nodenum
Use specified NUMA node on target.
-s, --ssl Use ssl connection for migration.
-c, --change_home_server
Change home server for managed domains.
Error: can't connect: [Errno 104] Connection reset by peer
Please provide any additional information below.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
