virt-aa-helper: do not fail with memory slots specified in guest xml
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
The Ubuntu-power-systems project |
Fix Released
|
Critical
|
Canonical Server | ||
libvirt (Ubuntu) |
Fix Released
|
Undecided
|
Ubuntu on IBM Power Systems Bug Triage |
Bug Description
== Comment: #1 - INDIRA P. JOGA <email address hidden> - 2018-01-04 11:57:53 ==
Problem Description:
===================
Not able to start the guest 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
> Defined the guest boslcp3g1 from host machine
root@boslcp3:/home# virsh list --all
Id Name State
-------
- boslcp3g1 shut off
> Started the guest and it fails with ?cannot load AppArmor profile 'libvirt-
root@boslcp3:/home# virsh start --console boslcp3g1
error: Failed to start domain boslcp3g1
error: internal error: cannot load AppArmor profile 'libvirt-
> Not able to start the any of the guests from KVM host machine.
XML:
****
root@boslcp3:/home# virsh dumpxml boslcp3g1
<domain type='kvm'>
<name>
<uuid>
<maxMemory slots='16' unit='KiB'
<memory unit='KiB'
<currentMemory unit='KiB'
<memoryBacking>
<hugepages>
<page size='2048' unit='KiB' nodeset='0'/>
</hugepages>
</memoryBacking>
<vcpu placement='static' current=
<resource>
<partition>
</resource>
<os>
<type arch='ppc64le' machine=
<boot dev='hd'/>
<boot dev='network'/>
<bootmenu enable='yes'/>
</os>
<features>
<acpi/>
<apic/>
</features>
<cpu mode='host-model' check='partial'>
<model fallback=
<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>
<on_reboot>
<on_crash>
<devices>
<emulator>
<disk type='block' device='disk'>
<driver name='qemu' type='raw'/>
<source dev='/dev/
<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-
<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-
<target dev='sdc' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
</disk>
<controller type='scsi' index='0' model='
<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-
<target index='0'/>
</controller>
<controller type='pci' index='1' model='pci-root'>
<model name='spapr-
<target index='1'/>
</controller>
<interface type='direct'>
<mac address=
<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>
== Comment: #3 - INDIRA P. JOGA <email address hidden> - 2018-01-05 00:06:42 ==
This is blocking the test execution.
Regards,
Indira
== Comment: #5 - INDIRA P. JOGA <email address hidden> - 2018-01-05 00:41:19 ==
> Collected 1717970.apport log
root@boslcp3:/tmp# sudo apport-cli -f --save /tmp/1717970.apport -p linux-image-
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.....tar: Removing leading `/' from member names
....tar: Removing leading `/' from member names
tar: Removing leading `/' from member names
tar: /var/log/opal-elog: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors
.......
> root@boslcp3:/tmp# ls -l 1717970.apport
-rw-r--r-- 1 root root 1941570 Jan 4 17:35 1717970.apport
> Attached /tmp/1717970.apport log
Other info:
***********
root@boslcp3:~# sudo grep -Hi uuid /etc/libvirt/
/etc/libvirt/
root@boslcp3:~# ls -l /etc/apparmor.
total 8
-rw-r--r-- 1 root root 314 Oct 24 07:30 TEMPLATE.lxc
-rw-r--r-- 1 root root 164 Oct 24 07:30 TEMPLATE.qemu
== Comment: #6 - INDIRA P. JOGA <email address hidden> - 2018-01-05 00:49:43 ==
== Comment: #10 - Shivaprasad G. Bhat <email address hidden> - 2018-01-05 02:53:44 ==
apparmor-profiles package was missing. Now, the guest is staring. Let me know if there is more to this bug or we can close it
== Comment: #12 - INDIRA P. JOGA <email address hidden> - 2018-01-07 13:35:32 ==
> Reopening the bug as i am still facing issue while starting the other guest boslcp3g2 from boslcp3 host machine as below.
root@boslcp3:~# virsh start --console boslcp3g2
error: Failed to start domain boslcp3g2
error: internal error: cannot load AppArmor profile 'libvirt-
> checked for kern.log
root@boslcp3:~# grep virt /var/log/kern.log
root@boslcp3:~#
> Also checked the apparmor.service which is active
root@boslcp3:~# systemctl status apparmor.service
? apparmor.service - AppArmor initialization
Loaded: loaded (/lib/systemd/
Active: active (exited) since Sun 2018-01-07 01:15:17 CST; 43min ago
Docs: man:apparmor(7)
http://
Process: 6239 ExecReload=
Main PID: 1576 (code=exited, status=0/SUCCESS)
> Also checked for apparmor-profiles packages and it shows
root@boslcp3:~# dpkg --list "apparmor"*
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii apparmor 2.11.0-2ubuntu18 ppc64el user-space parser utility for AppArmor
ii apparmor-profiles 2.11.0-2ubuntu18 all profiles for AppArmor Security policies
un apparmor-
ii apparmor-utils 2.11.0-2ubuntu18 ppc64el utilities for controlling AppArmor
> Unable to start the guest as it fails with cannot load AppArmor profile 'libvirt-
Please let me know if anything else missing to start the guest on KVM host machine
Regards,
Indira
== Comment: #13 - INDIRA P. JOGA <email address hidden> - 2018-01-07 23:19:32 ==
Attaching the boslcp3g2 guest xml below
root@boslcp3:~# virsh dumpxml boslcp3g2
<domain type='kvm'>
<name>
<uuid>
<maxMemory slots='16' unit='KiB'
<memory unit='KiB'
<currentMemory unit='KiB'
<vcpu placement='static' current=
<resource>
<partition>
</resource>
<os>
<type arch='ppc64le' machine=
<boot dev='hd'/>
<boot dev='network'/>
<bootmenu enable='yes'/>
</os>
<features>
<acpi/>
<apic/>
</features>
<cpu mode='host-model' check='partial'>
<model fallback=
<topology sockets='8' cores='4' threads='1'/>
</cpu>
<clock offset='utc'/>
<on_poweroff>
<on_reboot>
<on_crash>
<devices>
<emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2'/>
<source file='/
<target dev='sda' bus='scsi'/>
<address type='drive' controller='0' bus='0' target='0' unit='0'/>
</disk>
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2'/>
<source file='/
<target dev='sdb' bus='scsi'/>
<address type='drive' controller='0' bus='0' target='0' unit='1'/>
</disk>
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2'/>
<source file='/
<target dev='sdc' bus='scsi'/>
<address type='drive' controller='0' bus='0' target='0' unit='2'/>
</disk>
<controller type='scsi' index='0' model='
<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-
<target index='0'/>
</controller>
<controller type='pci' index='1' model='pci-root'>
<model name='spapr-
<target index='1'/>
</controller>
<interface type='direct'>
<mac address=
<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>
>
</domain>
Regards,
Indira
== Comment: #17 - Shivaprasad G. Bhat <email address hidden> - 2018-01-11 04:17:20 ==
Posted patch upstream for review.
https:/
Regards,
Indira
Changed in ubuntu-power-systems: | |
importance: | Undecided → Critical |
assignee: | nobody → Canonical Server Team (canonical-server) |
tags: | added: triage-g |
Changed in libvirt (Ubuntu): | |
status: | New → Triaged |
Changed in ubuntu-power-systems: | |
status: | New → Triaged |
summary: |
- ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Unable to start the guest from - Ubuntu1804 KVM host machine + virt-aa-helper: do not fail with memory slots specified in guest xml |
Changed in ubuntu-power-systems: | |
status: | Triaged → Fix Released |
tags: |
added: targetmilestone-inin1804 removed: targetmilestone-inin--- |
Default Comment by Bridge