Bug 1059665

Summary: virt-manager/KVM does not work with new Kernel 4.13.1-1
Product: [openSUSE] openSUSE Tumbleweed Reporter: Joaquín Rivera <jeriveramoya>
Component: BasesystemAssignee: Charles Arnold <carnold>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: jeriveramoya, jfehlig
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Joaquín Rivera 2017-09-21 06:57:31 UTC
virt-manager/KVM does not work with new Kernel 4.13.1-1. I came back to 4.12 and I could verify with KVM that started to work again.

libvirt package version is 3.6.0-2.1
qemu-kvm package version is 2.10.0-1.2
virt-manager version is 1.4.2-2.1 

virt-manager logs:

Error starting domain: internal error: child reported: Kernel does not provide mount namespace: Permission denied


> Traceback (most recent call last):
>  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
>    callback(asyncjob, *args, **kwargs)
>  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
>    callback(*args, **kwargs)
>  File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 82, in newfn
>    ret = fn(self, *args, **kwargs)
>  File "/usr/share/virt-manager/virtManager/domain.py", line 1489, in startup
>    self._backend.create()
>  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1062, in create
>    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
> libvirtError: internal error: child reported: Kernel does not provide mount namespace: Permission denied
Comment 1 Charles Arnold 2017-09-21 17:19:09 UTC
Libvirt is returning this error to virt-manager.

Could you try this command as root?

systemctl stop apparmor.service

then try virt-manager again and see if it works.
Comment 2 James Fehlig 2017-09-21 18:03:59 UTC
Duplicate of bug#1058847. A permanent solution is being hashed out upstream. In the meantime I've submitted a temporary fix to Factory.

*** This bug has been marked as a duplicate of bug 1058847 ***