Just making sure. Is this the vmx file that was created by vcld?
The displayName doesn't match what vmware.pm would create. displayName
is generally set to the internal imagename + the computername. Something
like esx3-win2003-v0vcl01
Aaron
On 4/6/10 3:41 PM, Kiran N wrote:
Thanks Aaron!
Please find the file below:
#!/usr/bin/vmware
config.version = "8"
virtualHW.version = "4"
floppy0.present = "false"
nvram = "Windows 2003 R2 EE.nvram"
deploymentPlatform = "windows"
virtualHW.productCompatibility = "hosted"
tools.upgrade.policy = "manual"
powerType.powerOff = "default"
powerType.powerOn = "default"
powerType.suspend = "default"
powerType.reset = "default"
displayName = "Windows 2003 R2 EE"
extendedConfigFile = "Windows 2003 R2 EE.vmxf"
scsi0.present = "true"
scsi0.sharedBus = "none"
scsi0.virtualDev = "lsilogic"
memsize = "4096"
scsi0:0.present = "true"
scsi0:0.fileName = "Windows 2003 R2 EE-000001.vmdk"
scsi0:0.deviceType = "scsi-hardDisk"
ide0:0.present = "true"
ide0:0.fileName = "/dev/scd0"
ide0:0.deviceType = "atapi-cdrom"
ide0:0.startConnected = "false"
ethernet0.present = "true"
ethernet0.wakeOnPcktRcv = "false"
ethernet0.networkName = "VM_Access"
ethernet0.addressType = "generated"
guestOSAltName = "Microsoft Windows Server 2003, Enterprise Edition
(32-bit)"
guestOS = "winnetenterprise"
uuid.location = "56 4d b0 02 f8 06 24 bf-2c 97 80 6c 8c 0e 37 24"
uuid.bios = "56 4d b0 02 f8 06 24 bf-2c 97 80 6c 8c 0e 37 24"
snapshot.action = "keep"
sched.cpu.min = "0"
sched.cpu.units = "mhz"
sched.cpu.shares = "normal"
sched.mem.minsize = "0"
sched.mem.shares = "normal"
toolScripts.afterPowerOn = "true"
toolScripts.afterResume = "true"
toolScripts.beforeSuspend = "true"
toolScripts.beforePowerOff = "true"
evcCompatibilityMode = "FALSE"
guestCPUID.0 = "0000000168747541444d416369746e65"
guestCPUID.1 = "00040f120000080000002001078bbbff"
guestCPUID.80000001 = "00040f120000035300000009ebd3fbff"
hostCPUID.0 = "0000000168747541444d416369746e65"
hostCPUID.1 = "00040f120002080000002001178bfbff"
hostCPUID.80000001 = "00040f12000003530000001febd3fbff"
sched.swap.derivedName =
"/vmfs/volumes/4a54aa4b-88146930-8e6f-00145e6d6a04/Windows 2003 R2
EE/Windows 2003 R2 EE-3bd65d97.vswp"
scsi0:0.redo = ""
userCPUID.0 = "0000000168747541444d416369746e65"
userCPUID.1 = "00040f120002080000002001078bbbff"
userCPUID.80000001 = "00040f120000035300000009ebd3fbff"
vmware.tools.requiredversion = "7303"
ethernet0.generatedAddress = "00:0c:29:0e:37:24"
tools.syncTime = "false"
ethernet0.generatedAddressOffset = "0"
ethernet1.present = "true"
ethernet1.networkName = "VCL VM Private Net Access"
ethernet1.addressType = "generated"
ethernet1.generatedAddress = "00:0c:29:0e:37:2e"
ethernet1.generatedAddressOffset = "10"
On Tue, Apr 6, 2010 at 3:27 PM, Aaron Peeler<aaron_pee...@ncsu.edu> wrote:
Could be something wrong with the .vmx file.
My first thought is to check the drive type - ide or scsi. esx doesn't
support ide drive types and any new computers added in have hda as the
default value in the database schema.
Could you share that portion of the vmx file?
Aaron
On 4/6/10 3:13 PM, Kiran N wrote:
Hello,
I resolved the SSH error, but now facing a new issue. By seeing the log I
think that the reservation process is failing in the last due to error :
VMControl error -999: Unknown error: The poweron operation failed
unexpectedly.
Please check the vcld log file below and let me know if anyone has a
solution for this error.
Thanks in advance..!
Kiran
2010-04-06 13:57:34|19162|31:31|reload|utils.pm:run_ssh_command(6259)|SSH
command executed on cleesx.democentral.ibm.com, command:
|19162|31:31|reload| /usr/bin/ssh -i /etc/vcl/vcl.key -l root -p 22 -x
cleesx.democentral.ibm.com 'vmware-cmd
/vmfs/volumes/VCL/esx3-win2003-v0vcl01/esx3-win2003-v0vcl01.vmx getstate'
2>&1
|19162|31:31|reload| returning (11, "VMControl error -11: No such v...")
2010-04-06 13:57:34|19162|31:31|reload|vmware.pm:
node_status(1914)|VMControl
error -11: No such virtual machine
2010-04-06 13:57:34|19162|31:31|reload|vmware.pm:node_status(1925)|vcl01
vmstate reports 0
2010-04-06 13:57:34|19162|31:31|reload|vmware.pm:
node_status(1963)|returning
node status hash reference ($node_status->{status}=RELOAD)
2010-04-06 13:57:34|19162|31:31|reload|new.pm:
reload_image(529)|node_status
returned a hash reference
2010-04-06 13:57:34|19162|31:31|reload|new.pm:
reload_image(534)|node_status
hash reference contains key {status}=RELOAD
--
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
