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.
Description of problem:
sound device model listed in virt-manager user-mode GUI should keep consistent with root mode
Version-Release number of selected component (if applicable):
libvirt-1.2.17-3.el7.x86_64
libvirt-python-1.2.17-2.el7.x86_64
virt-manager-1.2.1-4.el7.noarch
How reproducible:
100%
Steps to Reproduce:
1. Login in host with non-root user, then launch virt-manager in user mode:
$ virt-manager -c qemu:///session
2. Add a local "QEMU/KVM" connection: Click File-->Add Connection-->Hyperviso choose "QEMU/KVM", others as default, click "Connect".
After input root password, connection added.
3. Prepare some guest installed in User mode and Root mode:
eg: Guest in user mode called: rhel6.7-released
Guest in root mode called: ovmf
4. Change sound device model or add a new sound to guest.
Actual results:
After step4: in user mode, sound model list is: ac97, es1370, ich6, ich9, pcspk, sb16
but in root modeļ¼ sound model list is: ac97, ich6, ich9
Expected results:
sound device model listed in virt-manager user-mode GUI should keep consistent with root-mode
Additional info:
Closing as duplicate, the bug doesn't seems to be relevant, but the root cause is the same.
*** This bug has been marked as a duplicate of bug 1258691 ***
Description of problem: sound device model listed in virt-manager user-mode GUI should keep consistent with root mode Version-Release number of selected component (if applicable): libvirt-1.2.17-3.el7.x86_64 libvirt-python-1.2.17-2.el7.x86_64 virt-manager-1.2.1-4.el7.noarch How reproducible: 100% Steps to Reproduce: 1. Login in host with non-root user, then launch virt-manager in user mode: $ virt-manager -c qemu:///session 2. Add a local "QEMU/KVM" connection: Click File-->Add Connection-->Hyperviso choose "QEMU/KVM", others as default, click "Connect". After input root password, connection added. 3. Prepare some guest installed in User mode and Root mode: eg: Guest in user mode called: rhel6.7-released Guest in root mode called: ovmf 4. Change sound device model or add a new sound to guest. Actual results: After step4: in user mode, sound model list is: ac97, es1370, ich6, ich9, pcspk, sb16 but in root modeļ¼ sound model list is: ac97, ich6, ich9 Expected results: sound device model listed in virt-manager user-mode GUI should keep consistent with root-mode Additional info: