** Changed in: ubuntu-z-systems
Status: Triaged => 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/1835546
Title:
[20.04 FEAT] Base KVM setup for secure guests - qemu part
To mana
This bug was fixed in the package qemu - 1:4.2-3ubuntu4
---
qemu (1:4.2-3ubuntu4) focal; urgency=medium
* d/p/ubuntu/lp-1835546-*: backport the s390x protvirt feature (LP: #1835546)
* remove d/p/ubuntu/expose-vmx_qemu64cpu.patch: Stop adding VMX to qemu64
to avoid broken nesti
FYI - Added [1] to 4.2-3ubuntu4~ppa7 in PPA 3985
[1]: https://lists.nongnu.org/archive/html/qemu-
devel/2020-03/msg07969.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835546
Title:
[20.04 FEA
Add https://lists.nongnu.org/archive/html/qemu-
devel/2020-03/msg07969.html I guess?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835546
Title:
[20.04 FEAT] Base KVM setup for secure guests - qemu
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835546
Title:
[20.04 FEAT] Base KVM setup for secure guests - qemu part
To manage notifi
To be clear, if you want to continue testing without the coming libvirt
it is fine to just stay on 3985 and go on as-is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835546
Title:
[20.04 FEAT] Bas
FYI For testing I have put this *also* into a different PPA
=> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3986/
This shall help (me) to test it together with some intended libvirt
changes.
For now the qemu content in regard to s390x-protvirt is the same in the
old 3985 and the ne
Thanks for the extended testing!
Ack that is the only change:
$ git range-diff v4.2.0..cborntra/pv42_v11 v4.2.0..cborntra/pv42_v12
...
13: 3c664ea0a6 = 13: 3c664ea0a6 vhost: correctly turn on
VIRTIO_F_IOMMU_PLATFORM
14: 5081c651c9 = 14: 5081c651c9 Sync pv
15: db0a53ee22 ! 15: 295b91aa9d s39
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/381033
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835546
Title:
[20.04 FEAT] Base KVM setup
The attachment "focal_qemu_content.diff" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, an
For completeness reasons (and the FFe at LP 1866866) please see the attached
debdiff.
But for better readability the following link is probably preferable:
https://github.com/borntraeger/qemu/commits/pv42
** Patch added: "focal_qemu_content.diff"
https://bugs.launchpad.net/ubuntu-z-systems/
Hi,
we will not take the following commit:
commit 9da000ea0ae75fbdf14f6e7dc49ad324ba3fe190
Author: Christian Borntraeger
Date: Thu Mar 19 07:02:20 2020 -0400
rebuild bios
As a general Ubuntu (and Debian) policy implies that we build everything from
source for serviceability (and to no get
** Changed in: qemu (Ubuntu)
Status: Incomplete => New
** Changed in: ubuntu-z-systems
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835546
Title:
[20.0
For the time being I pushed a best effort inclusion of the patch in
comment #6 as "qemu_4.2-3ubuntu2~ugly1" into the PPA that xnox already
linked.
=> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3970
I further hit and needed changes for:
- ERROR: unknown option --disable-bluez
...
This even brings in 5.0 types, moves around vl.c and all that - it isn't
even good for a quick build on the PPA IMHO (Ack to comment #7).
Really, don't think about the "package" too much just provide a stack of
commits for 4.2, I'm fine if that is just a git branch on top of tag:
v4.2.0 and will c
This is a very akward submission. Where is the git repository with
backport?
Ideally against the ubuntu's focal git source tree with all patches
already applied (aka treat it just like a normal git repo)
https://code.launchpad.net/~usd-import-
team/ubuntu/+source/qemu/+git/qemu/+ref/applied/ubuntu
The QEMU review is still ongoing. As a stop-gap measure it would be great to
have PPA with a preliminary build of QEMU (master level + patches).
Attached is a full diff on top of 4.2.
Since the attached patch obsoletes some of the debian/patches content, the
following series file should suffice:
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835546
Title:
[20.04 FEAT] Base KVM setup for secure guests - qemu part
To manage notifications abo
18 matches
Mail list logo
