** Changed in: cloud-archive/mitaka
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1626972
Title:
QEMU memfd_create fallback mechanism
** Changed in: cloud-archive/mitaka
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626972
Title:
QEMU memfd_create fallback mechanism change for
For Mitaka, this bug will be included in UCA together with the fix for:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1656480
When it becomes available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package qemu - 1:2.5+dfsg-5ubuntu10.7
---
qemu (1:2.5+dfsg-5ubuntu10.7) xenial; urgency=medium
[ Rafael David Tinoco ]
* Fixed wrong migration blocker when vhost is used (LP: #1626972)
- d/p/vhost_migration-blocker-only-if-shared-log-is-used.patch
Thanks Christian! Will do!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626972
Title:
QEMU memfd_create fallback mechanism change for security drivers
To manage notifications about this bug go
On Tue, Jan 24, 2017 at 1:52 AM, Rafael David Tinoco <
rafael.tin...@canonical.com> wrote:
> Christian, could you please move Xenial for me ? I have some
> end users waiting for this. Thank you very much.
>
I can't - IIRC that is up to the SRU Team, I pinged the #ubuntu-release
channel if one
For me we had enough tests already. Upstream development/tests, Zesty,
Yakkety. Christian, could you please move Xenial for me ? I have some
end users waiting for this. Thank you very much.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ping - we have the next fix for Xenial in the queue - all others are
released now, has this one "baked" enough for Xenial SRU to migrate?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626972
Title:
This bug was fixed in the package qemu - 1:2.6.1+dfsg-0ubuntu5.2
---
qemu (1:2.6.1+dfsg-0ubuntu5.2) yakkety; urgency=medium
[ Rafael David Tinoco ]
* Fixed wrong migration blocker when vhost is used (LP: #1626972)
- d/p/vhost_migration-blocker-only-if-shared-log-is-used.patch
Commit 0d34fbabc13 has been released with QEMU v2.8
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626972
Title:
QEMU memfd_create
Yakkety Verification (with 3.13 kernel from Trusty since a <= 3.17
kernel is needed). This verifies that Ubuntu Cloud Archive repositories
will be alright with this new packages (from Xenial / Yakkety).
## CURRENT
inaddy@(ykvm01):~$ apt-cache policy qemu-kvm
qemu-kvm:
Installed:
Xenial Verification (with 3.13 kernel from Trusty since a <= 3.17 kernel
is needed). This verifies that Ubuntu Cloud Archive repositories will be
alright with this new packages (from Xenial / Yakkety).
## CURRENT
inaddy@(xkvm01):~$ apt-cache policy qemu-kvm
qemu-kvm:
Installed:
Hello Antonio (@arcimboldo)
The fix only makes sense for newer QEMUs (>= Xenial, like the one from
Mitaka Ubuntu Cloud Archive).
OBS:
The "migration check" is done in VHOST initialization functions when the
devices are virtually attached to the virtual machine. If you are using
kernel 3.13 and
@jamespage, @cpaelzer,
I'll verify this fix in couple of days so it can be released.
Thank you!
Rafael
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626972
Title:
QEMU memfd_create fallback
** Also affects: cloud-archive/mitaka
Importance: Undecided
Status: New
** Changed in: cloud-archive/mitaka
Status: New => Fix Committed
** Changed in: cloud-archive
Status: Fix Released => Invalid
--
You received this bug notification because you are a member of Ubuntu
** Also affects: cloud-archive/mitaka
Importance: Undecided
Status: New
** Changed in: cloud-archive/mitaka
Status: New => Fix Committed
** Changed in: cloud-archive
Status: Fix Released => Invalid
--
You received this bug notification because you are a member of Ubuntu
Hi all,
I am facing this issue too, and although I can confirm the patch can be
easily backported to Trusty (we run Mitaka on Trusty), some of our
customers have VMs started with the old qemu and I cannot live migrate
anymore or update qemu without stopping and starting the VM.
Do you have any
Hello Rafael, or anyone else affected,
Accepted qemu into yakkety-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.6.1+dfsg-
0ubuntu5.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package qemu - 1:2.6.1+dfsg-0ubuntu7~cloud0
---
qemu (1:2.6.1+dfsg-0ubuntu7~cloud0) xenial-ocata; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
qemu (1:2.6.1+dfsg-0ubuntu7) zesty; urgency=medium
.
[ Rafael David Tinoco ]
* Fixed
This bug was fixed in the package qemu - 1:2.6.1+dfsg-0ubuntu7~cloud0
---
qemu (1:2.6.1+dfsg-0ubuntu7~cloud0) xenial-ocata; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
qemu (1:2.6.1+dfsg-0ubuntu7) zesty; urgency=medium
.
[ Rafael David Tinoco ]
* Fixed
** Changed in: cloud-archive
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626972
Title:
QEMU memfd_create fallback mechanism change for security
** Changed in: cloud-archive
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1626972
Title:
QEMU memfd_create fallback mechanism change for
Commit 0d34fbabc13 is upstream, so setting this to "Fix committed", too.
** Changed in: qemu
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626972
Title:
Hello Rafael, 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.7 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Ok, update into Zesty has passed and you already supplied the SRU Template.
Uploaded to Xenial and Yakkety queues for the SRU Team to consider your Fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package qemu - 1:2.6.1+dfsg-0ubuntu7
---
qemu (1:2.6.1+dfsg-0ubuntu7) zesty; urgency=medium
[ Rafael David Tinoco ]
* Fixed wrong migration blocker when vhost is used (LP: #1626972)
- d/p/vhost_migration-blocker-only-if-shared-log-is-used.patch
--
Some other stages of my extra tests are currently WIP, but those that
work worked fine on the ppa I built of your debdiffs.
That covers:
- migration with various workloads
- different types of migrations (live, offline, postcopy)
- upgrading onto the new qemu version
- migration into the upgraded
Uploaded into Zesty - per SRU policy (and experience that always
something happens at the last minute at LP build/tests) waiting with the
SRU uploads until that fully migrated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Collection of extra test logs if we have to search for
anything in them later on."
https://bugs.launchpad.net/qemu/+bug/1626972/+attachment/4781992/+files/bug-1626972-migration-fix-tinoco-sts-extraverifications.tgz
--
You received this bug notification because you are
Thanks Rafael - the upstream work on this is excellent!
I already built all those fine and I'm now looking into some regression
checks before considering/doing an upload to Dev-Release & SRU-queue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Patch added: "zesty_qemu_2.6.1+dfsg-0ubuntu7.debdiff"
https://bugs.launchpad.net/qemu/+bug/1626972/+attachment/4781485/+files/zesty_qemu_2.6.1+dfsg-0ubuntu7.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Tue, Nov 22, 2016 at 1:02 PM, Rafael David Tinoco <
rafael.tin...@canonical.com> wrote:
> Right now Zesty is behind Yakkety because of a Security Update. Not sure
> you need me to attach a debdiff for Zesty as well. Let me know.
>
Arr - bad timing It got an upload about 5 minutes ago.
So yes
** Description changed:
- And, when libvirt starts using apparmor, and creating apparmor profiles
- for every virtual machine created in the compute nodes, mitaka qemu (2.5
- - and upstream also) uses a fallback mechanism for creating shared
- memory for live-migrations. This fall back mechanism,
Right now Zesty is behind Yakkety because of a Security Update. Not sure
you need me to attach a debdiff for Zesty as well. Let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626972
Title:
Took some more time here because of LP: #1621269.
** Patch added: "yakkety_qemu_2.6.1+dfsg-0ubuntu5.2.debdiff"
https://bugs.launchpad.net/qemu/+bug/1626972/+attachment/4781464/+files/yakkety_qemu_2.6.1+dfsg-0ubuntu5.2.debdiff
--
You received this bug notification because you are a member of
Thanks Christian,
Then I'll finish this SRU first. Will work in the vhost mmap log file
right after.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626972
Title:
QEMU memfd_create fallback
** Patch added: "xenial_qemu_2.5+dfsg-5ubuntu10.7.debdiff"
https://bugs.launchpad.net/qemu/+bug/1626972/+attachment/4781425/+files/xenial_qemu_2.5+dfsg-5ubuntu10.7.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cloud-archive
Status: New => In Progress
** Changed in: cloud-archive
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626972
Title:
QEMU memfd_create fallback mechanism change for security
On Fri, Nov 18, 2016 at 11:21 AM, Rafael David Tinoco <
rafael.tin...@canonical.com> wrote:
> With customers using vhost-user that might
> still cause migration problems, but, likely, those are the vast
> minority.
>
It is and has migration issues in general atm anyway - see:
For Ubuntu Xenial (Mitaka), Yakkety (Newton), Zesty: Commit 0d34fbabc1
fixes the issue for vhost-net kernel. Vhost-net kernel doesn't use
shared log so the verification is not used and apparmor profiles won't
block the live migration. With customers using vhost-user that might
still cause
** Also affects: qemu (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Zesty)
Importance: Undecided
Assignee: Rafael David Tinoco (inaddy)
Status: In Progress
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status:
** Changed in: qemu (Ubuntu Xenial)
Status: New => In Progress
** Changed in: qemu (Ubuntu Yakkety)
Status: New => In Progress
** Changed in: qemu (Ubuntu Xenial)
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
** Changed in: qemu (Ubuntu Yakkety)
Assignee:
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: New => In Progress
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) => Rafael David Tinoco (inaddy)
--
You received this bug notification because you are a member of
44 matches
Mail list logo
