Hi Mark,
I'm guessing the disk extents defined in the .vmdk file don't match what's in
the directory. Open up vmwarelinux-xubuntu904-v0.vmdk and look for the "Extent
description" section. There should be some additional .vmdk files listed under
this section. Compare these file names to the contents of the
vmwarelinux-xubuntu904-v0 directory. Do all of the files listed in the .vmdk
file exist?
The extent section gets updated during the image capture process when vcld
renames the .vmdk files. This may have gotten hung up. The remaining .vmdk
files in the directory should be named vmwarelinux-xubuntu904-v0-s00x.vmdk,
where the 'x' in s00x is numbered sequentially. If the main .vmdk file
(vmwarelinux-xubuntu904-v0.vmdk) contains different extent names, try to edit it
to match what's in the directory and try to start the VM again.
Hope this helps,
Andy
Mark Gardner wrote:
Making a bit of progress... Hit another snag. After the image is copied, it
tries to start it up but hits an error because the VM requires user input:
|32571|10:10|new| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x
localvmhost 'vmware-cmd
/home/vm/vmware/vmwarelinux-xubuntu904-v0vmguest-1/vmwarelinux-xubuntu904-v0vmguest-1.vmx
start' 2>&1
...
|32571|10:10|new| VMControl error -16: Virtual machine requires user input
to continue
Starting the VM up in the vmware GUI client gives the error "Cannot open the
disk
'/images/vmware/vmwarelinux-xubuntu904-v0/vmwarelinux-xubuntu904-v0.vmdk' or
one of the snapshot disks it depends on. Reason: Failed to lock the file.".
The disk image exists:
$ ls -l
/images/vmware/vmwarelinux-xubuntu904-v0/vmwarelinux-xubuntu904-v0.vmdk
2524548 -rw------- 1 root root 2524544 Apr 28 09:53
/images/vmware/vmwarelinux-xubuntu904-v0/vmwarelinux-xubuntu904-v0.vmdk
As far as I can tell, there are no locks on the disk anyware.
I am enclosing the vcld.log.
Thanks in advance,
Mark
