[Kernel-packages] [Bug 1603902] Re: qemu-img convert hangs on Ubuntu Server 16.04 with 100% cpu

Thanks Matt, yeah we actually had no similar report in all the time. It is unclear to me if there still is something needed in the kernel, but it is unclear which (if any) qemu change needs to be done as there is no external reproducer. It is good to hear that in your case after working heavily

[Kernel-packages] [Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86

I re-deployed one of my systems to Xenial. For the complexity of going back I took what kernel is currently active which was 4.4.0-224 With that I spun up the Xubuntu 32 bit iso you referred. For the sake of completeness I also did the same on 4.15.0-20-generic (also with newer qemu of bionic).

[Kernel-packages] [Bug 1239109] Re: aarch64 clock_gettime with CLOCK_REALTIME_COARSE or CLOCK_MONOTONIC_COARSE fails with SIGBUS or SIGSEGV

This bug was fixed in the package libqb - 1.0.3-1 --- libqb (1.0.3-1) unstable; urgency=medium [ Christoph Berg ] * [3e6a1ea] Remove Richard and myself from Uploaders [ Ferenc Wágner ] * [2dbb472] Update old style gbp.conf section names * [c566381] New upstream release

[Kernel-packages] [Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86

Hmm, so it is not even burning CPU for anything neither in the Host (usr ~=qemu, sys ~=kernel) nor in the guest itself (~=guest). The KVM exits confirm that, it doesn't do a a lot entry/exit is the pass in/out of guest context and the only meaningful exit means it emulates an instruction. So if

[Kernel-packages] [Bug 1239109] Re: aarch64 clock_gettime with CLOCK_REALTIME_COARSE or CLOCK_MONOTONIC_COARSE fails with SIGBUS or SIGSEGV

** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/libqb/+git/libqb/+merge/345212 -- 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/1239109 Title: aarch64

[Kernel-packages] [Bug 1239109] Re: aarch64 clock_gettime with CLOCK_REALTIME_COARSE or CLOCK_MONOTONIC_COARSE fails with SIGBUS or SIGSEGV

Actually lets close libqb with the sync then (when the Delta is dropped). ** Changed in: libqb (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1239109] Re: aarch64 clock_gettime with CLOCK_REALTIME_COARSE or CLOCK_MONOTONIC_COARSE fails with SIGBUS or SIGSEGV

This very very likely was fixed a long time ago, but I wanted to be sure. So I used this simple test program: #include #include #include #include void timespec_diff(const struct timespec *start, const struct timespec *stop, struct timespec *result) { if ((stop->tv_nsec

[Kernel-packages] [Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86

For the per thread view use: $ sudo pidstat -t -p For perf to track kvm exits you can install it like: $ sudo apt install linux-tools-common And then run while your guest hangs (or not in the good case) as: $ sudo perf stat -e 'kvm:*' -a sleep 1h More on [1] if you want. [1]:

[Kernel-packages] [Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86

Hi Skipper, thanks for sharing the qemu cmdline, there is nothing odd in this and I can run a system like that (not a win 10 guest) just fine. What about the per thread stats I asked, which threads are busy and where do they consume time? Depending on your experience you could even check "perf

[Kernel-packages] [Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86

Also a per qemu thread view is often useful, you might also add $ pidstat -t -p Further since this is reported as kernel update regression I'll flag it as that for now. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: regression-update -- You

[Kernel-packages] [Bug 1766534] Re: libguestfs cannot start the qemu process on s390x

Given the current Final Freeze for 18.04 this will (if done) have to be an SRU for 18.04 as well. I just did the initial triage, but will leave it for the screener team to ensure it is as needed. ** Also affects: libguestfs (Ubuntu) Importance: Undecided Status: New ** Changed in:

[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

Fix for chrony (following networkd-dispatcher change in bug 1765152) uploaded to bionic-unapproved as 3.2-4ubuntu4 -- 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:

[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

Tested on chrony which has a NetworkManager dispatch script that also works as a hook for networkd-dispatcher. Works fine by just dropping the links for now. Changes visible when these hooks are in place 1. when sources get unreachable it detects offlining immediately (instead of trying all the

[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

Nice summary, but wrong bug - sorry for the noise here :-/ -- 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: replacement of ifupdown with netplan needs integration for

[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

Lets break this into use cases in Bionic: I was not sure who should win in each case. We might either want the clear "order" chrony > ntp > openntp > systemd-timesyncd Or we might want a "last installed" approach, but that is hard as upgrades to not count here only real "install". What would

[Kernel-packages] [Bug 1739665] Re: [FFE][Feature] KVM CLX avx512_vnni

There wasn't a xen commit listed (and we didn't bump the xen version so we haven't picked it up by accident). I'd assume this is a Won't Fix for 18.04 and might appear sometime later. Is there any xen change to consider (later on) or was xen just optionally listed but doesn't come to life? **

[Kernel-packages] [Bug 1723914] Re: ubuntu-kvm-unit test failed with emulator test on ppc64le

# sudo ./run_tests.sh -v [...] TESTNAME=emulator TIMEOUT=90s ACCEL= ./powerpc/run powerpc/emulator.elf -smp 1 FAIL emulator SKIP h_cede_tm (test marked as manual run only) MIGRATION=yes TESTNAME=sprs TIMEOUT=90s ACCEL= ./powerpc/run powerpc/sprs.elf -smp 1 -append '-w' FAIL sprs Upgrade to fix

[Kernel-packages] [Bug 1723904] Re: ubuntu-kvm-unit test failed with sprs test on ppc64le

same test as the other bug - so same update # sudo ./run_tests.sh -v [...] TESTNAME=emulator TIMEOUT=90s ACCEL= ./powerpc/run powerpc/emulator.elf -smp 1 FAIL emulator SKIP h_cede_tm (test marked as manual run only) MIGRATION=yes TESTNAME=sprs TIMEOUT=90s ACCEL= ./powerpc/run powerpc/sprs.elf

[Kernel-packages] [Bug 1739665] Re: [FFE][Feature] KVM CLX avx512_vnni

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

[Kernel-packages] [Bug 1723914] Re: ubuntu-kvm-unit test failed with emulator test on ppc64le

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

[Kernel-packages] [Bug 1723904] Re: ubuntu-kvm-unit test failed with sprs test on ppc64le

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 Kernel Packages, which

[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

I heard people talk about it, but realized the tracker is missing a Task for openvswitch: /etc/network/if-post-down.d/openvswitch /etc/network/if-pre-up.d/openvswitch IIRC all the discussions correctly that was one of the harder cases due to "Pre" not really being a defined thing anymore. The

[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

Revert will be hanlded via bug 1761175 -- 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:POWER9:DD2.2 - Unable to start a KVM guest with default machine

[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

@Breno - I agree to #3 but since we have no hard ETA on the kernel I want to avoid punting qemu to the very last few days. History told me that always something happens/blocks and if we would miss GA we can't SRu to keep the final pseries-bionic type in sync. For #4 there is no good "keep in

[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

@Seth - that is fine, for the Kernel we only need to rely on "will be out before Bionic release" and that looks good - don't feel pushed. The updates were about asking IBM "If we assume the kernel fixes will be there, should we remove the qemu mitigation (as we can't remove it after Bionic

[Kernel-packages] [Bug 1723904] Re: ubuntu-kvm-unit test failed with sprs test on ppc64le

Regression tests started on all arches -- 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/1723904 Title: ubuntu-kvm-unit test failed with sprs test on ppc64le Status in linux package in

[Kernel-packages] [Bug 1723914] Re: ubuntu-kvm-unit test failed with emulator test on ppc64le

Regression tests started on all arches -- 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/1723914 Title: ubuntu-kvm-unit test failed with emulator test on ppc64le Status in The

[Kernel-packages] [Bug 1723904] Re: ubuntu-kvm-unit test failed with sprs test on ppc64le

Tested the new build with the outlined testcase: MIGRATION=yes TESTNAME=sprs TIMEOUT=90s ACCEL= ./powerpc/run powerpc/sprs.elf -smp 1 -append '-w' PASS sprs ** Description changed: [Impact] - * Certain Guest features (SPRS) of power8 isa are not working through -a migration. +  

[Kernel-packages] [Bug 1723914] Re: ubuntu-kvm-unit test failed with emulator test on ppc64le

Tested the new build with the outlined testcase: TESTNAME=emulator TIMEOUT=90s ACCEL= ./powerpc/run powerpc/emulator.elf -smp 1 PASS emulator ** Description changed: [Impact] - * on start of qemu-system-ppc64 MSR_SF is not set correctly -So it doesn't start 64bit as it should +  *

[Kernel-packages] [Bug 1723904] Re: ubuntu-kvm-unit test failed with sprs test on ppc64le

SRU Template prepared Once ppa is built: - Regression tests - per case tests Note: test build in ppa at https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/3224 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1723914] Re: ubuntu-kvm-unit test failed with emulator test on ppc64le

SRU Template prepared Once ppa is built: - Regression tests - per case tests Note: test build in ppa at https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/3224 ** Description changed: + [Impact] + + * on start of qemu-system-ppc64 MSR_SF is not set correctly +So it doesn't

[Kernel-packages] [Bug 1723904] Re: ubuntu-kvm-unit test failed with sprs test on ppc64le

** Description changed: + [Impact] + + * Certain Guest features (SPRS) of power8 isa are not working through +a migration. + + * This is part of the ongoing LTS HW exploitation and a fixup to some +verification tests at the same time. + + [Test Case] + + * 1. deploy xenial + HWE

[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"

Also since the change was identified to be in the kernel, set qemu to Won't Fix -- 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/1730717 Title: Some VMs fail to reboot with "watchdog:

[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"

Thanks that this gets into releases now. I wonder about Bionic's status - any update on that? ** Changed in: qemu-kvm (Ubuntu Zesty) Status: New => Won't Fix ** Changed in: qemu-kvm (Ubuntu Bionic) Status: Confirmed => Won't Fix ** Changed in: qemu-kvm (Ubuntu Artful)

[Kernel-packages] [Bug 1723914] Re: ubuntu-kvm-unit test failed with emulator test on ppc64le

Since this fix is in 2.6 is is in >=Yakkety, so nonly considering Xenial for the SRU ** Also affects: qemu (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Xenial)

[Kernel-packages] [Bug 1723904] Re: ubuntu-kvm-unit test failed with sprs test on ppc64le

I plan to combine this with the fix for bug 1723914 which would allow you to only run one verification for both. -- 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/1723904 Title:

[Kernel-packages] [Bug 1723904] Re: ubuntu-kvm-unit test failed with sprs test on ppc64le

Since the fix is in 2.9 only Xenial is considered for the SRU as >=Artful is good ** Also affects: qemu (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu Xenial)

[Kernel-packages] [Bug 1723914] Re: ubuntu-kvm-unit test failed with emulator test on ppc64le

It generally looks good, there are some minor details but I can fix those up when preparing the upload. In this case it isn't much more than identifying the right upstream change, but thanks a lot as this is often the most important part! I plan to combine this with the fix for bug 1723904 which

[Kernel-packages] [Bug 1739665] Re: [FFE][Feature] KVM CLX avx512_vnni

It would be required for Xen as well if it will be done, but I didn't hear on Xen in regard to this so I don't know. SMB might share his opinion on this for xen and he is generally subscribed to xen so he will see the updates. -- You received this bug notification because you are a member of

[Kernel-packages] [Bug 1739665] Re: [FFE][Feature] KVM CLX avx512_vnni

I'll ping the release team to ack the FFE: To make it easier, the change is really just "giving names to formerly undefined bits" => https://git.qemu.org/?p=qemu.git;a=commit;h=aff9e6e46a343e1404498be4edd03db1112f0950 -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1739665] Re: [FFE][Feature] KVM CLX avx512_vnni

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

[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

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

[Kernel-packages] [Bug 1736947] Re: Very long boot time with Chelsio T320 10GBASE-R RNIC adapter

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

[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

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:

[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

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

[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

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:

[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

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)

[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

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:

[Kernel-packages] [Bug 1752026] Re: Ubuntu18.04:POWER9:DD2.2 - Unable to start a KVM guest with default machine type(pseries-bionic) complaining "KVM implementation does not support Transactional Memo

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

[Kernel-packages] [Bug 1723914] Re: ubuntu-kvm-unit test failed with emulator test on ppc64le

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

[Kernel-packages] [Bug 1723914] Re: ubuntu-kvm-unit test failed with emulator test on ppc64le

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

[Kernel-packages] [Bug 1742892] Re: [Power 9] ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Unable to start the guest with more than 1 thread on ubuntu1804 KVM host machine.

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

[Kernel-packages] [Bug 1712803] Re: spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe kernel

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=

[Kernel-packages] [Bug 1742892] Re: [Power 9] ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Unable to start the guest with more than 1 thread on ubuntu1804 KVM host machine.

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]

[Kernel-packages] [Bug 1712803] Re: spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe kernel

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

[Kernel-packages] [Bug 1712803] Re: spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe kernel

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

[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

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

[Kernel-packages] [Bug 1712803] Re: spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe kernel

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:

[Kernel-packages] [Bug 1712803] Re: spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe kernel

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

[Kernel-packages] [Bug 1712803] Re: spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe kernel

** 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

[Kernel-packages] [Bug 1712803] Re: spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe kernel

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

[Kernel-packages] [Bug 1742892] Re: [Power 9] ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Unable to start the guest with more than 1 thread on ubuntu1804 KVM host machine.

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.

[Kernel-packages] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

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

[Kernel-packages] [Bug 1712803] Re: spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe kernel

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

[Kernel-packages] [Bug 1712803] Re: spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe kernel

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

[Kernel-packages] [Bug 1712803] Re: spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe kernel

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:

[Kernel-packages] [Bug 1742892] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Unable to start the guest with more than 1 thread on ubuntu1804 KVM host machine.

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)

[Kernel-packages] [Bug 1742712] [NEW] package removal leave scripts that fail lacking the binaries

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

Re: [Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

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

Re: [Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

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

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

@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.

[Kernel-packages] [Bug 1712831] Re: 4.12.0-11-generic - crashing in infrastructure on i386 openvswitch tests

*** 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

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel opps destroying interfaces on i386

>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

[Kernel-packages] [Bug 1712831] Re: 4.12.0-11-generic - crashing in infrastructure on i386 openvswitch tests

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:

[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

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.

[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

@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

[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

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

[Kernel-packages] [Bug 1734326] Re: qemu-kvm in zesty proposed failed with KVM_GET_DEVICE_ATTR failed error

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

[Kernel-packages] [Bug 1734326] Re: qemu-kvm in zesty proposed failed with KVM_GET_DEVICE_ATTR failed error

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.

[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

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

[Kernel-packages] [Bug 1734326] Re: qemu-kvm in zesty proposed failed with KVM_GET_DEVICE_ATTR failed error

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:

[Kernel-packages] [Bug 1726818] Re: vagrant artful64 box filesystem too small

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

[Kernel-packages] [Bug 1726818] Re: vagrant artful64 box filesystem too small

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

[Kernel-packages] [Bug 1722702] Re: libvirt - vnc port selection regression with newer kernels

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

[Kernel-packages] [Bug 1722702] Re: libvirt - vnc port selection regression with newer kernels

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

[Kernel-packages] [Bug 1732162] Re: Zesty / Artful zKVM does not have /dev/kvm

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

[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

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

[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

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

[Kernel-packages] [Bug 1563887] Re: qemu-system-ppc64 freezes on starting image on ppc64le

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

[Kernel-packages] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

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

[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

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

[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

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

[Kernel-packages] [Bug 1722702] Re: libvirt - vnc port selection regression with newer kernels

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

[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"

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

[Kernel-packages] [Bug 1730717] Re: Some VMs fail to reboot with "watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]"

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

[Kernel-packages] [Bug 1712831] Re: 4.12.0-11-generic - crashing in infrastructure on i386 openvswitch tests

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 =

[Kernel-packages] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

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

[Kernel-packages] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

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

[Kernel-packages] [Bug 1722702] Re: libvirt - vnc port selection regression with newer kernels

@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

[Kernel-packages] [Bug 1723904] Re: ubuntu-kvm-unit test failed with sprs test on ppc64le

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,

  1   2   3   4   >