[Qemu-discuss] RES: ESX 4.1 does not recognize the converted VMDK file

[Flavio Borup]

Using FC/b win Windows, and comparing two converted .VMDK files (first one
using parameter monolithicFlat and the second one, not), the diff is:


Comparing files [monolithicFlat].vmdk and defaul-non-monolithicFlat.VMDK
00000000: EB 4B
00000001: 48 44
00000002: 90 4D
00000003: 10 56
00000004: 8E 01
00000005: D0 00
00000006: BC 00
00000008: B0 03
00000009: B8 00
0000000C: 8E 00
0000000D: D8 00
0000000E: 8E 20
0000000F: C0 08
00000010: FB 00
00000011: BE 00
00000013: 7C 00
00000014: BF 80
00000016: 06 00
00000017: B9 00
00000019: 02 00
0000001A: F3 00
0000001B: A4 00
0000001C: EA 01
0000001D: 21 00
0000001E: 06 00
00000021: BE 00
00000022: BE 00
00000023: 07 00
00000024: 38 14
00000025: 04 00
00000026: 75 00
00000027: 0B 00
00000028: 83 00
00000029: C6 00
0000002A: 10 00
0000002B: 81 00










Comparing files HDD1.vmdk and HDD2.VMDK, both files, from a fully functional
VM, cretaed by ESX

000001B8: 15 C9
000001B9: 87 F0
000001BA: B2 FB
000001BB: D5 AA
000001BE: 80 00
000001C3: DF FE
000001C4: 13 FF
000001C5: 0C FF
000001CB: 20 E8
000001CC: 03 7F
000001CD: 00 0C
000001CF: DF 00
000001D0: 14 00
000001D1: 0C 00
000001D2: 07 00
000001D3: FE 00
000001D4: FF 00
000001D5: FF 00
000001D7: 28 00
000001D8: 03 00
000001DB: D0 00
000001DC: 3C 00
000001DD: 06 00
00000E10: 8F 1D
00000E11: BA 18
00000E12: 01 2C
00000E13: 62 0F
00000E30: 2B B0
00000E31: DF C8
00000E32: 45 D2
00000E33: AD BE
00000E34: 5B 2A
00000E35: D7 C3
00000E36: 92 51
00000E37: 4B 49
00000E38: 9F A5
00000E39: E4 DA
00000E3A: 89 40
00000E3B: 1A B8
00000E3C: 22 31
00000E3D: 67 B6

-----Mensagem original-----
De: Fam Zheng [mailto:address@hidden
Enviada em: quarta-feira, 21 de outubro de 2015 10:58
Para: Flavio Borup <address@hidden>
Cc: address@hidden
Assunto: Re: [Qemu-discuss] ESX 4.1 does not recognize the converted VMDK
file

On Wed, 10/21 08:02, Flavio Borup wrote:
> ESX 4.1 does not recognize the converted VMDK file
>
>
>
> I´ve converted a VHDX file to .VMDK file with the following command:
>
>
>
>
>
> qemu-img convert -f vhdx "source.vhdx" -o subformat=monolithicFlat -O
> vmdk "destination.vmdk"
>
>
>
>
>
> I want a fixed size .VMDK, so, mission accomplished, a 16GB (dynamic)
> .VHDX turned into a 65 GB .VMDK file (the actual size of the disk)
>
>
>
> In vSpehere client, the file was uploaded to the storage (2 files, a
> little “flat” file and another 65 GB .VMDK file)
>
>
>
>
>
> But...
>
>
>
> The vSphere client does not recognize anything in the directory,
> showing an empty folder. I tried to move the converted .VMDK files to
> another directory with other regular .VMDK files, all files were seen,
> expect the converted .VMDK file.
>

Can you create a working monolithicFlat file with vSphere and compare it
with the converted one? vSphere is known to be picky on some fields in
undocumented way..

Fam

-- 
O conteúdo desta mensagem e de seus anexos é de uso restrito e 
confidencial, sendo o seu sigilo protegido por lei. 
Estas informações não podem ser divulgadas sem prévia autorização escrita. 
Se você não é o destinatário desta 
mensagem, ou o responsável pela sua entrega, apague-a imediatamente e avise 
ao remetente, respondendo a esta mensagem.
Alertamos que esta mensagem transitou por rede pública de comunicação, 
estando, portanto, sujeita aos riscos inerentes
a essa forma de comunicação. A QUEIROZ GALVÃO ÓLEO E GÁS S.A não se 
responsabiliza por conclusões, opiniões, ou outras
informações nesta mensagem que não tenham sido emitidas por seus 
integrantes. 
O recebimento de mensagens na sua caixa postal corporativa pode ocorrer em 
horário diverso ao desenvolvimento das atividades funcionais. O fato de ter 
acesso ao recurso , por si só,não representa solicitação a trabalhar.

This e-mail and any attachments are confidential and may also be 
privileged. If you are not the named recipient, please 
notify the sender immediately and do not disclose the contents to any other 
person, use it for any purpose, store or copy
the information. In the event of any technical difficulty with this email, 
please contact the sender. 
A QUEIROZ GALVÃO ÓLEO E GÁS S.A. is not responsible for conclusion, 
opinions or any kind of information in this
message that doesn’t come from our personnel.
The incoming mensagens on your corporate mailbox may occur in a different 
time of the development of functional activites. The access to the resource 
do not mean that are pending working request.