Problem when converting a VM

[tthibus]

Hello everybody !

First thing: it's my first message here so I hope I will do it right; and for the moment I am not sure of posting in the good section.

If it not the case, just let me informed.

So, my problem is this one: I convert my primary (and alone) AD server from P2V with Converter Standalone 4.3.0. No problem happend during the conversion. Because I had no other server, I choose a conversion to workstation VM.

Then I install on the server (A Dell PowerEdge T300) VMWare ESXi vSphere 5.0 and it works good.

I install also in a VM (Windows Server 2008 R2) vCenter Server 5.0.

Now, when I want to convert the AD Server into a infrastructure machine, impossible. Each time I have this error: "Invalid fault".

The VM was located on a NAS configured with NFS, I moved it to my own computer (where I run the converter), and the same thing happened.

I posted the logs it let me download. I hope somebody will be able to help me.

Thanks for your help,

Trevis

[helltejas]

you can't install vCenter on ADC...i think your problem happens because of that only

check out vmware bestpractice paper.

[AndreTheGiant]

Welcome to the community.

If if is already a VM, have you tried to copy (with the VM powered off) all file files in a datastore and add the vmx file to the inventory?

[Rahim_from_PSPL]

Hello Trevis,

Welcome to community.

lets start the trubleshooting step by step.

1) Try to reboot the machine first & then start the conversion.

2) mean time try to upload the Workstation VM on your ESXI host datastore & add the VM to inventory & update the VMtool.

Thanks.

[tthibus]

Thank you guys for your answers.

For the moment the problem is still there but here are some informations:

I restart the ESXi host, and of course the vCenter Server, but also my own personal computer where I use the Standalone converter.

I move the VM into the local datastore (3 SCSI in RAID 5 mode)k like this no network problem.

Browsing this datastore, I add the VM in the inventory -> OK

I tried to start the VM wut with this error:

Une erreur inattendue a été reçue de l'hôte ESX lors de la mise sous tension de VM vm-41.
Échec d'activation du module DevicePowerOn.
Impossible de créer un périphérique SCSI virtuel pour scsi0:0, '/vmfs/volumes/4f8026d9-cfe53fdc-528e-002219a226d8/Machines virtuelles/SERVER-COMPANY.com/SERVER-COMPANY.com.vmdk'
Impossible d'ouvrir le disque scsi0:0 : le type du disque 7 n'est pas pris en charge ou n'est pas valide. Assurez-vous que le disque a été importé.

Yes it's a french version (because I'm french ).

I should be traduced by :

Unnattended error received from the ESX host when starting VM vm-41.

Failure of activation DevicePowerOn module.

Impossible to create a virtual SCSI device for scsi0:0, '/vmfs/volumes/4f8026d9-cfe53fdc-528e-002219a226d8/Machines virtuelles/SERVER-COMPANY.com/SERVER-COMPANY.com.vmdk'

Impossible to open the disk scsi0:0: the disk 7 type is not supported or not valid. Be sure it have been imported.

So that's why I try to convert the VM to an infrastructure one.

I tried to convert a copy of the VM in my local disk (on my own computer) into the vCenter Server and it doesn't work (I tried the both VM version : 7 and 8).

I tried to convert a copy of the VM in my local disk (on my own  computer) into the ESXi Server and it doesn't work too (I tried the both  VM version : 7 and 8).

Be informed that:

I canot upgrade VMTools because the VM doesn't start.

The vCenter Server is install in a VM machine with Windows Server 2008 R2 but there is no role no this server (AD, DNS or other).

Thanks for your help,

Trevis.

[continuum]

> I tried to convert a copy of the VM in my local disk (on my own computer) into the vCenter Server and it doesn't work

"it does not work" is not really helpful - please post exact error messages

[alwaysnodowntim]

Please refer to kb article,  kb.vmware.com/kb/1028943.  Let me know if this doesn't work or you need help.

[alwaysnodowntim]

Also, I did notice that you said that you chose to convert the vm to a workstation.  This would be a hosted product format of vmware workstation. Try importing the server.   The details are below.

