Thanks Josh, Mike, Mike, It makes more sense now. I'm in the process of creating a new image (Update Images) and in the Create Image process I specified that it should have 2048MB of RAM. We'll see how that takes off. (It failed btw, but I don't think it because of this).
I was just confused that the VCL was taking an image with 2GB of RAM and "downsizing" it when it captured. I thought the VCL would capture the image as is. And part of me forgot I was working with VMs (not really, but kind of) and that the VCL could edit the VM settings whenever it wanted to. Adam > -----Original Message----- > From: Josh Thompson [mailto:[email protected]] > Sent: Monday, July 30, 2012 10:13 AM > To: [email protected] > Subject: Re: RAM after capture > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Adam, > > The "minimum RAM" terminology is left over from when VCL started and > only did > bare-metal provisioning. The idea was that if an image needed 4GB of RAM > to > run and you had some computers with only 2GB of RAM, the image would > never be > assigned to a computer with less than 4GB of RAM, but could be assigned to > a > computer with more than 4GB of RAM. > > For VMs, we found it made the most sense to just specify the specs desired > for > the VM. However, we should have also updated the terms to be displayed > differently for VM vs bare metal images. I just created VCL-605 to ensure > these terms are updated in the next release. > > Josh > > On Monday, July 30, 2012 1:18:20 PM Hechler, Adam wrote: > > Thanks Mike, > > > > So after I capture the image, I go into Edit Image Profiles and edit the one > > I just captured? I'm confused because those advanced options say > "Minimum > > RAM." Is it not really the "minimum RAM" but rather "specific RAM?" Why > > is the VCL dropping the RAM down to 512MB when the original image > (before > > capture) had 2048MB? > > > > Adam > > > > From: Waldron, Michael H [mailto:[email protected]] > > Sent: Monday, July 30, 2012 9:12 AM > > To: [email protected] > > Subject: RE: RAM after capture > > > > Adam > > > > The amount of RAM assigned to the VM is set on the image profile. Edit the > > image profile under Manage Images, and click on Advance Options. The > RAM > > setting there is what will be assigned to a VM whenever that particular > > image is loaded. > > > > Mike Waldron > > Systems Specialist > > ITS Research Computing > > University of North Carolina at Chapel Hill > > CB #3420, ITS Manning, Rm 2509 > > 919-962-9778 > > ________________________________ > > From: Hechler, Adam [[email protected]] > > Sent: Monday, July 30, 2012 9:07 AM > > To: [email protected]<mailto:[email protected]> > > Subject: RAM after capture > > Hi everyone, > > > > Maybe this is a simple one but I haven't been able to find an answer in any > > docs. > > > > We are using VMWare Server 2 and VCL 2.2.1 > > > > I have a Windows XP image on the VMWare Server. It has a 50GB HD and 2 > GB of > > RAM. When I capture it into VCL, it only has 512MB of RAM. All of our > > "computers" in the VCL are configured to allow for 4GB of RAM. Is there a > > flag or setting I should be checking? > > Do I just manually change the RAM on the vm (using the VI Client) after > > capturing it? I'm hesitant to manually change things due to our previous > > errors/issues. > > > > We have some engineering software that is definitely going to need the > 2GB > > of RAM. > > > > Thanks, > > Adam > > > > > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > Adam Hechler > > Senior Analyst /PC Systems Administrator > > Rensselaer Polytechnic Institute > > 275 Windsor Street > > Hartford, CT 06120 USA > > Ph: 860-548-2446 > > Email: [email protected]<mailto:[email protected]> > > Web: http://www.ewp.rpi.edu<http://www.ewp.rpi.edu/> > - -- > - ------------------------------- > Josh Thompson > VCL Developer > North Carolina State University > > my GPG/PGP key can be found at pgp.mit.edu > > 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. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.17 (GNU/Linux) > > iEYEARECAAYFAlAWloYACgkQV/LQcNdtPQNpowCfRp18AKoyL3p9VxWbhfFp > mTL1 > XXsAnA/uH4unNuDfcKyYxQzANkcwUa4g > =MOlt > -----END PGP SIGNATURE-----
