This bug was fixed in the package linux - 4.13.0-25.29
---
linux (4.13.0-25.29) artful; urgency=low
* linux: 4.13.0-25.29 -proposed tracker (LP: #1741955)
* CVE-2017-5754
- Revert "UBUNTU: [Config] updateconfigs to enable PTI"
- [Config] Enable PTI with UNWINDER_FRAME_POI
qemu (1:2.8+dfsg-3ubuntu2.9~cloud1) xenial-ocata; urgency=medium
* reverted "Backport support for GICv3/vITS save/restore (LP 1710019)."
as there was an arm regressions found in zesty-proposed (cancelled before
SRU release).
--
You received this bug notification because you are a membe
This fix has been reverted in qemu 1:2.8+dfsg-3ubuntu2.9~cloud1 to align
with Zesty. qemu 1:2.8+dfsg-3ubuntu2.9~cloud1 has now been released to
ocata-updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Changed in: cloud-archive/ocata
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710019
Title:
support GICv3 ITS save/restore & migration
To manage notificat
This bug was fixed in the package qemu - 1:2.8+dfsg-3ubuntu2.8~cloud0
---
qemu (1:2.8+dfsg-3ubuntu2.8~cloud0) xenial-ocata; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
qemu (1:2.8+dfsg-3ubuntu2.8) zesty; urgency=medium
.
* Backport support for GICv3/vITS sa
This bug was fixed in the package linux - 4.13.0-19.22
---
linux (4.13.0-19.22) artful; urgency=low
* linux: 4.13.0-19.22 -proposed tracker (LP: #1736118)
* CVE-2017-1000405
- mm, thp: Do not make page table dirty unconditionally in touch_p[mu]d()
linux (4.13.0-18.21) artful
Oh I see that was artful, thanks dannf for clarifiaction.
So no reasons to move on bug 1734326 unless you come back having it analyzed
then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710019
Titl
@Christian: I don't know that we need Po-Hsu to retest bug 1734326 - the
accepted fix as for the artful kernel - there's no artful QEMU
counterpart needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
artful verification:
ubuntu@seyfert:~/vm-save-restore$ ./test.sh
+ i=0
+ [ -f /var/log/libvirt/qemu/4172-0.log ]
+ name=4172-0
+ ./randmac.py
+ mac=00:16:3e:7b:3b:f1
+ uuidgen
+ uuid=33815e19-0f44-4e6f-8209-ada375484ba3
+ mktemp
+ xml=/tmp/tmp.Mc2sJDaknd
+ cp template.xml /tmp/tmp.Mc2sJDaknd
+ tra
@Kleber - that would mean we also want to ping Po-Hsu for a bug 1734326 retest?
He would need a ppa for that - @Dannf do you still have that in a ppa for him
to test against the kernel in proposed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hi @dannf,
Could you please verify the artful fix with the latest kernel on
-proposed?
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710019
Title:
support GICv3 ITS save/restore & migr
Thanks Andy,
I pushed a revert to qemu's packaging git to ensure there is no accidential
upload of the same content on the next zesty SRU.
@Dannf - once you had time to sort out the acceptance for the zesty kernel as
well as this regressions and come to want to push this again let us know.
I set
Removed qemu from zesty-proposed based on this discussion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710019
Title:
support GICv3 ITS save/restore & migration
To manage notifications about this
** Tags removed: verification-needed-zesty verification-ocata-needed
** Tags added: verification-failed-zesty verification-ocata-failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710019
Title:
s
On Fri, Nov 24, 2017 at 4:51 AM, ChristianEhrhardt
<1710...@bugs.launchpad.net> wrote:
> Hi Dann,
> maybe it was good to hold off on this.
> It seems it causes a regression on arm, see bug 1734326.
> Also by holding for an arbitrary amount of time it might block the SRU queue
> for something else.
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verifica
Hi Dann,
maybe it was good to hold off on this.
It seems it causes a regression on arm, see bug 1734326.
Also by holding for an arbitrary amount of time it might block the SRU queue
for something else.
If you agree I'd ask you to let the SRU team cancel the upload from proposed.
And you can then
Hello dann, or anyone else affected,
Accepted qemu into ocata-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo add-apt-rep
** Changed in: linux (Ubuntu Artful)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Artful)
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/1
I've verified this for zesty, using my patched zesty kernel.
Demonstration of that follows. However, the kernel patches have not yet
been approved for zesty, and may never be. I'll hold-off on updating the
tags here until a) we have a final answer on the kernel patches or b) we
decide there is valu
Hello dann, or anyone else affected,
Accepted qemu into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.8+dfsg-
3ubuntu2.8 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
** 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/1710019
Title:
support GICv3 ITS save/restore & migration
To manage notifica
Uploaded qemu_2.8+dfsg-3ubuntu2.8 to unapproved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710019
Title:
support GICv3 ITS save/restore & migration
To manage notifications about this bug go to
I have kicked off a verification run on the ppa to check the qemu in there.
I passed all stages just fine, which means you are likely fine to go when you
have the kernel ready.
Thanks for also clarifying if we need to BP the #1731051 fix in relation to
this change.
Ack - Feel free to upload the
Note: tested version was 1:2.8+dfsg-3ubuntu2.7+lp1710019.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710019
Title:
support GICv3 ITS save/restore & migration
To manage notifications about this
** Description changed:
[Impact]
Virtual machines on GICv3-based ARM systems cannot be saved/restored or
migrated.
This feature was added in QEMU 2.10.
[Test Case]
ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav
Domain 7936-0 saved to 7936-0.sav
ubuntu@grotrian:~$ sudo
I have a staging PPA that I'm using for testing at ppa:dannf/lp1710019.
The QEMU there is the attached debdiff (trivially) forward-ported to the
latest qemu in updates, and the kernel has the patches I plan to submit
to the kernel team. I've verified that this all works together on a
zesty system.
Ok, Dann - thanks for the clarification.
So per the SRU rules to not regress on updates that would then be Zesty,
Artful, Bionic.
With Qemu being ok since Artful and Kernel needing your backports in Zesty 4.10
and Artful 4.13 then.
I'm setting up the tasks correctly then.
Do you want me to eval
libvirt's apparmor policy doesn't allow for restoring instances from /tmp, so
I've updated my reproducer tool:
https://code.launchpad.net/~dannf/+git/vm-save-restore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
I plan to submit my backport to zesty's (4.10) kernel - I haven't yet
investigated the feasibility of backporting this feature to xenial's
virt stack. With respect to QEMU, at this time I'm only requesting that
the backport for zesty be considered.
--
You received this bug notification because yo
I assume this is:
commit b92382620e33c9f1bcbcd7c169262b9bf0525871
KVM: arm/arm64: vgic-its: Fix return value for device table restore
And some more patches around it.
Ok, so this gets into 4.14, which will only be available for Bionic and as HWE
for Xenial.
For Qemu as you stated changes are
@Christian: The blocking issue was with the kernel. It has now been
fixed upstream and I've begun submitting SRU patches for the kernel. +1
from me on proceeding with the QEMU portion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Zesty)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Zesty)
Status: Triaged
On Wed, Sep 6, 2017 at 7:20 PM, dann frazier
wrote:
>
> Until that concludes, I can't be 100% sure that QEMU will require no
> further patches. But once that is resolved, then I think your proposed
> plan above sounds good.
>
Thanks for clarification - sounds good, give an update here then once
On Wed, Sep 6, 2017 at 2:50 AM, ChristianEhrhardt
<1710...@bugs.launchpad.net> wrote:
> Dann, I don't want to miss the activity here - so the next step you are
> expecting is me to evaluate the diff in detal and prep a qemu SRU?
> Along that you will do regression tests on arm and I could do x86/p
Dann, I don't want to miss the activity here - so the next step you are
expecting is me to evaluate the diff in detal and prep a qemu SRU?
Along that you will do regression tests on arm and I could do x86/ppc/s390x?
Is that correct then I'd create a ppa for both of us to do the checks or
is somet
On Wed, Aug 30, 2017 at 12:35 AM, ChristianEhrhardt
<1710...@bugs.launchpad.net> wrote:
> Hi Dann,
> Sorry to ask, really I'm not neglecting all the work you do here.
> But it is a huge set of changes (17 files changed, 929 insertions(+), 46
> deletions(-), and not all arm only) and I wonder as Ze
Hi Dann,
Sorry to ask, really I'm not neglecting all the work you do here.
But it is a huge set of changes (17 files changed, 929 insertions(+), 46
deletions(-), and not all arm only) and I wonder as Zesty will never have the
4.13 kernel (as HWE is for LTS only).
If it only works with the newer
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710019
Title:
support GICv3 ITS save/restore & migration
To manage notifications about this bug go to:
https://bugs.launchpad.net
** Patch added: "qemu-zesty-gicv3sr.debdiff"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1710019/+attachment/4940998/+files/qemu-zesty-gicv3sr.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Hi Dann,
Yes, I will upstream the patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710019
Title:
support GICv3 ITS save/restore & migration
To manage notifications about this bug go to:
https
Here's a backport for zesty's QEMU, tested with the 4.13.0-7.8 kernel
from ppa:canonical-kernel-team/unstable w/ the patch from Comment #10
applied.
** Changed in: qemu (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bu
@Vijaya: Yes, that patch does resolve the issue for me, thanks! Do you
plan to submit this upstream?
@Christian: Yep - I'll open one.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubu
That is a kernel patch.
@Vijaya/Dannf - should we add a kernel task for them to be aware of?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710019
Title:
support GICv3 ITS save/restore & migration
With the below patch, The issue seems resolved. Please check and let me
know.
diff --git a/virt/kvm/arm/vgic/vgic-its.c b/virt/kvm/arm/vgic/vgic-its.c
index aa6b68d..63f8ac3 100644
--- a/virt/kvm/arm/vgic/vgic-its.c
+++ b/virt/kvm/arm/vgic/vgic-its.c
@@ -2142,7 +2142,7 @@ static int vgic_its_resto
Was able to reproduce the issue with 4.13 + latest qemu with the scripts
provided.
Issue seems to be with restoring of ITS table is failing. Investigating further.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
4.13-rc6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710019
Title:
support GICv3 ITS save/restore & migration
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
(AppArmor/pflash issue has been forked off in to LP: #1710960)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710019
Title:
support GICv3 ITS save/restore & migration
To manage notifications about
Hi Dan was already on that error:
"2017-08-14T23:43:10.255936Z qemu-system-aarch64: -drive
file=/home/ubuntu/vm-start-stop/vms/7936-0_CODE.fd,if=pflash,format=raw,unit=0,readonly=on:
Failed to lock byte 100"
Actually it should be fixed by the last libvirt adding apparmor rules to allow
that.
I di
On Mon, Aug 14, 2017 at 2:24 AM, ChristianEhrhardt
<1710...@bugs.launchpad.net> wrote:
> Ok, thanks for calrification good to know this is in your hands.
>
> About:
> [*] Note: you currently need to boot the Ubuntu kernel w/ apparmor=0 to work
> with latest upstream QEMU
>
> I haven't seen anythin
Ok, thanks for calrification good to know this is in your hands.
About:
[*] Note: you currently need to boot the Ubuntu kernel w/ apparmor=0 to work
with latest upstream QEMU
I haven't seen anything like that when testing 2.10-rc1/rc2 - is that arm
specific (apparmor usually prefers to fail eve
Here's the test tool I'm using to verify this. It spins up a zesty guest
and gives it time to get past the bootloader and into Linux, then tries
to save and restore it.
tar xvfz vm-save-restore.tar.gz
cd vm-save-restore
./setup.sh
./test.sh
I've tested this on an artful host, running the 4.12.0-1
Indeed! I've updated the bug status to reflect that. Currently I do have
a backport to 2.8 that seems to be working as well as latest upstream.
That is, I can save and restore a UEFI guest, prior to starting Linux.
I'm working on diagnosing an issue where a guest that has been saved
after Linux has
Hi Dann,
you aready added half a SRU template - so are you knowing/working on a fix
already?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710019
Title:
support GICv3 ITS save/restore & migration
54 matches
Mail list logo
