VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
1 Replies Last post: May 15, 2009 12:08 PM by efulton  

Requested file "[VMFS] LabMan/504/000504-Windows2008STDFull.vmdk" not found posted: May 13, 2009 9:23 PM

Click to view vincensh's profile Lurker 1 posts since
Nov 5, 2008
Hi all,

newbie to the community.....have been battling an issue over the past 3 days. I have a VM in VC, which I am trying to pull into Lab Manager as a template - Import Template.

However I receive the following error - Requested file "VMFS_INFRA LabMan/504/000504-Windows2008STDFull.vmdk" not found

When I check the datastore that the VM resides I can see the VMDK file there, so am unsure on why it says it cannot be found...

The vmx file for the VM has the following entries;

#!/usr/bin/vmware
floppy0.startconnected = "FALSE"
tools.upgrade.policy = "useGlobal"
uuid.action = "keep"
ide0:0.clientdevice = "false"
usercpuid.80000001 = "00000000000000000000000120000000"
ide0:0.startconnected = "false"
sched.mem.max = "4096"
ethernet0.wakeonpcktrcv = "false"
scsi0.sharedbus = "none"
extendedconfigfile = "000504-WNZAKLDS1.vmxf"
scsi0.present = "true"
deploymentplatform = "windows"
guestcpuid.1 = "0001067800010800000822010febfbff"
numvcpus = "2"
guestos = "winvista"
powertype.reset = "default"
memsize = "2048"
sched.mem.shares = "normal"
virtualhw.productcompatibility = "hosted"
guestcpuid.80000001 = "00000000000000000000000120000000"
ethernet0.addresstype = "static"
serial0.present = "false"
displayname = "000504-wnzaklds1"
mks.thumb.targetwidth = "64"
scsi0:1.filename = "000504-WNZAKLDS1-0-1.vmdk"
ide0:0.filename = "/dev/cdrom"
tools.synctime = "false"
evccompatibilitymode = "FALSE"
uuid.location = ""
mks.thumb.filename = "current.png"
serial0.yieldonmsrread = "true"
virtualhw.version = "4"
scsi0:0.devicetype = "scsi-hardDisk"
ethernet0.present = "true"
powertype.suspend = "default"
tools.deploypkg.filename = ""
ethernet0.virtualdev = "e1000"
usercpuid.1 = "0001067600040800000822010febfbff"
floppy0.connected = "FALSE"
uuid.bios = "50 0a 39 63 20 63 bf 9d-bc 12 4f 48 6d 7b 08 48"
ide0:0.connected = "FALSE"
sched.scsi0:0.shares = "normal"
log.filename = "vmware.log"
ide0:0.present = "true"
hostcpuid.80000001 = "00000000000000000000000120000000"
usercpuid.0 = "0000000a756e65476c65746e49656e69"
sched.cpu.min = "0"
sched.mem.minsize = "0"
scsi0:0.present = "true"
ide0:0.devicetype = "atapi-cdrom"
scsi0:1.present = "true"
vmware.tools.requiredversion = "7202"
mks.thumb.targetheight = "48"
scsi0.virtualdev = "lsilogic"
ethernet0.address = "00:50:56:3d:01:e6"
ethernet0.networkname = "LabMan Default-2LM61"
floppy0.present = "false"
powertype.poweroff = "default"
guestcpuid.0 = "0000000a756e65476c65746e49656e69"
scsi0:0.redo = ""
serial0.filename = "/dev/ttyS0"
usb.present = "false"
hostcpuid.1 = "0001067600040800000ce3bdbfebfbff"
config.version = "8"
powertype.poweron = "default"
sched.cpu.units = "mhz"
mks.thumb.updateperiodsecs = "5"
machine.id = "numnics=1&macaddr_0=00:50:56:3d:01:e6&bootproto_0=static&ip_0=10.204.34.190&netmask_0=255.255.254.0&gateway_0=10.204.34.5&dns1_0=10.204.34.115&dns2_0=10.204.32.115&suffix_0=nzakl.danet&primaryNic=0&computerName=WNZAKLDS1&UseSysPrep=Yes&bitMask=1&markerid=234404041&reconfigToken=887047522"
nvram = "000353-Windows2008STDFull.nvram"
sched.swap.derivedname = "/vmfs/volumes/48eda33e-b4edc3d0-db1f-001a64d47f64/LabMan/504/000504-WNZAKLDS1-52a21be4.vswp"
hostcpuid.0 = "0000000a756e65476c65746e49656e69"
sched.cpu.shares = "normal"
scsi0:0.filename = "000504-Windows2008STDFull.vmdk"
scsi0:1.deviceType = "scsi-hardDisk"
scsi0:1.redo = ""
guestOSAltName = "Microsoft Windows Vista (32-bit)"
sched.cpu.affinity = "all"
migrate.hostlog = "./000504-WNZAKLDS1-52a21be4.hlog"

Is there a procedure I should undertake to ensure that
a) it's looking for the correct VMDK file
b) any manual way to resolve this

Thanks

Click to view efulton's profile Hot Shot 123 posts since
May 17, 2007
That looks like a vm that is already in lab manager. Or at least was once in this or another lab manager installation, and LM really isn't equipped to expect a VC VM to even have a linked-clone chain, so I suspect it's failing to find the next vmdk in the chain.

What kind of history has this VM had?

Does that UUID on the sched.swap.device 48eda33e-b4edc3d0-db1f-001a64d47f64 match the uuid of your filesystem?

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities