Thanks for the update, it is able to run OpenBSD guest with VirtIO network interface without crash now.
Thanks for the update, it is able to run OpenBSD guest with VirtIO network interface without crash now.
It doesn't fix #1443250. Running import dlib
in python3 still fails with undefined symbol error.
$ python3
Python 3.6.1 (default, May 9 2017, 15:52:14)
[GCC 7.1.1 20170503 (Red Hat 7.1.1-1)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import dlib
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib64/python3.6/site-packages/dlib/__init__.py", line 1, in <module>
from .dlib import *
ImportError: /usr/lib64/python3.6/site-packages/dlib/dlib.so: undefined symbol: _ZN5boost6python6detail11init_moduleER11PyModuleDefPFvvE
dlib/add_python_module
in dlib 18.18 only checks for python-py34
, so it cannot find the name python3
used by Fedora. Either replacing python-py34
with python3
, or updating dlib to 19.4 (the version used by rawhide), can fix the problem.
I cannot start virtual machines after installing this update.
$ virsh -c qemu:///system start <vm>
error: Failed to start domain <vm>
error: SELinux policy denies access.
Systemd journal:
audit: USER_AVC pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='avc: denied { start } for auid=n/a uid=0 gid=0 cmdline="/usr/lib/systemd/systemd-machined" scontext=system_u:system_r:systemd_machined_t:s0 tcontext=system_u:system_r:init_t:s0 tclass=system exe="/usr/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'
systemd-machined: Failed to start machine scope: Access denied
libvirtd: SELinux policy denies access.
selinux-policy-3.13.1-191.10.fc24 doesn't have this problem.
It works without crash now.
Permission problem in makepkg is fixed.
I have used the patch for one month, and I didn't find any problem. Packages in testing seems to work fine.
VNC works now.
I think it is nice to get this update, but #1245477 still happens when fprintd.service crashes.
xen-qemu-dom0-disk-backend.service works fine now.
xen-qemu-dom0-disk-backend.service is broken: ExecStart=@BINDIR@/qemu-system-i386 -xen-domid 0
It seems that we have to wait for the xorg-x11-drv-vmmouse update. kernel-core-4.0.4-303.fc22.x86_64 conflicts xorg-x11-drv-vmmouse < 13.0.99
CPU usage issue fixed
ImportError problem fixed
glibmm and gtkmm build problems are fixed.
Kernel panic problem is fixed when running as Xen dom0.
Kernel panic when running as Xen dom0 on Asus B23E laptop. 3.18.3 also has this problem. 3.17.x works fine. Log: http://www.csie.ntu.edu.tw/~lantw44/logs/linux-3.18.4-crash-dmesg
Can this update be pushed to stable? It has stayed in testing for more than one week.
nft works fine.
It seems to work without problem.