You cannot use a vSphere Client to migrate virtual machines created with VMware Workstation or VMware GSX Server into your ESX system. However, you can use the vmkfstools -I command to import the virtual disk into your ESX system and then attach this disk to a new virtual machine you create in ESX.

You must import the virtual disk first because you cannot power on disks exported in

2gbsparse format on an ESX host.

Procedure

1.	Import a Workstation or GSX Server disk into your /vmfs/volumes/myVMFS/ directory or any subdirectory.
2.	In the vSphere Client, create a new virtual machine using the Custom configuration option.
3.	When you configure a disk, select Use an existing virtual disk and attach the Workstation disk you imported.

[tthibus]

Hi !

When I say : "It doesn't work", I mean that I stay in the same situation with the same messages.

I will be more explicit next time..

Thanks

[tthibus]

Hi everyone.

Thank you for your answers.

Excuse my silence since these days but I was really (soooo) busy.

Because I didn't find enough quickly the solution to this problem (and despite your precious help), and because I HAD to keep going, I have done

differently.

Now I don't have problem anymore (for the moment?!) and want to REALLY thank all of you who tried to help me.

I really appreciate.

Hope one day I could help back.

See you,

Trévis

[Courvoisier]

Dear Thibus,

If we had your solution here, it would avoid some people as me to remake the same questions...

I have the same error

(Impossible d'ouvrir le disque scsi0:0 : le type du disque 7 n'est pas pris en charge ou n'est pas valide. Assurez-vous que le disque a été importé.), but not the solution.

I think (not experimented by me to today), that VMware communities is not only for questions, but also for solutions...

[UmeshAhuja]

Hi,

Might solve the problem, Try to convert the VM through VMware Converter 5.0.0 build-470252.

[continuum]

> Impossible d'ouvrir le disque scsi0:0 : le type du disque 7 n'est pas  pris en charge ou n'est pas valide. Assurez-vous que le disque a été  importé

use vmkfstools like this
vmkfstools -i uploaded.vmdk final.vmdk

this will fix the "type7 is not supported" problem

[Courvoisier]

Thank you for your answers !

Actually, I didn't know that I had to convert the file in its extension itself; I tried to convert in .ovf (on the server with the command line)...

seemed to be completed, but didn't work.

I thought I would have convert it in .vmfs but did not try it.

I go from the idea that your solution converting the extension in itself is right, but did not try it.

Finally, and fortunately, I had with my .vmdk (StressLinux 0.7.106, for stresstests) a very light .vmx file (!), so light, that I did not see at the moment that it could be used for converting it in an exploitable file.. ..whose I cannot see the extension. Think it is effectively .vmdk (or .dsk, or others I cannot see on the proposed choice), the proposed ones by vCenter, selecting the datastore.

Hope this can help (convert a .vmx).

I'll try the solution of converting the extension in itself when I have a moment .

Thank you again.

[continuum]

sorru - I have absolutely no idea what you are talking about

changing extensions ???
ovf ???

not sure how that is related ..

[Vijay_JS]

Hi,

Try the conversion VMware Vcenter convertor Standalone server 5.0.0. build 470252. I had the same issue and fixed with this build.

Thanks

Vijay.J 

[tthibus]

Hi everyone.

Last time I have been not enough sharp in my message.

I just told that "I HAD to keep going" without tell how.

First thing: the VM with the conversion problem was a domain server used in a little company (1 server / 4 computers). I also had to change the domain name.

I wanted to virtualize the primary domain server, let it on the network and add a new server (but secondary) and migrate the computers to the new domain.

But with my problem of conversion, I didn't have enough time to resolve them.

So I choose to change the domain and migrate all the computers one by one. It was less "clean", but it worked.

It is this way I didn't solve my problem but I bypassed it.

I felt that a few hours to migrate all the computers to the new domain, with a new server was better than search during hours to solve my conversion problem.

One more time, thanks to all of you for help.

I hope the ones who will find this message will also find the answer.

Bye,

Trévis.

[CERKYR]

Hello,

Then, what is the proposal to fix this problem ?
I hava the same problem with the version 6.5 : VMconverter and ESXi.