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.
Bug 595313 - libvirtError: internal error Process exited while reading console log output: char device redirected to /dev/pts/0
Summary: libvirtError: internal error Process exited while reading console log output:...
Keywords:
Status: CLOSED DUPLICATE of bug 593909
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.0
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Daniel Veillard
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 582286
TreeView+ depends on / blocked
 
Reported: 2010-05-24 10:59 UTC by Alexander Todorov
Modified: 2010-05-24 11:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-24 11:20:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Alexander Todorov 2010-05-24 10:59:10 UTC
Description of problem:
On fresh RHEL6 (snap #5) installation I get a traceback when trying to create a new guest:

qemu: could not open disk image /var/lib/libvirt/images/srvd1.img: Invalid argument
' : Unable to complete install '<class 'libvirt.libvirtError'> internal error Process exited while reading console log output: char device redirected to /dev/pts/0
qemu: could not open disk image /var/lib/libvirt/images/srvd1.img: Invalid argument

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/create.py", line 1559, in do_install
    dom = guest.start_install(False, meter = meter)
  File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 972, in start_install
    return self._do_install(consolecb, meter, removeOld, wait)
  File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 1037, in _do_install
    "install")
  File "/usr/lib/python2.6/site-packages/virtinst/Guest.py", line 1008, in _create_guest
    dom = self.conn.createLinux(start_xml, 0)
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 1262, in createLinux
    if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
libvirtError: internal error Process exited while reading console log output: char device redirected to /dev/pts/0
qemu: could not open disk image /var/lib/libvirt/images/srvd1.img: Invalid argument

'

I have SELinux in permissive mode.

Version-Release number of selected component (if applicable):
libvirt-0.8.1-6.el6.x86_64
virt-manager-0.8.4-3.el6.noarch


How reproducible:
always


Steps to Reproduce:
1. Create new guest with virt-manager using default settings.
2.
3.
  
Actual results:
Traceback

Expected results:
new guest is created

Additional info:

Comment 1 Daniel Berrangé 2010-05-24 11:20:29 UTC
This is a KVM bug 593909

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


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