Announcement

Collapse
No announcement yet.

VMware server 2.0 virtual machine move (to another machine) fault

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • VMware server 2.0 virtual machine move (to another machine) fault

    Hi guys,

    I have problem to move/copy vmware Server 2.0 vm from one physical server to another.

    Orig physical server: Intel 1530CLR server with WinXP x64 Pro installed.
    Destination server: Intel 1530AHLX server with WinServer 2003 R2 x64 installed.
    On both servers VMware server 2.0 installed. VM's OS is RHEL ES 4.4 32bit.

    The VM works perfectly on the orig server, but I have to move it to another machine. I switched off the VM, copied the whole directory to the same path on the destination server. Then I'm trying to add the VM in VMware server 2.0.
    I'm receiving the following error:

    The selected virtual machine is not recognized on this system. The cause of this problem may be that the virtual machine's .vmx file is corrupted, or that the virtual machine version is newer than is recognized by the host. You can remove the virtual machine from the inventory if you believe that it is not recoverable.Click the link below to remove the virtual machine from the inventory.Remove Virtual MachineTo help diagnose the issue, you can check the virtual machine files at their last known location: "[Virtual Machines] VSTESTS/VSTESTS.vmx".


    Another thing which I tried to do is to create new VM and to attach the .vmdk file.. but another error here: "The selected file is not a valid virtual disk file. Please choose a different one"..


    However, I uninstalled (on the destination server) the VMware server, and installed VMware player - and hooray!.. the VM is running.

    It's not a specific Virtual Machine, because I tried to copy another two VMs, and same result here..

    So, the conclusion is that it's not a hardware fault (it works on VMware Player), but some annoying configuration miss.

    I have these files within the VM folder:
    ILLINUXVS01.nvram
    ILLINUXVS01.vmdk
    ILLINUXVS01.vmsd
    ILLINUXVS01.vmxf
    ILLINUXVS01-flat.vmdk
    vmware-0.log
    vmware-1.log
    vmware-2.log
    vmware.log
    VSTESTS.vmsd
    VSTESTS.vmx
    VSTESTS.vmxf

    This is the content of VSTESTS.vmx file:
    .encoding = "windows-1255"
    config.version = "8"
    virtualHW.version = "7"
    floppy0.present = "FALSE"
    mks.enable3d = "TRUE"
    pciBridge0.present = "TRUE"
    pciBridge4.present = "TRUE"
    pciBridge4.virtualDev = "pcieRootPort"
    pciBridge4.functions = "8"
    pciBridge5.present = "TRUE"
    pciBridge5.virtualDev = "pcieRootPort"
    pciBridge5.functions = "8"
    pciBridge6.present = "TRUE"
    pciBridge6.virtualDev = "pcieRootPort"
    pciBridge6.functions = "8"
    pciBridge7.present = "TRUE"
    pciBridge7.virtualDev = "pcieRootPort"
    pciBridge7.functions = "8"
    vmci0.present = "TRUE"
    nvram = "ILLINUXVS01.nvram"
    virtualHW.productCompatibility = "hosted"
    ft.secondary0.enabled = "TRUE"
    tools.upgrade.policy = "upgradeAtPowerCycle"
    powerType.powerOff = "soft"
    powerType.powerOn = "hard"
    powerType.suspend = "hard"
    powerType.reset = "soft"
    displayName = "VSTESTS"
    extendedConfigFile = "VSTESTS.vmxf"
    memsize = "512"
    ide0:0.present = "TRUE"
    ide0:0.fileName = "ILLINUXVS01.vmdk"
    ide0:0.writeThrough = "TRUE"
    ide1:0.present = "TRUE"
    ide1:0.fileName = "D:\Virtual Machines\Red Hat Enterprise Linux ES 4 Update 4 (x86)\RHEL4-U4-i386-ES-disc4.iso"
    ide1:0.deviceType = "cdrom-image"
    ide1:0.allowGuestConnectionControl = "FALSE"
    ethernet0.present = "TRUE"
    ethernet0.allowGuestConnectionControl = "FALSE"
    ethernet0.features = "1"
    ethernet0.wakeOnPcktRcv = "FALSE"
    ethernet0.networkName = "Bridged"
    ethernet0.addressType = "generated"
    usb.present = "TRUE"
    ehci.present = "TRUE"
    guestOS = "rhel4"
    uuid.location = "56 4d d2 68 6f 66 55 1f-82 95 43 f3 d6 03 76 70"
    uuid.bios = "56 4d d2 68 6f 66 55 1f-82 95 43 f3 d6 03 76 70"
    vc.uuid = "52 4d 4b 87 e8 36 f2 12-fd 23 1d 81 48 71 f6 5b"
    ide1:0.startConnected = "TRUE"
    ethernet0.generatedAddress = "00:0c:29:03:76:70"
    tools.syncTime = "FALSE"
    ide0:0.redo = ""
    vmotion.checkpointFBSize = "134217728"
    pciBridge0.pciSlotNumber = "17"
    pciBridge4.pciSlotNumber = "21"
    pciBridge5.pciSlotNumber = "22"
    pciBridge6.pciSlotNumber = "23"
    pciBridge7.pciSlotNumber = "24"
    usb.pciSlotNumber = "32"
    ethernet0.pciSlotNumber = "33"
    ehci.pciSlotNumber = "34"
    vmci0.pciSlotNumber = "35"
    ethernet0.generatedAddressOffset = "0"
    vmci0.id = "2040435782"


    Please advise,
    Thanks.

  • #2
    Re: VMware server 2.0 virtual machine move (to another machine) fault

    If you create a new VM and only copy the virtual disk accross, does it mount?
    Gareth Howells

    BSc (Hons), MBCS, MCP, MCDST, ICCE

    Any advice is given in good faith and without warranty.

    Please give reputation points if somebody has helped you.

    "For by now I could have stretched out my hand and struck you and your people with a plague that would have wiped you off the Earth." (Exodus 9:15) - I could kill you with my thumb.

    "Everything that lives and moves will be food for you." (Genesis 9:3) - For every animal you don't eat, I'm going to eat three.

    Comment


    • #3
      Re: VMware server 2.0 virtual machine move (to another machine) fault

      Hi gforceindustries,

      thanks for the reply.

      As I wrote below:

      Another thing which I tried to do is to create new VM and to attach the .vmdk file.. but another error here: "The selected file is not a valid virtual disk file. Please choose a different one"..

      I tried to mount both ILLINUXVS01.vmdk and ILLINUXVS01-flat.vmdk.
      Same error received.

      Comment


      • #4
        Re: VMware server 2.0 virtual machine move (to another machine) fault

        Oops, missed that one.

        Are both host OSes running the same filesystem (presumably NTFS)?

        Are you absolutely sure both installations of VMware are the same version?
        Gareth Howells

        BSc (Hons), MBCS, MCP, MCDST, ICCE

        Any advice is given in good faith and without warranty.

        Please give reputation points if somebody has helped you.

        "For by now I could have stretched out my hand and struck you and your people with a plague that would have wiped you off the Earth." (Exodus 9:15) - I could kill you with my thumb.

        "Everything that lives and moves will be food for you." (Genesis 9:3) - For every animal you don't eat, I'm going to eat three.

        Comment


        • #5
          Re: VMware server 2.0 virtual machine move (to another machine) fault

          Thanks for the reply.
          I found solution for this fault (at least the VM is running now). The problem was in encoding differences within the .vmx and .vmdk files. On the origin host, the VM machines configured with windows-1255, while on the destination host the VM machines configured with windows-1252. I have edited this manually.. and it works! I hope that this is the only change that I have to execute...
          Does anyone know if there's another location where I shall edit this settings? Where from VMware takes this configuration? Is there any manual that explains encoding role in these files?
          Thanks.

          Comment


          • #6
            Re: VMware server 2.0 virtual machine move (to another machine) fault

            My first time - Hello everyone.

            Same problem:

            Build VM machine when Host is XP SP2.
            Shut down VM Machine and copy files to other host that is Win server 2003 -R2 SP2.
            Add to Data store -OK
            Add machine - No, wrote something about "invalid machine"

            Then I edited the VMX file as you wrote and it woked.
            But VMDK was the problem now.

            You wrote that you edited the VMX and the VMDK, right?
            So how did you edit your VMDK?

            How can I edit a 3.5 Giga file?


            Thanks

            Comment

            Working...
            X