** Tags added: cscc
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1783140
Title:
KVM live migration fails
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux pac
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
** Changed in: ubuntu-power-systems
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
Yes both are known to be flaky - thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1783140
Title:
KVM live migration fails
Status in The Ubuntu-power-systems project:
In Progress
This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.32
---
qemu (1:2.5+dfsg-5ubuntu10.32) xenial; urgency=medium
* fix migration of new guests on ppc64el (LP: #1783140)
Fixed by backporting two patches from the 2.6.x stable branch
- d/p/ubuntu/lp-1783140-virtio-set
I see the following autopkgtest failures:
Regression in autopkgtest for open-iscsi (amd64): test log
Regression in autopkgtest for ubuntu-image (amd64): test log
However looking at the history the particular tests failing seem to be
flaky and unrelated to this SRU, and all the others continue to
Testes as-is (to confirm we hit the bug)
1.0.0 (12:53:43): MIGRATE: in-release migrations
1.1.0 (12:53:43): Clean testbeds
1.1.1 (12:53:43): stop containers
1.1.2 (12:53:43): orig: restore containers from snapshot: xenial
1.1.3 (12:53:43): Restore testkvm-xenial-from
1.1.4 (12:53
Hello bugproxy, or anyone else affected,
Accepted qemu into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.5+dfsg-
5ubuntu10.32 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
Prep complete:
- Regression tests from the PPA
- Tests of the bug being fixed on the PPA
- MP review
- SRU Template
Uploading for consideration by the SRU Team
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
** Description changed:
+ [Impact]
+
+ * Backport fix from the 2.6.2 stable branch to the qemu 2.5 in Xenial
+
+ * Newer guests might use virtio attributes that are clobbered on
+migration with the old qemu code.
+
+ [Test Case]
+
+ * Setup two Xenial hosts on ppc64el
+
+ * Create a
PPA prepared at:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3412
MP:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/354695
Test of the case on the PPA is successful.
But I'll need a regression check on that before going on.
** Changed in: qemu (Ubuntu)
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/354695
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1783140
Title:
KVM live migra
TL;DR:
- a KVM guest with the kernel change as identified above
- works on Bionic host (kernel 4.15 / qemu 2.11 / libvirt 4.0)
- migrating on a Xenial host (kernel 4.4 / qemu 2.5 / libvirt 1.3.1) fails
VQ 0 size 0x100 Guest index 0x8101 inconsistent with Host index 0x81: delta
0x8080
error whi
2a) is an upstream decision to have better disk integrity guarantees.
There is a release notes entry since 17.10 (which is also refrenced from the
18.04 release notes)
=> https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes#qemu_2.10
2b) is I think an upstream change by the PPC devs actually.
I'll
Note to myself:
Combine mainline kernel: git://kernel.ubuntu.com/ubuntu/linux.git
Ubuntu kernel: git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
in one repo.
Get git://kernel.ubuntu.com/ubuntu/kteam-tools.git
Setup needed chroots (amd64 + arch you need)
sudo ./make_chroot bionic amd64 http://archi
Expected closest good/bad as git Builds:
Last 4.13 git tag Ubuntu-4.13.0-32.35 - working
First 4.14 git tag Ubuntu-4.14.0-11.13 -
$ git bisect start
$ git bisect good Ubuntu-4.13.0-32.35
$ git bisect bad Ubuntu-4.14.0-11.13
Build is slow, but it seems I can bisect from here ...
Arr shortly after
** Changed in: ubuntu-power-systems
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1783140
Title:
KVM live migration fails
Status in The Ubuntu-pow
4.15.0-33-generic Failed,
4.4.0-134-generic we know works.
I tested 4.13.0-46-generic and it worked (as expected after the positive 17.10
report in comment #23)
checking different builds from there
Bionic builds (so even the 4.13.0-32.35 being "before" the tested -46 it is the
Bionic build of it
I can also confirm that driving the same case on x86 is not affected.
I'd be glad to pull in PPC-Developers in case they know of any virtio
bugfix that was done in qemu and/or kernel that might be related.
--
You received this bug notification because you are a member of Kernel
Packages, which i
Reproduced:
2018-09-06T08:25:22.816912Z qemu-system-ppc64: VQ 0 size 0x100 Guest index
0x8101 inconsistent with Host index 0xfd: delta 0x8004
2018-09-06T08:25:22.816963Z qemu-system-ppc64: error while loading state for
instance 0x0 of device 'pci@8002000:01.0/virtio-net'
2018-09-06T08:25:
Last comments synced to launchpad indicated that migration of 18.04
guests, using 16.04 hypervisor is still not working.
And it would be nice, if it did.
So to me it looks like the bug is still present, even if you want to
close this ticket on your side.
ps. last comment we have synced prior to
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1783140
Title:
KVM live migration fails
Status i
** Changed in: ubuntu-power-systems
Assignee: Canonical Server Team (canonical-server) => Canonical Kernel
Team (canonical-kernel-team)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
** Changed in: ubuntu-power-systems
Status: New => Incomplete
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-t
Yes, 16.10, 17.04, 17.10 releases are end of life, but they should still
be accessible via http://old-releases.ubuntu.com/ubuntu (16.10, 17.04)
or regular archive mirrors (17.10, but it will at some point move to
old-releases).
So you could deploy 16.04 and dist-upgrade via old-releases.ubuntu.com
I got one P8 machine working but no second one that I could reach from there to
test the migratio.
My usual tricks around that with lxd containers didn't work atm so I rely on
people with more P8 HW.
I asked a few people to poll on P8 Devs to take a look as well.
--
You received this bug notif
Thanks, that makes sense.
So it really seems to be the newer virtio drivers in the guest that triggers it
- which is why the move to the HWE kernel
For test systems, I tried to grab a p8 but it failed to install three times in
a row. Not sure what is broken atm, so at least for a while I'll rel
I did not suggest to install the Cloud Archive code in the 18.04 Guest.
You said your host is 16.04 (Xenial) and there the different UCA's should be
tried to bring new qemu/libvirt code to your host and due to that check if
these newer versions already have a fix we would look for instead of debu
Ok, reading that your guests are customer systems I assume you'd need to
setup a test system somewhere to confirm if different host
qemu/libvirt/kernel versions would fix it.
The list of interesting checks:
16.04 Host as-is + 18.04 Guest + qemu from UCA Ocata
16.04 Host as-is + 18.04 Guest + qemu
Also is this a thing that was triggered once, or reproducible every time you
run it.
In the latter case it might be very hard to track down.
I checked and as part of the qemu verification I do run&migrate older guests in
newer hipervisors.
I do not yet do vice versa in a lot of tests, so even if
Of the listed guests I assume Ubuntu 18.04 has the newest guest Kernel (read
virtio drivers).
Several questions to ensure this is right:
1. could you report the kernel version of each of your test guests
(assuming 4.4 and 4.15 for Ubuntu, but the exact version would be great
to know)
2. it woul
This issue is either in 16.04 qemu (not able to handle the new guests)
or in 18.04s virtio drivers, so I'm adding a linux task for the kernel
first.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kerne
31 matches
Mail list logo
