Thanks Stephane and Christian!
Since we ...
a) have a workaround by manually adding the entry to the apparmor abstraction
(or dropping serial if that is an option)
b) having an explicit serial in the guest profile is not the default
c) KVM in LXD is more a "nice to have" solution than something
Re-prepared, and merged with another SRU that was ready now.
Pushed to SRU unapproved queue.
P.S. Since I pretest a lot one can already look at [1]. Please do note
that the iscsi dep8 test is a notorious noisy transient issue that is
not related to the update, but will likely be seen in -proposed
Thanks for the Detail Robin!
--
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/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
Status in QEMU:
Invalid
Status in lin
Note: tested version was 1:2.8+dfsg-3ubuntu2.7+lp1710019.1
--
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/1710019
Title:
support GICv3 ITS save/restore & migration
Status in linux packa
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
Hi,
I investigated this a bit.
TL;DR - this is intentionally off by default and opt in.
To use it you need:
- in the host set kvm.nested=1
- depending on your other virt stack set you might need to set host-passthrough
or the sief2 feature (qemu -cpu host or ...,sief2=1)
Then the guest will have
Waiting on the kernel fix to fully release, but as we won't change
libvirt updating the task.
** Changed in: libvirt (Ubuntu Artful)
Status: Confirmed => Won't Fix
** Changed in: libvirt (Ubuntu)
Status: Won't Fix => Fix Released
--
You received this bug notification because you a
Since on 8th Nov you wrote "in 5 days or it will be dropped" (I verified
and it was good) I expected a fix to be released already.
Not super important, but can you share an ETA on this?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
Hi cking,
I rarely use it, but for me (on Xenial) the following worked.
$ sudo apt install vagrant virtualbox
$ vagrant init ubuntu/artful64
# note that you have to elminate all KVMs before you can do the next step
$ vagrant up
$ vagrant ssh
vagrant@ubuntu-artful:~$ df -h /
Filesystem Size
With the above in comment #17 I see the limited size after boot and the crash
in dmesg.
But then a repro with
$ sudo resize2fs /dev/sda1
doesn't work - well it works, but that is the problem it works to resize
without triggering the issue "again".
--
You received this bug notification because
This likely is due to the major backport action in bug 1710019.
This SRU is stalled anyway by disagreement of kernel and hwe - so I've asked to
cancel it from -proposed and take some time to take a look.
Thanks for the report - it helped to catch that before being released.
** Changed in: qemu-k
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
After discussion the offfending change in zesty-proposed will be cancelled.
Once done I'll set this to "Fix Released" (even thou it is the non-release that
fixes it).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
Cancelled from proposed, done ...
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed => 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/bugs/1734326
Title:
qemu-kvm in zes
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
@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 Kernel
Packages, which is subscr
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
Any update on the integration of networkd-dispatcher or a similar
technology to allow the dependent packages to use that?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
Hi,
For Qemu this needs a a feature freeze exception for the qemu change was
identified after 1st of March.
Sorry, I missed the update with the upstream sha for a bit, otherwise I'd have
marked it as FFE earlier, but IMHO it is no problem.
The patch is rather small and does not imply extra danger
If you want to experiment with early qemu 2.11 on this take a look at the ppa
at:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3108
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
Current is 1:2.5+dfsg-5ubuntu10.16, and while there is a security update
for 1:2.5+dfsg-5ubuntu10.17 incoming we can - as discussed - test from a
ppa.
To stay ahead of the soon to be expected 1:2.5+dfsg-5ubuntu10.17 I'll
call mine 1:2.5+dfsg-5ubuntu10.18~ppa1 (actually skipping 17 for now so
you s
** Description changed:
+ [Impact]
+
+ * Xenial with HWE kernel (matching new relesaes) and qemu without cloud
+archive (not matching new releases) could trigger hypercalls that are
+not supported in xenials-qemu.
+
+ * There is no "real" case other than kvm tests yet to trigger it ye
Prepped SRU template here in the bug, also the builds in the ppa are
complete.
--
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/1712803
Title:
spapr_hcall from ubuntu_kvm_unit_test failed
Also passed all regression tests on ppc without a hickup.
Other than waiting for the security update to pass we are ready.
--
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/1712803
Title:
s
FYI: The discussion in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889010
nicely outlined that we rely on those hooks in chrony.
That makes having them working critical for 18.04 to have it working correctly
for late or changing network topology.
We (cyphermox and me) discussed how I could
I refreshed the tested changes on top of the security update and pushed
it for SRU review into Xenial.
** Changed in: qemu (Ubuntu Xenial)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
Waiting for the SRU Team to ack it into x-proposed now
--
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/1712803
Title:
spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe
2.11 is now in Bionic - you don't need the ppa anymore to test this.
Looking forward to hear from that test.
--
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/1742892
Title:
[Power 9] ISST-
On Xenial + HWE as-is:
ubuntu@wichita:~/kvm-unit-tests$ sudo ./run_tests.sh -v; cat
logs/spapr_hcall.log
TESTNAME=selftest-setup TIMEOUT=90s ACCEL= ./powerpc/run powerpc/selftest.elf
-smp 2 -m 256 -append 'setup smp=2 mem=256'
PASS selftest-setup
TESTNAME=spapr_hcall TIMEOUT=90s ACCEL= ./powerp
Thanks Indira for the retest with the new versions.
And if I am reading it correct that means the libvirt/qemu uploads fixed this
issue in 18.04.
** Changed in: qemu (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packa
Hi Po-Hsu,
are you still debugging this - or do you want to ask this to be mirrored to IBM?
It could again be something that is only working in latter versions - and
depending on the change we might (or not) backport the fix.
--
You received this bug notification because you are a member of Kern
I think there is no general "mirror all" policy.
It just seems to me that this is requiring an architecture expert which would
be at IBM.
I'll subscribe manoj/jfh and let them decide.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
For 1. I mostly agree, the default is currently off in code and in 2.11 there
is this for backwards compatability:
smc->default_caps.caps[SPAPR_CAP_HTM] = SPAPR_CAP_ON;
We would have to
- Moving that "keep the old default" entry to 2.10 (to cover <=2.10)
spapr_machine_2_10_class_options
sm
Sorry, but to be sure is that a clear "yes please disable HTM by default
in qemu on ppc64el for Ubuntu 18.04" ?
--
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/1752026
Title:
Ubuntu18.04:
To the mini-discussion above - yes it would be default off on P8 as well then.
But by selecting an older machine type, or - even better - using the new type
but with cap-htm=on
Starting the fix in qemu early next week then (the one outlined as (A)
in comment #4.
** Changed in: qemu (Ubuntu)
FYI: There is bug 1753826 which postponed the release/testing of this one a bit.
Currently in rebuild/test together.
--
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/1752026
Title:
Ubuntu1
BTW - tests on P8 are already good on my side, and since the request
from IBM came fro P9 I have to assume it will be good there. But e.g.
cross release migration X->B and such I had tested explicitly to be
sure.
That said, please be aware that this will be a remaining "itch" for you at the
curre
Fix pushed to bionic proposed, I'll track migration after it built and
some time for the tests have passed.
--
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/1752026
Title:
Ubuntu18.04:POWE
rdma-core is on 17.0-1 in latest Debian and Ubuntu Bionic 18.04.
This includes there fix as also outlined by bdrung.
Therefore setting this to fix released.
** Changed in: rdma-core (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ker
Per former comments and no new related issues closing the bug to clean
up.
** Changed in: iproute2 (Ubuntu)
Status: Triaged => Invalid
** Changed in: iproute2 (Ubuntu Trusty)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
** Changed in:
Hi,
I have seen this issue once but never found a root cause when trying to
reproduce. I ended up with one system showing the behavior you mentioned and
others not without seeing the difference why.
I thank you a lot to throw in the info that in your case it is the
changing kernel version that b
Duping my bug (with the failed repro) onto this.
--
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/1722702
Title:
libvirt - vnc port selection regression with newer kernels
Status in libvi
There is no apport collect needed, this is known upstream and applies to
all >=4.11 - fix is in 4.14-rc2 but should be part of 4.13 on release to
avoid regressions in more programs.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: libvirt (Ubuntu)
Status:
I'd ask the kernel Team to integrate the following changes into our 4.13 kernel
release to avoid any sort of update-regressions related to SO_REUSEPORT [1]
- Reproducer [2] without libvirt, how to use in [3]
- Fixes are submitted as [3] - [6]
- If I tracked them correctly they went upstream withou
Thanks Daniel,
after discussing shortly on IRC and checking all the references together:
- https://www.redhat.com/archives/libvir-list/2017-September/msg00519.html
- https://bugzilla.redhat.com/show_bug.cgi?id=1432684
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863266
- http://www.spinics.n
Pinged the kernel team (smb) to take a look as I'd be scared of this and
further consequences of the regression when Xenial HWE kernels and
Artful will be released.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
Hi Po-Hsu,
what do you mean by "introduced by the old qemu version"?
I assume you are testing new kernels by the kernel-da-key tag?
So do you mean "the new (maybe HWE) kernel fails this test on xenial" - and
your assumption is that it triggers there because qemu doesn't have the right
fixes to be
Catched Po-Hsu on IRC.
He will outline the steps to get the test elf image and then we should
mirror to IBM so they can check which ppc changes would be needed. Based
on knowing that we can then decide to SRU or not.
** Tags added: pp64el
** Tags removed: pp64el
** Tags added: ppc64el
--
You
As with bug 1712803 please outline the steps to get the test elf image
and then we should mirror to IBM so they can check which ppc changes
would be needed. Based on knowing that we can then decide to SRU or not.
--
You received this bug notification because you are a member of Kernel
Packages, w
@smb - Yes that is the correct summary
--
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/1722702
Title:
libvirt - vnc port selection regression with newer kernels
Status in libvirt package
Yeah, such a change needs some reasoning and since (at least to me) it
is not yet clear how such few guests consume so much aio resources we
need to check that.
If you can provide:
1. the increase per guest spawned
2. are all your guests having more or less the same xml or do some have more
disks
Thanks for checking cborntra!
The referred patch is in 4.14-rc1.
I'm not so sure on backports of this, but at least for the Artful and HWE
kernel of 4.13 this would be good to have.
@Kernel Team - could you take a look and consider 2a8a9867 for our 4.13
kernels?
@Xnox - changing the global defa
On Wed, Jan 10, 2018 at 5:45 PM, Joseph Salisbury
wrote:
> Thanks for the feedback, Christian. I would much rather install them
> manually. I am able to do that without a problem. However, I am unable
> to access the GRUB menu in the usual way to select a specific kernel.
If you test through a
Public bug reported:
Today I saw on IRC this reported:
raub@desktop:~$ sudo ifdown --force br0 && sudo brctl delbr br0
/etc/network/if-down.d/ubuntu-fan: 29: /etc/network/if-down.d/ubuntu-fan:
/usr/sbin/fanctl: not found
run-parts: /etc/network/if-down.d/ubuntu-fan exited with return code 127
br
We are working on qemu 2.11 which IMHO could be the reason for your issues as
well.
Do you happen to know if there are qemu patches post 2.10 needed as well for
the P9 machines?
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status
Thanks for identifying the changes, both changes are in since 2.6 so I'm
first marking the bug tasks accordingly.
** Also affects: qemu (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: qe
The patch seems easy enough, only the second has some very minor noise when
applying.
Let me know if I should do the backport or if you want to provide patches
against 2.5 (patches against 2.5 as of the qemu git is fine).
In terms of SRU scheduling I think prio is low, but it is easy enough and
Hi Yasmins,
you can either attach the patches as files here on the LP bug or point me to a
git branch of yours that I can reach.
Unless you want to do the related packaging work as well that is all I need.
I can easily do the wrap up of the patches into the packaging for you.
TL;DR - I'm not goin
Hi Heinz-Werner,
thanks for the ping.
I think we agreed back then that the config itself is a Ubuntu wide
thing - but I haven't seen any discussions on procps or in general to
lift it. But then as I outlined in comment #7 any limit can be too low.
I'll set the KVM task to won't fix to clearly mark
Rechecked today on artful:
OVS: 2.8.0-0ubuntu2
Kernel: 4.13.0-16-generic
Based on the cloud image of today, which is post release.
Still crashing with the simple steps to reproduce I listed above:
[ 37.370757] IP: add_grec+0x28/0x440
[ 37.371002] *pdpt = 1dacc001 *pde = 000
ping - still broken as of today in Bionic when updating openvswitch.
Asking for a bump of the force-badtest for now ...
--
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/1712831
Title:
4.12
>From the Dup - FYI
To reproduce do:
$ autopkgtest-buildvm-ubuntu-cloud -a i386 -r artful -s 10G
$ pull-lp-source openvswitch
$ autopkgtest --apt-upgrade --shell --no-built-binaries
openvswitch_2.8.0~git20170809.7aa47a19d-0ubuntu1.dsc -- qemu
~/work/autopkgtest-artful-i386.img
# This guest curren
*** This bug is a duplicate of bug 1736390 ***
https://bugs.launchpad.net/bugs/1736390
** This bug has been marked a duplicate of bug 1736390
openvswitch: kernel opps destroying interfaces on i386
--
You received this bug notification because you are a member of Kernel
Packages, which is
@Joseph - if you mean 2nd level so:
Machine
->KVM
-> $ autopkgtest-buildvm-ubuntu-cloud -a i386 -r artful -s 10G
That could be an issue - for 2nd level being famous for only working mostly.
But why would you do so - since the tests are in VMs they are already
more or less host release agnostic.
On Fri, Jan 5, 2018 at 9:27 PM, Joseph Salisbury
wrote:
> I'm able to install a kernel using kvm:
> kvm -m 512 -hda ./autopkgtest-artful-i386.img
If that works for you fine.
> Is there a way to modify the autopkgtest command line to tell it which
> kernel to boot? When I have multiple test kern
Out of the IRC discussions documenting potentially related issues:
- this bug: KVM: Host-Kernel: Xenial-GA, Qemu: Xenial-Ocata, Guest: Bionic
- bug 1722311 KVM: Host-Kernel: Xenial-GA, Qemu: Xenial, Guest: Artful - some
relation to cache pressure
- bug 1713751 AWS: triggered by Xenial kernel updat
Torkoal (our Jenkins node) was idle atm and Ryan reported he had seen the
issues there before, so trying there as well.
This is LTS + HWE - Kernel 4.10.0-38-generic, qemu: 1:2.5+dfsg-5ubuntu10
I thought about your case since you seem just to start a lot of them and reboot,
this shouldn't be so mu
Test from [2] in c #8.
4.13.0-16-generic
gcc bind-collision.c && ./a.out
bind: Address already in use
AF_INET check failed.
$ gcc -D CHECK_IPV6 bind-collision.c && ./a.out
AF_INET6 success
AF_INET success
$ gcc bind-collision.c && ./a.out
AF_INET success
>From proposed:
4.13.0-17-generic
$ gcc b
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
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
Hi Scott,
the howto is mixed for Desktop users, Server users and selective upgrades.
For your case you only need the most simple case which would be:
Essentially you want to:
# Check - all other updates done (to clear the view)
$ apt list --upgradable
Listing... Done
# Enable proposed for z on
I upgraded my Xenial test system to linux-virtual-hwe-16.04-edge and with that
it is working fine.
So we have a good testcase (thanks Rolando) a crash dmesg on the issue and
confirmed that it is solved in a newer kernel.
Comes down to bisecting maybe, but there is a chance the kernel team
just k
Checking the issue that was referred shows it was handled and fixed in
1. Kernel
https://github.com/torvalds/linux/commit/37091fdd831f28a6509008542174ed324dd645bc
which is 4.6 and thereby fixed in >=Yakkety.
2. Systemd https://github.com/systemd/systemd/pull/2422 that went into systemd
230 which
I discussed the multipath-tools dependency in the context of Debian.
But for multipath it really is a dependency.
The bug will soon switch to closed (wont'fix)
Yet OTOH it only is that for multiapth-tools-boot and kpartx-boot.
These are optional installs - even multipath-tools only suggests that.
Public bug reported:
Hi,
this seems to me to be a kernel crash of some sorts.
Somewhat in the spirit of older bugs:
- bug 1630940
- bug 1630578
Xnox asked me to look into a hang on openvswitch dep8 tests.
What I found initially was in the log just
"ERROR: Removing temporary files on testbed tim
The last two known good runs on LP infra also were on the same kernel
4.12.0.11.12, no idea yet what has changed.
Maybe the openvswitch upload itself a while ago - but that worked as well on LP
infra ... ?
--
You received this bug notification because you are a member of Kernel
Packages, which
Hi Bot,
this issue does not need the usual logs IMHO, reproducible as instructed "on
demand" - setting back to new.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in U
ok, every bot is different, this one wants confirmed to be silent.
Setting that ...
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
Installed requested mainline in my autopkgtest environment created as described
above.
Booting correctly by default and verified to boot into this by default.
Now kicking the autopkgtest that was hanging before, but still running into the
crash.
On the serial console (connect as described above)
nee: ChristianEhrhardt (paelzer) => (unassigned)
--
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/1712232
Title:
[Feature] KNM: KNM NIs Enabling
Status in intel:
New
Status in linux p
Public bug reported:
Hi,
there is this patch in discussion [1].
If I read correctly between the lines that is supposed to go to -stable trees
as well as to linxu-s390x next (4.14) submissions.
But the change is rather big and we have to consider taking that early or as
SRU or not at all.
I wan
Also asking Lou to reverse mirror and let Christian Borntraeger (Author)
be added on the mirror of this.
--
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/1713765
Title:
Consider "s390/mm:
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
Continued the discussion on IRC:
[10:19] cpaelzer: just to shortcut. FWIW, this fix is only necessary
if you have guest that use storage keys - e.g. an 16.04 guest should not
trigger this problem.
[10:21] hws: do we have any linux guests that use storgae keys in
the meantime?
[10:21] I m
I was asked to also recheck:
Working on artful for me as well:
[...]
root@cpaelzer-artful:/home/ubuntu/xfstests-dev# ./check tests/xfs/073
FSTYP -- xfs (non-debug)
PLATFORM -- Linux/ppc64le cpaelzer-artful 4.11.0-10-generic
MKFS_OPTIONS -- -f -bsize=4096 /dev/loop1
MOUNT_OPTIONS -
Hi Cody,
that would be a bug (feature request) against (upstream) overlayfs then right?
I wonder this being against "cloud-initramfs-tools (Ubuntu)".
Lets retarget the bug at overlayfs for now to discuss in that context (which is
the kernel package).
Or OTOH you meant to want us to consider pick
I thank you for your report and your help to make Ubuntu better.
But for now I'll mark it incomplete until it is clear what the requested action
shall be.
Please feel free to set back to new when the clarification is provided.
--
You received this bug notification because you are a member of Ke
There could be two potential changes that caused this regression,
looking at [1]:
It either is the newer OVS 2.8 or the Kernel 4.12.
There are two good tests with OVS-2.8 in a row.
2017-08-10 16:37:12 UTC
2017-08-14 11:20:32 UTC
Given the current rate of success (5/24) it is rather unlikely that
You can add/remove kernels to the guest by mounting them like via qemu-nbd.
To properly install boot it directly in kvm and then run dpkg.
That way I tested the mainline kernel above and the same way I switched back to
[1].
With that I got correctly the older kernel:
autopkgtest [13:48:11]: tes
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, 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
Realized a plymouth task would be right when I checked for the bug
number to pass it along.
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
And @bdmurray - what you tried surely was good - don't be overmodest :-)
Never the less exact step-by-step commands can't hurt.
--
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/1696102
Titl
[21:30] Could you update the test case with the setup you
configured on diamond? I just used the environment you had configured so
I'm not convinced what I tried at home was good.
Helping where I can :-)
Trying to add a full path of "how to reproduce"
# Prep VM
$ uvt-simplestreams-libvirt --verb
I feel a bit like a retry bot - no offense - but you do realized that I
posted steps to reproduce on the initial post already right?
Maybe it helps to document the steps to exchange a kernel.
1. you have an image created like
autopkgtest-buildvm-ubuntu-cloud -a i386 -r artful -s 10G
2. you mount
Seth missed to actually close it, doing so.
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu)
Assignee: Seth Forshee (sforshee) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
There seems to be an update-regression in Artful.
Booting a recent Artful guest now again also throws:
[485006.367929] Facility 'TM' unavailable, exception at 0xd00021617f10,
MSR=90009033
[485006.367943] Oops: Unexpected facility unavailable exception, sig: 6 [#14]
[485006.367945] SMP
** Also affects: linux-aws (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1716616
Title:
linux-aws: -proposed tracker
St
Hi,
I think this is more a "is it time to rethink the default fs.aio-max-nr than a
qemu problem.
In general pick any limit and you will be able to create a testcase breaking it.
Are all these bugs ... do we need to set all limits to unlimited - I'm sure you
agree not to.
Anyway I agree to Viktor
OTOH I wonder to some extend how you exceded the 65k with "just" 18 guests.
Not strictly required, but it might be very interesting before your system
becomes unavailable to track:
$ sysctl fs.aio-nr
while starting the guests. How much get added per guest, would the settle down
after the guest
101 - 200 of 346 matches
Mail list logo
