Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Descriptionhyao@redhat.com
2013-05-06 08:00:02 UTC
Description of problem:
Failed to start gust after adding sound device es1370 or changing sound device mode to es1370.
Version-Release number of selected component (if applicable):
libvirt-1.0.5-1.el7.x86_64
virt-manager-0.10.0-0.1.gitd3f9bc8e.el7.noarch
How reproducible:
100%
Steps to Reproduce:
1. A guest without sound device is available.
2. Hardware details is open and add a Sound device via Add Hardware->Sound-> Model:es1370-> Finish.
3. The sound device is added and start the guest by click "Power on the virtual machine" button.
Actual results:
Failed to start gust after adding sound device es1370 with the following error:
Error starting donain: Unable to read from monitor: Connection reset by peer.
Check the log from: virt-manager.log rhel6.log.
Expected results:
Start guest without any error.
Additional info
Also can't start a guest with sound device after changing the sound device mode to es1370.
Trackback after adding es1370 device and starting the guest:
2013-05-06 16:18:34,165 (engine:880): Starting vm 'rhel6'
2013-05-06 16:18:34,169 (asyncjob:193): Creating async job for function cb=<function tmpcb at 0x2fc90c8>
2013-05-06 16:18:34,773 (error:78): dialog message: Error starting domain: Unable to read from monitor: Connection reset by peer : Error starting domain: Unable to read from monitor: Connection reset by peer
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 101, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 123, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1174, in startup
self._backend.create()
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 692, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: Unable to read from monitor: Connection reset by peer
Comment 8Martin Kletzander
2013-06-12 09:18:28 UTC
Moving to POST:
commit 1ca9d6ebd2195ebc9e495c2cae5be28aa11c62a8
Author: Martin Kletzander <mkletzan>
Date: Wed Jun 12 10:49:30 2013 +0200
Update supported models (bz 959888)
I've checked this bug on virt-manager-0.10.0-1.el7.noarch, es1370 model option for the sound device is removed from virt-manager. This bug could be verified
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.