Bug 525581
Summary: | SELinux prevented pt_chown from using the terminal 1. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Guy Streeter <streeter> |
Component: | qemu | Assignee: | Glauber Costa <gcosta> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 11 | CC: | berrange, dwmw2, gcosta, itamar, jaswinder, jforbes, markmc, nobody, patmans, quintela, virt-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-10-01 16:30:54 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Guy Streeter
2009-09-24 21:49:28 UTC
using the recommended setsebool -P allow_daemons_use_tty=1 doesn't help. I still get the selinux violation and am unable to start a new vm. Unable to complete install '<class 'libvirt.libvirtError'> internal error unable to start guest: qemu: could not open monitor device 'pty' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/create.py", line 1501, in do_install dom = guest.start_install(False, meter = meter) File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 541, in start_install return self._do_install(consolecb, meter, removeOld, wait) File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 633, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 974, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: internal error unable to start guest: qemu: could not open monitor device 'pty' (In reply to comment #1) > using the recommended > > setsebool -P allow_daemons_use_tty=1 > > doesn't help. I still get the selinux violation and am unable to start a new > vm. I had a similar problem just now, it was working yesterday. I rebooted today, and tried to run an existing vm, it failed with the could not open pty, and a selinux alert. I checked, and allow_daemons_use_tty was on: [root@palm ~]# getsebool allow_daemons_use_tty allow_daemons_use_tty --> on I "set" it again: [root@palm ~]# setsebool -P allow_daemons_use_tty=1 [root@palm ~]# getsebool allow_daemons_use_tty allow_daemons_use_tty --> on And then when I ran the VM it started up *but* I might have still gotten another selinux alert for the pty - I can't tell since I had multiple alerts, and don't know if there are any VM logs that show the time I "ran" the instance. Raising the severity on this as I am unable to use Virtual Machine Manager at all because of it. Marking as a duplicate of bug #515521 I think you just need selinux-policy-3.6.12-82.fc11 and the /dev/pts line in /etc/fstab fixed to look like: devpts /dev/pts devpts gid=5,mode=620 0 0 *** This bug has been marked as a duplicate of bug 515521 *** |