Public bug reported:

== Comment: #0 - Satheesh Rajendran <[email protected]> - 2018-02-17 11:44:57 
==
---Problem Description---
virsh domcapabilities fails with "unable to find any emulator to serve 
'ppc64le' architecture", and libvirt unable to define/start a guest with error 
"could not find capabilities for arch=ppc64le ",
and virt-install complains as host does not have virtualisation support looks 
like the root cause of all these errors are same.

Host is able to boot the kvm guest from qemu fine.

#/usr/bin/kvm -M pseries -nographic -serial /dev/pts/0 -monitor stdio 
/home/sath/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2
 -device virtio-scsi-pci -m 5120 -smp 1 -vga none
(qemu) info status
VM status: running
(qemu) info kvm
kvm support: enabled
(qemu) info cpus
* CPU #0: nip=0x000000000dbe4acc thread_id=12917
(qemu) 


Env:
4.15.0-10-generic
ii  qemu-kvm                               1:2.11+dfsg-1ubuntu1                 
ppc64el      QEMU Full virtualization on x86 hardware
ii  libvirt-bin                            4.0.0-1ubuntu2                       
ppc64el      programs for the libvirt library

# lsmod|grep kvm
kvm_hv                132653  1
kvm                   223734  4 kvm_hv


Contact Information = [email protected] 
 
---uname output---
Linux ltc-boston8 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:21:52 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = power9 
 
---Steps to Reproduce---
 virsh domcapabilities
error: failed to get emulator capabilities
error: invalid argument: unable to find any emulator to serve 'ppc64le' 
architecture ----------------NOK

2. # virsh domcapabilities --emulatorbin /usr/bin/qemu-system-ppc64
error: failed to get emulator capabilities
error: internal error: QEMU / QMP failed: qemu-system-ppc64: could not acquire 
pid file: Permission denied      --------------------NOK

3.# virsh define vm1
error: Failed to define domain from vm1
error: invalid argument: could not find capabilities for arch=ppc64le 
---------------NOK


# cat vm1 
<domain type='kvm'>
  <name>vm1</name>
  <memory unit='G'>8</memory>
  <vcpu placement='static'>1</vcpu>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='ppc64le' machine='pseries-bionic'>hvm</type>
    <boot dev='hd'/>
  </os>
  <cpu>
    <topology sockets='1' cores='1' threads='1'/>
  </cpu>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/kvm</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source 
file='/home/sath/avocado-fvt-wrapper/data/avocado-vt/images/ubuntu-18.04-ppc64le.qcow2'/>
      <backingStore/>
      <target dev='sda' bus='scsi'/>
      <alias name='scsi0-0-0-0'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <controller type='scsi' index='0' model='virtio-scsi'>

<alias name='scsi0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 
function='0x0'/>
    </controller>
    <controller type='usb' index='0'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 
function='0x0'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'>
      <alias name='pci.0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:a7:a8:a9'/>
      <source bridge='virbr0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' 
function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
      <alias name='serial0'/>
      <address type='spapr-vio' reg='0x30000000'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
      <address type='spapr-vio' reg='0x30000000'/>
    </console>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' 
function='0x0'/>
    </memballoon>
    <panic model='pseries'/>
  </devices>
  <seclabel type='dynamic' model='apparmor' relabel='yes'>
  </seclabel>
</domain>


4) #/usr/bin/virt-install --connect=qemu:///system --hvm
ERROR    Host does not support virtualization type 'hvm' -----------NOK
 
Userspace tool common name: ii  libvirt-bin                            
4.0.0-1ubuntu2                       ppc64el      programs for the libvirt 
library 
 
The userspace tool has the following bit modes: both 

Userspace rpm: ii  libvirt-bin                            4.0.0-1ubuntu2
ppc64el      programs for the libvirt library

Userspace tool obtained from project website:  na 
 
*Additional Instructions for [email protected]: 
-Post a private note with access information to the machine that the bug is 
occuring on.
-Attach ltrace and strace of userspace application.

== Comment: #3 - Shivaprasad G. Bhat <[email protected]> - 2018-02-20 
00:44:49 ==
This is some apparmor issue. 

The qemu is not able to access /var/lib/libvirt  directory when run as
qemu:qemu.

I changed the user  to root:root, the things are working fine now.

Want this to be mirrored to Canonical to figure out more on why the
issue with non-root user.

Thanks,
Shiva

== Comment: #6 - SRIKANTH AITHAL <[email protected]> - 2018-02-20 02:19:49 
==
(In reply to comment #3)
> This is some apparmor issue. 
> 
> The qemu is not able to access /var/lib/libvirt  directory when run as
> qemu:qemu. 
> 
> I changed the user  to root:root, the things are working fine now. 
> 
> Want this to be mirrored to Canonical to figure out more on why the issue
> with non-root user.
> 
> Thanks,
> Shiva

Can we have this mirrored to Canonical please?
Since we have workaround I am reducing severity to ship, still this issue 
should be resolved noting that customers would prefer using non-root users.

** Affects: libvirt (Ubuntu)
     Importance: Undecided
     Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
         Status: New


** Tags: architecture-ppc64le bugnameltc-164807 severity-critical 
targetmilestone-inin---

** Tags added: architecture-ppc64le bugnameltc-164807 severity-critical
targetmilestone-inin---

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750543

Title:
  [power9][Ubuntu 18.04][4.15.0-10-generic][libvirt-bin-4.0.0-1ubuntu2]
  KVM guest unable start from libvirt "could not find capabilities for
  arch=ppc64le " (kvm)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1750543/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to