Hi,
Do the hosts have the same number of cpu core numbers and threads ?
-Wei
On Thu, 15 Feb 2024 at 15:24, Vivek Kumar <vivek.ku...@indiqus.com.invalid>
wrote:
> Hello,
>
> I have just deployed a new ACS 4.18.1 with KVM ( Ubuntu 22 ). I have 5
> hosts in a cluster but only on 2 hosts migration is working, on another 3
> it’s not working. Logs says below -
>
> 2024-02-15 12:34:09,831 ERROR [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-11:ctx-28d97c02 job-53/job-54 ctx-779439d6)
> (logid:0d5e6412) Invocation exception, caused by:
> com.cloud.utils.exception.CloudRuntimeException: Exception during migrate:
> org.libvirt.LibvirtException: Invalid value '0-87' for 'cpuset.cpus':
> Invalid argument
> 2024-02-15 12:34:09,831 INFO [c.c.v.VmWorkJobHandlerProxy]
> (Work-Job-Executor-11:ctx-28d97c02 job-53/job-54 ctx-779439d6)
> (logid:0d5e6412) Rethrow exception
> com.cloud.utils.exception.CloudRuntimeException: Exception during migrate:
> org.libvirt.LibvirtException: Invalid value '0-87' for 'cpuset.cpus':
> Invalid argument
> 2024-02-15 12:34:09,831 DEBUG [c.c.v.VmWorkJobDispatcher]
> (Work-Job-Executor-11:ctx-28d97c02 job-53/job-54) (logid:0d5e6412) Done
> with run of VM work job: com.cloud.vm.VmWorkMigrate for VM 5, job origin: 53
> 2024-02-15 12:34:09,831 ERROR [c.c.v.VmWorkJobDispatcher]
> (Work-Job-Executor-11:ctx-28d97c02 job-53/job-54) (logid:0d5e6412) Unable
> to complete AsyncJobVO: {id:54, userId: 2, accountId: 2, instanceType:
> null, instanceId: null, cmd: com.cloud.vm.VmWorkMigrate, cmdInfo:
> rO0ABXNyABpjb20uY2xvdWQudm0uVm1Xb3JrTWlncmF0ZRdxQXtPtzYqAgAGSgAJc3JjSG9zdElkTAAJY2x1c3RlcklkdAAQTGphdmEvbGFuZy9Mb25nO0wABmhvc3RJZHEAfgABTAAFcG9kSWRxAH4AAUwAB3N0b3JhZ2V0AA9MamF2YS91dGlsL01hcDtMAAZ6b25lSWRxAH4AAXhyABNjb20uY2xvdWQudm0uVm1Xb3Jrn5m2VvAlZ2sCAARKAAlhY2NvdW50SWRKAAZ1c2VySWRKAAR2bUlkTAALaGFuZGxlck5hbWV0ABJMamF2YS9sYW5nL1N0cmluZzt4cAAAAAAAAAACAAAAAAAAAAIAAAAAAAAABXQAGVZpcnR1YWxNYWNoaW5lTWFuYWdlckltcGwAAAAAAAAAAXNyAA5qYXZhLmxhbmcuTG9uZzuL5JDMjyPfAgABSgAFdmFsdWV4cgAQamF2YS5sYW5nLk51bWJlcoaslR0LlOCLAgAAeHAAAAAAAAAAAXNxAH4ABwAAAAAAAAAGcQB-AAlwcQB-AAk,
> cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> result: null, initMsid: 12079656927289, completeMsid: null, lastUpdated:
> null, lastPolled: null, created: Thu Feb 15 12:34:07 UTC 2024, removed:
> null}, job origin:53
> com.cloud.utils.exception.CloudRuntimeException: Exception during migrate:
> org.libvirt.LibvirtException: Invalid value '0-87' for 'cpuset.cpus':
> Invalid argument
> at
> com.cloud.vm.VirtualMachineManagerImpl.migrate(VirtualMachineManagerImpl.java:2795)
> at
> com.cloud.vm.VirtualMachineManagerImpl.orchestrateMigrate(VirtualMachineManagerImpl.java:2659)
> at
> com.cloud.vm.VirtualMachineManagerImpl.orchestrateMigrate(VirtualMachineManagerImpl.java:5439)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> com.cloud.vm.VmWorkJobHandlerProxy.handleVmWorkJob(VmWorkJobHandlerProxy.java:107)
> at
> com.cloud.vm.VirtualMachineManagerImpl.handleVmWorkJob(VirtualMachineManagerImpl.java:5536)
> at
> com.cloud.vm.VmWorkJobDispatcher.runJob(VmWorkJobDispatcher.java:102)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
> at
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
> at
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
> at
> org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:568)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at
> java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:829)
> 2024-02-15 12:34:09,837 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Work-Job-Executor-11:ctx-28d97c02 job-53/job-54) (logid:0d5e6412) Complete
> async job-54, jobStatus: FAILED, resultCode: 0, result: rO0ABXNy
>
>
> All the hypvervisor nodes are simmer, and installed agent and setup using
> the automations script. Any suggestion what to look at ?
>
>
>
>
>
>
>
> Vivek Kumar
> Sr. Manager - Cloud & DevOps
> TechOps | Indiqus Technologies
>
> vivek.ku...@indiqus.com <mailto:vivek.ku...@indiqus.com>
> www.indiqus.com <https://www.indiqus.com/>
>
>
>
>
>
> --
> This message is intended only for the use of the individual or entity to
> which it is addressed and may contain confidential and/or privileged
> information. If you are not the intended recipient, please delete the
> original message and any copy of it from your computer system. You are
> hereby notified that any dissemination, distribution or copying of this
> communication is strictly prohibited unless proper authorization has been
> obtained for such action. If you have received this communication in
> error,
> please notify the sender immediately. Although IndiQus attempts to sweep
> e-mail and attachments for viruses, it does not guarantee that both are
> virus-free and accepts no liability for any damage sustained as a result
> of
> viruses.
>
