[Kernel-packages] [Bug 1755999] [NEW] Reproducible hang in ext4 generic/430 with xfstest from upstream
Public bug reported: While testing the latest xfstest from upstream, the generic/430 test will hang with ext4 test. It looks like this issue was caused by the following command to copy beyond the file: /usr/sbin/xfs_io -i -f -c "copy_range -s 4000 -l 2000 /home/ubuntu/test/test-430/file" "/home/ubuntu/test/test-430/beyond" The copied file will have a correct MD5 as expected. e68d4a150c4e42f4f9ea3ffe4c9cf4ed beyond But the command will never return. The file size of test-430/file is 5000, so a copy_range call with source offset 4000 with length 1000 works, but > 1000 does not. Steps: 1. Deploy a node with Bionic (should have a /dev/sdb available for the test) 2. Run: sudo apt-get install git python-minimal -y git clone --depth=1 https://github.com/Cypresslin/autotest-client-tests.git -b kteam-xfstest-upstream git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests 3. Run the test with the following command: AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ (The test suite can be built manually, but it's easier to do this with autotest framework) To run this test solely after the test partition has been creation on /dev/sdb: mkdir /home/ubuntu/test cd autotest/client/tmp/xfstests/src/xfstests-bld/xfstests-dev sudo su export TEST_DIR=/home/ubuntu/test export TEST_DEV=/dev/sdb1 ./check generic/430 Tested with the latest mainline kernel, 4.16.0-041600rc5-generic, and the bug still exist. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 [modified: boot/vmlinuz-4.15.0-10-generic] ProcVersionSignature: User Name 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1148 F pulseaudio /dev/snd/controlC1: ubuntu 1148 F pulseaudio Date: Thu Mar 15 14:24:46 2018 InstallationDate: Installed on 2018-03-15 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) MachineType: Dell Inc. Dell Precision M3800 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=d1980d27-9063-4d92-aa10-1fb240453d8d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/14/2014:svnDellInc.:pnDellPrecisionM3800:pvrA07:rvnDellInc.:rnDellPrecisionM3800:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: While testing the latest xfstest from upstream, the generic/430 test will hang with ext4 test. - It looks like this issue was caused by the following command to copy beyond the file: /usr/sbin/xfs_io -i -f -c "copy_range -s 4000 -l 2000 /home/ubuntu/test/test-430/file" "/home/ubuntu/test/test-430/beyond" The copied file will have a correct MD5 as expected. e68d4a150c4e42f4f9ea3ffe4c9cf4ed beyond But the command will never return. + The file size of test-430/file is 5000, so a copy_range call with source + offset 4000 with length 1000 works, but > 1000 does not. + Steps: - 1. Deploy a node with Bionic (should have a /dev/sdb available for the test) - 2. Run: - sudo apt-get install git python-minimal -y - git clone --depth=1 https://github.com/Cypresslin/autotest-client-tests.git -b kteam-xfstest-upstream - git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest - rm -fr autotest/client/tests - ln -sf ~/autotest-client-tests autotest/client/tests - 3. Run the test with the following command: - AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ + 1. Deploy a node with Bionic (should have a /dev/sdb available for the test) + 2. Run: + sudo apt-get install git python-minimal -y + git clone --depth=1 https://github.com/Cypresslin/autotest-client-tests.git -b kteam-xfstest-upstream + git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest + rm -fr autotest/client/tests + ln -sf ~/autotest-client-tests autotest/client/tests + 3. Run the test with the following command: +
[Kernel-packages] [Bug 1755804] Re: IMA policy parsing is broken in 4.13
Yes, this kernel works as expected, thanks. I presume that despite this being marked as Artful the fix will get into Xenail hwe releases. Is this correct? -- 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/1755804 Title: IMA policy parsing is broken in 4.13 Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: Linux kernel version 4.13 has a bug in IMA policy parsing that prevents setting IMA measurements and appraisal options per fsuuid. The issue can be reproduced with simple ima_policy: # fsuuid=$(blkid -s UUID -o value /dev/sda1) # cat > ima_policy << EOF dont_appraise fsuuid=$fsuuid dont_measure fsuuid=$fsuuid EOF # cat ima_policy > /sys/kernel/security/ima/policy cat: write error: Invalid argument # dmesg | tail [ 928.069606] audit: type=1805 audit(1521031959.907:18): action="dont_appraise" fsuuid="aef88a4e-dbea-4cc7-be8b-03cf8501cc8f" res=0 [ 928.069895] audit: type=1802 audit(1521031959.908:19): pid=1806 uid=0 auid=0 ses=1 op="update_policy" cause="invalid-policy" comm="cat" res=0 [ 928.070829] IMA: policy update failed [ 928.070860] audit: type=1802 audit(1521031959.909:20): pid=1806 uid=0 auid=0 ses=1 op="policy_update" cause="failed" comm="cat" res=0 The same policy can be successfully loaded on v4.10: (v4.10) # dmesg | tail [ 54.071383] IMA: policy update completed [ 54.071484] kauditd_printk_skb: 1 callbacks suppressed [ 54.071487] audit: type=1805 audit(1521030962.958:15): action="dont_appraise" fsuuid="aef88a4e-dbea-4cc7-be8b-03cf8501cc8f" res=1 [ 54.071491] audit: type=1805 audit(1521030962.958:16): action="dont_measure" fsuuid="aef88a4e-dbea-4cc7-be8b-03cf8501cc8f" res=1 [ 54.071493] audit: type=1802 audit(1521030962.958:17): pid=1793 uid=0 auid=0 ses=1 op="policy_update" cause="completed" comm="cat" res=1 The bug is fixed in the mainline kernel: [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/security/integrity/ima/ima_policy.c?id=36447456e1cca853188505f2a964dbbeacfc7a7a --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 14 12:37 seq crw-rw 1 root audio 116, 33 Mar 14 12:37 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=aef88a4e-dbea-4cc7-be8b-03cf8501cc8f ro console=tty1 console=ttyS0 crashkernel=384M-2G:128M,2G-:256M ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-36-generic N/A linux-backports-modules-4.13.0-36-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images Uname: Linux 4.13.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: pkcs11 _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755804/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751234] Re: Unable to insert test_bpf module on Bionic s390x
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => Medium ** Changed in: ubuntu-z-systems Status: New => 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/1751234 Title: Unable to insert test_bpf module on Bionic s390x Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: The ubuntu_bpf_jit test failed on s2lp6g002 with Bionic kernel. Error message: modprobe: ERROR: could not insert 'test_bpf': Invalid argument When you try to insert the module with insmod it shows: $ sudo insmod /lib/modules/4.15.0-9-generic/kernel/lib/test_bpf.ko insmod: ERROR: could not insert module /lib/modules/4.15.0-9-generic/kernel/lib/test_bpf.ko: Invalid module format $ dpkg -S /lib/modules/4.15.0-9-generic/kernel/lib/test_bpf.ko linux-image-4.15.0-9-generic: /lib/modules/4.15.0-9-generic/kernel/lib/test_bpf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Feb 23 09:31:55 2018 HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.171 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1751234/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1493481] Re: bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state from avctp_confirm_cb:server_cb from g_main_dispatch
Fix released (zero crash reports after 15.04) ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1493481 Title: bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state from avctp_confirm_cb:server_cb from g_main_dispatch Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with version 4.101-0ubuntu25.1~overlay2, the problem page at https://errors.ubuntu.com/problem/1c7ce0e3d4d00429fd1a154776e90a7b6a1a3ca5 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493481/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1493528] Re: bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state from session_cb from g_main_dispatch:g_main_context_dispatch
Fix released (zero crash reports after 15.04) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1493528 Title: bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state from session_cb from g_main_dispatch:g_main_context_dispatch Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with version 4.101-0ubuntu25.1~overlay2, the problem page at https://errors.ubuntu.com/problem/b2077378adbdb76716399672a8b463aeffbfea17 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1493528] Re: bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state from session_cb from g_main_dispatch:g_main_context_dispatch
Fix released (zero crash reports after 15.04) ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1493528 Title: bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state from session_cb from g_main_dispatch:g_main_context_dispatch Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with version 4.101-0ubuntu25.1~overlay2, the problem page at https://errors.ubuntu.com/problem/b2077378adbdb76716399672a8b463aeffbfea17 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1747639] Re: [18.04 FEAT] Automatically detect layer2 setting in the qeth device driver
** Changed in: ubuntu-z-systems Status: Fix Committed => 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/1747639 Title: [18.04 FEAT] Automatically detect layer2 setting in the qeth device driver Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Follow-on of https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1541544 Now we have an enhancement as part of kernel 4.16. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1747639/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755470] Re: [P9, Power NV][Witherspoon][Ubuntu 18.04][Perf] : PMU events by name it is not listed under perf list
** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- 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/1755470 Title: [P9,Power NV][Witherspoon][Ubuntu 18.04][Perf] : PMU events by name it is not listed under perf list Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Shriya R. Kulkarni- 2018-01-03 04:50:13 == Problem Description : = PMU events by name is not listed under perf list on Witherspoon Machine. root@ltc-wspoon12:~# perf list | grep pm_ power:dev_pm_qos_add_request [Tracepoint event] power:dev_pm_qos_remove_request[Tracepoint event] power:dev_pm_qos_update_request[Tracepoint event] power:device_pm_callback_end [Tracepoint event] power:device_pm_callback_start [Tracepoint event] power:pm_qos_add_request [Tracepoint eve Hardware details : == uname -a : Linux ltc-wspoon12 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine : Witherspoon + DD2.0 + Power NV FW : OP9_v1.19_1.94 OS : Ubuntu 18.04 root@ltc-wspoon12:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Bionic Beaver (development branch)" VERSION_ID="18.04" == Comment: #14 - Gustavo Luiz Ferreira Walbon - 2018-03-08 07:58:19 == To set up the perf to list all PMU events for P9. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1755470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755979] Re: Cpu utilization showing system time for kvm guests (performance) (sysstat)
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Importance: Undecided => High ** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: ubuntu-power-systems Status: New => Triaged ** Tags added: triage-g -- 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/1755979 Title: Cpu utilization showing system time for kvm guests (performance) (sysstat) Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - JENIFER HOPPER- 2018-03-14 16:20:47 == +++ This bug was initially created as a clone of Bug #163375 +++ ---Problem Description--- All KVM guest cpu utilization is being reported as sys% time in the host. It turns out Guest time accounting (CONFIG_VIRT_CPU_ACCOUNTING_GEN) has been broken since v4.13 by commit: commit 8b24e69fc47e43679bb29ddb481aa0e8dce2a3c5 Author: Paul Mackerras Date: Mon Jun 26 15:45:51 2017 +1000 KVM: PPC: Book3S HV: Close race with testing for signals on guest entry --- That is now fixed and upstream accepted in Paulus' tree as git commit: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-fixes=61bd0f66ff92d5ce765ff9850fd3cbfec773c560 ("KVM: PPC: Book3S HV: Fix guest time accounting with VIRT_CPU_ACCOUNTING_GEN") Please include this patch in Ubuntu so that guest cpu accounting is correct. Contact Information = jhop...@us.ibm.com ---uname output--- Linux ltc-b114 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 5104-22C ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Start a KVM guest, run something that generates cpu utilization in the guest, observe mpstat on the host. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1755979/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1755979] [NEW] Cpu utilization showing system time for kvm guests (performance) (sysstat)
You have been subscribed to a public bug: == Comment: #0 - JENIFER HOPPER- 2018-03-14 16:20:47 == +++ This bug was initially created as a clone of Bug #163375 +++ ---Problem Description--- All KVM guest cpu utilization is being reported as sys% time in the host. It turns out Guest time accounting (CONFIG_VIRT_CPU_ACCOUNTING_GEN) has been broken since v4.13 by commit: commit 8b24e69fc47e43679bb29ddb481aa0e8dce2a3c5 Author: Paul Mackerras Date: Mon Jun 26 15:45:51 2017 +1000 KVM: PPC: Book3S HV: Close race with testing for signals on guest entry --- That is now fixed and upstream accepted in Paulus' tree as git commit: https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-fixes=61bd0f66ff92d5ce765ff9850fd3cbfec773c560 ("KVM: PPC: Book3S HV: Fix guest time accounting with VIRT_CPU_ACCOUNTING_GEN") Please include this patch in Ubuntu so that guest cpu accounting is correct. Contact Information = jhop...@us.ibm.com ---uname output--- Linux ltc-b114 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 5104-22C ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Start a KVM guest, run something that generates cpu utilization in the guest, observe mpstat on the host. ** Affects: ubuntu-power-systems Importance: High Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-165731 severity-high targetmilestone-inin--- -- Cpu utilization showing system time for kvm guests (performance) (sysstat) https://bugs.launchpad.net/bugs/1755979 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp