Jayd603 commented on issue #10246: URL: https://github.com/apache/cloudstack/issues/10246#issuecomment-2925980006
Yup, stopping the instance and starting solved the problem. I notice that qemu was updated on the host and VMs were running on the old binaries, possibly related. > We noticed we still have it for a part of the virtual machines. > > I tried to get to the bottom of this: > > * I compared the domainXML of both "normal" and "buggy" VM: everything is the same except the disk paths, MAC addresses and other elements unique to a VM. > * When I try to migrate a buggy VM, I see in the agent log that it VIR_MIGRATE_NON_SHARED_DISK option is used, which is the right one. > > However, the libvirt still throws this exception. Thus I suspect there is some bug in the qemu or libvirt process. > > [@Jayd603](https://github.com/Jayd603) What seems to solve it for a buggy VM is stopping and starting it in Cloudstack. Once the VM is stopped/started, it can be live-migrated. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
