Bug 635328 - error starting SDL guest w/o selinux: failed to retrieve chardev info in qemu with 'info chardev'
Summary: error starting SDL guest w/o selinux: failed to retrieve chardev info in qemu...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 14
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-19 02:29 UTC by Anderson Silva
Modified: 2012-01-24 21:50 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-24 21:50:54 UTC


Attachments (Terms of Use)
selinux errors related to this report. (41.11 KB, application/octet-stream)
2010-09-19 02:29 UTC, Anderson Silva
no flags Details
/var/log/libvirt/qemu/XP-vpn.log (1.15 KB, text/plain)
2010-11-25 03:48 UTC, Bryan O'Sullivan
no flags Details
virsh dumpxml XP-vpn (2.01 KB, application/xml)
2010-11-25 03:50 UTC, Bryan O'Sullivan
no flags Details
testvm.log (30.42 KB, text/plain)
2011-04-06 17:06 UTC, Andrew McNabb
no flags Details
testvm.dumpxml (1.75 KB, text/plain)
2011-04-06 17:06 UTC, Andrew McNabb
no flags Details

Description Anderson Silva 2010-09-19 02:29:49 UTC
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:

Comment 1 Andrew McNabb 2010-11-04 20:10:32 UTC
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.

Comment 2 Cole Robinson 2010-11-17 23:37:33 UTC
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?

Comment 3 Bryan O'Sullivan 2010-11-25 03:48:35 UTC
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

Comment 4 Bryan O'Sullivan 2010-11-25 03:50:35 UTC
Created attachment 462802 [details]
virsh dumpxml XP-vpn

Attached virsh dumpxml output.

Comment 5 Bryan O'Sullivan 2010-11-25 03:52:01 UTC
(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.

Comment 6 Bryan O'Sullivan 2010-11-25 03:58:41 UTC
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.

Comment 7 Andrew McNabb 2011-04-06 17:06:04 UTC
Created attachment 490342 [details]
testvm.log

I know others have posted their logs, but here's mine, too.

Comment 8 Andrew McNabb 2011-04-06 17:06:28 UTC
Created attachment 490343 [details]
testvm.dumpxml

Comment 9 Andrew McNabb 2011-04-06 17:07:07 UTC
(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.

Comment 10 Andrew McNabb 2011-04-06 17:09:13 UTC
(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".

Comment 11 Fedora Admin XMLRPC Client 2011-09-22 17:58:59 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 12 Fedora Admin XMLRPC Client 2011-09-22 18:02:46 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 13 Fedora Admin XMLRPC Client 2011-11-30 19:59:00 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 14 Fedora Admin XMLRPC Client 2011-11-30 19:59:50 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 15 Fedora Admin XMLRPC Client 2011-11-30 20:05:09 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 16 Fedora Admin XMLRPC Client 2011-11-30 20:05:23 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 17 Cole Robinson 2012-01-24 21:50:54 UTC
F14 is EOL, please reopen if this is still relevant in a more recent fedora.


Note You need to log in before you can comment on or make changes to this bug.