3.0
Table Of Contents
- User’s Manual
- Contents
- About This Book
- Introduction
- System Requirements
- Application Requirements
- Memory Requirements for Cold Cloning
- Virtual Machine and System Image Requirements
- Restoring VCB Images in Converter
- Supported Destinations
- Configuring Permissions for VirtualCenter Users
- Level of Internationalization Support
- How Converting Affects Settings
- Changes to Virtual Hardware
- TCP/IP Port Requirements
- Remote Hot Cloning Troubleshooting Tips
- Installing and Uninstalling
- Converting Machines
- Using the Converter Boot CD for Local Cold Cloning
- Configuring VMware Virtual Machines
- Managing Tasks
- Appendix: Migration with p2vTool Command-Line Interface
- Glossary
- Index
VMware, Inc. 69
Appendix A Appendix: Migration with p2vTool Command-Line Interface
Source Machines and Destination Machines
Youcanusep2vToolwithlive,hosted,andmanagedsourcemachinesorvirtualappliances,andhostedand
manageddestinationmachinesorvirtualappliances.
Alivemachinecanonlybeasourceandhastheseattributes:
Canbeaphysicalmachineoravirtualmachine.
Performsaliveimportthatavoidshavingtoshutdownthesourcemachine.
Mustbepowered‐onatthetimeofimport.
Ahostedmachinecanbeasourceordestinationandhastheseattributes:
Isaflat‐filevirtualmachine,typicallyfromaVMwareWorkstationproductorasupportedbackupformat.
Mustbeaccessiblefromthelocalmachine’soperatingsystem.(Itcanbeonanetworkshare,butthe
networksharemustbemountedbeforerunningp2vTool.)
Ifusedasasource,thevirtualmachinemustbepoweredoffatthetimeofimport.
Amanagedmachinecanbeasourceordestinationandhastheseattributes:
VirtualmachinesrunningonanESXServermachine.
TheservercanbespecifiedasanESXServermachineortheVirtualCenterserverthatismanagingit.
Ifusedasasource,thevirtualmachinemustbepoweredoffatthetimeoftheimport.
Avirtualappliancecanbean.ovffileoran.ovafilethatcontainsagroupoffiles.Youcaninstallavirtual
appliancefromanylocalorremotefilesystemaccessiblefromthe
sourcemachineorfromaremotemachine
pathsharedoverthenetwork.
Withp2vTool,youcanmigratevolumestoseparatedisks.SettheattributeseparateDisk=”true”inthe
volumeCloneInfonodeforeachvolumeyouwanttoplaceonaseparatedisk.Donotsetthisattributefor
activeorsystemvolumes.See
Example A‐5,“ImportingaManagedSourcetoaManagedDestination,
ExplicitlySpecifyingOptionalParameters,”onpage 72andExample A‐9,“XMLOutputforthep2vTool-q
[--query]Option,”onpage 74.
Restoring VCB Images
VCBenablesitsuserstobackupentireESXServervirtualmachines,storingthebackupusingWorkstation
disks,a.vmxfile,andacatalogfile.Thep2vToolcanrestoreVCBimagesintoESXServer3.xmachines,both
standaloneandthosemanagedbyVirtualCenter,andcanalsoimportthemtohostedproducts.
Thep2vTooldoesnotpreservecertainvirtualmachinepropertiesunlesssettingsfortheattributesthatcan
preservethepropertiesareincludedintheinputXMLfile.Preservingthesepropertiesisapplicableonlytoa
managedproductdestination.Table A‐2showstheattributesthatneedattentiontopreservetheseproperties.
Fora
VMwarehostedproductdestination,donotsettheattributes,becausevirtualmachinepropertiesarenot
preserved.
Informationinthecatalogfileisnotextracted.Torestoretothesamelocation,viewtheoriginalcatalogfile
andincludethatinformationintheinputXMLfile.
Table A-2. Settings to Preserve Properties
Node Attribute Settings
ImportParams keepIdentity Defaultisfalse.Settotrue topreservethevirtual
machineidentity
preserveDeviceBackingInfo Defaultisfalse.Settotruetopreservethedevicebacking
informationforCD‐ROM,floppy,serialport,andparallel
port.
NicMappings preserveNicsInfo Defaultisfalse.Settotruetousethenetworkadapter
informationfromthesource.