RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
qemu can't create ptys

Version-Release number of selected component (if applicable):
libvirt-3.0.0-2.el7.aarch64
kernel-4.10.0-1.el7.aarch64
qemu-kvm-rhev-2.8.0-5.el7.aarch64

How reproducible:
100%

Steps to Reproduce:
1. create guets with serial console (<serial type='pty'/>).
2. try boot it.

Actual results:
kraxel@seattle ~# virsh start arm-b64
error: Failed to start domain arm-b64
error: internal error: qemu unexpectedly closed the monitor:  -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-4-arm-b64/org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device virtio-balloon-pci,id=balloon0,bus=pci.3,multifunction=on,addr=0x0.0x1 -msg timestamp=on
2017-03-01T09:45:13.095390Z qemu-kvm: -serial pty: Failed to create PTY: No such file or directory
2017-03-01T09:45:13.095640Z qemu-kvm: -serial pty: could not connect serial device to character backend 'pty'

Expected results:
guest boots.

Additional info:

Created attachment 1258622 [details]
guest config

Try editing /etc/libvirt/qemu.conf and set

 namespaces = []

and then restart libvirtd

If that fixes it, then hopefully the forthcoming 3.1.0 will provide the real fix.

> Try editing /etc/libvirt/qemu.conf and set
> 
>  namespaces = []
> 
> and then restart libvirtd

Works.

Looks similar to bug 1421036...

Gerd,

this is libvirt-3.1.0-rc2:

https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=12657547

It contains fixes for bug 1421036. Does it solve your problem?

(In reply to Michal Privoznik from comment #6)
> Gerd,
> 
> this is libvirt-3.1.0-rc2:
> 
> https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=12657547
> 
> It contains fixes for bug 1421036. Does it solve your problem?

Running libvirt-3.1.0-1.el7.aarch64 now, issue is fixed.

*** This bug has been marked as a duplicate of bug 1421036 ***