convert vmware image to virtual pc image

Discussion in 'Virtual PC' started by Stijn Pauwels, Feb 13, 2004.

  1. Is there a tool or convertor to convert allready made
    WMware images/sessions to Virtual pc images?
    So we do not need to restart the whole installations that
    were made with WMware?
    We want to use starting with Virtual PC.
     
    Stijn Pauwels, Feb 13, 2004
    #1
    1. Advertisements

  2. Stijn Pauwels

    J.Stone Guest

    I'm looking for the same thing.

    Need to convert existing VMware virtual machines to
    Microsoft Virtual PC.

    Thanks!
     
    J.Stone, Feb 13, 2004
    #2
    1. Advertisements

  3. Stijn Pauwels

    lallous Guest

    Hello

    There might be an automated way to do that, however I can think of:
    1)make a share between VMWare and real PC
    2)Install an imaging software in the VMWare and create an image of the
    VMWare harddisk into the real PC

    That way you have an image of the vmware machine on your real PC

    Now install VPC and make a share w/ real PC and then restore the image from
    the real pc to the virtual PC.

    p.s: Perhaps VMWare's hardware configuration and VPC's hardware config are
    not the same thus you might want to reinstall Windows or run setup to update
    its hardware database.

    HTH
    Elias
     
    lallous, Feb 13, 2004
    #3
  4. Stijn Pauwels

    Robert Moir Guest

    Put aside the fact that the machines are virtual for a moment.

    You wish to move an image of an OS on one system to another system with
    different hardware - how would you go about it and what difficulties would
    you expect?
     
    Robert Moir, Feb 13, 2004
    #4
  5. Stijn Pauwels

    Conrad Guest

    It is possible to do. In your VMWare machine uninstall
    the tools and the video adapter (I think we had problems
    with the video adapter). Use a Ghost boot floppy in
    VMWare (I am not sure what NIC driver to use, but it is
    included in Ghost). Then make another floppy for VPC and
    use one of the DEC drivers). Then puch the image into
    the VPC.

    It is not terribly fast but it works. On the first boot
    of the machine, it will be slow (it will redetect all the
    drivers). Also, if you get a processor error in VPC when
    you boot the new machine, turn on/off the ACPI bios
    setting.
     
    Conrad, Feb 13, 2004
    #5
  6. Stijn Pauwels

    Steve Jain Guest

    VMware's VM Tools must be removed from the guest prior to migration.
    Removal of this application removes VMware's proprietary Video Driver
    as well as the current integration features of VMware.

    General Notes on Win98 Migrations

    Windows 98 migrations are relatively easy. Simply ghost the VMware
    Virtual Windows 98 machine and deploy the resulting image to the
    target Virtual PC/Server VM.

    On first boot, the newly ghosted Virtual Machine will redetect and
    load new drivers for the emulated environment.

    General Notes on Windows NT 4 Migrations

    Windows NT migrations are similar to Windows 98 Migrations with the
    following exception:

    The user must manually uninstall the AMD Pcnet NIC and install the DEC
    21x4 NIC driver once Windows NT 4 has loaded.

    General Notes on Windows 2000/XP Migrations

    Windows 2000 and XP are both ACPI enabled operating Systems. Virtual
    PC by default does not have ACPI enabled. After ghosting the Virtual
    PC image, ACPI must be enabled within the guest's emulated BIOS.

    Due to differences between VMware's emulated architecture and Virtual
    PC's, a raw VMware guest ghost image will result in a 0x0017
    inaccessible disk error when the target Virtual PC VM is launched.
    Prior to ghosting the VMware session, the IDE drivers and subsystem
    must be reloaded.

    Ghosting to a Network

    Required Tools for Network Migration using Ghost:

    Ghost boot disk with AMD Pcnet NIC Drivers
    Ghost boot disk with Dec 21x4/Intel 21143 NIC Drivers

    Migrating from VMware



    Preparing the VMware image

    Do to differences in emulated hardware; certain drivers must be
    replaced within a VMware image prior to ghosting. This will allow
    the image to access Virtual PC's emulated hardware after receiving the
    initial Ghost Image.

    This process requires the following:

    " Ghost network boot disk with AMD PCINET driver for the VMware
    session

    " Ghost network boot disk with DEC EtherWorks DE 434-435 driver
    for the Virtual PC Session.

    Removing VM Tools

    1. Launch VMware
    2. Launch selected VMware guest
    3. Remove VMtools from within guest
    4. Reboot Guest

    Replacing Key VMware Drivers

    1. Click START, go to RUN, type in "CMD", hit ENTER
    2. At the command prompt, type in: CD %SystemRoot%\Driver
    Cache\i386
    3. Run the following command lines

    expand driver.cab -f:atapi.sys %SystemRoot%\System32\Drivers
    expand driver.cab -f:intelide.sys %SystemRoot%\System32\Drivers
    expand driver.cab -f:pciide.sys %SystemRoot%\System32\Drivers
    expand driver.cab -f:pciidex.sys %SystemRoot%\System32\Drivers

    Note: If you using Windows 2000, you may want to use spX.cab, where X
    is the highest number listed instead of driver.cab

    4. Create the following merge.reg file by cutting and pasting the
    lines below

    ********* START COPY AFTER THIS LINE *************
    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\primary_ide_channel]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="atapi"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\secondary_ide_channel]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="atapi"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*pnp0600]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="atapi"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*azt0502]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="atapi"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\gendisk]
    "ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
    "Service"="disk"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#cc_0101]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_0e11&dev_ae33]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_0601]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_5513]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1042&dev_1000]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_105a&dev_4d33]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0640]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1097&dev_0038]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0001]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0150]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5215]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5219]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5229]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="pciide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1106&dev_0571]
    "Service"="pciide"
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1222]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="intelide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1230]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="intelide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2411]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="intelide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2421]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="intelide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7010]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="intelide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="intelide"

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7199]
    "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
    "Service"="intelide"

    ;Add driver for Atapi (requires atapi.sys in drivers directory)

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi]
    "ErrorControl"=dword:00000001
    "Group"="SCSI miniport"
    "Start"=dword:00000000
    "Tag"=dword:00000019
    "Type"=dword:00000001
    "DisplayName"="Standard IDE/ESDI Hard Disk Controller"
    "ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
    52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\
    00,73,00,79,00,73,00,00,00

    ;Add driver for intelide (requires intelide.sys in drivers directory)

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IntelIde]
    "ErrorControl"=dword:00000001
    "Group"="System Bus Extender"
    "Start"=dword:00000000
    "Tag"=dword:00000004
    "Type"=dword:00000001
    "ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
    52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,6e,00,74,00,65,00,6c,00,69,\
    00,64,00,65,00,2e,00,73,00,79,00,73,00,00,00


    ;Add driver for pciide (requires pciide.sys and pciidex.sys in drivers
    directory)

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PCIIde]
    "ErrorControl"=dword:00000001
    "Group"="System Bus Extender"
    "Start"=dword:00000000
    "Tag"=dword:00000003
    "Type"=dword:00000001
    "ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
    52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\
    00,2e,00,73,00,79,00,73,00,00,00
    ************ END COPY ABOVE THIS LINE ***************

    5. Merge "merge.reg" into the system by double clicking.
    6. Shut down the VMware guest

    Ghosting the VMware Image

    1. Boot the VMware guest using a Ghost boot disk configured with
    an AMD PCNet NIC driver
    2. Attach to a Ghost Multicast session and dump the image

    Deploying the Image to Virtual PC

    1. Create a new Virtual PC Guest machine
    2. Boot the guest using a ghost boot disk configured with a DEC
    EtherWorks DE 434-435 NIC driver
    3. Attach to a Ghost Multicast session and load the image
    4. Restart the Virtual PC sessions (you may need to configure the
    guest to support ACPI depending on the OS that is being loaded. This
    can be done by accessing the emulated guest BIOS during startup)
    5. Let all devices redetect

    Final Steps

    Once the Virtual Machine loads properly within Virtual PC, simply copy
    the .VHD to the designated location for the Virtual Server .VHDs and
    specify the path within Virtual Server during Virtual Machine
    creation.



    Steve Jain, Microsoft MVP for Virtual PC for Windows
    Website: http://www.essjae.com
     
    Steve Jain, Mar 1, 2004
    #6
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.