Created attachment 448251 [details] selinux errors related to this report. Description of problem: When trying to add a SDL Virtual Display to a Virtual Machine using virt-manager, I get the following error: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 878, in run_domain vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 1321, in startup self._backend.create() File "/usr/lib64/python2.6/site-packages/libvirt.py", line 333, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: operation failed: failed to retrieve chardev info in qemu with 'info chardev' If I turn off selinux, it works fine. This error is based on this article: http://linuxgazette.net/178/silva.html - I understand selinux is not recommended to be turned off, but to get this working that was the only way I was able to getting working. Version-Release number of selected component (if applicable): It has been like this with all version of 'yum groupinstall Virtualization' at least on Fedora 13. How reproducible: Error happens every time. It goes away when I turn off selinux. I have attached the audit.log w/ the qemu-kvm errors. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I have selinux disabled, and I'm still getting this error. As far as I can tell, my traceback is identical to Anderson's except that I'm using Fedora 14: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 878, in run_domain vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 1321, in startup self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 333, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: operation failed: failed to retrieve chardev info in qemu with 'info chardev' This problem makes it impossible to start a virtual machine.
Anderson, FYI a couple of your questions in that posting are answered here: http://fedoraproject.org/wiki/Virtualization_tips#Known_issues There is also a bug open tracking libvirt, SDL, and selinux issues: https://bugzilla.redhat.com/show_bug.cgi?id=609279 Andrew, can you provide: /var/log/libvirt/qemu/$vmname.log virsh dumpxml $vmname Does tail -f /var/log/audit.log show anything when you try to start the guest?
Created attachment 462801 [details] /var/log/libvirt/qemu/XP-vpn.log I've attached the log file from attempting to start my VM. Here's the associated backtrace: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 878, in run_domain vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 1321, in startup self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 333, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error Process exited while reading console log output: char device redirected to /dev/pts/1 No protocol specified No protocol specified Could not initialize SDL(No available video device) - exiting
Created attachment 462802 [details] virsh dumpxml XP-vpn Attached virsh dumpxml output.
(In reply to comment #2) > Andrew, can you provide: > > /var/log/libvirt/qemu/$vmname.log > virsh dumpxml $vmname I did this, since I have the same problem as Andrew - see comment #3 and comment #4 above. > Does tail -f /var/log/audit.log show anything when you try to start the guest? No.
FYI, I was able to work around this by editing qemu.conf to run as user myself, group myself. It seems to be a pty permission issue.
Created attachment 490342 [details] testvm.log I know others have posted their logs, but here's mine, too.
Created attachment 490343 [details] testvm.dumpxml
(In reply to comment #2) > Does tail -f /var/log/audit.log show anything when you try to start the guest? I am running with SELinux disabled.
(In reply to comment #6) > FYI, I was able to work around this by editing qemu.conf to run as user myself, > group myself. It seems to be a pty permission issue. For what it's worth, my qemu.conf has these set to user = "root" and group = "root".
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
F14 is EOL, please reopen if this is still relevant in a more recent fedora.