*** This bug is a duplicate of bug 341006 ***
https://bugs.launchpad.net/bugs/341006
** This bug has been marked a duplicate of bug 341006
ease cloning of virtual images by disabling mac address rules
--
Network interfaces names changed in KVM guest cloned with virt-clone
https://bugs.lau
** Changed in: udev (Ubuntu)
Status: Confirmed => Triaged
** Changed in: udev (Ubuntu)
Importance: Undecided => Wishlist
--
Network interfaces names changed in KVM guest cloned with virt-clone
https://bugs.launchpad.net/bugs/345234
You received this bug notification because you are a m
** Package changed: kvm (Ubuntu) => udev (Ubuntu)
--
Network interfaces names changed in KVM guest cloned with virt-clone
https://bugs.launchpad.net/bugs/345234
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I consider this to be a bug, since only Xen devices seem to be taken
care of, but KVM/Qemu devices aren't. A fix for this is mentioned in the
comments.
--
Network interfaces names changed in KVM guest cloned with virt-clone
https://bugs.launchpad.net/bugs/345234
You received this bug notification
I found this thread on the Ubuntu forums that also discusses this
problem (in combination with VMware, but that's beside the point, since
this happens whenever an ubuntu/debian system is cloned):
http://ubuntuforums.org/showthread.php?t=1045715
There are several solutions to this bug:
- Simply del
I'm experiencing the same thing here. The host runs Ubuntu 9.10 server, the
guest as well.
I think this bug results from the fact that virt-clone changes the MAC address
of the quest. If I remember correctly debian-based distributions change the
name of a network interface if they detect a new
