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.

Bug 689372

Summary: More detail message should display for failing to live update keymap in virt-manager
Product: Red Hat Enterprise Linux 6 Reporter: Min Zhan <mzhan>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: medium    
Version: 6.1CC: dyuan, llim, mzhan, vbian
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-10 22:15:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Min Zhan 2011-03-21 09:03:42 UTC
Description of problem:
As described in BZ 672749 comment #1, Keymap hotplug is not supported. But in virt-manager, when guest is running status, keymap dropdown list value can be changed, Click Apply, popup the message:Some changes may require a guest reboot to take effect.

Version-Release number of selected component (if applicable):
virt-manager-0.8.6-3.el6.noarch
# uname -a
Linux dhcp-65-85.nay.redhat.com 2.6.32-120.el6.x86_64 #1 SMP Mon Mar 7 11:59:40 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
qemu-kvm-0.12.1.2-2.150.el6.x86_64
libvirt-0.8.7-13.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Make sure a guest is in running status
2. Click vm detail page, Change keymap value, Click Apply
  
Actual results:
Pop up message: Some changes may require a guest reboot to take effect.

Expected results:
If the keymap is not allowed to hotplug, please greyout this option for running guest or show a little 'details' expander if the hotplug fails so the user can see an error message though.

Additional info:

Comment 1 RHEL Program Management 2011-04-04 02:01:38 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 2 Cole Robinson 2011-04-07 17:09:42 UTC
*** Bug 672749 has been marked as a duplicate of this bug. ***

Comment 3 Cole Robinson 2011-04-07 17:10:15 UTC
Deferring to 6.2

Comment 4 Cole Robinson 2011-06-10 22:15:48 UTC
There's another bug already tracking this, duping to that one.

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