Red Hat Bugzilla – Bug 516120
unable to start guest: qemu: could not open serial device 'pty'
Last modified: 2009-09-04 03:51:04 EDT
selinux is permissive.
create a new vm in virt-manager
set the install to an iso
do not create storage
try to start the vm
Error starting domain: internal error unable to start guest: qemu: could not open serial device 'pty
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 567, in run_domain
File "/usr/share/virt-manager/virtManager/domain.py", line 652, in startup
File "/usr/lib64/python2.6/site-packages/libvirt.py", line 293, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error unable to start guest: qemu: could not open serial device 'pty'
Could you include ~/.virt-manager/virt-manager.log and /var/log/libvirt/qemu/$guest.log ?
Hmm, this sounds similar to bug #511179
Created attachment 357068 [details]
Created attachment 357069 [details]
Side note, since virt-manager is unusable as a non-root user this is done by logging into X as a normal user and using sudo -s to get root. (I don't know if that is in any way relevant)
I am running on Fedora 11 with the "preview" set which includes libvirt-0.7.0-3.fc11 (BTW< shouldn't that be "f11" rather than "fc11") an qemu-kvm.
I sure hope someone is working on the fix for this problem!
Right now I cannot run any linux virtual machine or define one. Even if I manually edit the guest xml file to add the pts definitions. Both virt-manager AND virsh start do not work ... both get the same error.
Okay, this is openpty() in qemu-kvm process failing
You say selinux is permissive, so it's not #515521
The qemu-kvm process is now running as the qemu user. What permissions does /dev/pts have?
I too am experiencing this bug. I try to start any of the three VMs I have and I get:
libvirtError: internal error unable to start guest: qemu: could not open monitor device 'pty'
I assume this is related to the recent qemu updates in Fedora 11?
I have tried running as a regular user and being prompted for the root password and running it directly as root... and I still get the same error.
Scott: could you try reverting to 0.10.5-3 and see if that helps:
if not, it rules out 0.10.6 as the cause
Also, what permissions are on your /dev/ptmx
They should be:
$> ls -l /dev/ptmx
crw-rw-rw-. 1 root tty 5, 2 2009-08-21 10:12 /dev/ptmx
$> ls -lZ /dev/ptmx
crw-rw-rw-. root tty system_u:object_r:ptmx_t:s0 /dev/ptmx
Eric had different permissions and was going to try correcting them to see if that helps
With 'fixed' perms and ownership like you show in comment #9 I am thus far unable to reproduce this problem.
I was unable to view that koji page for some reason. I accepted the cert but then got an SSL nego. error. In any event I saw fix that one of the SELinux guys came up with in a related bug report that involved changing how devpts is mounted (which is probably what that koji page documents?) and that worked for me.
Okay, closing this then
If anyone knows how /dev/ptmx or /dev/pts came to have incorrect permissions, please let us know