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 1027576 - The MAC address of cloned guest should be the same as customized from virt-manager
Summary: The MAC address of cloned guest should be the same as customized from virt-ma...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-manager
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Giuseppe Scrivano
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1113520
TreeView+ depends on / blocked
 
Reported: 2013-11-07 06:47 UTC by tingting zheng
Modified: 2015-03-05 10:03 UTC (History)
4 users (show)

Fixed In Version: virt-manager-1.1.0-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 10:03:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Debug info from virt-manager (22.04 KB, text/plain)
2013-11-07 06:47 UTC, tingting zheng 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0427 0 normal SHIPPED_LIVE virt-manager bug fix and enhancement update 2015-03-05 14:38:46 UTC

Description tingting zheng 2013-11-07 06:47:16 UTC 
Created attachment 820892 [details]
Debug info from virt-manager

Description
The MAC address of cloned guest should be the same as customized from virt-manager,also no error shows when set the same address as another guest

Version:
virt-manager-0.10.0-5.el7.noarch
libvirt-1.1.1-11.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Launch virt-manager,prepare a guest with shutdown status.
2. Right click the guest,click "clone","Clone virtual machine" dialog pop out.
3. On the dialog,from "Networking",click "Details",a new dialog "Change MAC address" pop out.
4. Input a new MAC address or just keep the original default MAC address,click "OK".
5. Click "clone".
6. After clone is finished,check the MAC address of the new cloned guest,it's not the same as you set in step 4.
7. If set the new MAC address as the same address of original guest,no error occurs,while create a new guest from virt-manager,set the fixed MAC address as one which has been used by other guests,error will pop out:
"Mac address collision":"The MAC address '*******' is in use by another virtual machine."

Actual results：
As description.

Expected results:
The MAC address of cloned guest should be the same as customized from virt-manager and error shows when set the same address as another guest

Additional info:
1.From virt-manager debug info,the newly set MAC address appeared in Clone guest xml,however,it set an random MAC address when create the new cloned guest.
Attached the debug info,my customized MAC address is "52:54:00:ce:20:00".

2.The issue can not be reproduced on rhel 6 system.

3.MAC address can be set successfully from virt-clone command.
# virt-clone -o test -n newtest --mac=54:52:00:ccd:aa -f /var/lib/libvirt/images/testtest.img
Allocating 'testtest.img'                                                                  | 1.0 GB  00:00:00    
Clone 'newtest' created successfully.
Comment 2 Giuseppe Scrivano 2014-07-21 15:27:11 UTC 
patch sent upstream:

https://www.redhat.com/archives/virt-tools-list/2014-July/msg00077.html
Comment 3 Giuseppe Scrivano 2014-07-29 08:40:58 UTC 
commit 148576d69eac2fd06ebbb5c573df3f341d327234
Author: Giuseppe Scrivano <gscrivan>
Date:   Mon Jul 21 13:54:38 2014 +0200

    virtinst, clone: use the specified MAC address for the new VM
    
    Prevent setup_clone from changing the self._clone_macs list so that
    further calls will access the same data.
    
    Closes: https://bugzilla.redhat.com/show_bug.cgi?id=1027576
    
    Signed-off-by: Giuseppe Scrivano <gscrivan>
Comment 5 tingting zheng 2014-09-11 07:32:48 UTC 
Tested pass with:
virt-manager-1.1.0-1.el7.noarch

Steps:
1. Launch virt-manager,prepare a guest with shutdown status.
2. Right click the guest,click "clone","Clone virtual machine" dialog pop out.
3. On the dialog,from "Networking",click "Details",a new dialog "Change MAC address" pop out.
4. Input a new MAC address or just keep the original default MAC address,click "OK".
5. Click "clone".
6. After clone is finished,check the MAC address of the new cloned guest,it's 
 the same as set in step 4.
7. If set the new MAC address as the same address of original guest,error will show as:Error changing MAC address: The MAC address '52:54:00:0b:aa:bb' is in use by another virtual machine.

Refer to the above comments,move the bug to VERIFIED.
Comment 7 errata-xmlrpc 2015-03-05 10:03:02 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.

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