RHEV3 : evaluator guide Lab2 (cloned redhat VM)

Latest response


During my evaluation, as part of Lab2, I mainly focused on cloning and templating Windows machines. All goes well for me.

I'm now trying to clone (and power on!) a base redhat virtual machine.

All goes well except that the cloned VM has not network confirgured...except the clone own settings: eth name, MAC...

Search a lot, I managed getting a working clone by editing ifcfg-eth0 and 70-persistent-net.rules (*)

My question: why this is not automatically done as part of the cloning?




vi /etc/sysconfig/network-scripts/ifcfg-eth0

vi /etc/udev/rules.d/70-persistent-net.rules


This is a known issue, and we are working on defining a tool that would assist in preparing VMs for cloning. For now, you can edit ifcfg-ethX and persistent-net.rules and also run sys-unconfig (or just place a file called .unconfigure in / (root) of the guest)


More details can be found here: https://access.redhat.com/kb/docs/DOC-34457

Currently you need to remove details like this from vm that is going to be cloned manually before trying to make a clone. So it's a manual task you need to do before creating a template.


Long term solution virt-sysprep - see http://libguestfs.org/virt-sysprep.1.html -  is still work in progress

Thanks for your respective answers.