RE: Image Creation from Base Image
I dealt with this issue of the network interfaces changing assignments in our
Ubuntu images.
For Ubuntu 9.04 and earlier:
Create /etc/udev/rules.d/90-persistent-net.rules file.
Contents:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{type}=="1",
KERNEL=="eth*", OPTIONS="ignore_device"
This prevents the device rules from assigning eth0 and eth1 different names
because the mac addresses don't match the original machine.
For Ubuntu 10.04 and later:
Instead of creating 90-persistent-net.rules file, create
/etc/init.d/udev-netrule script to remove
70-persistent-net.rules file on shutdown, so it doesn't exist when image is
captured.
Contents:
/bin/rm -f /etc/udev/rules.d/70-persistent-net.rules
Link to /etc/rc0.d/S10udev-netrule and /etc/rc6.d/S10udev-netrule.
Mike Waldron
Systems Specialist
ITS Research Computing
University of North Carolina at Chapel Hill
CB #3420, ITS Manning, Rm 2509
919-962-9778
From: Evelio Quiros [evq...@fiu.edu]
Sent: Tuesday, November 15, 2011 12:35 PM
To: vcl-user@incubator.apache.org
Subject: Re: Image Creation from Base Image
That¹s great. Looking forward to the new release.
But how were you able to manage new images before?
Does the problem not exist in other Linux distros ?
Q
On 11/15/11 12:19 PM, "Josh Thompson" wrote:
>-BEGIN PGP SIGNED MESSAGE-
>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 pgp.mit.edu
>-BEGIN PGP SIGNATURE-
>Version: GnuPG v2.0.17 (GNU/Linux)
>
>iEYEARECAAYFAk7Cnw4ACgkQV/LQcNdtPQOtoACfdpLAkwJFJbtmhYyCAV7lU2AX
>XnEAn3I4k4j297Esk1GjQKXIFIQUuAQr
>=j2SP
>-END PGP SIGNATURE-
Re: Image Creation from Base Image
Yes in the 2.3 release there is a step in the Linux.pm 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. Aaron On Tue, Nov 15, 2011 at 12:19 PM, Josh Thompson wrote: > -BEGIN PGP SIGNED MESSAGE- > 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 pgp.mit.edu > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.17 (GNU/Linux) > > iEYEARECAAYFAk7Cnw4ACgkQV/LQcNdtPQOtoACfdpLAkwJFJbtmhYyCAV7lU2AX > XnEAn3I4k4j297Esk1GjQKXIFIQUuAQr > =j2SP > -END PGP SIGNATURE- > -- 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.
Re: Image Creation from Base Image
That¹s great. Looking forward to the new release. But how were you able to manage new images before? Does the problem not exist in other Linux distros ? Q On 11/15/11 12:19 PM, "Josh Thompson" wrote: >-BEGIN PGP SIGNED MESSAGE- >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 pgp.mit.edu >-BEGIN PGP SIGNATURE- >Version: GnuPG v2.0.17 (GNU/Linux) > >iEYEARECAAYFAk7Cnw4ACgkQV/LQcNdtPQOtoACfdpLAkwJFJbtmhYyCAV7lU2AX >XnEAn3I4k4j297Esk1GjQKXIFIQUuAQr >=j2SP >-END PGP SIGNATURE-
Re: Image Creation from Base Image
-BEGIN PGP SIGNED MESSAGE- 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 pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) iEYEARECAAYFAk7Cnw4ACgkQV/LQcNdtPQOtoACfdpLAkwJFJbtmhYyCAV7lU2AX XnEAn3I4k4j297Esk1GjQKXIFIQUuAQr =j2SP -END PGP SIGNATURE-
Image Creation from Base Image
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 ? Regards, Q
