Re: Live migration failed to newly provisioned KVM host
Hi Lucian and Marcus, Good day to you, and thank you for your email! Yes, different version of QEMU is the culprit. I have upgraded QEMU to the same version as the other hosts and live migration is now working fine. Thanks for all your help. Cheers. On Sat, Apr 19, 2014 at 6:10 AM, Marcus shadow...@gmail.com wrote: Yes, it looks as though the two machines are running different versions of qemu/libvirt, as the destination doesn't support the machine type that the VM has defined in it's XML on the source host. On Fri, Apr 18, 2014 at 3:43 PM, Nux! n...@li.nux.ro wrote: On 18.04.2014 19:45, Indra Pramana wrote: Unable to migrate due to internal error Process exited while reading console log output: Supported machines are: pc Standard PC (alias of pc-1.0) pc-1.0 Standard PC (default) pc-0.14Standard PC pc-0.13Standard PC pc-0.12Standard PC pc-0.11Standard PC, qemu 0.11 pc-0.10Standard PC, qemu 0.10 isapc ISA-only PC What OS versions are you running and also what KVM versions, do you have anything extra enabled in the agent (eg a specific CPU type vs the generic KVM cpu)? Additionally do check https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/sect-Live_migration_and_RHEL_compatibility.html#Live_Migration_Compatibility -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
Live migration failed to newly provisioned KVM host
Dear all,
I am using CloudStack 4.2.0 and KVM hypervisor. I just provisioned a new
KVM host and I am able to add the host into the zone/cluster, it's up and
routing. This new host is using a different (newer) type of server, but
using the same type of CPUs as per CloudStack's requirements on KVM hosts.
However, when I tried to live migrate a VM from an existing host to the new
host, the migration failed with below error messages:
2014-04-19 01:05:09,448 DEBUG [agent.transport.Request]
(AgentManager-Handler-1:null) Seq 37-1003166672: Processing: { Ans: ,
MgmtId: 161342671900, via: 37, Ver: v1, F
lags: 110,
[{com.cloud.agent.api.MigrateAnswer:{result:false,details:internal
error Process exited while reading console log output: Supported machines
are:\npc
Standard PC (alias of pc-1.0)\npc-1.0 Standard PC
(default)\npc-0.14Standard PC\npc-0.13Standard PC\npc-0.12
Standard PC\npc-0.11Standard PC, qemu 0.11\npc-0.10Standard PC,
qemu 0.10\nisapc ISA-only PC\n,wait:0}}] }
2014-04-19 01:05:09,448 DEBUG [agent.manager.AgentAttache]
(AgentManager-Handler-1:null) Seq 37-1003166672: No more commands found
2014-04-19 01:05:09,448 DEBUG [agent.transport.Request]
(Job-Executor-29:job-14256 = [ bd6a0c53-a1ee-4348-9afd-5a697772d794 ]) Seq
37-1003166672: Received: { Ans: , MgmtId: 161342671900, via: 37, Ver: v1,
Flags: 110, { MigrateAnswer } }
2014-04-19 01:05:09,448 ERROR [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-29:job-14256 = [ bd6a0c53-a1ee-4348-9afd-5a697772d794 ])
Unable to migrate due to internal error Process exited while reading
console log output: Supported machines are:
pc Standard PC (alias of pc-1.0)
pc-1.0 Standard PC (default)
pc-0.14Standard PC
pc-0.13Standard PC
pc-0.12Standard PC
pc-0.11Standard PC, qemu 0.11
pc-0.10Standard PC, qemu 0.10
isapc ISA-only PC
2014-04-19 01:05:09,449 INFO [cloud.vm.VirtualMachineManagerImpl]
(Job-Executor-29:job-14256 = [ bd6a0c53-a1ee-4348-9afd-5a697772d794 ])
Migration was unsuccessful. Cleaning up: VM[User|test-dd]
Any advise on why the migration was unsuccessful?
Looking forward to your reply, thank you.
Cheers.
Re: Live migration failed to newly provisioned KVM host
On 18.04.2014 19:45, Indra Pramana wrote: Unable to migrate due to internal error Process exited while reading console log output: Supported machines are: pc Standard PC (alias of pc-1.0) pc-1.0 Standard PC (default) pc-0.14Standard PC pc-0.13Standard PC pc-0.12Standard PC pc-0.11Standard PC, qemu 0.11 pc-0.10Standard PC, qemu 0.10 isapc ISA-only PC What OS versions are you running and also what KVM versions, do you have anything extra enabled in the agent (eg a specific CPU type vs the generic KVM cpu)? Additionally do check https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/sect-Live_migration_and_RHEL_compatibility.html#Live_Migration_Compatibility -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
Re: Live migration failed to newly provisioned KVM host
Yes, it looks as though the two machines are running different versions of qemu/libvirt, as the destination doesn't support the machine type that the VM has defined in it's XML on the source host. On Fri, Apr 18, 2014 at 3:43 PM, Nux! n...@li.nux.ro wrote: On 18.04.2014 19:45, Indra Pramana wrote: Unable to migrate due to internal error Process exited while reading console log output: Supported machines are: pc Standard PC (alias of pc-1.0) pc-1.0 Standard PC (default) pc-0.14Standard PC pc-0.13Standard PC pc-0.12Standard PC pc-0.11Standard PC, qemu 0.11 pc-0.10Standard PC, qemu 0.10 isapc ISA-only PC What OS versions are you running and also what KVM versions, do you have anything extra enabled in the agent (eg a specific CPU type vs the generic KVM cpu)? Additionally do check https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/sect-Live_migration_and_RHEL_compatibility.html#Live_Migration_Compatibility -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro
