We are working on qemu 2.11 which IMHO could be the reason for your issues as
well.
Do you happen to know if there are qemu patches post 2.10 needed as well for
the P9 machines?
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
** Tags added: qemu-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/1742892
Title:
ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Unable to start the guest
with more than 1 thread on ubuntu1804 KVM host machine.
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Incomplete
Status in qemu package in Ubuntu:
Incomplete
Bug description:
== Comment: #0 - INDIRA P. JOGA <indira.pr...@in.ibm.com> - 2018-01-07
13:18:32 ==
Problem Description:
===================
Not able to start the ubutnu1804 guest with more than 1 thread on ubuntu1804
KVM host machine
Steps to re-create:
==================
> Installed Ubuntu1804 on boslcp3 host.
root@boslcp3:/home# uname -a
Linux boslcp3 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017
ppc64le ppc64le ppc64le GNU/Linux
root@boslcp3:/home# uname -r
4.13.0-17-generic
> Installed qemu-kvm libvirt-bin ubuntu-vm-builder bridge-utils
packages
root@boslcp3:/home# virsh version
Compiled against library: libvirt 3.6.0
Using library: libvirt 3.6.0
Using API: QEMU 3.6.0
Running hypervisor: QEMU 2.10.1
> root@boslcp3:~# ppc64_cpu --smt
SMT is off
> Defined the guest boslcp3g1 from host machine
root@boslcp3:/home# virsh list --all
Id Name State
----------------------------------------------------
- boslcp3g1 shut off
Please cherry pick
commit 45c940ba490df28cb87b993981a5f63df6bbb8db
Author: Paul Mackerras <pau...@ozlabs.org>
Date: Fri Nov 18 17:43:30 2016 +1100
KVM: PPC: Book3S HV: Treat POWER9 CPU threads as independent subcores
> Started the guest and it fails with the error
root@boslcp3:~# virsh start --console boslcp3g1
error: Failed to start domain boslcp3g1
error: internal error: process exited while connecting to monitor:
2018-01-05T02:54:37.762120Z qemu-system-ppc64: -chardev pty,id=charserial0:
char device redirected to /dev/pts/3 (label charserial0)
2018-01-05T02:54:37.829236Z qemu-system-ppc64: Cannot support more than 1
threads on PPC with KVM
> Unable to start the guest with more than 1 Thread from Ubuntu1804
KVM host machine.
XML:
****
root@boslcp3:/home# virsh dumpxml boslcp3g1
<domain type='kvm'>
<name>boslcp3g1</name>
<uuid>95374879-0ed3-4562-a00f-e47d9aaf285c</uuid>
<maxMemory slots='16' unit='KiB'>10485760</maxMemory>
<memory unit='KiB'>6291456</memory>
<currentMemory unit='KiB'>6291456</currentMemory>
<memoryBacking>
<hugepages>
<page size='2048' unit='KiB' nodeset='0'/>
</hugepages>
</memoryBacking>
<vcpu placement='static' current='16'>32</vcpu>
<resource>
<partition>/machine</partition>
</resource>
<os>
<type arch='ppc64le' machine='pseries-2.10'>hvm</type>
<boot dev='hd'/>
<boot dev='network'/>
<bootmenu enable='yes'/>
</os>
<features>
<acpi/>
<apic/>
</features>
<cpu mode='host-model' check='partial'>
<model fallback='forbid'>power9</model>
<topology sockets='2' cores='8' threads='2'/>
<numa>
<cell id='0' cpus='0-7' memory='3145728' unit='KiB'/>
<cell id='1' cpus='8-15' memory='3145728' unit='KiB'/>
</numa>
</cpu>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>coredump-restart</on_crash>
<devices>
<emulator>/usr/bin/qemu-system-ppc64</emulator>
<disk type='block' device='disk'>
<driver name='qemu' type='raw'/>
<source
dev='/dev/disk/by-id/wwn-0x600507680183050d28000000000002a4-part1'/>
<target dev='sda' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x05'
function='0x0'/>
</disk>
<disk type='block' device='disk'>
<driver name='qemu' type='raw'/>
<source dev='wwn-0x600507680183050d28000000000002a4-part2'/>
<target dev='sdb' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06'
function='0x0'/>
</disk>
<disk type='block' device='disk'>
<driver name='qemu' type='raw'/>
<source dev='wwn-0x600507680183050d28000000000002a4-part3'/>
<target dev='sdc' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07'
function='0x0'/>
</disk>
<controller type='scsi' index='0' model='virtio-scsi'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x02'
function='0x0'/>
</controller>
<controller type='usb' index='0' model='qemu-xhci'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x03'
function='0x0'/>
</controller>
<controller type='pci' index='0' model='pci-root'>
<model name='spapr-pci-host-bridge'/>
<target index='0'/>
</controller>
<controller type='pci' index='1' model='pci-root'>
<model name='spapr-pci-host-bridge'/>
<target index='1'/>
</controller>
<interface type='direct'>
<mac address='52:54:00:e5:81:1f'/>
<source dev='enP2p1s0f0' mode='bridge'/>
<model type='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x01'
function='0x0'/>
</interface>
<serial type='pty'>
<target port='0'/>
<address type='spapr-vio' reg='0x30000000'/>
</serial>
<console type='pty'>
<target type='serial' port='0'/>
<address type='spapr-vio' reg='0x30000000'/>
</console>
<memballoon model='virtio'>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04'
function='0x0'/>
</memballoon>
<panic model='pseries'/>
</devices>
</domain>
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1742892/+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
