I am assuming that moving a VM built in Fusion to Workstation usually works. But in this example when the Workstation tries to boot the VM it stops on the PXE message "No boot filename received" then "Operating System not found"
Has anyone ever experienced this or know what might be wrong? File permissions maybe? Is there something I should do the vmx to make the system compatible?
The VM OS is Windows Server 2008 (64 bit)
Thanks for any help
The guest isn't seeing a bootable hard disk...
Did you
1 - Shut down the guest OS and VM before copying/moving it, not merely suspend it?
2 - Make sure to copy the ENTIRE VM folder, with all files?
Thanks for answering.
The VM was shutdown but it's possilbe that Fusion VMWare was still running.
The only file that the Fusion creates is an extension of .vmwarevm As far as I know in Fusion when you create a VM there are no folders or other files. Is this a correct assumption? In the Virtual Machine Library, I did a right click on the VM and "Show in Finder" to make sure I had the right file.
Could the problem be that the .vmwarevm needs to be converted for use in Workstation? I thought I read that it was a simple file copy to the PC for sharing.
Thanks for any help
Kevin
kagatone wrote: The only file that the Fusion creates is an extension of .vmwarevm
The container with the .vmwarevm extension is a Package on a Mac and is really nothing more then a File Folder which contains the actual files that comprise the Virtual Machine. With the Virtual Machine shutdown from within the Guest OS, not suspended and VMware Fusion closed one should be able to copy the Package to another location and run it with another VMware product like VMware Player or VMware Workstation.
Could the problem be that the .vmwarevm needs to be converted for use in Workstation?
Provided the Virtual Hardware Versions are compatible then no conversion should be necessary. BTW VMware Fusion 4.x and VMware Workstation 8.x are compatible.
It turns out that the Windows hosts machine bios did not have VT enabled (Virtualization Technology) We switched that on (again from the bios) and it worked.
Thanks everyone for your suggestions.