firestartah
Virtuoso
Virtuoso

Can't add vmdk file to exisiting machine

Jump to solution

We received a vmdk file from client which they want us to add to one of their existing vm's. After uploading it to the datastore of the vm, when trying to add it, it doesn't show. It can only be seen if i create a new VM and specify the disk as the system disk. However, it then does not start. The vmdk file didn't come with a config file. Does anyone know how to get around this?






If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".

Gregg Robertson, VCP3,4 , MCSE, MCSA, MCTS, MCITP

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful". Gregg http://thesaffageek.co.uk
0 Kudos
1 Solution

Accepted Solutions

I am presuming you only have the 'flat' vmdk file, not the smaller vmdk descriptor which explains why you cannot see it in the VI Client (the descriptor file is what you actually see when browsing for a VMDK file, not the actual flat file / data file) once you have imported it. If the file has come from Vmware Server or Workstation it should still have a descriptor file with it - without it you are stuck. If you dont have both files, I am not sure that you can convert it using Vmware convertor - you would have to try that one for yourself as per the previous advice.

You could try recreating the VMDK descriptor for the flat file. There is a VMware KB on how to do this:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100251...






If you found this helpful, please consider awarding some points

If you found this helpful, please consider awarding some points

View solution in original post

0 Kudos
4 Replies
AWo
Immortal
Immortal

Was that .vmdk created by an ESX guest or by a different VMware product? If you got only one file named vmdk it comes most likely not from ESX. Than you need to convert it.


AWo

VCP 3 & 4

Author @ vmwire.net

\[:o]===\[o:]

=Would you like to have this posting as a ringtone on your cell phone?=

=Send "Posting" to 911 for only $999999,99!=

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
0 Kudos

>Than you need to convert it

And there is special tool called vCenter Converter designed for tasks such as this.


---

MCSA, MCTS, VCP, VMware vExpert '2009

http://blog.vadmin.ru

EMCCAe, MCITP: SA+VA, VCP 3/4/5, VMware vExpert http://blog.vadmin.ru
0 Kudos

I am presuming you only have the 'flat' vmdk file, not the smaller vmdk descriptor which explains why you cannot see it in the VI Client (the descriptor file is what you actually see when browsing for a VMDK file, not the actual flat file / data file) once you have imported it. If the file has come from Vmware Server or Workstation it should still have a descriptor file with it - without it you are stuck. If you dont have both files, I am not sure that you can convert it using Vmware convertor - you would have to try that one for yourself as per the previous advice.

You could try recreating the VMDK descriptor for the flat file. There is a VMware KB on how to do this:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100251...






If you found this helpful, please consider awarding some points

If you found this helpful, please consider awarding some points
0 Kudos
firestartah
Virtuoso
Virtuoso

I had tried to use converter already. Pauls idea was correct although we managed to get the files off the user again and this time it had all the files needed so there was no need to try troubleshoot it in the end.






If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".

Gregg Robertson, VCP3,4 , MCSE, MCSA, MCTS, MCITP

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful". Gregg http://thesaffageek.co.uk
0 Kudos