Bug 544729 - When cloning, network iface doesn't start
Summary: When cloning, network iface doesn't start
Keywords:
Status: CLOSED DUPLICATE of bug 524269
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-06 08:14 UTC by Renich Bon Ciric
Modified: 2010-02-27 00:22 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-02-27 00:22:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Renich Bon Ciric 2009-12-06 08:14:38 UTC
Description of problem:
When you clone a f12 img (minimal install), your eth0 wont start.

Version-Release number of selected component (if applicable):
virt-manager-0.8.0-7.fc12.noarch

How reproducible:
Install a fedora 12 minimal installation. Run it and verify it works. Try cloning it and run the other one. Try turning eth0 on and watch it fail.

Steps to Reproduce:
1. Do a f12 virtual installation
2. Clone it
3. Try starting the eth0
  
Actual results:
The interface fails to connect

Expected results:
It should connect

Additional info:
I think I know what the problem is. When cloning, the interface's mack address get's updated. So, in /etc/udev/rules.d/70-persistent-net.rules you have eth0 registered with the old mac address.

The "clone" function should update this mac address to the new one (or regenerate this file).

I hope this helps.

Comment 1 Paul Jenner 2010-01-18 22:27:18 UTC
Is this effectively a duplicate of bug #524269 ?

Comment 2 Renich Bon Ciric 2010-01-27 01:21:30 UTC
yes, definitelly... but not limited to that only... Maybe there're more things to do in order for the interface to appear correctly as eth1 and with it's new mac address...

Comment 3 Cole Robinson 2010-02-27 00:22:42 UTC
Duping to 524269, we can discuss extra steps there.

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


Note You need to log in before you can comment on or make changes to this bug.