problem starting vmware player with the gcc4 compiled disk image

[starsseed]

VMWare Workstation fail when opening then virtual disk image : "File not found: haiku-pre-alpha-gcc4.vmdk"
When I convert the disk with VitualDiskConverter ( ​http://starsseed.free.fr/VirtualDiskConverter.exe ) the virtual machine starts normaly and Haiku boot successfully
The embedded descriptor seems to be correct. May be a problem in the SparseExtentHeader struct

​http://www.haiku-os.org/community/forum/problem_starting_vmware_image#comment-12056

[starsseed]

the tool used to convert the virtual disk

[umccullough]

This appears to only be an issue with the gcc4 versions of the vmware images. Can someone who uses vmware test-build their own and determine if this really an issue with the vmdk header creation, or if it's an issue specifically with the machine doing the builds for the haiku-files.org page (run by Phil)

[svend]

I played around a bit with the GCC4 image and found that it must have something to do with the naming of the vmware disk image or something in the header of it, that I don't know. As soon as the naming of the diskimage differs from "haiku-alpha.vmdk" vmware won't recognize the image. Tested on VMWare Workstation 6.5 build-118166

[svend]

I finally build a vmware-image with gcc4 included and I have the same symptoms as before. If it is named different than haiku.vmdk it is not recognized by vmware.

[mmadia]

Replying to svend:

I finally build a vmware-image with gcc4 included and I have the same symptoms as before. If it is named different than haiku.vmdk it is not recognized by vmware.

Correct, the .vmdk must use the exact filename, as specified in the ReleaseBuildProfiles or UserBuildConfig.

ticket #4519 includes updated .vmx files. one for "haiku.vmdk" and another for 'haiku-alpha.vmdk' Some additional changes as well.

I'm uncertain if this should be closed-->invalid or if additional steps are needed.

[starsseed]

• my .vmx file references the virtual disk "haiku-pre-alpha-gcc4.vmdk"
  
• the file name of the virtual disk is "haiku-pre-alpha-gcc4.vmdk"
  
• the internal name of the virtual disk is "haiku-pre-alpha-gcc4.vmdk" in the

descriptor header

• everything seems to be correct in the descriptor header, but something seems to be different in the SparseExtentHeader struct

for me the vmware error message is inacurate. the problem can comes from anything but the filename.

[svend]

As stated I build this image on my own and created a new VM and therefore a new .vmx file. But the result stays the same. The .vmx references the correct disk image, the names are correct. I looked at the code that creates the vmdk and I think the creation of the uuid can be a problem. I took a quick look but I'm not sure wether the filename is included. I'll take a look at it when I'm at home again.

[svend]

I looked further at it, the thing with the UUID was the wrong direction I think. I build a new image and set another name in the build file. A long as the name stays the same as given in the buildfile the image is recognized by vmware. If the name is changed to anything else it won't be recognized. I think the problem with the gcc4 image is that it is build with another name an is then renamed. Which somehow breaks something. At least changing the name in the buildfile will fix the problem in a user point of view.

[starsseed]

Fixed

it works well now.

please close this ticket.

[stippi]

Thanks for the update!