Yes. Just a small file path change in the capture routine.

-A

On 7/16/10 2:42 PM, Kiran N wrote:
Thank you Aaron, Brian..!!
I tried creating an image and reloading it and it worked fine..!
Aaron.. I guess the only change you made was to the vmware.pm file rite..?

Thanks once again..!

On Fri, Jul 16, 2010 at 9:15 AM, Aaron Peeler<aaron_pee...@ncsu.edu>  wrote:

  Yes. It's the same bug here. No problem - I'll create the jira issue and
get it updated.

Kiran,
I've cleaned up your sandbox image. Try it again when you get a chance.

Aaron

All, so your not wondering what this sandbox image is. Within the NCSU VCL
production instance we have a standalone VCL sandbox environment that can be
checked out. It was used during a recent VCL bootcamp and is also useful for
development work, etc.
More info about the bootcamp:
http://renoir.csc.ncsu.edu/VCL/Program/program.html





On 7/16/10 8:42 AM, Brian Copcea wrote:

Hello all -

When we spoke earlier Kiran, this was the directory problem I suspected
but
the Error -16 threw me off.

There is a bug in vmware.pm for ESX that makes the directory name for the
new image, and then uses the move command in an attempt to rename the
previously named directory under the<reservation number><vm guest>   schema
to the correct image name.  However, since it created the new directory
already, it simply copies the directory under the correctly named
directory
instead of actually renaming the images as intended.

I don't know if this bug exists for the code for GSX/VMware Server as
well,
but I would guess it does with the above directory structure you gave that
this is what is happening.  I will try to reply to this thread later with
the exact location of the ESX vmware.pm code I had to change and see if I
can find any GSX counterparts.

Aaron, I said I would submit a Jira issue about this and I got a bit slack
-
I'll try to get that done this weekend.

I hope this helps and makes sense...

Sincerely,

Brian Copcea



On Thu, Jul 15, 2010 at 4:27 PM, Kiran N<kiran.nellima...@gmail.com>
  wrote:

  Sorry I think I did not put in correct words.. I am able to run ssh
vmhost1
and login to vmhost1. But the current problem is the missing .vmdk
files..


On Thu, Jul 15, 2010 at 4:01 PM, Josh Thompson<josh_thomp...@ncsu.edu

wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday July 15, 2010, Kiran N wrote:

Michael, I am unable to login to the vmhost1, I think some access

issue..
not sure..!
Once you are logged in to the management node vm within the sandbox

image,

you
should just be able to run "ssh vmhost1" to connect to it.  If you can't

do

that, then you have bigger problems because that is how vcld (from
within
the
sandbox) runs commands on the vmhost.

Josh
- --
- -------------------------------
Josh Thompson
Systems Programmer
Advanced Computing | VCL Developer
North Carolina State University

josh_thomp...@ncsu.edu
919-515-5323

my GPG/PGP key can be found at pgp.mit.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)

iEUEARECAAYFAkw/aSMACgkQV/LQcNdtPQOm5ACdEe56rEujUfSC3YkQJJ1tWIH8
tdAAlA1r3JGkXd7/1Qoj/Z1gJHGeIJo=
=rxgF
-----END PGP SIGNATURE-----


--
Thanks,
Kiran


--

Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University
aaron_pee...@ncsu.edu
919-513-4571





--

Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University
aaron_pee...@ncsu.edu
919-513-4571

Reply via email to