when I am migrating a resized VM, it's fail. [closed]
Hi, guys, I created a cirros vm and I can migrated it between two compute node. It's OK. But, when I resize it, then migrated it , it will occur error, migration fail. The log look like below:
openstack version: folsom server OS: ubuntu
source node: 2014-08-11 18:02:30 28890 ERROR nova.virt.libvirt.driver [-] [instance: 4e892e83-cf58-46fd-aa47-50bc78ecf045] Live Migration failure: operation failed: migration job: unexpectedly failed
source node libvirt log: 2014-08-11 07:01:46.755+0000: 2470: error : qemuMigrationUpdateJobStatus:946 : operation failed: migration job: unexpectedly failed
target node: 2014-08-11 18:02:12 12956 ERROR nova.virt.libvirt.driver [-] [instance: 4e892e83-cf58-46fd-aa47-50bc78ecf045] During wait destroy, instance disappeared.
So, I want to know why don't resize it, it can be migrated. But after resize, it occur error. Thank you!
What is the command you are using to resize the VM?
We have used the virt-resize and it worked so far all the time moving from one node to another. Some links you may already know:
http://libguestfs.org/virt-resize.1.html
http://docs.openstack.org/image-guide...
Thank for your reply. I use the command like this: nova resize f81cdd11-b30b-4187-a654-55e99770d512 f97bfa70-e15b-4876-86cb-cfbb38bccaf6 Is the usage correct? :)
See this link below for nova resize and confirm your resize is OK or not. Add the correct flavor for resize. http://docs.openstack.org/user-guide/...
I resized a vm successfully, then migration is fail. But it won't occur error before I resize it. So why?
You mentioned Folsom and Ubuntu. May be you could try Icehouse and Ubuntu1404 in which I could live migrate like this.
nova resize NovaID flavorID
nova resize-confirm NovaID
nova list
nova live-migration NovaID HostName
-- the server status becomes active after this 'resize-confirm' command.
-- See whether you can access the VM after resize in your current machine before migrate.
-- If not, try 'nova revert-resize NovaID' and see that instance coming up.
-- You can create a snapshot of the image after resize and move to the destination node, create an instance in destination node to see the resized image indeed works.