Yes in the 2.3 release there is a step in the pre_capture
routine to delete this file on each capture.

But the newer Linux versions will actually recreate this file on
startup, just deleting will work for the first image capture but not
any after that. Older distros, deleting it was a long-term fix.
So for an immediate workaround in the 2.2.1 code, I've seen success in
deleting this file and then creating a directory of this name in your
image and recapture.

rm /etc/udev/rules.d/70-persistent-net.rules
mkdir /etc/udev/rules.d/70-persistent-net.rules

Hope this helps.

On Tue, Nov 15, 2011 at 12:19 PM, Josh Thompson <> wrote:
> Hash: SHA1
> On Tuesday November 15, 2011, Evelio Quiros wrote:
>> Hello,
>> I was able to successfully capture a base image.
>> I have added the image to the image group.
>> However, when I try to make a reservation, or create a new image,
>> It eventually fails. I watch the VM server and see that a new VM was
>> started. It does start a new VM with the correct MAC addresses,
>> but Redhat detects these changed MACs as new interfaces, and assigns them
>> to eth2 and eth3. Consequently, they are not brought up, the machine never
>> dhcp's, and the image fails to contact the vcl server.
>> Should I delete the network persistence rules before capturing the image ?
> Exactly - that one has really been a problem for us.  I believe Aaron actually
> committed a change for vcld that will be in 2.3 that automatically deletes it
> at capture time.
> Josh
>> Regards,
>> Q
> - --
> - -------------------------------
> Josh Thompson
> VCL Developer
> North Carolina State University
> my GPG/PGP key can be found at
> Version: GnuPG v2.0.17 (GNU/Linux)
> XnEAn3I4k4j297Esk1GjQKXIFIQUuAQr
> =j2SP

Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University

All electronic mail messages in connection with State business which
are sent to or received by this account are subject to the NC Public
Records Law and may be disclosed to third parties.

Reply via email to