kubevirt: Migrations fail after update to v0.35.0 to v0.36.0-rc.0
/kind bug
What happened:
- start a VMI on kubevirt v0.35.0
- update to v0.36.0-rc.0
- attempt to migrate vmi
migration fails due to changes in the libvirt container that virt-launcher is based on.
Warning Migrated 93s virt-handler, node01 VirtualMachineInstance migration uid f22e325a-df9c-4946-8143-b284aed4e5ae failed. reason:Live migration failed virError(Code=38, Domain=10, Message='Cannot check QEMU binary /usr/libexec/qemu-kvm: No such file or directory')
on 0.36.0-rc.0 the qemu binary is located here.
[root@vmi-ephemeral /]# virsh dumpxml default_vmi-ephemeral | grep qemu
<emulator>/usr/bin/qemu-system-x86_64</emulator>
on 0.35.0 the qemu binary is located here
[root@vmi-ephemeral /]# virsh dumpxml default_vmi-ephemeral | grep qemu
<emulator>/usr/libexec/qemu-kvm</emulator>
This change in location breaks migrations after the update.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 35 (35 by maintainers)
Commits related to this issue
- dockerfile: Create compatibility symlink Before switching to vanilla Fedora packages, we were using rebuilt RHEL content: one of the main differences is that with the former QEMU is installed as /... — committed to andreabolognani/kubevirt-libvirt by andreabolognani 4 years ago
- dockerfile: Create compatibility symlink Before switching to vanilla Fedora packages, we were using rebuilt RHEL content: one of the main differences is that with the former QEMU is installed as /... — committed to andreabolognani/kubevirt-libvirt by andreabolognani 4 years ago
- Revert "dockerfile: Create compatibility symlink" Turns out the migration issues go further than what can be addressed with a symlink, so let's stop creating it. https://github.com/kubevirt/kubevirt... — committed to andreabolognani/kubevirt-libvirt by andreabolognani 4 years ago
This is an annoying design limitation in libvirt as the same MTU field touchs both host side TAP device MTU, and reports guest side MTU. Possibly we should find a way to separate that so we can set guest MTU without touching host side