Created attachment 1450062 [details] Virtual Manager screenshoot Description of problem: Today after kernel upgrade stop working KVM $ uname -r 4.18.0-0.rc0.git5.1.fc29.x86_64 $ rpm -qa | grep kernel | sort abrt-addon-kerneloops-2.10.10-1.fc29.x86_64 kernel-4.17.0-0.rc7.git2.1.fc29.x86_64 kernel-4.18.0-0.rc0.git2.1.fc29.x86_64 kernel-4.18.0-0.rc0.git5.1.fc29.x86_64 kernel-core-4.17.0-0.rc7.git2.1.fc29.x86_64 kernel-core-4.18.0-0.rc0.git2.1.fc29.x86_64 kernel-core-4.18.0-0.rc0.git5.1.fc29.x86_64 kernel-headers-4.18.0-0.rc0.git5.1.fc29.x86_64 kernel-modules-4.17.0-0.rc7.git2.1.fc29.x86_64 kernel-modules-4.18.0-0.rc0.git2.1.fc29.x86_64 kernel-modules-4.18.0-0.rc0.git5.1.fc29.x86_64 kernel-modules-extra-4.17.0-0.rc7.git2.1.fc29.x86_64 kernel-modules-extra-4.18.0-0.rc0.git2.1.fc29.x86_64 kernel-modules-extra-4.18.0-0.rc0.git5.1.fc29.x86_64 libreport-plugin-kerneloops-2.9.5-1.fc29.x86_64 Error starting domain: internal error: qemu unexpectedly closed the monitor: ioctl(KVM_CREATE_VM) failed: 12 Cannot allocate memory 2018-06-11T14:16:34.716803Z qemu-system-x86_64: failed to initialize KVM: Cannot allocate memory Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 66, in newfn ret = fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1344, in startup self._backend.create() File "/usr/lib64/python3.6/site-packages/libvirt.py", line 1068, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor: ioctl(KVM_CREATE_VM) failed: 12 Cannot allocate memory 2018-06-11T14:16:34.716803Z qemu-system-x86_64: failed to initialize KVM: Cannot allocate memory
a) Can you share kernel logs b) If you boot back into the older kernel does it work?
Created attachment 1450094 [details] dmesg
b) yes with kernel $ uname -r 4.18.0-0.rc0.git2.1.fc29.x86_64 KVM works as expected. But there is good news on kernel 4.18.0-0.rc0.git5.1.fc29.x86_64 hardware acceleration for MP4 via vaapi on AMD GPU start works without hangs. https://bugs.freedesktop.org/show_bug.cgi?id=106430
There was a revert upstream which should fix the issue. Should be in kernel-4.18.0-0.rc0.git6.1.fc29
Sorry that should be kernel-4.18.0-0.rc0.git7.1.fc29
Fix came in from Linus' tree today so I'm going to close this
Laura, can i ask you question? It's normal that after running KVM I saw such locks? # lslocks -u | grep unknown Here I am rinning virtual machine in virtual-manager. # lslocks -u | grep unknown (unknown) -1 OFDLCK READ 0 100 101 /home... (unknown) -1 OFDLCK READ 0 103 103 /home... (unknown) -1 OFDLCK READ 0 201 201 /home... (unknown) -1 OFDLCK READ 0 203 203 /home...