Re: [ovirt-users] Clone / New VM from Template changing network interfaces
Hi Mark, The problem is that you need to seal the source vm before creting the template. http://www.ovirt.org/Sealing_Linux_VM Thanks, Raz Tamir Red Hat Israel oVirt Engine Version: 3.5.0.1-1.el6 When cloning or creating a new vm, the network interfaces in /etc/udev/rules.d/70-persistent-net.rules is getting changed - rendering the new new VM un-networkable. The original file looks like this: [image: Inline image 1] However, once the VM is either cloned or a new VM created from a template of this source VM, the file looks like this: [image: Inline image 2] The 'correct' interfaces are still there, but out of sequence and there are two additional interfaces that do not belong there. Ovirt admin console is showing the correct number of interfaces as seen in this image: [image: Inline image 3] Any idea what is causing this? Thank you for your assistance. *** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 800.885.8886 x128 | mste...@telvue.com | http://www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www.facebook.com/telvue ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Clone / New VM from Template changing network interfaces
oVirt Engine Version: 3.5.0.1-1.el6 When cloning or creating a new vm, the network interfaces in /etc/udev/rules.d/70-persistent-net.rules is getting changed - rendering the new new VM un-networkable. The original file looks like this: [image: Inline image 1] However, once the VM is either cloned or a new VM created from a template of this source VM, the file looks like this: [image: Inline image 2] The 'correct' interfaces are still there, but out of sequence and there are two additional interfaces that do not belong there. Ovirt admin console is showing the correct number of interfaces as seen in this image: [image: Inline image 3] Any idea what is causing this? Thank you for your assistance. *** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 800.885.8886 x128 | mste...@telvue.com | http://www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www.facebook.com/telvue ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Clone / New VM from Template changing network interfaces
Thank you very much for this quick response! *** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 800.885.8886 x128 | mste...@telvue.com | http://www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www.facebook.com/telvue On Fri, Feb 5, 2016 at 7:46 AM, Pavel Gashev wrote: > Solution: > > http://www.ovirt.org/OVirt_Administration_Guide#Sealing_a_Linux_Virtual_Machine_for_Deployment_as_a_Template > > > From: on behalf of Mark Steele < > mste...@telvue.com> > Date: Friday 5 February 2016 at 15:07 > To: "users@ovirt.org" > Subject: [ovirt-users] Clone / New VM from Template changing network > interfaces > > oVirt Engine Version: 3.5.0.1-1.el6 > > When cloning or creating a new vm, the network interfaces in > /etc/udev/rules.d/70-persistent-net.rules is getting changed - rendering > the new new VM un-networkable. > > The original file looks like this: > > # PCI device 0x1af4:/sys/devices/pci:00/:00:04.0/virtio1 > (virtio-pci) > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR(address)=="00:01:a4:a2:b4:04", ATTR(dev_id)=="0x0", ATTR(type)=="1", > KERNEL=="eth*", NAME="eth1" > > # PCI device 0x1af4:/sys/devices/pci:00/:00:03.0/virtio0 > (virtio-pci) > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR(address)=="00:01:a4:a2:b4:03", ATTR(dev_id)=="0x0", ATTR(type)=="1", > KERNEL=="eth*", NAME="eth0" > > # PCI device 0x1af4:/sys/devices/pci:00/:00:05.0/virtio2 > (virtio-pci) > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR(address)=="00:01:a4:a2:b4:05", ATTR(dev_id)=="0x0", ATTR(type)=="1", > KERNEL=="eth*", NAME="eth2" > > However, once the VM is either cloned or a new VM created from a template > of this source VM, the file looks like this: > > # PCI device 0x1af4:/sys/devices/pci:00/:00:04.0/virtio1 > (virtio-pci) > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR(address)=="00:01:a4:a2:b4:04", ATTR(dev_id)=="0x0", ATTR(type)=="1", > KERNEL=="eth*", NAME="eth1" > > # PCI device 0x1af4:/sys/devices/pci:00/:00:03.0/virtio0 > (virtio-pci) > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR(address)=="00:01:a4:a2:b4:03", ATTR(dev_id)=="0x0", ATTR(type)=="1", > KERNEL=="eth*", NAME="eth0" > > # PCI device 0x1af4:/sys/devices/pci:00/:00:05.0/virtio2 > (virtio-pci) > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR(address)=="00:01:a4:a2:b4:05", ATTR(dev_id)=="0x0", ATTR(type)=="1", > KERNEL=="eth*", NAME="eth2" > > # PCI device 0x1af4:/sys/devices/pci:00/:00:04.0/virtio1 > (virtio-pci) > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR(address)=="00:01:a4:a2:b4:10", ATTR(dev_id)=="0x0", ATTR(type)=="1", > KERNEL=="eth*", NAME="eth3" > > # PCI device 0x1af4:/sys/devices/pci:00/:00:03.0/virtio1 > (virtio-pci) > SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", > ATTR(address)=="00:01:a4:a2:b4:0f", ATTR(dev_id)=="0x0", ATTR(type)=="1", > KERNEL=="eth*", NAME="eth5" > > The 'correct' interfaces are still there, but out of sequence and there > are two additional interfaces that do not belong there. > > Ovirt admin console is showing the correct number of interfaces as seen in > this image: > > [image: Inline image 3] > > *** > *Mark Steele* > CIO / VP Technical Operations | TelVue Corporation > TelVue - We Share Your Vision > 800.885.8886 x128 | mste...@telvue.com | http://www.telvue.com > twitter: http://twitter.com/telvue | facebook: > https://www.facebook.com/telvue > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Clone / New VM from Template changing network interfaces
Solution: http://www.ovirt.org/OVirt_Administration_Guide#Sealing_a_Linux_Virtual_Machine_for_Deployment_as_a_Template From: mailto:users-boun...@ovirt.org>> on behalf of Mark Steele mailto:mste...@telvue.com>> Date: Friday 5 February 2016 at 15:07 To: "users@ovirt.org<mailto:users@ovirt.org>" mailto:users@ovirt.org>> Subject: [ovirt-users] Clone / New VM from Template changing network interfaces oVirt Engine Version: 3.5.0.1-1.el6 When cloning or creating a new vm, the network interfaces in /etc/udev/rules.d/70-persistent-net.rules is getting changed - rendering the new new VM un-networkable. The original file looks like this: # PCI device 0x1af4:/sys/devices/pci:00/:00:04.0/virtio1 (virtio-pci) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:01:a4:a2:b4:04", ATTR(dev_id)=="0x0", ATTR(type)=="1", KERNEL=="eth*", NAME="eth1" # PCI device 0x1af4:/sys/devices/pci:00/:00:03.0/virtio0 (virtio-pci) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:01:a4:a2:b4:03", ATTR(dev_id)=="0x0", ATTR(type)=="1", KERNEL=="eth*", NAME="eth0" # PCI device 0x1af4:/sys/devices/pci:00/:00:05.0/virtio2 (virtio-pci) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:01:a4:a2:b4:05", ATTR(dev_id)=="0x0", ATTR(type)=="1", KERNEL=="eth*", NAME="eth2" However, once the VM is either cloned or a new VM created from a template of this source VM, the file looks like this: # PCI device 0x1af4:/sys/devices/pci:00/:00:04.0/virtio1 (virtio-pci) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:01:a4:a2:b4:04", ATTR(dev_id)=="0x0", ATTR(type)=="1", KERNEL=="eth*", NAME="eth1" # PCI device 0x1af4:/sys/devices/pci:00/:00:03.0/virtio0 (virtio-pci) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:01:a4:a2:b4:03", ATTR(dev_id)=="0x0", ATTR(type)=="1", KERNEL=="eth*", NAME="eth0" # PCI device 0x1af4:/sys/devices/pci:00/:00:05.0/virtio2 (virtio-pci) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:01:a4:a2:b4:05", ATTR(dev_id)=="0x0", ATTR(type)=="1", KERNEL=="eth*", NAME="eth2" # PCI device 0x1af4:/sys/devices/pci:00/:00:04.0/virtio1 (virtio-pci) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:01:a4:a2:b4:10", ATTR(dev_id)=="0x0", ATTR(type)=="1", KERNEL=="eth*", NAME="eth3" # PCI device 0x1af4:/sys/devices/pci:00/:00:03.0/virtio1 (virtio-pci) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:01:a4:a2:b4:0f", ATTR(dev_id)=="0x0", ATTR(type)=="1", KERNEL=="eth*", NAME="eth5" The 'correct' interfaces are still there, but out of sequence and there are two additional interfaces that do not belong there. Ovirt admin console is showing the correct number of interfaces as seen in this image: [Inline image 3] *** Mark Steele CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 800.885.8886 x128 | mste...@telvue.com<mailto:mste...@telvue.com> | http://www.telvue.com<http://www.telvue.com/> twitter: http://twitter.com/telvue | facebook: https://www.facebook.com/telvue ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Clone / New VM from Template changing network interfaces
oVirt Engine Version: 3.5.0.1-1.el6 When cloning or creating a new vm, the network interfaces in /etc/udev/rules.d/70-persistent-net.rules is getting changed - rendering the new new VM un-networkable. The original file looks like this: # PCI device 0x1af4:/sys/devices/pci:00/:00:04.0/virtio1 (virtio-pci) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:01:a4:a2:b4:04", ATTR(dev_id)=="0x0", ATTR(type)=="1", KERNEL=="eth*", NAME="eth1" # PCI device 0x1af4:/sys/devices/pci:00/:00:03.0/virtio0 (virtio-pci) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:01:a4:a2:b4:03", ATTR(dev_id)=="0x0", ATTR(type)=="1", KERNEL=="eth*", NAME="eth0" # PCI device 0x1af4:/sys/devices/pci:00/:00:05.0/virtio2 (virtio-pci) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:01:a4:a2:b4:05", ATTR(dev_id)=="0x0", ATTR(type)=="1", KERNEL=="eth*", NAME="eth2" However, once the VM is either cloned or a new VM created from a template of this source VM, the file looks like this: # PCI device 0x1af4:/sys/devices/pci:00/:00:04.0/virtio1 (virtio-pci) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:01:a4:a2:b4:04", ATTR(dev_id)=="0x0", ATTR(type)=="1", KERNEL=="eth*", NAME="eth1" # PCI device 0x1af4:/sys/devices/pci:00/:00:03.0/virtio0 (virtio-pci) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:01:a4:a2:b4:03", ATTR(dev_id)=="0x0", ATTR(type)=="1", KERNEL=="eth*", NAME="eth0" # PCI device 0x1af4:/sys/devices/pci:00/:00:05.0/virtio2 (virtio-pci) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:01:a4:a2:b4:05", ATTR(dev_id)=="0x0", ATTR(type)=="1", KERNEL=="eth*", NAME="eth2" # PCI device 0x1af4:/sys/devices/pci:00/:00:04.0/virtio1 (virtio-pci) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:01:a4:a2:b4:10", ATTR(dev_id)=="0x0", ATTR(type)=="1", KERNEL=="eth*", NAME="eth3" # PCI device 0x1af4:/sys/devices/pci:00/:00:03.0/virtio1 (virtio-pci) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR(address)=="00:01:a4:a2:b4:0f", ATTR(dev_id)=="0x0", ATTR(type)=="1", KERNEL=="eth*", NAME="eth5" The 'correct' interfaces are still there, but out of sequence and there are two additional interfaces that do not belong there. Ovirt admin console is showing the correct number of interfaces as seen in this image: [image: Inline image 3] *** *Mark Steele* CIO / VP Technical Operations | TelVue Corporation TelVue - We Share Your Vision 800.885.8886 x128 | mste...@telvue.com | http://www.telvue.com twitter: http://twitter.com/telvue | facebook: https://www.facebook.com/telvue ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
