Public bug reported: This s an issue found while testing for a planned update. Filing it as bug to work together on it.
PPA: https://launchpad.net/~paelzer/+archive/ubuntu/bug-1830243-1832622-1828495-sruregressiontests/+packages (U) = Updated to the new version (O) = orig version as in the archive now Migrations fails from old versions to the new Disco version: - Cosmic (O) -> Disco (U) -> fail - Disco (O) -> Disco (U) -> fail Migration works in other cases where the same backport should be active: - Bionic (O) -> Bionic (U) -> works Also it works if both peers of the migration are updated - Disco (U) -> Disco (U) -> works The same worked without the update - Disco (O) -> Disco (O) -> works And the same code in later versions work as well: - Disco (U) -> Eoan (O) The case that fails is the recently added host-model migration check, so there might be soemthing we miss so far in the test setup. Error: $ virsh migrate --unsafe --live kvmguest-disco-normal qemu+ssh://10.21.151.7/system error: internal error: process exited while connecting to monitor: 2019-07-11T21:33:29.584326Z qemu-system-x86_64: can't apply global Haswell-noTSX-IBRS-x86_64-cpu.md-clear=on: Property '.md-clear' not found TL;DR of the case: 1. Get two Disco systems (x86) 2. one system has the base version, one the new version of qemu 3. start a guest with type "host-model" 4. migrate that guest between the two systems ** Affects: qemu (Ubuntu) Importance: Undecided Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Changed in: qemu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836299 Title: Migration with Host model fails to set md-clear (not yet released in archive) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1836299/+subscriptions -- ubuntu-bugs mailing list email@example.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs