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 907399 - Error occurs after change selinux from static to dynamic on virt-manager
Summary: Error occurs after change selinux from static to dynamic on virt-manager
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Martin Kletzander
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-04 09:48 UTC by tingting zheng
Modified: 2013-11-21 20:38 UTC (History)
7 users (show)

Fixed In Version: virt-manager-0.9.0-19.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 907390
Environment:
Last Closed: 2013-11-21 20:38:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1646 0 normal SHIPPED_LIVE virt-manager bug fix update 2013-11-20 21:53:27 UTC

Comment 1 Martin Kletzander 2013-02-05 13:11:22 UTC 
Patch proposed upstream:

https://www.redhat.com/archives/virt-tools-list/2013-February/msg00028.html
Comment 2 Martin Kletzander 2013-07-16 08:38:14 UTC 
Fixed upstream with:

commit b6f0ba364f6376793989450869db83e117586cec
Author: Martin Kletzander <mkletzan>
Date:   Tue Feb 5 12:28:06 2013 +0100

    Add support for security relabeling
Comment 5 luxin 2013-08-02 09:56:40 UTC 
I can reproduce this bug:

Version:
virt-manager-0.9.0-18.el6.x86_64
libvirt-0.10.2-18.el6_4.9.x86_64

Steps for Reproduce:
1. Prepare an VM which is not running.
2. Issue "virt-manager" to open virt-manager.
3. Select the existing VM, then "open" -> "details" -> "Overview" -> "Security"
4. Select "static" option, then specify a label,and apply it.
such as: "system_u:system_r:svirt_t:s0:c100,c200"
5. Change selinux to dynamic,then apply

Result:
Error occurs after change selinux from static to dynamic from virt-manager: Error changing VM configuration: unsupported configuration: dynamic label type must use resource relabeling

Verify:
libvirt-0.10.2-21.el6.x86_64
virt-manager-0.9.0-19.el6.x86_64

Steps for Verify:
1. Prepare an VM which is not running.
2. Issue "virt-manager" to open virt-manager.
3. Select the existing VM, then "open" -> "details" -> "Overview" -> "Security"
4. Select "static" option, then specify a label,and apply it.
such as: "system_u:system_r:svirt_t:s0:c100,c200"
5. Change selinux to dynamic,then apply

Result:
No error shows and change selinux from static to dynamic successfully.
Comment 6 errata-xmlrpc 2013-11-21 20:38:47 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1646.html
Note You need to log in before you can comment on or make changes to this bug.