[Kernel-packages] [Bug 1752026] Comment bridged from LTC Bugzilla

2018-04-10 Thread bugproxy 
--- Comment From bssrika...@in.ibm.com 2018-04-10 06:53 EDT---
We have got the qemu build with htm-on today [April 10th]. Now we are able to 
start compat mode guests with htm-on.. apart from bug 166570 things look good. 
We can close this one.

-- 
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 type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  qemu-cmd line:

  libvirt+   4283  1 99 09:26 ?00:00:38 qemu-system-ppc64
  -enable-kvm -name

[Kernel-packages] [Bug 1752026] Comment bridged from LTC Bugzilla

2018-04-04 Thread bugproxy 
--- Comment From bren...@br.ibm.com 2018-04-04 08:50 EDT---
Hi Frank,

First of all, thanks for caring about this bug and accepting the out-of-
the-tree patches.

You are right, the motivation to include this patchset is to re-enable
the HTM in the KVM guests. So, we just need to schedule the fixes on
both side.

Here are some assumptions I have:

1) If you need to revert the qemu-kvm "HTM off" patches right now, We
can survive, since we have a internal kernel that contains the fix, and
we can use this custom kernel in the mean time. Not a big deal.

2) On the other side, I understand that the Final Freeze for Ubuntu will
be in April 19th, so, we still have some time to release qemu, how long
can we wait without affecting the time to we spend testing this package?

3) Releasing the fixed kernel prior to the fixed qemu package would be
better than the other way around.

4) Can't we fix fix qemu now and keep it in the proposed until the
kernel is released?

Thanks!

--- Comment From lagar...@br.ibm.com 2018-04-04 08:55 EDT---
One other possibility could be to have the changes going into the kernel and, 
then, remove the workaround from QEMU. QEMU with the workaround should continue 
to work with the kernel with the proper changes. HTM will be disabled in the 
guests, which would not be needed anymore, but would not block a VM from 
running.

Anyway, I am OK either way. We need to make progress here and I
understand this came in late. We need to have the fixes in the kernel
and the workaround out of QEMU. If that means we will have a broken QEMU
for few days, that would be OK. We can continue our tests with previous
versions of kernel and QEMU until everything is settled in bionic
repositories or disable HTM by hand when running tests.

-- 
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 type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev

[Kernel-packages] [Bug 1752026] Comment bridged from LTC Bugzilla

