smoser was able to reproduce (without uvt btw) and found up to 20171208 working.
The manifest diff then is much smaller.
Essentially:
+cloud-init 17.1-53-ga5dc0f42-0ubuntu1
+grub-legacy-ec217.1-53-ga5dc0f42-0ubuntu1
+libassuan0:amd64 2.5.1-1
Of those only the first seems related
Hi Julian,
I have broken down the testcase into reproducible steps:
Testcase - TL;DR get running guest with IP and enable libvirt nss:
$ apt install libnss-libvirt libvirt-dameon-system
$ apt update
$ uvt-simplestreams-libvirt sync --source http://cloud-images.ubuntu.com/daily
arch=amd64 label=da
Ok, so I will add this on the next libvirt merge to be safe on bionic.
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732030
Title:
@Tamas - your stack trace might help to identify another source of such
issues, let us know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732030
Title:
'apt update' dies with seccomp error
To man
Hi Nathan,
I highly appreciate you coming up with the change proposed here as I can
include it when working on this set of packages anyway.
IMHO it is an actual feature request, even thou the reasons to have missed to
add the feature earlier lie in the past - I want you to understand why, so I
a
** Tags added: libvirt-18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732030
Title:
'apt update' dies with seccomp error
To manage notifications about this bug go to:
https://bugs.launchpad.n
** Changed in: libvirt (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716028
Title:
qemu 2.10 locks images with no feature flag
To manage notifications a
Thanks for splitting this issue out of our former work Sean.
I must admit I mostly use save/restore but less so suspend to ram - and even if
so I don#t use the guest agent to do so, but all of that is worth testing.
I started with a repro of said case.
Usual updating to the latest versions of all
> I'm already of why the prebuilt ones were removed,
great
> but that doesnt't
> actually answer how they were missed when updating qemu to 2.7 (vmxnet3
> PXE is mentioned in the changelog).
Updating qemu is distinct from updating ipxe.
So when we moved what was I think qemu 2.6.1 -> 2.8 that di
(late) Hi,
You are right Laurent, IMHO they should be added.
Not very critical since as of today there are no conffiles in there yet, but
still right to do so.
Adding an Ubutu task to include the fix and actually also the script to
better support the freeze/thaw operations.
** Also affects: qemu
The link you added has changed a lot, but due to the feats of git the
following will do for what you initially suggested.
https://github.com/systemd/systemd/blob/61ee6939819963b7845c101485e188ca2a8119c6/src/basic/util.c#L1871
--
You received this bug notification because you are a member of Ubun
I submitted a change based on the suggestion upstream:
http://lists.nongnu.org/archive/html/qemu-devel/2017-12/msg02142.html
Grml, due to LP posts being mirrored on the ML this is kind of redundant when
viewed from the ML.
But I want to leave that info for LP-only-readers as well :-/
--
You re
Sorry - found some other qemu-guest-agent issues along that were easier to
address and I did so right away.
Back on this now.
The actions run by the guest-agent are:
- guest-sync (this is only to ensure no old content is on the channel, no
relation to suspend)
- guest-suspend-ram (the actual sus
qemu-guest-agent and pm-utils are both universe so adding a dependency or
better a recommends as that is what it correctly is is an option if that turns
out to help.
Independent to a fix of this issue (which we don't know yet if it is one) it
would also ensure that anything that plug into /usr/l
Note: it really isn't suspended as after a while the guest console shows:
[ 606.312026] INFO: task pm-suspend:1258 blocked for more than 120 seconds.
[ 606.316500] Not tainted 4.13.0-19-generic #22-Ubuntu
[ 606.320080] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
messa
Thanks for the ping Nikunj!
** Changed in: slof (Ubuntu Bionic)
Status: New => Triaged
** Tags added: slof-18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734856
Title:
Can't boot VM w
There is no other mode in /sys/power/mem_sleep than the default s2sleep
to try.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737786
Title:
(arm64) unable to dompmwakeup a vm after being suspended
Taking away acpi, apic, pae features in libvirt.
I know I need to work on my platform so I leave that as-is.
It still freezes up at the same step:
[ 924.376385] PM: Syncing filesystems ... done.
[ 924.380381] PM: Preparing system for sleep (freeze)
[ 924.394818] Freezing user space processes .
I tried a few things more but not worth to mention - all dead ends.
Eventually I asked upstream if anybody ever achieved that and got no yes.
@Sean - given that this might have never worked so far and the package
being "only" universe did you ever see that succeed in a former version?
If not maybe
@Nikunj - do you happen to know if Alexey is planning an official
release soon that would include this fix?
Note: this is the first Delta to take, but I look into it as it is critical.
We want to get back to have upstream release a version, debian pick it up and
we become a sync again in bionic.
Hi,
I don't want to wait too long, so while waiting for an answer I made a ppa
available that should be tested to confirm this fix is good (for bionic).
Please test on Bionic from ppa:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3079
I'll mark the bug incomplete to clearly reflec
I tried to verify the case and fix myself which is a prereq for good steps to
reproduce for the SRU anyway.
I came up with test steps based on what was initially reported.
$ uvt-simplestreams-libvirt --verbose sync --source
http://cloud-images.ubuntu.com/daily arch=ppc64el label=daily release=bio
Tried the base 2 + 2x20 = 42 disks.
Still working for me as-is.
To summarize what I wait on:
1. better steps to reproduce - if possible slight modification to my suggested
workflow and even more so if possible without needing double digit amount of
real disks
2. please test/verify the ppa linked
This looks promising
https://www.eecis.udel.edu/~mills/ntp/html/miscopt.html#interface
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737998
Title:
trying to bind on all interfaces is a good default
Public bug reported:
The default is "grab all" which is great for convenience and can be
configured to be differently by argument -I (interface) or interface
commands in the config.
Currently it is "too" open on that.
I see it trying to bing link local addresses for each of the KVM guests I spawn
Reading more into [1] and [2] I'm not 100% if ntp just has an issue or
if in general we should mask this interface type like:
interface ignore fe80::/64
[1]: https://www.eecis.udel.edu/~mills/ntp/html/miscopt.html#interface
[2]:
https://www.cisco.com/c/en/us/support/docs/ip/ip-version-6-ipv6/113
Ok I debugged more and it seems that the situation where i was unable to bind
is the special one.
I usually got this now:
Dec 13 15:24:31 bionic-test-kvm ntpd[6142]: Listen normally on 8 vnet0
[fe80::fc54:ff:fe46:80ed%10]:123
Dec 13 15:24:31 bionic-test-kvm ntpd[6142]: new interface(s) found:
** Also affects: ntp (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: ntp (Ubuntu Bionic)
Importance: Undecided
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Changed in: open-vm-tools (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/1737753
Title:
open-vm-tools 2:10.1.15-1build1 ADT test failure with linux 4.15.0-
As expected I could solve the issue in a test via
flags=(attach_disconnected).
Although I had cases where the issue appeared and others where it never
showed up - didn't find the difference for that yet. Never the less the
fix will help the affected cases and should not break others.
The worst is
No fix on [1] yet to be merged and the package is a sync from Debian atm.
Debian and we are up to date to latest Upstream.
So I reported to upstream in [2] for now.
[1]: https://github.com/vmware/open-vm-tools
[2]: https://github.com/vmware/open-vm-tools/issues/217
** Bug watch added: github.com
Thanks a lot Simon for your thoughts - this is exactly what I was
looking for.
"On a hypervisor, binding on link local IPs is undesirable IMHO"
Thats what I thought as well
But - if there is valid use of link locals in general - as I was unsure of and
you as well suggest there might be folks doi
I was in discussion with Kurt Roeckx on NTPsec before and the NTPsec
folks as well but never had the time to continue - thanks you a lot for
packaging it up Richard. I subscribed myself to 819806.
Nice to hear that this will fix it for you as well!
--
You received this bug notification because y
It was still working with 20 disks and boot index, but 48 made it.
Thanks Nikunj for the bood index hint.
Overall testcase:
# Prep a guest
$ uvt-simplestreams-libvirt --verbose sync --source
http://cloud-images.ubuntu.com/daily arch=ppc64el label=daily release=bionic
$ uvt-kvm create --password=u
** Description changed:
+ [Impact]
+
+ * Booting a KVM guest with many disks considered as potential boot device
+fails on ppc64le
+
+ * In detail this was an overflow, so now the processing of devices is
+changed to use dynamic allocation which works with higher numbers of
+dev
Thanks for the info Nikunj.
That means we can likely soon pick it up as a sync from Debian again.
But for now can fix it by picking your changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734856
** Changed in: nova (Ubuntu)
Importance: Medium => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694159
Title:
Complete libvirt migration to Debian style packaging (dependencies,
conf
This is a very old Delta we are still carrying.
Compared to a lot of the delta which just has no trace where it came from this
one had at least a bug link - yeah - thanks Jamie!
So for documentation purpose I'm updating here as I'm about to remove
the related Delta on the next merge as it is safe
My former tests focussed on the testcase.
I deployed a fresh power8 system and ran some more tests on the proposed change
but found no issues - that said going on.
That said I pushed an MP for review of the packaging changes.
@Nikunj / IBM - waiting on your check of the PPA as well if you can fi
Nice to hear it works now, thanks Andreas for the hints.
Closing bug.
** Changed in: samba (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734859
Title:
** Tags added: qemu-file-locking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1709818
Title:
Failed to lock byte 100
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu
** Tags added: qemu-file-locking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710960
Title:
QEMU 2.10 may require AppArmor updates for pflash devices
To manage notifications about this bug go to:
** Tags added: qemu-file-locking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726804
Title:
rules for images on attach-device not containing lock permission
To manage notifications about this bug
Per Debian fix in 5.1.2-1
"AFAIKS, autofs is providing a .service now with an After=sssd"
This is in Ubuntu as of Zesty.
I'll mark the tasks accordingly.
Adding the service in Xenial in general might have too much risk to cause other
regressions - not sure thou - I beg your pardon - this is just
Hi,
actually even on the bionic build this is missing.
See [1] throwing:
dh_installdocs -O--parallel
dh_installdocs: Cannot find (any matches for) "FAQ" (tried in .)
So I'd assume that the new debhelper is more tolerant about that but it would
be nice to fix in newer releases just as much.
Hi Bryan,
I only knew about tftpd of the dependencies and for that the main counterpart
is vsftpd.
So I can only agree to the suggestion to demote it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/173
Github reply uncovered that I had no idea what this does :-/ Topic vmxnet
(deprecated) vs vmxnet3.
OTOH - Debian packaging might have had a reason to keep it, so I'll need to
report there and let them decide if dropping or fixing is the right choice.
--
You received this bug notification becaus
** Bug watch added: Debian Bug tracker #884656
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884656
** Also affects: open-vm-tools (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884656
Importance: Unknown
Status: Unknown
--
You received this bug notification b
** Tags added: qemu-18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350435
Title:
tcg.c:1693: tcg fatal error
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad
I saw the new upstream release, over the next time this will be picked up by
Debian and we make it a sync again then.
For now I pick the fix as tested from the ppa into Bionic.
Once that migrated I'll look at the SRUs into X-A.
** Changed in: slof (Ubuntu Bionic)
Status: Incomplete => Fix
** Also affects: strongswan (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: strongswan (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: strongswan (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notific
So the final commit for this issue on 5.5.2 is [1].
Current Ubuntu releases are on
- Zesty/Artful on 5.5.1
- Xenial on 5.3.5
Purely from a "patch applies" POV this applies to all three.
But obviously the confidence that this works perfectly fine is much higher on
5.5.1 than on 5.3.5.
I have som
** Description changed:
+ [Impact]
+
+ * charon unnecessarily selects a wrong PSK in some cases:
+* A site-to-site connection using resolvable hostnames (e.g., DynDNS) as
identities in /etc/ipsec.secrets and a Roadwarrior connection (using %any as
remote peer identity)
+* Multiple site
The Bionic fix is about to complete now'ish.
Since this (if triggered) is effectively blocking the messages to appear in the
syslog this can hide an arbitrary amount of further issues that the user then
has next to no grasp on how to tackle.
So SRU worthy for Artful IMHO.
Adding template soon.
** Description changed:
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+
+ [Test Ca
MPs for the packaging change in X/Z/A up for review and linked in the
bug.
** Changed in: slof (Ubuntu Artful)
Status: Confirmed => In Progress
** Changed in: slof (Ubuntu Zesty)
Status: Confirmed => In Progress
** Changed in: slof (Ubuntu Xenial)
Status: Confirmed => In Pro
Doing another bigger check set on Xenial and then opening up the MPs for
review.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734856
Title:
Can't boot VM with more than 16 disks (slof buffer issue
Thanks Andreas, yes I see it nearly everywhere as well.
Also thanks to spot that I missed to uopdate impact - done.
Discussion on the MP going on ...
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
-
- * justification for backporting the fix to t
Public bug reported:
We found this in ntp, but I think it is a general issue in the ordering.
The tail of NTPs postinst looks like that:
if [ "$1" = "triggered" ]; then
# The default configuration uses a leapfile from tzdata
Public bug reported:
Newer NTP gets the following apparmor denials on start:
apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd"
name="/usr/local/sbin/" pid=6421 comm="ntpd" requested_mask="r" denied_mask="r"
fsuid=0 ouid=0
apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd"
na
** Description changed:
[Impact]
* NTP has new isolation features which makes it trigger apparmor issues.
- * Those apparmor issues not only clutter the log and make other things
-less readable, they also prevent ntp from reporting its actual
-messages.
- * Fix is opening the a
Ok, all my tests look good, but they are rather trivial compared to some setups
in the wild.
I have a ppa with what I'd like to move to proposed if confirmed at [1].
I pushed a Merge Proposal for the packaging changes and got an ack by
fellow packagers.
@Jan-Otto - could you test the case with y
Tests good - MPs open for packaging review
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734856
Title:
Can't boot VM with more than 16 disks (slof buffer issue)
To manage notifications about this
Hi Laz,
thank you for your report.
Thanks for the log, I mostly looked at the condensed version like:
$ awk '/iscsiadm/ {gsub("[0-9]*: debug : virCommandRunAsync:2429 :","");
gsub("+",""); gsub("^2017-12-18 ",""); print $0}' 20171218-libvirt.txt |
pastebinit
=> http://paste.ubuntu.com/262141
Uploaded for the SRU team to evaluate
** Changed in: ntp (Ubuntu Artful)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727202
Title:
[17.10 regression] AppArm
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816172
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727699
Title:
SSL issue upgrading postfix
To manage notifications about this bug go to:
The line you wonder essentially does:
set_postconf -F -c "/etc/postfix" submission/inet/chroot=y
And yes this is setting the "y" in your case I'd think.
As I outlined before this was (I guess) meant to carry the old default to stay
the same on an upgrade.
IMHO this is fine on a certain upgrade
You'd add [2] and always take packages from there non selectively.
So normal add-apt-repository and after that just update/upgrade as usual
according to your maintenance policies.
I'd say that while libvirt/qemu can break things I'd have very rarely seen
those to manifest as system instabilities
Review on the MPs is complete and it is now sponsored for SRU review in
[xenial/zesty]-unapproved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717040
Title:
Please backport libzstd 1.3.1+dfsg-1 (
In testing newer virt stack I still hit this and need the workarounds to get it
to work :-/
Any update and/or ETA on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679704
Title:
libvirt profi
Sorry Elmo, I came from the xinetd dependencies side and you are
absolutely right tftp != ftp, but as Bryan already pointed out, then
tftpd-hpa.
But one more potential user came to my mind - MAAS back then used I think a
python based tftp.
Adding them to be sure - not that they (planned to) chang
Regression tests good as well, moving it to x-unapproved for the SRU Team to
consider.
=> qemu_2.5+dfsg-5ubuntu10.25_source.changes
** Changed in: qemu (Ubuntu Xenial)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Regression tests good as well, moving it to x-unapproved for the SRU Team to
consider.
=> qemu_2.5+dfsg-5ubuntu10.25_source.changes
** Changed in: qemu (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: qemu (Ubuntu)
Status: New => Fix Released
--
You received this bug
Tested shutting down 40 guests with this through the service - worked fine this
time.
If shutdown is really really fast (like small guests on a speedy host, you
might see "Failed to determine state of guest ..." but that is fine. It only
means it is gone fast, we don't have to wait for it and we
Start/Stop-Looped a bunch of guests with extra nwfilters, but as I
mentioned in the SRU Template it is inherently racy and so far never
triggered for me. So this isn't a full verification, but more a sanity
check.
Regression tests good as well, moving it to x-unapproved for the SRU Team to
consid
Thanks for the repro steps, to add to that is only triggers if the HW REALLY
can do HW Timestamping (which likely is the reason it was missed as e.g. virtio
devs can't).
You can check with:
ethtool -T
>From man chrony.conf
This directive is supported on Linux 3.19 and newer. The NIC must supp
Working fine, can be reviewed without ppa as it is a config change only.
My checks are good on this.
@Josh I added you as reviewer since you have the env ready to confirm.
** Changed in: chrony (Ubuntu)
Status: New => In Progress
** Changed in: chrony (Ubuntu)
Importance: Undecided =>
Would be what is missing:
Apr 05 07:23:44 node-horsea chronyd[19961]: Enabled HW timestamping (TX only)
on eno1
Apr 05 07:23:44 node-horsea chronyd[19961]: Enabled HW timestamping (TX only)
on eno2
Apr 05 07:23:44 node-horsea chronyd[19961]: Enabled HW timestamping (TX only)
on eno3
Apr 05 07:23
Reported to Debian to get in sync later on, linking debian bug 894879
** Bug watch added: Debian Bug tracker #894879
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894879
** Also affects: chrony (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894879
Importance: Unknown
Once more - I tried on x86 and ppc64 for this this morning.
The same case as outlined in comment #7.
TL;DR:
- x86 works now, the reported issue of virSecurityManagerSetMemoryLabel missing
is fixed
- ppc64 also passes the reported issue
- ppc64 hangs further down on the attach at bug 1679704
ppc
Example Deny:
[ 774.341606] audit: type=1400 audit(1522915593.238:42): apparmor="DENIED"
operation="setrlimit" info="cap_sys_resource" error=-13
profile="/usr/sbin/libvirtd" pid=8376 comm="libvirtd" rlimit=memlock
value=96468992 peer="libvirt-70a586a2-ef34-4954-91ea-9a6ecab52da3"
Source: libvi
FYI: Test case of the mem hotplug in
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1755153/comments/7
Only triggers on powerpc as they lock some memory while doing so (x86
does not).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
For Ubuntu: PPA: https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3225
Regression test against ppa looked good tonight.
There are new changes which I need to add for two more bugs.
But testing from the ppa is ok right now already.
@Luke: Please test against this PPA, as I want to ens
FYI: PPA build with the fix for privateTmp is available in a PPA
Versioning changes slightly (better to do these SRUs regularly).
So the new version is below the old one, be sure to update correctly when
testing this.
Consider using
sudo ppa-purge ppa:ci-train-ppa-service/3152
Before using the n
PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3225
Regression test against ppa was ok tonighz, but I need to respin to add
more things before pushing to Bionic.
If you want to pre-test feel free to use this PPA.
Given the change thou I assume we can just let it roll in (under u
PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3225
Regression test against ppa looked good tonight.
But there are more bugs for ppc (bug 1761371 and bug 1761372) coming in which I
want to consider, bundle and reverify together.
If you want to pre-test feel free to use this PPA
FYI: PPA build with the fix for privateTmp is available in a PPA
Versioning changes slightly (better to do these SRUs regularly).
So the new version is below the old one, be sure to update correctly when
testing this.
=> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3226
Still conf
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761175
Title:
Revert the temporary mitigation of Power9
Merged in the change from bug 1761371 as it is almost part of the same series
and has the same dependencies.
Closed the other bug as dup and added the change to the list in the bug
description.
** Description changed:
== Comment: #0 - Satheesh Rajendran - 2018-04-04
08:58:54 ==
---Problem
*** This bug is a duplicate of bug 1761372 ***
https://bugs.launchpad.net/bugs/1761372
This shares quite a lot of dependent patches with 1761372
I'd like to handle the discussion on these as one.
Therefore I'll close this bug as dup and add the requested change to
1761372.
** This bug has be
I'm still evaluating this (quite some time now), but I want to share the
interim TL;DR for you to consider.
All those patches are part of a huge rewrite and handling of sprs.
Yes the series has "only" (already a lot) 7 patches, but it seems due to
dependencies this easily will get 10 or even 20+.
A bunch of the dependencies went in through the 2.11.1 stable updates:
$ git log --oneline hw/ppc/spapr_caps.c
eab4b51 target/ppc/spapr_caps: Add new tristate cap safe_indirect_branch
d7aa3d0 target/ppc/spapr_caps: Add new tristate cap safe_bounds_check
3dc1227 target/ppc/spapr_caps: Add new trist
After all it might not be too bad, due to the others being already in the
stable fixes.
Most apply clean (with some offsets thou).
The last patch with the new 2.12 type is what has some fails.
But those are fixable and are expected (since our 2.11/2.12 types differ).
I'll add a further cleanup to
So all that, to provide a -sxxm type that is NOT the default (not in
your patches, so I didn't make it the default in mine).
I wonder, what is the benefit of this then.
If users need to change the machine type, then they can just as well set the
CFPC/SBBC/IBS caps right?
Since we are not changin
If you want any of these sxxm defaults to be the default of the default machine
type ... ARGL too much default exception.
Rephrase:
If you want the changes to the CAPs that the 2.12-sxxm type starts to be
applied to the default machine type "pseries-bionic" let me know.
Until Bionic release we c
Same (=please let me know asap) is true if instead you want any of:
pseries-2.11-sxxm
pseries-bionic-sxxm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761372
Title:
backport needed for spectre/mel
We discussed on IRC, but I have to admit I'm unsure what to do on this.
Especially since different hosts with same SW levels are exposing different
behavior.
Closing with a quote from IRC
[15:20] but really don't spend time on this, I can use the command line
Thanks for the discussion still, le
We went with 4.0 for bionic, so fix released.
** Changed in: libvirt (Ubuntu)
Status: New => 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/1738770
Title:
Support for Skylake-Ser
Thanks Luke.
I tried the same from the deb of libc for arm in bionic.
Down from
real0m2.031s
to
real0m0.002s
So confirmed as well.
** Changed in: qemu (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
>
> > I wonder, what is the benefit of this then.
> > If users need to change the machine type, then they can just as well set
> the
> > CFPC/SBBC/IBS caps right?
>
> I believe the issue is similar to what we initially hit with:
>
> Bug 165081 - LP1752026- Ubuntu18.04:POWER9:DD2.2: Unable to start
301 - 400 of 5815 matches
Mail list logo
