** Description changed: [ Impact ] - * failure on migration of VM from Jammy to Noble - on Intel CPUs with waitpkg feature + * failure on migration of VM from Jammy to Noble + on Intel CPUs with waitpkg feature [ Test Plan ] - 1) On Intel CPU with waitpkg feature - (Granite Rapids or newer) + 1) On Intel CPU with waitpkg feature + (Granite Rapids or newer) - $ cat /proc/cpuinfo | grep waitpkg + $ cat /proc/cpuinfo | grep waitpkg - 2) create 2 lxd containers: jammy and Noble - install virt stack in the containers - $ apt install qemu-system-x86 libvirt-daemon-system libvirt-clients ovmf + 2) create 2 lxd containers: jammy and Noble + install virt stack in the containers + $ apt install qemu-system-x86 libvirt-daemon-system libvirt-clients ovmf - 3) In the jammy container, create a VM with the following domain + 3) In the jammy container, create a VM with the following domain definition: - <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> - <name>test-migration</name> - <memory unit='GiB'>2</memory> - <os> - <type arch='x86_64' machine='q35'>hvm</type> - </os> - <cpu mode='host-model' check='partial'/> - </domain> + <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> + <name>test-migration</name> + <memory unit='GiB'>2</memory> + <os> + <type arch='x86_64' machine='q35'>hvm</type> + </os> + <cpu mode='host-model' check='partial'/> + </domain> - $ virsh define vm.xml - $ virsh start test-migration + $ virsh define vm.xml + $ virsh start test-migration - 4) Add Noble host into /etc/hosts + generate SSH private key + deploy key to - Noble container - - 5) Migrate to Noble - $ virsh migrate --unsafe --live test-migration qemu+ssh://10.111.230.165/system - (10.111.230.165 = IP of the Noble container) + 4) Add Noble host into /etc/hosts + generate SSH private key + deploy key to + Noble container + + 5) Migrate to Noble + $ virsh migrate --unsafe --live test-migration qemu+ssh://10.111.230.165/system + (10.111.230.165 = IP of the Noble container) We get the following error on the migration: error: operation failed: guest CPU doesn't match specification: missing features: waitpkg - [ Where problems could occur ] - * This fix enable the feature waitpkg and can unveil hidden bugs + * This fix enable the feature waitpkg and can unveil hidden bugs related to the waitpkg feature in the VMs where software leverages it. + Such effects would be limited to x86 Intel CPUS. The model mapping is + never easy, but that should more or less translate to Core (Alder Lake & + Newer, Core Ultra (Meteor Lake & Newer) and Xeon (Sapphire Rapids and + newer). Thereby it is one of those cases that are like "not everywhere, + but we should watch out for these CPUs types when reports about + potential regressions come in". [ Other Info ] - * I did test the proposed fix with different migration combination and + * I did test the proposed fix with different migration combination and it is a success. - ---- The migration tests fail for cross migration from jammy to noble: lxc exec testkvm-jammy-from -- virsh migrate --unsafe --live kvmguest- jammy-normal qemu+ssh://10.177.76.31/system error: operation failed: guest CPU doesn't match specification: missing features: waitpkg
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2142099 Title: migration jammy to noble fails due to missing feature : waitpkg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2142099/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
