Converting VMWARE images

Discussion in 'Parallels Transporter' started by dominic.giles, Dec 4, 2006.

  1. dominic.giles

    dominic.giles

    Messages:
    9
    Hi.

    Most VMWare disk images will come on a number of disks... and feature a VMX file as well.

    The transporter client seems designed only to "transport" a single vmdk file. Does this mean that this process needs to be restarted for each vmdk device....

    Does the transporter ignore all of the seetings in the VMX file, I realise many of them are specific to a VM setup, but some are not (disk caching etc).

    Im afraid I cant test this since Transporter fails straight away after selecting the first of several vmdk files. It does work selecting the second etc.

    And finally why do I need a Boot disk.. This is impracticle in many situations... I realise the licensing issues (Windows?) but I use it for Linux images where I know longer have a boot disk.

    Thanks

    Dom.
     
  2. dominic.giles

    dominic.giles

    Messages:
    9
    Some Progress on the VMWare frond anyway

    So... I have made a little progress

    I used the VMWare diskmanger utility to merge all of my 2GB vmware disk images into a single disk... No problem so far. It runs fine under vmware.

    I then ran compressor on it which made it through the first stage. It then asks me if I want to make the image bootable which I do... It then attempted to complete the final stage. It correctly identified the image as an XP image and got to It got to about 50% of the way through when it said that it had failed and aborted the transport.

    The disk image is just over 7GB in size and is for XP service pack 2

    I've tried this twice. Same result same place. I don't appear to get any stack traces I can post...

    Should I just forget about this for a while or is there something else I can do?

    Dom.
     
  3. ajwans

    ajwans

    Messages:
    24
    What I did to convert my VMWare images to Parallels (they were win2k and winXP) was
    to boot the VMWare image and install the transporter agent, then connect to it from
    Transporter on the Mac and it sucks it down into a Parallels image.

    It was the only way I could convert it because my VMWare images were guests to a Linux
    host so I had no way to access the image files from a win32 platform.

    Worked well for me.
    andy
     
  4. dominic.giles

    dominic.giles

    Messages:
    9
    Working..

    I've upgraded to the latest build and tried again...

    This time using the mac os version of transporter... This failed again in the same place (must be something to do with my image) however I created a new parallels vm using the disk image that had been converted... (it asks you during the process if you'd like to use an exisiting disk)

    Parallels created a new machine and allowed me to boot it up (which worked fine)...

    Im not sure that this isn't an issue with my VMware image... but it works fine now...

    Dom.
     
  5. Andrew @ Parallels

    Andrew @ Parallels Parallels Developers

    Messages:
    1,507
    To convert multiple part VMware disk image you should choose 1-st one. Parallels Transporter will convert whole disk and merge it into single Parallels HDD image.
     
  6. tangential

    tangential Bit Poster

    Messages:
    50
    What if your vmware is linux, not windows host

    I have images I built under vmware on linux.

    Can I convert those to parallels?

    What would be the proper steps?

    Thanks

    John
     
  7. jp20r

    jp20r

    Messages:
    13
    Andrew,
    need yr advice :
    i used 1970 w/ W 2000, no problems
    today i tried 3106. it doesnt work w/ W 2000 (?), but after several install it works perfect w/ XP.
    my question: unedr XP I dont have neither the applications nor the documents that I have under W2000. "C" in XP is empty, while evrything is in "C" under W2000. How do I use Transporter to transfer all datas from C(W2000) to C(XP). I've gone thru the pdf but still confused on waht are the right steps.
    can u help ?
    thks jpr@nyc.com
     
  8. lhotka

    lhotka

    Messages:
    4
    And how do we tell which is the first disk?

    Here's all the files in the VM Image

    winxppro.vmx
    winxppro.vmsd
    winxppro.nvram
    winxppro-Snapshot5.vmsn
    winxppro-Snapshot4.vmsn
    winxppro-Snapshot3.vmsn
    winxppro-Snapshot1.vmsn
    WinXP-000022-cl1-000009-cl1.vmdk.READLOCK
    WinXP-000022-cl1-000009-cl1.vmdk
    WinXP-000022-cl1-000009-cl1-s016.vmdk
    WinXP-000022-cl1-000009-cl1-s015.vmdk
    WinXP-000022-cl1-000009-cl1-s014.vmdk
    WinXP-000022-cl1-000009-cl1-s013.vmdk
    WinXP-000022-cl1-000009-cl1-s012.vmdk
    WinXP-000022-cl1-000009-cl1-s011.vmdk
    WinXP-000022-cl1-000009-cl1-s010.vmdk
    WinXP-000022-cl1-000009-cl1-s009.vmdk
    WinXP-000022-cl1-000009-cl1-s008.vmdk
    WinXP-000022-cl1-000009-cl1-s007.vmdk
    WinXP-000022-cl1-000009-cl1-s006.vmdk
    WinXP-000022-cl1-000009-cl1-s005.vmdk
    WinXP-000022-cl1-000009-cl1-s004.vmdk
    WinXP-000022-cl1-000009-cl1-s003.vmdk
    WinXP-000022-cl1-000009-cl1-s002.vmdk
    WinXP-000022-cl1-000009-cl1-s001.vmdk
    WinXP-000022-cl1-000009-cl1-000004.vmdk.WRITELOCK
    WinXP-000022-cl1-000009-cl1-000004.vmdk
    WinXP-000022-cl1-000009-cl1-000004-s016.vmdk
    WinXP-000022-cl1-000009-cl1-000004-s015.vmdk
    WinXP-000022-cl1-000009-cl1-000004-s014.vmdk
    WinXP-000022-cl1-000009-cl1-000004-s013.vmdk
    WinXP-000022-cl1-000009-cl1-000004-s012.vmdk
    WinXP-000022-cl1-000009-cl1-000004-s011.vmdk
    WinXP-000022-cl1-000009-cl1-000004-s010.vmdk
    WinXP-000022-cl1-000009-cl1-000004-s009.vmdk
    WinXP-000022-cl1-000009-cl1-000004-s008.vmdk
    WinXP-000022-cl1-000009-cl1-000004-s007.vmdk
    WinXP-000022-cl1-000009-cl1-000004-s006.vmdk
    WinXP-000022-cl1-000009-cl1-000004-s005.vmdk
    WinXP-000022-cl1-000009-cl1-000004-s004.vmdk
    WinXP-000022-cl1-000009-cl1-000004-s003.vmdk
    WinXP-000022-cl1-000009-cl1-000004-s002.vmdk
    WinXP-000022-cl1-000009-cl1-000004-s001.vmdk
    WinXP-000022-cl1-000009-cl1-000003.vmdk.READLOCK
    WinXP-000022-cl1-000009-cl1-000003.vmdk
    WinXP-000022-cl1-000009-cl1-000003-s016.vmdk
    WinXP-000022-cl1-000009-cl1-000003-s001.vmdk
    WinXP-000022-cl1-000009-cl1-000002.vmdk.READLOCK
    WinXP-000022-cl1-000009-cl1-000003-s006.vmdk
    WinXP-000022-cl1-000009-cl1-000003-s005.vmdk
    WinXP-000022-cl1-000009-cl1-000003-s004.vmdk
    WinXP-000022-cl1-000009-cl1-000003-s003.vmdk
    WinXP-000022-cl1-000009-cl1-000003-s002.vmdk
    WinXP-000022-cl1-000009-cl1-000002-s016.vmdk
    WinXP-000022-cl1-000009-cl1-000003-s011.vmdk
    WinXP-000022-cl1-000009-cl1-000003-s010.vmdk
    WinXP-000022-cl1-000009-cl1-000003-s009.vmdk
    WinXP-000022-cl1-000009-cl1-000003-s008.vmdk
    WinXP-000022-cl1-000009-cl1-000003-s007.vmdk
    WinXP-000022-cl1-000009-cl1-000002-s014.vmdk
    WinXP-000022-cl1-000009-cl1-000003-s015.vmdk
    WinXP-000022-cl1-000009-cl1-000003-s014.vmdk
    WinXP-000022-cl1-000009-cl1-000003-s013.vmdk
    WinXP-000022-cl1-000009-cl1-000003-s012.vmdk
    WinXP-000022-cl1-000009-cl1-000002-s015.vmdk
    WinXP-000022-cl1-000009-cl1-000002.vmdk
    WinXP-000022-cl1-000009-cl1-000002-s013.vmdk
    WinXP-000022-cl1-000009-cl1-000002-s012.vmdk
    WinXP-000022-cl1-000009-cl1-000002-s011.vmdk
    WinXP-000022-cl1-000009-cl1-000002-s010.vmdk
    WinXP-000022-cl1-000009-cl1-000002-s009.vmdk
    WinXP-000022-cl1-000009-cl1-000002-s008.vmdk
    WinXP-000022-cl1-000009-cl1-000002-s006.vmdk
    WinXP-000022-cl1-000009-cl1-000002-s007.vmdk
    WinXP-000022-cl1-000009-cl1-000002-s005.vmdk
    WinXP-000022-cl1-000009-cl1-000002-s004.vmdk
    WinXP-000022-cl1-000009-cl1-000002-s003.vmdk
    WinXP-000022-cl1-000009-cl1-000002-s002.vmdk
    WinXP-000022-cl1-000009-cl1-000002-s001.vmdk
    WinXP-000022-cl1-000009-cl1-000001.vmdk.READLOCK
    WinXP-000022-cl1-000009-cl1-000001.vmdk
    WinXP-000022-cl1-000009-cl1-000001-s016.vmdk
    WinXP-000022-cl1-000009-cl1-000001-s015.vmdk
    WinXP-000022-cl1-000009-cl1-000001-s014.vmdk
    WinXP-000022-cl1-000009-cl1-000001-s013.vmdk
    WinXP-000022-cl1-000009-cl1-000001-s012.vmdk
    WinXP-000022-cl1-000009-cl1-000001-s011.vmdk
    WinXP-000022-cl1-000009-cl1-000001-s010.vmdk
    WinXP-000022-cl1-000009-cl1-000001-s009.vmdk
    WinXP-000022-cl1-000009-cl1-000001-s008.vmdk
    WinXP-000022-cl1-000009-cl1-000001-s007.vmdk
    WinXP-000022-cl1-000009-cl1-000001-s006.vmdk
    WinXP-000022-cl1-000009-cl1-000001-s005.vmdk
    WinXP-000022-cl1-000009-cl1-000001-s004.vmdk
    WinXP-000022-cl1-000009-cl1-000001-s003.vmdk
    WinXP-000022-cl1-000009-cl1-000001-s002.vmdk
    vmware-2.log
    WinXP-000022-cl1-000009-cl1-000001-s001.vmdk
    vmware.log
    stats32-2
    stats32
    HDrive-000022-cl1-000009-cl1.vmdk.READLOCK
    HDrive-000022-cl1-000009-cl1.vmdk
    HDrive-000022-cl1-000009-cl1-s013.vmdk
    HDrive-000022-cl1-000009-cl1-s007.vmdk
    HDrive-000022-cl1-000009-cl1-s002.vmdk
    HDrive-000022-cl1-000009-cl1-s001.vmdk
    HDrive-000022-cl1-000009-cl1-s003.vmdk
    HDrive-000022-cl1-000009-cl1-000004.vmdk
    HDrive-000022-cl1-000009-cl1-000004-s013.vmdk
    HDrive-000022-cl1-000009-cl1-000004-s012.vmdk
    HDrive-000022-cl1-000009-cl1-000004-s011.vmdk
    HDrive-000022-cl1-000009-cl1-000004-s010.vmdk
    HDrive-000022-cl1-000009-cl1-000004-s009.vmdk
    HDrive-000022-cl1-000009-cl1-000004-s008.vmdk
    HDrive-000022-cl1-000009-cl1-000004-s007.vmdk
    HDrive-000022-cl1-000009-cl1-000004-s006.vmdk
    HDrive-000022-cl1-000009-cl1-000004-s005.vmdk
    HDrive-000022-cl1-000009-cl1-000003.vmdk
    HDrive-000022-cl1-000009-cl1-000003-s012.vmdk
    HDrive-000022-cl1-000009-cl1-000003-s009.vmdk
    HDrive-000022-cl1-000009-cl1-000003-s013.vmdk
    HDrive-000022-cl1-000009-cl1-000003-s008.vmdk
    HDrive-000022-cl1-000009-cl1-000003-s007.vmdk
    HDrive-000022-cl1-000009-cl1-000003-s006.vmdk
    HDrive-000022-cl1-000009-cl1-000003-s005.vmdk
    HDrive-000022-cl1-000009-cl1-000004-s003.vmdk
    HDrive-000022-cl1-000009-cl1-000004-s002.vmdk
    HDrive-000022-cl1-000009-cl1-000003-s004.vmdk
    HDrive-000022-cl1-000009-cl1-000003-s003.vmdk
    HDrive-000022-cl1-000009-cl1-000003-s001.vmdk
    HDrive-000022-cl1-000009-cl1-000002.vmdk.READLOCK
    HDrive-000022-cl1-000009-cl1-000003-s002.vmdk
    HDrive-000022-cl1-000009-cl1-000003-s011.vmdk
    HDrive-000022-cl1-000009-cl1-000002.vmdk
    HDrive-000022-cl1-000009-cl1-000002-s012.vmdk
    HDrive-000022-cl1-000009-cl1-000003-s010.vmdk
    HDrive-000022-cl1-000009-cl1-000002-s010.vmdk
    HDrive-000022-cl1-000009-cl1-000002-s011.vmdk
    HDrive-000022-cl1-000009-cl1-000004-s001.vmdk
    HDrive-000022-cl1-000009-cl1-000003.vmdk.READLOCK
    HDrive-000022-cl1-000009-cl1-000002-s008.vmdk
    HDrive-000022-cl1-000009-cl1-000002-s003.vmdk
    HDrive-000022-cl1-000009-cl1-000002-s002.vmdk
    HDrive-000022-cl1-000009-cl1-000002-s001.vmdk
    HDrive-000022-cl1-000009-cl1-000001.vmdk.READLOCK
    HDrive-000022-cl1-000009-cl1-000001.vmdk
    HDrive-000022-cl1-000009-cl1-000001-s012.vmdk
    HDrive-000022-cl1-000009-cl1-000001-s013.vmdk
    HDrive-000022-cl1-000009-cl1-000001-s011.vmdk
    HDrive-000022-cl1-000009-cl1-000001-s009.vmdk
    HDrive-000022-cl1-000009-cl1-000001-s008.vmdk
    HDrive-000022-cl1-000009-cl1-000001-s007.vmdk
    HDrive-000022-cl1-000009-cl1-000001-s006.vmdk
    HDrive-000022-cl1-000009-cl1-000001-s005.vmdk
    HDrive-000022-cl1-000009-cl1-000001-s004.vmdk
    HDrive-000022-cl1-000009-cl1-000001-s003.vmdk
    HDrive-000022-cl1-000009-cl1-000001-s002.vmdk
    HDrive-000022-cl1-000009-cl1-000001-s001.vmdk
    HDrive-000022-cl1-000009-cl1-000004-s004.vmdk
    564d7dd7-000b-f70e-5a35-51a9476db18a.vmem.WRITELOCK
    HDrive-000022-cl1-000009-cl1-000001-s010.vmdk
    HDrive-000022-cl1-000009-cl1-000002-s006.vmdk
    HDrive-000022-cl1-000009-cl1-000002-s005.vmdk
    564d7dd7-000b-f70e-5a35-51a9476db18a.vmem
    HDrive-000022-cl1-000009-cl1-000002-s004.vmdk
    HDrive-000022-cl1-000009-cl1-s011.vmdk
    HDrive-000022-cl1-000009-cl1-s009.vmdk
    SDPDemoScript.doc
    HDrive-000022-cl1-000009-cl1-s008.vmdk
    vmware-0.log
    HDrive-000022-cl1-000009-cl1-000004.vmdk.WRITELOCK
    stats32-0
    HDrive-000022-cl1-000009-cl1-s006.vmdk
    HDrive-000022-cl1-000009-cl1-s005.vmdk
    HDrive-000022-cl1-000009-cl1-s004.vmdk
    HDrive-000022-cl1-000009-cl1-000002-s013.vmdk
    HDrive-000022-cl1-000009-cl1-s012.vmdk
    HDrive-000022-cl1-000009-cl1-s010.vmdk
    vmware-1.log
    stats32-1
    HDrive-000022-cl1-000009-cl1-000002-s007.vmdk
    HDrive-000022-cl1-000009-cl1-000002-s009.vmdk
     

Share This Page