2018-04-04 Thread bugproxy 
--- Comment From bssrika...@in.ibm.com 2018-04-04 04:18 EDT---
(In reply to comment #48)
> Since the kernel team is now investigating the integration of the kernel
> patches into bionic (the kernel bits are already Fix Committed), we should
> plan to get the temporary workaround again removed from qemu-kvm.
> It's hard to time it in a way that the kernel changes are rolled-out and the
> qemu workaround got removed at the same time.
> So this could lead to a short time of the qemu mitigation being reverted,
> but the kernel not yet being released, which would make you need the
> cap-htm=0ff workaround. But that way it would be much safer that both
> changes are available prior to the release of 18.04 Bionic.
> Hence the question (to IBM) is if it would be okay to plan ahead and to get
> the qemu changes reverted back now?

Yes, we need the qemu workaround to be removed. I see all required
kernel patches are in master-next of bionic. Understand that both of
these cannot be timed.. but having qemu changes revert today.. would we
get updated kernel and qemu in tomorrows daily build? just wanted to
understand what would be time window..

-- 
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 type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please

[Kernel-packages] [Bug 1752026] Comment bridged from LTC Bugzilla

2018-04-02 Thread bugproxy 
--- Comment From lagar...@br.ibm.com 2018-04-02 19:22 EDT---
The patches that make it possible to use HTM in guests running on POWER9 
processors are now in the PowerPC kernel maintainer tree and will be requested 
to get merged into kernel 4.17:

681c617b7c42 KVM: PPC: Book3S HV: Work around TEXASR bug in fake suspend state
87a11bb6a7f7 KVM: PPC: Book3S HV: Work around XER[SO] bug in fake suspend mode
4bb3c7a0208f KVM: PPC: Book3S HV: Work around transactional memory bugs in 
POWER9
7672691a08c8 powerpc/powernv: Provide a way to force a core into SMT4 mode
b5af4f279323 powerpc: Add CPU feature bits for TM bug workarounds on POWER9 v2.2
9bbf0b576d32 powerpc: Free up CPU feature bits on 64-bit machines
dd0efb3f11cc powerpc: Book E: Remove unused CPU_FTR_L2CSR bit
c0d64cf9fefd powerpc: Use feature bit for RTC presence rather than timebase 
presence

Fom Paul Mackerras: for a backport, we can probably avoid the feature
bit rework, I hope, and just find two free CPU feature bits. If there
aren't 2 free feature bits then let me know, we might be able to
scavenge some that are only used on Book E or something.

-- 
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 type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails

[Kernel-packages] [Bug 1752026] Comment bridged from LTC Bugzilla

2018-03-23 Thread bugproxy 
--- Comment From sathe...@in.ibm.com 2018-03-23 01:53 EDT---
(In reply to comment #43)
> - Today, I setup Ubuntu KVM on my Boston system using Ubuntu 18.04 daily
> build below
>
>http://cdimages.ubuntu.com/ubuntu-server/daily/current/
>
> - With today build, it no longer has the Transaction Memory error when start
> up a KVM guest. So the fix in this LTCbug mhave made it into Ubuntu daily
> build.

(In reply to comment #43)
> - Today, I setup Ubuntu KVM on my Boston system using Ubuntu 18.04 daily
> build below
>
>http://cdimages.ubuntu.com/ubuntu-server/daily/current/
>
> - With today build, it no longer has the Transaction Memory error when start
> up a KVM guest. So the fix in this LTCbug mhave made it into Ubuntu daily
> build.

Hi Nguyen,

Pauls patch(https://patchwork.ozlabs.org/project/kvm-
ppc/list/?series=35017) yet to get merged in linux master as of
now{f36b7534b833 (HEAD -> master, upstream/master) Merge branch 'akpm'
(patches from Andrew)}

Does ubuntu daily kernel include custom patches?

If it does not include custom patches and one reason why you do not hit
the issue now, coz qemu disable cap-htm by default temporarily till the
above kernel patches included, check if that is the case.

you can confirm the TM patches are included by explicitly start qemu-kvm
command with cap-htm=on

Regards,
-Satheesh.

-- 
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 type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off

[Kernel-packages] [Bug 1752026] Comment bridged from LTC Bugzilla

2018-03-22 Thread bugproxy 
--- Comment From nguy...@us.ibm.com 2018-03-22 15:48 EDT---
- Today, I setup Ubuntu KVM on my Boston system using Ubuntu 18.04 daily build 
below

http://cdimages.ubuntu.com/ubuntu-server/daily/current/

- With today build, it no longer has the Transaction Memory error when
start up a KVM guest. So the fix in this LTCbug mhave made it into
Ubuntu daily build.

-- 
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 type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  qemu-cmd line:

  libvirt+

[Kernel-packages] [Bug 1752026] Comment bridged from LTC Bugzilla

2018-03-21 Thread bugproxy 
--- Comment From s...@us.ibm.com 2018-03-21 12:20 EDT---
Gustavo, would you please add this patch to the Ubuntu kernel you created with 
the trap/HMI patches?

-- 
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 type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  qemu-cmd line:

  libvirt+   4283  1 99 09:26 ?00:00:38 qemu-system-ppc64
  -enable-kvm -name guest=virt-tests-vm1,debug-threads=on -S -object
  secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4

[Kernel-packages] [Bug 1752026] Comment bridged from LTC Bugzilla

2018-03-21 Thread bugproxy 
--- Comment From p...@au1.ibm.com 2018-03-21 07:12 EDT---
The latest version of the patches has been posted and is available at 
https://patchwork.ozlabs.org/project/kvm-ppc/list/?series=35017. I will add a 
note when the series has been put in a maintainer's tree.

-- 
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 type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  qemu-cmd line:

  libvirt+   4283  1 99 09:26 ?00:00:38 qemu-system-ppc64
  -enable-kvm -name

[Kernel-packages] [Bug 1752026] Comment bridged from LTC Bugzilla

2018-03-20 Thread bugproxy 
--- Comment From nguy...@us.ibm.com 2018-03-20 16:38 EDT---
I went to https://www.spinics.net/lists/kvm/msg165629.html but it only has 
source code change for the problem.

Can Linux team build a patch against Ubuntu 18.04 kernel
4.15.0-12-generic for test team to install.  Thanks

-- 
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 type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  qemu-cmd line:

  libvirt+   4283  1 99 09:26 ?00:00:38 qemu-system-ppc64
  -enable-kvm -name

[Kernel-packages] [Bug 1752026] Comment bridged from LTC Bugzilla

2018-03-13 Thread bugproxy 
--- Comment From sathe...@in.ibm.com 2018-03-13 12:52 EDT---
Paul's RFC patch to kernel, https://www.spinics.net/lists/kvm/msg165629.html

-- 
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 type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  qemu-cmd line:

  libvirt+   4283  1 99 09:26 ?00:00:38 qemu-system-ppc64
  -enable-kvm -name guest=virt-tests-vm1,debug-threads=on -S -object
  secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4

[Kernel-packages] [Bug 1752026] Comment bridged from LTC Bugzilla

2018-03-01 Thread bugproxy 
--- Comment From s...@us.ibm.com 2018-03-01 15:07 EDT---
(In reply to comment #29)
> (In reply to comment #28)
> > (In reply to comment #27)
> > > @paelzer yes, that is us agreeing with your plan
> >
> > Does it mean that we are not going to have HTM support on KVM guests, even
> > in POWER8?
>
> you would use the 2.10 machine type for that, right?
Right. This is about the new machine type.

-- 
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 type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

[Kernel-packages] [Bug 1752026] Comment bridged from LTC Bugzilla

2018-03-01 Thread bugproxy 
--- Comment From s...@us.ibm.com 2018-03-01 10:42 EDT---
@paelzer yes, that is us agreeing with your plan
>A) We switch the default to HTM=off in qemu "now" (as soon as you ack this) to 
>be safe
>B) If you get the kernel fixes upstream fast enough for the kernel Team to 
>pick up in time:
>...

Sorry for the delay.

-- 
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 type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  qemu-cmd line:

  libvirt+   4283  1 99 09:26 ?00:00:38

[Kernel-packages] [Bug 1752026] Comment bridged from LTC Bugzilla

2018-02-28 Thread bugproxy 
--- Comment From sura...@au1.ibm.com 2018-03-01 01:22 EDT---
Seems like the best option in my opinion

-- 
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 type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  qemu-cmd line:

  libvirt+   4283  1 99 09:26 ?00:00:38 qemu-system-ppc64
  -enable-kvm -name guest=virt-tests-vm1,debug-threads=on -S -object
  secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4
  -virt-tests-vm1/master-key.aes -machine

[Kernel-packages] [Bug 1752026] Comment bridged from LTC Bugzilla

2018-02-28 Thread bugproxy 
--- Comment From sthou...@in.ibm.com 2018-03-01 00:00 EDT---
*** Bug 165240 has been marked as a duplicate of this bug. ***

-- 
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 type(pseries-bionic) complaining "KVM implementation does not
  support Transactional Memory, try cap-htm=off" (kvm)

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  == Comment: #0 - Satheesh Rajendran  - 2018-02-23 
08:31:06 ==
  ---Problem Description---
  libvirt unable to start a KVM guest complaining about cap-htm machine 
property to be off

  Host Env:
  # lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  160
  On-line CPU(s) list: 0-159
  Thread(s) per core:  4
  Core(s) per socket:  20
  Socket(s):   2
  NUMA node(s):2
  Model:   2.2 (pvr 004e 1202)
  Model name:  POWER9 (raw), altivec supported
  CPU max MHz: 3800.
  CPU min MHz: 2166.
  L1d cache:   32K
  L1i cache:   32K
  L2 cache:512K
  L3 cache:10240K
  NUMA node0 CPU(s):   0-79
  NUMA node8 CPU(s):   80-159

  ii  qemu-kvm  1:2.11+dfsg-1ubuntu2
  ppc64el  QEMU Full virtualization on x86 hardware

  ii  libvirt-bin   4.0.0-1ubuntu3
  ppc64el  programs for the libvirt library

  # lsmcode
  Version of System Firmware : 
   Product Name  : OpenPOWER Firmware
   Product Version   : open-power-SUPERMICRO-P9DSU-V1.03-20180205-imp
   Product Extra :  occ-577915f
   Product Extra :  skiboot-v5.9-240-g081882690163-pcbedce4
   Product Extra :  petitboot-v1.6.6-p019c87e
   Product Extra :  sbe-095e608
   Product Extra :  machine-xml-fb5f933
   Product Extra :  hostboot-9bfb201
   Product Extra :  linux-4.14.13-openpower1-p78d7eee

  
   
  Contact Information = sathe...@in.ibm.com 
   
  ---uname output---
  4.15.0-10-generic
   
  Machine Type = power9 boston 2.2 (pvr 004e 1202) 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Boot a guest from libvirt with default pseries machine type or 
pseries-bionic

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  Starting install...
  ERRORinternal error: process exited while connecting to monitor: 
,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=26 
-device 
virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:77:78:79,bus=pci.0,addr=0x1 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x3000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
  2018-02-23T14:21:11.081809Z qemu-system-ppc64: KVM implementation does not 
support Transactional Memory, try cap-htm=off
  Domain installation does not appear to have been successful.
  If it was, you can restart your domain by running:
virsh --connect qemu:///system start virt-tests-vm1
  otherwise, please restart your installation.

  2. Fails to boot..

  Note: if we specify machine type as pseries=2.12 it boots fine like
  below

  /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 
'virt-tests-vm1' --machine pseries-2.12 --memory=32768 
--vcpu=32,sockets=1,cores=32,threads=1 --import --nographics --serial pty 
--memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk 
path=/var/lib/libvirt/images/workspace/runAvocadoFVTTest/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2,bus=scsi,size=10,format=qcow2
 --network=bridge=virbr0,model=virtio,mac=52:54:00:77:78:79 --noautoconsole
  WARNING  No operating system detected, VM performance may suffer. Specify an 
OS with --os-variant for optimal results.

  qemu-cmd line:

  libvirt+   4283  1 99 09:26 ?00:00:38 qemu-system-ppc64
  -enable-kvm -name guest=virt-tests-vm1,debug-threads=on -S -object
  secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-4
  -virt-tests-vm1/master-key.aes -machine