Virtual Machine to Physical Machine Migration (V2P
Contents
1. drivers Perc 4 symmpi inf Dell PERC 4 im LSI Logic 1020 1030 Driver symmpi tag 10 VMWARE TECHNICAL NOTE vmware Updating the Hal in the sysprep inf File If the target system requires a different HAL hardware abstraction layer than the source system a line can be included in the Unattended section of the sysprep inf file That is if the virtual machine is a multi processor and the target machine is a single processor and this information is required to align the number of processors To change from a uni processor source virtual machine to a multi processor target system add the line Unattended UpdateHAL ACPIAPIC_MP windir inf hal inf To change from a multi processor source virtual machine to a uni processor target system 1 Add the line Unattended UpdateHAL ACPIAPIC_UP SystemDrive Sysprep i386 Uniproc Mp2up inf 2 Copy the uni processor files from the Windows 2000 product CD to the Sysprep distribution folder For example copy from the directory SOEMS 1 Sysprep i386 Uniproc The files to copy are as follows Mp2up inf Mp2up cat Kernel32 dl Ntdll dll Win32k sy_ Winsrv dl_ You do not need to expand the unexpanded files The detection does this automatically when needed 3 Ifa service pack updates these files the updated files need to be copied into the folder Running Sysprep Run Sysprep from the directory in which it was copied This prepares the image f2. format for txtsetup oem General format section key valuel value2 The hash introduces a comment d d Strings with embedded spaces commas or hashes should be double quoted Disks This section lists all disks in the disk set lt description gt is a descriptive name for a disk used when prompting for the disk lt tagfile gt is a file whose presence allows setup to recognize that the disk is inserted lt directory gt is where the files are located on the disk dl Dell PERC 4 im LSI Logic 1020 1030 Driver symmpi tag Defaults This section lists the default selection for each required hardware component If a line is not present for a component the default defaults to the first item in the lt component_name gt section see below lt component_name gt is one of computer display keyboard mouse scsi lt id gt is a unique lt within the component gt string to be associated with an option scsi SYMMPI_2K scsi 16 VMWARE TECHNICAL NOTE vmware This section lists the options available for a particular component id is the unique string for the option description is a text string presented to the user in a menu Xkey name gives the name of the key to be created for the component in HKEY LOCAL MACHINE ControlSet001 Services de db db de dod SYMMP
3. DEV_000F amp SUBSYS_014D1028 C drivers mraid2k Oemsetup inf DELL PERC 3 4 RAID Driver for Windows 2000 mraid2k sys PCINEN 101E amp DEV 1960 amp SUBSYS 05111028 C drivers mraid2k Oemsetu PERC 3 4 RAID Driver for Windows 2000 mraid2k sys PCINVEN 1000 amp DEV 1960 amp SUBSYS 05181028 C drivers mraid2k Oemsetup inf DELL PERC 3 4 RAID Driver for Windows 2000 mraid2k sys 60M 60M 60M 60M INF Adaptec Ultral60 ltra160 Windows2000 FMS4 0 SP5 ltra160 Windows2000 FMS4 0 SP5 INF Adaptec Ultral60 60 Windows2000 FMS4 0 SP5 60 Windows2000 FMS4 0 SP5 60 Windows2000 FMS4 0 SP5 60 Windows2000 FMS4 0 SP5 INF Adaptec Ultral60 INF Adaptec Ultral60 o o o inf V DELL inf WV DELL inf DELL 21 vmware PCINVEN 1000 amp DEV 1960 amp SUBSYS 05201028 C drivers mraid2k Oemsetup inf DELL PERC 3 4 RAID Driver for Windows 2000 mraid2k sys PCINVEN 1011 amp DEV 0046 amp SUBSYS 13649005 C drivers perc2 perc2 inf De PERC 2 2 Si 3 Si 3 Di Windows 2000 Device Drivers raidiskl PCINEN 1011 amp DEV 0046 amp SUBSYS 13659005 C drivers perc2 perc2 inf De PERC 2 2 Si 3 Si 3 Di Windows 2000 Device Drivers raidiskl PCINVEN 1028 amp DEV 0001 amp SUBSYS 00011028 C drivers perc2 perc2 inf De PERC 2 2 Si 3 Si 3 Di Windows 2000 Device Driver
4. Perform your validation tests for the migrated system Validate that the boot ini file is correctly configured on the new physical system Use a text editor of choice and review the file Ensure that at a minimum the following drivers are installed in the physical machine e Network driver s e Disk controller driver s e Graphics driver e Keyboard and mouse drivers e Additional device drivers Search through your appropriate program directory Ensure that the disk on the physical machine has a signature written to it and that the disk is enabled as active A signature is a unique identifier that Windows assigns to a disk typically through the disk manager when you first mount the disk on a computer You can also use an imaging products such as Ghost to assign the signature to any raw target that has not been formatted for Windows Set up network configuration for the physical machine Ensure it is on the same network as the virtual machine Verify SID security identification information as necessary If you plan to have the source virtual machine run on the same network as the new physical machine you need to give the machine different SIDs The mini setup might have set this up During the Setup Manager wizard you have the option to configure the SID for the target physical machine Decide whether to keep the old SID or assign a new one Verify the HAL of the target physical machine corresponds with the HAL of
5. Customer Site Classes Technical Support www vmware com support Documentation all product lines Troubleshooting Hardware Compatibility for ESX Server Knowledge Base Perl API Documentation 14 VMWARE TECHNICAL NOTE vmware Service Contact Points Content Consulting Services consulting vmware com ESX Server Jumpstart Package P2V Migration Package DRB Disaster Recovery and Backup Package V2P Migration Package Server Consolidation Custom Consulting Examples The following sections provide samples of files and driver locations for reference purposes The sample txtsetup oem and smmpi inif file are used as resource for building the sample sysprep inif file Use the source files that correspond to your target hardware to build similar files e Sample txtsetup oem File e Sample smmpi inf File e Sample sysprep inf File VMWARE TECHNICAL NOTE vmware Sample txtsetup oem File txtsetup oem version 2K 3 for SYMMPI Windows drivers Windows 2000 Ok kk kk RRR A AERA ke e ke ke kk R khe ee ke de de kk kk de de ko kk kokk Copyright 2001 LSI Logic Corp All rights reserved This file is property of LSI Logic Corp and is licensed for use as is The receipt of or possession of this file does not convey any rights to modify its contents in whole or in part without the specific written consent of LSI Logic Corp KKK
6. Disk 3 Ethernet 1 Ethernet 2 RAM CPU quantity 1 or 2 CPU processor type GHz Graphics Miscellaneous devices 6 Make a snapshot or backup copy of the virtual machine to be migrated A snapshot feature is provided in your virtualization platform VMware Workstation GSX Server or ESX Server VMWARE TECHNICAL NOTE vmware Migrating a Virtual Machine to a Physical Machine Overview The following sections describe how to migrate a virtual machine running a Microsoft guest operating system to a physical machine Preparing Utilities on the Virtual Machine Creating a Directory for Hardware Drivers on the Virtual Machine Creating the sysprep inf and commandlines txt Files Creating a Mass Storage Section in the sysprep inf File Updating the Hal in the sysprep inf File Running Sysprep Transferring the Virtual Machine Image Booting the Target Physical Machine Installing Additional Drivers Completing the V2P Migration Preparing Utilities on the Virtual Machine To setup Microsoft Sysprep and other setup utilities on the virtual machine 1 Create a Sysprep directory on the virtual machine to be migrated source system For example C sysprep Download Sysprep 1 1 from the Microsoft Web site www microsoft com windows2000 downloads tools sysprep default asp Copy Sysprep 1 1 into the directory you created in step 1 Copy the following addition
7. I 2K Dell PERC 4 im LSI Logic 1020 1030 Driver Windows 2000 symmpi Hardwarelds scsi SYMMPI 2K id id id id PCINVEN 1000 amp DEV 0621 symmpi PCINVEN 1000 amp DEV 0622 symmpi PCINVEN 1000 amp DEV 0624 symmpi PCINVEN 1000 amp DEV 0030 symmpi This section lists the files that should be copied if the user selects a particular component option file type is one of driver port class dll hal inf or detect See below source disk identifies where the file is to be copied from and must match en entry in the Disks section filename is the name of the file This will be appended to the directory specified for the disk in the Disks section to form the full path of the file on the disk Files scsi SYMMPI 2K dl symmpi sys SYMMPI driver inf dl symmpi inf catalog dl symmpi2k cat Config SYMMPI This section specifies values to be set in the registry for particular component options Required values in the services xxx key are created automatically use this section to specify additional keys to be created in services xxx and values in services xxx and services xxx yyy lt key_name gt is relative to the services node for this device If it is empty then it refers to the services node If specified the key is created first lt value_name gt specifies the value to be set within the key lt value_type gt is a string like REG_DWORD See below dE dE de de dE de de
8. MMPI Inst PCINVEN 1000 amp DEV 0030 amp SUBSYS 011A1028 DevDescD1 SYMMPI Inst PCINVEN 1000 amp DEV 0030 amp SUBSYS 01241028 ControlFlags ExcludeFromSelect PCINVEN 1000 amp DEV 0621 ExcludeFromSelect PCINVEN 1000 amp DEV 0622 VMWARE TECHNICAL NOTE vmware ExcludeFromSelect PCINVEN 1000 amp DEV 0624 ExcludeFromSelect PCINVEN 1000 amp DEV 0030 ExcludeFromSelect PCINVEN 1000 amp DEV 0030 amp SUBSYS 01351028 ExcludeFromSelect PCINVEN 1000 amp DEV 0030 amp SUBSYS 011A1028 ExcludeFromSelect PCINVEN 1000 amp DEV 0030 amp SUBSYS 01241028 SYMMPI Inst CopyFiles SYMMPI CopyFiles AddReg SYMMPI AddReg SYMMPI Inst HW DelReg LegacyScsiportValues SYMMPI Inst Services AddService SYMMPI SPSVCINST ASSOCSERVICE SYMMPI Service Inst Miniport EventLog Inst SYMMPI Service Inst ServiceType SERVICE KERNEL DRIVERS StartType SERVICE BOOT STARTS ErrorControl SERVICE ERROR NORMAL ServiceBinary 12 symmpi sys LoadOrderGroup SCSI Miniport AddReg pnpsafe_pci_addreg SYMMPI_CopyFiles symmpi sys 1 SYMMPI AddReg HKLM SYSTEM CurrentControlSet V Services M Symmpi Parameters NDevice DriverParameter Pl aceHolder 0 HKLM SYSTEM VCurrentControlSet NV Services M Symmpi Parameters NDevice MaximumSGList 0x0001 0001 0x41 HKLM SYSTEM CurrentControlSet NV Services M Symmpi Parameters NDevice NumberOfRequests 0x0 0010001 0x80 LegacyScsiportValues HKR Scsiport BusNumber HKR Sc
9. VMWARE TECHNICAL NOTE vmware Virtual Machine to Physical Machine Migration This document describes how to migrate an existing virtual machine and migrate its files and configurations into a physical machine This is also known as virtual to physical migration or V2P migration The migration process uses third party tools to e Prepare the source virtual machine e Transfer the prepared source virtual machine to the hard drive of a physical machine The process for Microsoft guest operating system environments includes the use of Microsoft Sysprep 1 1 and a disk imaging tool such as Symantec Ghost The process for other operating systems involves an imaging tool but does not use Sysprep as this only works for Microsoft operating systems For Linux environments the Kudzu imaging tool is a reasonable choice For information on performing a V2P migration of a Linux guest operating system virtual machine refer to the documentation that accompanies your Linux imaging tool of choice The sections in this document are e V2P Migration Requirements e Preparing for a V2P Migration e Migrating a Virtual Machine to a Physical Machine Overview e Additional Resources e Examples V2P Migration Requirements The following sections list the V2P migration requirements and restrictions e V2P Migration Third Party Tool Requirements e V2P Migration Source Machine Requirements e V2P Migration Target Machine Requirements e V2P Migration Restriction
10. _9005 amp DEV_00C0 amp SUBSYS_F6200E11 C drivers adpul60m ADPU160M INF V Adaptec U ul60dsk1 PCI VEN_9005 amp DEV_0080 C drivers adpul60m ADPU Windows2000 FMS4 0 SP5 ul60dsk1 PCI VEN_9005 amp DEV_0080 amp SUBSYS_E2A09005 C drivers adpul60m ADPU160M INF Adaptec U ul60dsk1 PCINVEN 9005 amp DEV 0080 amp SUBSYS E2A00E11 C drivers adpul60m ADPU160M INF V Adaptec U ul60dsk1 PCI VEN_9005 amp DEV_0080 amp SUBSYS_62A09005 C drivers adpul60m ADPU160M INF V Adaptec U ul60dsk1 PCI VEN_9005 amp DEV_0080 amp SUBSYS_E2209005 C drivers adpul60m ADPU160M INF Adaptec U ul60dsk1 PCI VEN_9005 amp DEV_00CF C drivers adpul60m ADPU Windows2000 FMS4 0 SP5 ul60dsk1 PCINVEN 9005 amp DEV 008F C drivers adpul60m ADPU Windows2000 FMS4 0 SP5 ul60dsk1 PCINVEN 1028 amp DEV 000E amp SUBSYS 01231028 C drivers mraid2k Oemsetup inf DELL ltra ltra ltra ltra PERC 3 4 RAID Driver for Windows 2000 mraid2k sys PCI VEN_1028 amp DEV_000F amp SUBSYS_013B1028 C drivers mraid2k Oemsetu PERC 3 4 RAID Driver for Windows 2000 mraid2k sys PCI VEN_1028 amp DEV_000F amp SUBSYS_014A1028 C drivers mraid2k Oemsetup inf DELL PERC 3 4 RAID Driver for Windows 2000 mraid2k sys PCI VEN_1028 amp DEV_000F amp SUBSYS_014C1028 C drivers mraid2k Oemsetu PERC 3 4 RAID Driver for Windows 2000 mraid2k sys PCI VEN_1028 amp
11. al setup utilities to the Sysprep directory setupmgr exe setupmgx dll The files are on your Windows 2000 CD in the SUPPORT NTOOLS directory in the Deploy cab file You may need to extract the setup files from the cab file The setupmgr exe utility is used to create the sysprep inf file Remove older VMware drivers and the VMware Tools from the virtual machine You can use the Windows Add Remove Programs utility found through the Windows menus Start Settings Control Panel Add Remove Programs VMware Tools cannot be uninstalled from the physical machine being created in this process VMWARE TECHNICAL NOTE vmware Creating a Directory for Hardware Drivers on the Virtual Machine Create a directory for the hardware device drivers on the source virtual machine disk Then create one subdirectory for each device driver you need installed on the migrated system I Decide if you need the drivers available for plug and play detection You have the option to store these hardware device drivers in the Sysprep directory However the Sysprep directories and their contents are deleted after the Sysprep mini setup completes Ifthe hardware device drivers are stored in an alternate directory then the drivers remain on the virtual machine after the Sysprep mini setup is completed and they therefore can also be used for plug and play detection Create a directory for hardware drivers on the source virtual machine For exam
12. de de dE dE od value specifies the actual value its format depends on value type value Parameters PnpInterface 5 REG DWORD 1 17 VMWARE TECHNICAL NOTE vmware Sample smmpi inf File SYMMPI INF version 2K 5 Windows 2000 This is the INF file for Windows 2000 for the SYMMPI based PCI MPI environment ee ke ko kk ke ke kk kk ke ke kk kk kk ke ke kk kk ke hok kk kk ke ke ke kk kk ke ke kk ko koe ke kk ke Copyright 2001 LSI Logic Inc All rights reserved This file is property of LSI Logic Inc and is licensed for p use as is The receipt of or possession of this file does not F convey any rights to modify its contents in whole or in part without the specific written consent of LSI Logic Inc s Ok kk kk ke akk version signature Windows NT Class SCSIAdapter ClassGUID 4D36E97B E325 11CE BFC1 08002BE10318 Provider LSI DriverVer 07 17 2002 1 08 06 CatalogFile ntx86 symmpi2k cat DestinationDirs DefaultDestDir 12 DIRID DRIVERS SourceDisksFiles x86 symmpi sys 1 SourceDisksNames DiskDesc Manufacturer SLSIS LSI SDELL DELL LST DevDesc1 SYMMPI Inst PCINVEN 1000 amp DEV 0621 DevDesc2 SYMMPI Inst PCINVEN 1000 amp DEV 0622 DevDesc3 SYMMPI Inst PCINVEN 1000 amp DEV 0624 DevDesc4 SYMMPI Inst PCINVEN 1000 amp DEV 0030 DELL DevDescD1 SYMMPI Inst PCINVEN 1000 amp DEV 0030 amp SUBSYS 01351028 DevDescD1 SY
13. e Create an answer file that duplicates this computer s configuration Click Next 2000 Setup Manager Wizard New or Existing Answer File An answer file tells Setup how to install and configure Windows 4 Choose Sysprep Install Click Next setup Manager Wizard Product to Install Which product does this answer file install VMWARE TECHNICAL NOTE vmware 5 Complete the remainder of the screens to specify the configuration you want on the target computer 6 Setup for running Sysprep At the Additional Commands screen add the line C NsysprepNsysprep clean Through the Additional Commands screen the Setup Manager creates a commandlines txt file The additional line directs Sysprep to remove any drivers that were pre installed which do not match the current hardware set Windows 2000 Setup Manager Wizard Additional Commands You can add commands that will automatically run at the end of unattended Setup You can run any command that does not require you to be logged on Type the command in the box below and then click Add Command to run ee Command list sysprep deon Remove Bock Nen Cencel 7 Save both the commandlines txt and sysprep inf inthe same directory as Sysprep exe Configure the OEMPnp Drivers Path The DevicePath Value Name a REG EXPAND SZ data type at HKEY LOCAL MACHINENSOFTWAREMMicrosoft Windows V CurrentVersion is truncated when you exceed the 2047 characte
14. e Vinf subdirectory of the Windows system directory b Specify each storage adapter For example the following entries support the IDE controllers PCI and Intel whose drives are included on the Windows 2000 distribution disk The following example text is from a target physical machine SysprepMassStorage PCNVEN 8086 amp DEV 1222 windir inf mshdc inf PCNVEN 8086 amp DEV 1230 windir infimshdc inf PCNVEN 8086 amp DEV 7010 windir inf mshdc inf PCNVEN 8086 amp DEV 7111 windir inf mshdc inf PCNVEN 8086 amp DEV 2411 windir inf mshdc inf PCNVEN 8086 amp DEV 2421 9owindir9eNinfmshdc inf 4 For mass storage adapters not supported on the Windows distribution disk a Add lines in the mass storage section using the following format SysprepMassStorage hardware id path to device inf disk directory disk description disk tag Where hardware id gt the plug and play hardware identification number for the mass storage subsystem It can be found in the text setup oem file for the device from the VMWARE TECHNICAL NOTE vmware driver disk It is common for one text setup oem file to cover multiple mass storage devices If you want to pre install the driver for all of the devices covered by the file you must have one line for each hardware id listed in the file Check the driver inf file
15. e sequence to define and identify the new physical machine on the network fthe drivers were not configured correctly a blue screen appears with the error Inaccessible Boot Device during the boot process Check the configuration in the sysprep inf file to verify the drivers are correct for the target physical machine Refer to Creating the sysprep inf and commandlines txt Files on page 6 for information on how the file should be set up Installing Additional Drivers After mini setup completes you are prompted to install drivers for new hardware found on the target system This includes networking drivers for the hardware card in the target physical machines To locate drivers e Check the target physical machine s local system Some drivers are installed through the image tool e Check the manufacturer provided hardware device disks or the manufacturer web site Refer to Creating a Directory for Hardware Drivers on the Virtual Machine on page 6 for additional information Completing the V2P Migration Perform the clean up steps as follows 1 Remove residual VMware drivers 2 Scanthrough the event logs for the physical machine for problems with drivers or services and correct them 12 VMWARE TECHNICAL NOTE vmware Clear the event logs reboot and repeat the steps in section Booting the Target Physical Machine on page 12 and Installing Additional Drivers on page 12 until the event logs are Clear of critical issues
16. here you downloaded this document for copies of these inf files BM xSeries 345 330 Dell PowerEdge 2650 1650 Hewlett Packard ProLiant DL360 DL380 Fujitsu Siemens Computers PRMERGY RX800 RX600 RX300 RX200 P250 Migration Restrictions ACPI and non ACPI hardware migration Virtual machines created with Workstation version 4 0 or greater GSX Server 3 0 or greater or ESX Server 2 0 or greater emulate ACPI hardware Due to a Sysprep limitation virtual machines that emulate ACPI hardware can only be migrated to ACPI physical machines Virtual machines created with older versions of Workstation GSX Server and ESX Server emulate non ACPI hardware and can only be migrated to non ACPI physical boxes Reference 1 provides a compatibility matrix SMP virtual machines must be migrated to SMP compatible physical machines VMWARE TECHNICAL NOTE vmware Preparing for a V2P Migration Perform the following prior to migrating a virtual machine to a physical machine 1 dentify the source virtual machine to migrate This can be an original virtual machine or a copy of a virtual machine dentify the target physical machine to migrate to List all the hardware components of the target machine The following is a sample worksheet you can use to store the physical machine information Device Specifications CPU Type Speed MHz GHz Qty Processor Bus MHz Cache KB RAM size MB GB SCSI Con
17. ight 1998 2004 VMware Inc All rights reserved Protected by one or more of U S Patent Nos 6 397 242 6 496 847 6 704 925 and 6 711 672 patents pending VMware is a registered trademark and the VMware boxes logo GSX Server ESX Server Virtual SMP and VMotion are trademarks of VMware Inc Microsoft Windows and Windows NT are registered trademarks of Microsoft Corporation Linux is a registered trademark of Linus Torvalds All other marks and names mentioned herein may be trademarks of their respective companies Revision 20040507 Item P2V ENG Q204 002 22
18. or booting on the target system and shuts down the source virtual machine 1 From the powered on source virtual machine run Sysprep Select Windows Start Run Browse to the path for the sysprep exe file Click OK Alternatively at the command prompt type c sysprep sysprep pnp forceshutdown This command adds the PNP drivers path during the Mini Setup and consequently you are not prompted for the path to the PNP drivers at login 2 Shutdown the source virtual machine 11 VMWARE TECHNICAL NOTE vmware When the Sysprep process is complete if it does not automatically do so shutdown the source virtual machine Transferring the Virtual Machine Image Use any disk imaging product for example Ghost to transfer the image to the target system Transfer the virtual machine image using your preferred imaging tool For example Ghost To clone the image using your preferred imaging tool 1 Create boot floppy or FLP image for virtual machine 2 Create boot floppy for physical machine 3 Clone the image to the physical machine disk Refer to your imaging product documentation for a complete description of the imaging process Booting the Target Physical Machine Boot the target physical machine from the imaging tool boot floppy If everything for the new boot device is configured correctly Windows starts and runs a mini setup This is not a full install of the Windows operating system It is a wizard lik
19. ple C drivers Create a sub directory in the drivers directory for each driver you need installed on the migrated system For example C drivers network_storage This includes drivers for the SCSI boot drive as well as any other hardware on the target system whose drivers are not distributed on the Windows distribution disk Refer to Preparing for a V2P Migration on page 3 for information on identifying and locating all the device drivers needed to complete the V2P migration Copy the hardware driver into the appropriate subdirectory Typically hardware manufacturers provide this on their installation disk or you can find updated drivers at the hardware manufacturer s web site Creating the sysprep inf and commandlines txt Files To create the sysprep inf and commandlines txt files use the Setup Manager 1 Run the Setup Manager utility Choose Windows Start gt Run Browse to the Sysprep directory Select setupmgr exe Click OK VMWARE TECHNICAL NOTE vmware This utility was installed during the preparation phase Refer to Preparing Utilities on the Virtual Machine on page 5 Welcome to the Windows 2000 Setup Manager Wizard The Setup Manager wizard helps you create an answer file and a distribution folder so that you can periorm automatic installations of Windows 2000 on computers connected to your network To continue click Next 2 Continue with the Setup Manager wizard Click Next 3 Choos
20. r AutoUsers 5 RegionalSettings LanguageGroup 1 SetupMgr DistFolder C sysprep i386 DistShare win2000dist Identification JoinWorkgroup V2P VMS 20 vmware Networking InstallDefaultComponents No NetClients MS MSClient params MS MSClient SysprepMassStorage PCINEN 1000 amp DEV 0621 Logic 1020 1030 Driver PCINVEN 1000 amp DEV 0622 Logic 1020 1030 Driver PCINVEN 1000 amp DEV 0624 Logic 1020 1030 Driver C drivers symmpi symmpi symmpi tag C drivers symmpi symmpi symmpi tag C drivers symmpi symmpi symmpi tag PCI VEN_1000 amp DEV_0630 C drivers symmpi symmpi Logic 1020 1030 Driver symmpi tag inf Dell PERC 4 im LSI inf Dell PERC 4 im LSI inf Dell PERC 4 im LSI inf Dell PERC 4 im LSI PCINVEN 1000 amp DEV 0030 amp SUBSYS 01351028 C drivers symmpi symmpi in Dell PERC 4 im LSI Logic 1020 1030 Driver symmpi tag PCINVEN 1000 amp DEV 0030 amp SUBSYS 011A1028 C drivers symmpi symmpi inf Dell PERC 4 im LSI Logic 1020 1030 Driver symmpi tag PCINVEN 1000 amp DEV 0030 amp SUBSYS 01241028 C drivers symmpi symmpi inf Dell PERC 4 im LSI Logic 1020 1030 Driver symmpi tag PCI VEN_9005 amp DEV_00C0 C drivers adpul60m ADPU Windows2000 FMS4 0 SP5 ul60dsk1 PCI VEN_9005 amp DEV_00C0 amp SUBSYS_F6209005 C drivers adpul60m ADPU160M INF Adaptec U ul60dsk1 PCI VEN
21. r limit for the OEMPnpDriversPath in Sysprep inf No erroris reported To workaround this limit 1 Remove the OEMPnpDriversPath from Sysprep inf 2 Manually configure the DevicePath Value Name by using Regedt32 Separate each path by a semi colon and include the SystemDrive and SystemRoot reference with absolute paths This unlike the relative paths that are defaulted in the Syspref inf VMWARE TECHNICAL NOTE vmware Creating a Mass Storage Section in the sysprep inf File To define the mass storage requirements for the target physical machine edit the sysprep inf file 1 Using the text editor of your choice open the sysprep inf file created in the previous section Refer to Creating the sysprep inf and commandlines txt Files on page 6 for additional information 2 Create a Mass Storage Section which contains one line for each mass storage subsystem whose drivers you want to pre install before transferring the image to the target computer 3 For mass storage adapters supported on the Windows distribution disk a Add lines in the mass storage section using the following format SysprepMassStorage hardware id path to device inf gt Where hardware id the plug and play hardware identification number for the mass storage subsystem path to device inf the path to the inf file for the device in the image you are transferring This is usually in th
22. s VMWARE TECHNICAL NOTE vmware V2P Migration Third Party Tool Requirements To migrate your virtual machine to a physical machine you need the following third party tools instal led in the virtual machine Microsoft Sysprep 1 1 to prepare the image for transfer This must be installed on the source virtual machine This tool allows you to configure changes to hardware devices Symantec Ghost or any other image transfer software to transfer the prepared image You need a boot floppy for both the virtual machine and the physical machine Drivers for the target physical machine one for the target disk drive and possibly for other hardware such as ethernet adapters V2P Migration Source Machine Requirements Thes ource virtual machine must have been created by one of the VMware virtualization platforms In addition the virtual machine must be running one of the following Microsoft guest operating systems Windows 2000 Professional Server or Advanced Server Windows XP not tested Windows 2003 Windows NT 4 0 Workstation or Server not tested V2P Migration Target Machine Requirements The methods outlined in this technical note are intended to apply to most Windows based physi cal machines The V2P migration procedure has been tested with the following target host machines and an inf file for each these systems is provided Refer to the directory and or web locati V2P on w
23. s raidiskl PCINVEN 1028 amp DEV 0002 amp SUBSYS 00021028 C drivers perc2 perc2 inf De PERC 2 2 Si 3 Si 3 Di Windows 2000 Device Drivers raidiskl PCINVEN 1028 amp DEV 0003 amp SUBSYS 00031028 C drivers perc2 perc2 inf Dell PERC 2 2 Si 3 Si 3 Di Windows 2000 Device Drivers raidisk1 PCI VEN_1028 amp DEV_0002 amp SUBSYS_00D11028 C drivers perc2 perc2 inf Dell PERC 2 2 Si 3 Si 3 Di Windows 2000 Device Drivers raidisk1 PCINEN 1028 amp DEV 0002 amp SUBSYS 00D91028 C drivers perc2 perc2 inf De PERC 2 2 Si 3 Si 3 Di Windows 2000 Device Drivers raidiskl PCINVEN 1028 amp DEV O00A amp SUBSYS 01061028 C drivers perc2 perc2 inf Dell PERC 2 2 Si 3 Si 3 Di Windows 2000 Device Drivers raidiskl PCI VEN_1028 amp DEV_000A amp SUBSYS_011B1028 C drivers perc2 perc2 inf Dell PERC 2 2 Si 3 Si 3 Di Windows 2000 Device Drivers raidisk1 PCINEN 1028 amp DEV 000A amp SUBSYS 01211028 C drivers perc2 perc2 inf De PERC 2 2 Si 3 Si 3 Di Windows 2000 Device Drivers raidisk1 PCINVEN 9006 amp DEV 2140 amp SUBSYS 21409006 C drivers perc2 perc2 inf Dell PERC 2 2 Si 3 Si 3 Di Windows 2000 Device Drivers raidisk1 PCINVEN 9005 amp DEV 00C5 amp SUBSYS 00C51028 C drivers perc2 perc2 inf Dell PERC 2 2 Si 3 Si 3 Di Windows 2000 Device Drivers raidiskl VMware Inc 3145 Porter Drive Palo Alto CA 94304 www vmware com Copyr
24. siport LegacyInterfaceType HKR Scsiport SlotNumber pnpsafe pci addreg HKR Parameters VPnpInterface 5 0x00010001 0x00000001 Miniport EventLog Inst AddReg Miniport EventLog AddReg Miniport EventLog AddReg HKR EventMessageFile REG EXPAND SZ SystemRoot NSystem32MIoLogMsg dll HKR TypesSupported REG DWORD 7 Strings LSI LSI Logic DELL Dell DiskDesc LSI Logic PCI SCSI FC MPT Driver Install Disk 19 VMWARE TECHNICAL NOTE vmware DevDescl LSI Logic FC909 Fibre Channel Adapter DevDesc2 LSI Logic FC929 Fibre Channel Adapter DevDesc3 LSI Logic FC919 Fibre Channel Adapter DevDesc4 LSI Logic 1020 1030 Ultra320 SCSI Adapter DevDescD1 Dell PERC 4 im RAID Controller IO ICI ICICI ICI IO IAA IAA AA IO I IO I IK k Handy macro substitutions non localizable SPSVCINST_ASSOCSERVICE 0x00000002 SERVICE KERNEL DRIVER 1 SERVICE BOOT START 0 SERVICE ERROR NORMAL 1 REG EXPAND SZ 0x00020000 REG DWORD 0x00010001 Sample sysprep inf File SetupMgrTag Unattended UpdateHAL ACPIAPIC_MP windir inf hal inf OemSkipEula Yes OemPnPDriversPath C drivers InstallFilesPath C sysprep i386 TargetPath WINNT GuiUnattended AdminPassword passw0rd OEMSkipRegional 1 TimeZone 4 OemSkipWelcome 1 UserData FullName v2p ComputerName DELL V2P Display BitsPerPel 32 Xresolution 1024 YResolution 768 Vrefresh 85 LicenseFilePrintData AutoMode PerServe
25. the source virtual machine Additional Resources Additional resources are described in the following sections Sysprep References VMware Documentation Related Websites VMware Professional Services 13 VMWARE TECHNICAL NOTE vmware Sysprep References The follow two documents are included in the Sysprep package downloaded from Microsoft e Microsoft Windows 2000 Guide to Unattended Setup unattend doc Starting on Page 135 is a write up on updating the HAL for switching between uniprocessor and multiprocessor systems e Microsoft Windows 2000 Sysprep Update newsysprep doc This is a write up on updating the mass storage drivers when migrating between systems VMware Documentation The following VMware documentation is available on the product CD ROM and or on the VMware Website VMware ESX Server www vmware com support esx e VMware ESX Server User s Manual e ESX Server Release Notes VMware P2V Assistant www vmware com support p2v e VMware P2V Assistant Users Manual e P2V Assistant Release Notes Related Websites The following are Websites that can provide additional information e www vmware com e WWW sysprep com e www veritas com e Www powerquest com e www ghost com VMware Professional Services VMware Profession Services contact points are listed in the table below Service Contact Points Content Education Services education vmware com Open Enrollment and
26. to be sure it matches the reference here Use the long number identification even if a shortened version is listed For example the driver inf file may list this with the long name PCINVEN 1000 amp DEV 0030 amp SUBSYS 01241028 The textsetup oem file may list this with a short name PCINVEN 1000 amp DEV 0030 path to device inf the path to the inf file for the device in the image you are transferring This defines where you put the drivers For example C Ndrivers If when creating the drivers directory you placed the files from the boot disk for a device mydrive in the subdirectory mydir the path would be C drivers mydir mydrive inf lt disk directory gt the subdirectory where the driver file can be found This is relative to the directory specified in path to device inf gt Ifinthe same directory the value can be backslash disk description a description of the hardware supported by the driver being installed This can be found in the Disks section of the text setup oem file for the driver There should be a line for each disk of the format dl Hardware Description disk tag This field supports any text you need to create a clear description disks tag the name of the tag file for the driver disk It can be found in the same line of the text setup oem file for the driver b Specify each storage adapter For example SysprepMassStorage PCINVEN 1000 amp DEV 0621 C
27. troller Disk type Disk size GB Disk quantity NIC O Type Speed Duplex NIC 1 Type Speed Duplex NIC 2 Type Speed Duplex 4 Identify which drivers you might need One method is to view devices in the Registry These drivers must match the guest operating system on the source machine Check the Windows machine registry to identify possible drivers a Open the Registry Editor select Windows Start Run regedit 32 b In the Registry Editor select Local Machine System Current Control Settings Control Control Device Database c View the list of hardware and search for the GUID class corresponding to the hardware device d Record the name of the hardware device and the device driver identification Collect all the device drivers required to operate the devices on the target machine Refer to the e Software disk and documentation provided by the device manufacturer Web site of each device manufacturer vmware VMWARE TECHNICAL NOTE For example to find an IBM storage device driver from the website a Go to the IBM website www ibm com downloads and drivers b Search for servers gt storage type c View the list of drivers in the software device raid server driver matrix The following is a sample worksheet you can use to store hardware device drivers reference information Device Driver Disk Controller Disk 1 Disk 2
Download Pdf Manuals
Related Search