search for: 71ebb3fc051a48b2b45345b67bb1002b

..._uuid_source = "machine-id" and it didn't work even that nodes have different [root@modi01 kubevirt]# ./cluster-up/ssh.sh kind-1.17.0-worker root@kind-1:/# cat /etc/machine-id [root@modi01 kubevirt]# ./cluster-up/ssh.sh kind-1.17.0-control-plane root@kind-1:/# cat /etc/machine-id 71ebb3fc051a48b2b45345b67bb1002b Thanks On Thu, Mar 26, 2020 at 5:05 PM Daniel P. Berrangé <berrange@redhat.com> wrote: > On Thu, Mar 26, 2020 at 04:47:50PM +0200, Or Shoval wrote: > > Hello > > > > On kubevirt project we are using IpV6 Kind cluster, > > and trying to support migration, > &g...

...rt]# ./cluster-up/ssh.sh kind-1.17.0-worker > root@kind-1:/# cat /etc/machine-id > This machine-id really shouldn't be empty - this may well cause issues in libvirt. > [root@modi01 kubevirt]# ./cluster-up/ssh.sh kind-1.17.0-control-plane > root@kind-1:/# cat /etc/machine-id > 71ebb3fc051a48b2b45345b67bb1002b You can check what UUID libvirtd thinks it has using: $ virsh capabilities |xmllint --xpath /capabilities/host/uuid - If the UUIDs reported are different and you still get the migration error, then it is the duplicate hostname that is the problem. Regards, Daniel -- |: https://berrange.com...

Hello On kubevirt project we are using IpV6 Kind cluster, and trying to support migration, but since both of the containers are on the same host we get this error {"component":"virt-launcher","level":"error","msg":"internal error: Attempt to migrate guest to the same host