VMware Cloud Community
TristanT
Contributor
Contributor
Jump to solution

VM Template Problems

I am experiencing the same problem as - http://communities.vmware.com/message/964286

I have a VM template that worked well last week. This week when I try to deploy a VM from this template, I get error "A file was not found. datastorename-vmdiskname.vmdk" immediately on deploy attempt.

If I convert the template to a VM and then try to boot, I get error "Unable to access a file since it is locked".

To try and solve this, I have:

- used the lsof| grep servername technique describe in post above and was unable to find a file lock on any of the hosts in my cluster.

- I have removed the template from VC and re-added it.

- I have systematically put each cluster host into maintenance mode and then performed a reboot.

- reviewed security on the vmdk file and the vmx file - permissions are fine

- reviewed the format and configs in the vmx file - file paths are fine

Using latest builds of ESX and VC with all of the lastest updates. Guest is Win2K3 Std.

Your solutions are warmly appreciated and will net you points and a margarita at VMWorld.

Thanks!

Reply
0 Kudos
1 Solution

Accepted Solutions
admin
Immortal
Immortal
Jump to solution

Convert the template to a VM then run the vmkfstools -D on the -flat.vmdk file, not the .vmdk.

The vmdk is just a descriptor file and is not locked which is why the owner is all 0's.

View solution in original post

Reply
0 Kudos
9 Replies
Rubeck
Virtuoso
Virtuoso
Jump to solution

can you see the host UUID of the lock owner by doing a vmkfstools -D /vmfs/volume/datastore/name.vmdk? Look in vmkernel log.

/Rubeck

Reply
0 Kudos
TristanT
Contributor
Contributor
Jump to solution

I get no UUID when I run that command.

When I attempt to clone from template, the vmkernel shows:

Jul 21 11:22:21 pdxvhostp005 vmkernel: 45:20:15:02.217 cpu2:1036)FS3: 130:

Thanks much!

Tristan

Reply
0 Kudos
Rubeck
Virtuoso
Virtuoso
Jump to solution

"owner 00000000-00000000-0000-000000000000" ? Hmmm... I would call support with this one as it could be an issue with metadata on the LUN.

/Rubeck

Modrus
Contributor
Contributor
Jump to solution

Did you ever get a fix for this? I'm having the same problem.

Reply
0 Kudos
TristanT
Contributor
Contributor
Jump to solution

We never solved this problem, though after we updated ESX and VC with update 2, we've not seen it happen again.

Reply
0 Kudos
ASlyotov
Contributor
Contributor
Jump to solution

It's a mystic! We have absolutely same problem with template!

Even OS version of the guest VM is a same - W2k3 Std.

About one week deploy from it works fine, but today we have same 00000 owner:

Aug 15 12:11:55 esx09 vmkernel: 2:03:29:55.973 cpu4:1041)FS3: 130: <START (Template) W2K3STR2SP2ENG.vmdk>

Aug 15 12:11:55 esx09 vmkernel: 2:03:29:55.973 cpu4:1041)Lock [type 10c00001 offset 43878400 v 5283, hb offset 3232256

Aug 15 12:11:55 esx09 vmkernel: gen 9, mode 0, owner 00000000-00000000-0000-000000000000 mtime 184469]

Aug 15 12:11:55 esx09 vmkernel: 2:03:29:55.973 cpu4:1041)Addr <4, 117, 5>, gen 4827, links 1, type reg, flags 0x0, uid 0, gid 0, mode 100600

Aug 15 12:11:55 esx09 vmkernel: 2:03:29:55.973 cpu4:1041)len 418, nb 1 tbz 0, zla 2, bs 65536

Aug 15 12:11:55 esx09 vmkernel: 2:03:29:55.973 cpu4:1041)FS3: 132: <END (Template) W2K3STR2SP2ENG.vmdk>

ESX3.5Update2 build 110181

Virtual Center2.5 build 104215

My opinion: Last few months quality of Vmware products growing down. Looks like they programmers works under heavy time press and releasing unstable versions of the products.

Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

Convert the template to a VM then run the vmkfstools -D on the -flat.vmdk file, not the .vmdk.

The vmdk is just a descriptor file and is not locked which is why the owner is all 0's.

Reply
0 Kudos
TristanT
Contributor
Contributor
Jump to solution

Thanks much appk - that's exactly what I was looking for. Seemed to fix the problem we've been having!

Reply
0 Kudos
dougdavis22
Hot Shot
Hot Shot
Jump to solution

FYI,

People looking for ways to resolve this might want to look at the following as it's exactly what happened to us today:

http://communities.vmware.com/thread/152969

Rgds,

Doug.

Reply
0 Kudos