Using VMDK file

[Roggia]

Heeellp

I move all the files from a desktop to a VM that i´ve created in a ESXi

After turned off my VM I tried to Turn on againd without success.

I did many thing and I saw that there is a VMDK file with 31 Gb in the Datastore Browser. But I can´t do anything with this file

How can I made my VM works agais if I have just this file and nvram file ???

thanx

Daniel Roggia

[SuryaVMware]

When you say you have moved your file from desktop to a VM created on ESX, You mean the VM was originaly running on a Workstation or VMware server product, or you have copied it from another ESX server to your desktop?

If the VM was originally running on a WKs or a server product you might have to import the disk again.

use the vmkfstools -i <original file> <new file> and edit your VM's configuration to work with the new file. you should be good.

Let me know if you need more help with this.

-Surya

[Roggia]

No

I had a Server with Windows 2003 server running. I´ve installed a Windows 2008 server in a VM at ESXi and moved the files from the Windows 2003 server (from folder to folder). That Windows 2003 server was already formatted and I haven´t any backup cause I was wonderind how to make a VM backup directly in a ESXi

So, I haven´t VM before this one.

Wait for responses

Thx

Daniel Roggia

[SuryaVMware]

You mean to say you originaly had a Win2003 VM and you have re-formated the disk and installed Win2008 in it. now you want to get back to win2003. Correct me if i am wrong.

If my understanding is correct, you will not be able to revert the changes unless you have a snapshot taken before you started the windows 2008 installation or you have a backup of the VM with Windows 2003 installed.

Let me know exactly what you are looking for. If you have a backup of the 2003 VM you can restore it and have the 2003 running.

-Surya

[Roggia]

I think I should be more clear.

I have no backup, and my all data is on that 31gb file. Can I put that .vdmk file in my inventory again?

Sorry to my english

Sincerelly

D Roggia

[SuryaVMware]

Is it that you see the files on the datastore and not the VM in the VM inventory? I see there is no vmx file.

If so can you create a new VM pointing to the existing VMDK fil.

Start creating new VM and select Custom optio. when you are done selecting all the OS and other options ..

when it comes to disk select "Existing file from the datastore" and point the wizard to the vmdk file in the directory.

you will have the VM back in the inventory once you have finished the wizard.

-Surya

[Roggia]

yeah, now you understood my problem,

I did all that you said and when I will create (after I click at Finish button) that error message appear:

Incompatible device backing specified for device '4'. (attached image)

Any other idea =(

thanx for now

Daniel Roggia

[TomHowarth]

Daniel firstly welcome to the forums,

I would like to clear up some misunderstanding, I understand that english is not your primary language, so bear with me.

firstly was the original windows 2003 machine a physical server or a VM running under VMware Server 1 or Workstation??

secondly when you say you coppied the files to the new Windows 2008 server folder by folder do you mean the VMDK files or the file contained withing the VMDK (the actual guest OS files)

thirdly do you still have the original windows 2003 machine available.

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth

VMware Communities User Moderator

Blog: www.planetvm.net

[Roggia]

Thanks for the welcome

The original Windows 2003 was a physical server, but I don´t have anything from the older 2003. I moved all and that machine was with linux now, so I have to repair this problem using that VMDK file

The only file I have is that vmdk, but when I tried to put it on the inventory, the error message bellow apper:

Incompatible device backing specified for device '4'.

thanx

Daniel Roggia

[Karunakar]

Hi

This usually happens when the devices atached to the VM you have created are not supported.

can you check the below link , this might help you in some way.

As a work around, try to remove the attached devices to the VM, this can be done from edit settings, and remove CDROM, floppy, network device and then try to power on the virtual machine.

This should resolve the issue.

-Karunakar

[TomHowarth]

Daniel, what are we talking about here, OS files or data files??

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth

VMware Communities User Moderator

Blog: www.planetvm.net

[Roggia]

Tom

I need to start my VM with Windows Server 2008, but I couldn't put it in the ESXi inventory . I have the .vdmk file in the Datastore. The image attached at my first message show the .vdmk file that I have in the Datastore.

I need to put .vdmk file (windows 2008 server OS) in the ESXi inventory to start my Windows 2008 Server OS.

thx for now

Daniel Roggia

[Roggia]

Karunakar

I cannot start my VM because it´s not in the inventory. When I try to put it on the inventory, that error appear

thanx

Daniel Roggia

[Karunakar]

Hi,

I understand that when you put in to the inventory and then try to power on you get this error message.

This happens when you are trying to create a vm with unsupported devices.

can you try to change the devices attached to the VM, like type of controller and any other if you can, and then try to power on.

-Karunakar

[Roggia]

no

I can´t put in to the inventory this .vdmk file, I get the error message before the VM appear in the inventory

I can´t power on the vm because I can´t put it in to the inventory

Hope you understand 😃

thanks

Daniel Roggia

[Karunakar]

Yeah, i understood that.

can you find any othe files related to that virtual machine in the datastore?

or did you try to delete the older files of the VM

-Karunakar

[TomHowarth]

According to the original image you posted you do not have a virtual machine currently you only have a hard drive. can you try to recreate a VM from the VI and use the current VMDK. if that does not work create a brand new guest and install Windows 2008 in it and then attempt to add the original disk as a second HDD in the VM

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth

VMware Communities User Moderator

Blog: www.planetvm.net

[SuryaVMware]

Roggia,

I am back. Let's do this. Follow the steps below.

1) Login to the ESX server via ssh or directly on the console as root.

2) Go to the VMFS volume 'datastore1'.

cd /vmfs/volumes/datastore1

3) Move the vmdk from the VM's folder.

mv "Windows 2008 server 192.168.1.9/Windows 2008 server 192.168.1.9.vmdk" ./ (note there is a DOT preceeding the / )

4) Rename your VM directory.

mv "Windows 2008 server 192.168.1.9" backup

5) Create a new directory.

mkdir new

6) Import the vmdk to ESX server compatable mode with the vmkfstools command.

vmkfstools -i "/vmfs/volumes/datastore1/Windows 2008 server 192.168.1.9.vmdk" "/vmfs/volumes/datastore1/new/Windows 2008 server 192.168.1.9.vmdk" (Note: the 2nd path is not same as the first you are giving new in the path)

7) Once the import is finished, start creating the VM with what ever name you want and select the existing disk on the datastore, make sure you point it to the one in the new folder.

😎 Once the VM is created, move the VMDK file from the new directory to the VM folder and edit the VM settings again to point it to the VMDK disk in the folder.

You should be able to power on the VM at step 7 itself, however, I advice to take step 8 only to make sure you have all the files together.

Hope this helps. Let me know if you need further assistance.

-Surya

[Roggia]

I stop at step number 6, when I try the command above, the follow error appears

1. vmkfstools -i /vmfs/volumes/datastore1/Windows\ 2008\ server\ 192.168.1.9\ -flat.vmdk /vmfs/volumes/datastore1/new/Windows\ 2008\ server\ 192.168.1.9\ -flat.vmdk

DiskLib_Check() failed for source disk The file specified is not a virtual disk (15).

Maybe I did something wrong,

wait for more

thanks for now

Daniel Roggia

PS: The problem was space disk. I´m solving this problem

[SuryaVMware · Accepted solution]

You need to run it on the vmdk file not the -flat vmdk. However, with step 6 i should have been more clear you need to copy both the files .vmdk and -flat vmdk.

The .vmdk file is the data descriptor file where as the -flat vmdk is the actual file that holds the data for the VM. Your Virtual Machine will poin to the .vmdk file and the .vmdk file will have the reference to the -flat.vmdk file.

-Surya