You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Rakesh Venkatesh <ww...@gmail.com> on 2018/08/10 14:16:29 UTC
Error while migrating vm in ACS 4.7.1
Hello Folks
We are seeing some errors consistently while migrating vm's from one node
another node but still not able to find out the root cause of it. Can
anyone please let me know what might be causing the issue? The vm's are
migrated successfully though
This issue happens when I try to migrate the vm either from cloudmonkey
command or through UI.
Management server:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.3 LTS
Release: 12.04
Codename: precise
Error logs from management server:
Aug 10 12:35:48 node13 sh[50956]: 2018-08-10 12:35:48,243{GMT} INFO [
resource.wrapper.LibvirtMigrateCommandWrapper] (agentRequest-Handler-5:)
Waiting for migration of i-884-15037-VM to complete, waited 3000ms
Aug 10 12:35:48 node13 sh[50956]: 2018-08-10 12:35:48,486{GMT} INFO [
resource.wrapper.LibvirtMigrateCommandWrapper] (agentRequest-Handler-1:)
Waiting for migration of i-884-14365-VM to complete, waited 10000ms
Aug 10 12:35:49 node13 sh[50956]: libvirt: QEMU Driver error : internal
error: unable to execute QEMU command 'migrate-set-capabilities': There's a
migration process in progressAug 10 12:35:49 node13 sh[50956]: 2018-08-10
12:35:49,087{GMT} INFO [resource.wrapper.LibvirtMigrateCommandWrapper]
(agentRequest-Handler-1:) Migration thread for i-884-14365-VM is done
Aug 10 12:35:49 node13 sh[50956]: 2018-08-10 12:35:49,087{GMT} DEBUG
[resource.wrapper.LibvirtMigrateCommandWrapper] (agentRequest-Handler-1:)
Failed to execute while migrating domain: org.libvirt.LibvirtException:
internal error: unable to execute QEMU command 'migrate-set-capabilities':
There's a migration process in progress
Aug 10 12:35:49 node13 sh[50956]: 2018-08-10 12:35:49,087{GMT} DEBUG [kvm.
resource.LibvirtComputingResource] (agentRequest-Handler-1:) Restoring the
metadata of vm snapshots of vm i-884-14365-VM
Aug 10 12:35:49 node13 sh[50956]: 2018-08-10 12:35:49,088{GMT} DEBUG [cloud.
agent.Agent] (agentRequest-Handler-1:) Seq 367-5848768541070742315: { Ans: ,
MgmtId: 48674822042491, via: 367, Ver: v1, Flags: 10, [{
"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException:
internal error: unable to execute QEMU command 'migrate-set-capabilities':
There's a migration process in progress","wait":0}}] }
Agent:
# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial
Error logs from agent:
2018-08-10 12:17:26,030 DEBUG
[resource.wrapper.LibvirtMigrateCommandWrapper]
(agentRequest-Handler-4:null) Failed to execute while migrating domain:
org.libvirt.LibvirtException: internal error: unable to execute QEMU
command 'migrate-set-capabilities': There's a migration process in progress
2018-08-10 12:17:26,030 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-4:null) Restoring the metadata of vm snapshots of vm
i-884-14365-VM 2018-08-10 12:17:26,031 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-4:null) Seq 367-5848768541070742169: { Ans: , MgmtId:
48674822042491, via: 367, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException:
internal error: unable to execute QEMU command 'migrate-set-capabilities':
There's a migration process in progress","wait":0}}] }
2018-08-10 12:17:26,564 INFO
[resource.wrapper.LibvirtMigrateCommandWrapper]
(agentRequest-Handler-4:null) Live migration of instance i-884-14365-VM
initiated
--
Thanks and regards
Rakesh venkatesh
Re: Error while migrating vm in ACS 4.7.1
Posted by Rakesh Venkatesh <ww...@gmail.com>.
Hello Dag
I have seen this issue in two scenarios
1. While migrating multiple vm's
2. When a host is put into maintenance mode
So along with this vm there are other vm's that are being migrated as well.
I also see this in the log which is confusing me
|2018-08-10 12:17:26,030 INFO
[resource.wrapper.LibvirtMigrateCommandWrapper]
(agentRequest-Handler-4:null) Migration thread for i-884-14365-VM is done
Does that answer your question?
On Fri, Aug 10, 2018 at 4:21 PM Dag Sonstebo <Da...@shapeblue.com>
wrote:
> Hi Rakesh,
>
> “There's a migration process in progress” > have you done some digging to
> find out what is actually running?
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
>
> Dag.Sonstebo@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
> On 10/08/2018, 15:16, "Rakesh Venkatesh" <ww...@gmail.com>
> wrote:
>
> Hello Folks
>
> We are seeing some errors consistently while migrating vm's from one
> node
> another node but still not able to find out the root cause of it. Can
> anyone please let me know what might be causing the issue? The vm's are
> migrated successfully though
>
> This issue happens when I try to migrate the vm either from cloudmonkey
> command or through UI.
>
> Management server:
>
> $ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description: Ubuntu 12.04.3 LTS
> Release: 12.04
> Codename: precise
>
>
> Error logs from management server:
>
> Aug 10 12:35:48 node13 sh[50956]: 2018-08-10 12:35:48,243{GMT} INFO [
> resource.wrapper.LibvirtMigrateCommandWrapper]
> (agentRequest-Handler-5:)
> Waiting for migration of i-884-15037-VM to complete, waited 3000ms
> Aug 10 12:35:48 node13 sh[50956]: 2018-08-10 12:35:48,486{GMT} INFO [
> resource.wrapper.LibvirtMigrateCommandWrapper]
> (agentRequest-Handler-1:)
> Waiting for migration of i-884-14365-VM to complete, waited 10000ms
> Aug 10 12:35:49 node13 sh[50956]: libvirt: QEMU Driver error : internal
> error: unable to execute QEMU command 'migrate-set-capabilities':
> There's a
> migration process in progressAug 10 12:35:49 node13 sh[50956]:
> 2018-08-10
> 12:35:49,087{GMT} INFO [resource.wrapper.LibvirtMigrateCommandWrapper]
> (agentRequest-Handler-1:) Migration thread for i-884-14365-VM is done
> Aug 10 12:35:49 node13 sh[50956]: 2018-08-10 12:35:49,087{GMT} DEBUG
> [resource.wrapper.LibvirtMigrateCommandWrapper]
> (agentRequest-Handler-1:)
> Failed to execute while migrating domain: org.libvirt.LibvirtException:
> internal error: unable to execute QEMU command
> 'migrate-set-capabilities':
> There's a migration process in progress
> Aug 10 12:35:49 node13 sh[50956]: 2018-08-10 12:35:49,087{GMT} DEBUG
> [kvm.
> resource.LibvirtComputingResource] (agentRequest-Handler-1:) Restoring
> the
> metadata of vm snapshots of vm i-884-14365-VM
> Aug 10 12:35:49 node13 sh[50956]: 2018-08-10 12:35:49,088{GMT} DEBUG
> [cloud.
> agent.Agent] (agentRequest-Handler-1:) Seq 367-5848768541070742315: {
> Ans: ,
> MgmtId: 48674822042491, via: 367, Ver: v1, Flags: 10, [{
>
> "com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException:
> internal error: unable to execute QEMU command
> 'migrate-set-capabilities':
> There's a migration process in progress","wait":0}}] }
>
>
> Agent:
>
> # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu
> Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial
>
> Error logs from agent:
>
>
> 2018-08-10 12:17:26,030 DEBUG
> [resource.wrapper.LibvirtMigrateCommandWrapper]
> (agentRequest-Handler-4:null) Failed to execute while migrating domain:
> org.libvirt.LibvirtException: internal error: unable to execute QEMU
> command 'migrate-set-capabilities': There's a migration process in
> progress
> 2018-08-10 12:17:26,030 DEBUG [kvm.resource.LibvirtComputingResource]
> (agentRequest-Handler-4:null) Restoring the metadata of vm snapshots
> of vm
> i-884-14365-VM 2018-08-10 12:17:26,031 DEBUG [cloud.agent.Agent]
> (agentRequest-Handler-4:null) Seq 367-5848768541070742169: { Ans: ,
> MgmtId:
> 48674822042491, via: 367, Ver: v1, Flags: 10,
>
> [{"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException:
> internal error: unable to execute QEMU command
> 'migrate-set-capabilities':
> There's a migration process in progress","wait":0}}] }
>
> 2018-08-10 12:17:26,564 INFO
> [resource.wrapper.LibvirtMigrateCommandWrapper]
> (agentRequest-Handler-4:null) Live migration of instance i-884-14365-VM
> initiated
>
>
> --
> Thanks and regards
> Rakesh venkatesh
>
>
>
--
Thanks and regards
Rakesh venkatesh
Re: Error while migrating vm in ACS 4.7.1
Posted by Dag Sonstebo <Da...@shapeblue.com>.
Hi Rakesh,
“There's a migration process in progress” > have you done some digging to find out what is actually running?
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
Dag.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
On 10/08/2018, 15:16, "Rakesh Venkatesh" <ww...@gmail.com> wrote:
Hello Folks
We are seeing some errors consistently while migrating vm's from one node
another node but still not able to find out the root cause of it. Can
anyone please let me know what might be causing the issue? The vm's are
migrated successfully though
This issue happens when I try to migrate the vm either from cloudmonkey
command or through UI.
Management server:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.3 LTS
Release: 12.04
Codename: precise
Error logs from management server:
Aug 10 12:35:48 node13 sh[50956]: 2018-08-10 12:35:48,243{GMT} INFO [
resource.wrapper.LibvirtMigrateCommandWrapper] (agentRequest-Handler-5:)
Waiting for migration of i-884-15037-VM to complete, waited 3000ms
Aug 10 12:35:48 node13 sh[50956]: 2018-08-10 12:35:48,486{GMT} INFO [
resource.wrapper.LibvirtMigrateCommandWrapper] (agentRequest-Handler-1:)
Waiting for migration of i-884-14365-VM to complete, waited 10000ms
Aug 10 12:35:49 node13 sh[50956]: libvirt: QEMU Driver error : internal
error: unable to execute QEMU command 'migrate-set-capabilities': There's a
migration process in progressAug 10 12:35:49 node13 sh[50956]: 2018-08-10
12:35:49,087{GMT} INFO [resource.wrapper.LibvirtMigrateCommandWrapper]
(agentRequest-Handler-1:) Migration thread for i-884-14365-VM is done
Aug 10 12:35:49 node13 sh[50956]: 2018-08-10 12:35:49,087{GMT} DEBUG
[resource.wrapper.LibvirtMigrateCommandWrapper] (agentRequest-Handler-1:)
Failed to execute while migrating domain: org.libvirt.LibvirtException:
internal error: unable to execute QEMU command 'migrate-set-capabilities':
There's a migration process in progress
Aug 10 12:35:49 node13 sh[50956]: 2018-08-10 12:35:49,087{GMT} DEBUG [kvm.
resource.LibvirtComputingResource] (agentRequest-Handler-1:) Restoring the
metadata of vm snapshots of vm i-884-14365-VM
Aug 10 12:35:49 node13 sh[50956]: 2018-08-10 12:35:49,088{GMT} DEBUG [cloud.
agent.Agent] (agentRequest-Handler-1:) Seq 367-5848768541070742315: { Ans: ,
MgmtId: 48674822042491, via: 367, Ver: v1, Flags: 10, [{
"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException:
internal error: unable to execute QEMU command 'migrate-set-capabilities':
There's a migration process in progress","wait":0}}] }
Agent:
# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial
Error logs from agent:
2018-08-10 12:17:26,030 DEBUG
[resource.wrapper.LibvirtMigrateCommandWrapper]
(agentRequest-Handler-4:null) Failed to execute while migrating domain:
org.libvirt.LibvirtException: internal error: unable to execute QEMU
command 'migrate-set-capabilities': There's a migration process in progress
2018-08-10 12:17:26,030 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-4:null) Restoring the metadata of vm snapshots of vm
i-884-14365-VM 2018-08-10 12:17:26,031 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-4:null) Seq 367-5848768541070742169: { Ans: , MgmtId:
48674822042491, via: 367, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.MigrateAnswer":{"result":false,"details":"org.libvirt.LibvirtException:
internal error: unable to execute QEMU command 'migrate-set-capabilities':
There's a migration process in progress","wait":0}}] }
2018-08-10 12:17:26,564 INFO
[resource.wrapper.LibvirtMigrateCommandWrapper]
(agentRequest-Handler-4:null) Live migration of instance i-884-14365-VM
initiated
--
Thanks and regards
Rakesh venkatesh