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
User’s Manual
30 VMware, Inc.
Converting in Install-Less Mode
Install‐lessmodeentailsconvertingarunningremotephysicalcomputerwithoutinstallingthe
VMware Convertermanagerontothemachinefromwhichyouareinitiatingthemigration.Torunin
install‐lessmode,temporarilyinstalltheConverterManageronamachineandcopythefilesintheinstall
directorytoanetworkshare.
Afterthisyoucanmountthenetworksharefromanothermachineandrunthe
executablewithouthavingtoinstallitonthatparticularmachine.
AfterstartingtheConverterManagerfromthemountednetworkshare,followtheproceduresforconverting
aremotephysicalcomputerassource.
Creating a Separate Disk for Each Volume
Toeasestoragemanagement,ConverterprovidestheoptionontheSourceDatapagetomigrateallvolumes
excepttheactiveandsystemvolumestoseparatedisks.Convertingindividualvolumestocorresponding
virtualdisksandplacingtheindividualdisksacrossseparatedatastoresgivesyoumoredirectcontrolover
storagelimitations.
Theoption
tocreateaseparatediskforeachvolumeisavailableforallsources,exceptOVFsourceimages.The
destinationcanbeaVMwareInfrastructure(ESXServerorESXServermanagedbyVirtualCenter)orahosted
destination(Workstation).Forhosteddestinations,alldisksarestoredinthesamelocation.
Ifyouselect
Createaseparatediskforeachvolume,ontheAdvancedDatastorepagethenewdisksare
displayedintheorderinwhichthevolumesontheSource Datapagearedisplayed.Theactiveandsystem
disksarealwayslistedfirstandcanbeonthesameorondifferentdisks,depending
ontheiroriginal
configuration.Toverifythenewdisktowhichavolumeisassigned,comparethenewsizeforeachvolumeon
theSourceDatapagewiththedisksizeontheDatastorepage.
To migrate volumes across independent datastores on VMware Infrastructure virtual machines
1OntheSourceDatapage,selectthevolumestoconvertandspecifytheirsize.
2 SelectCreate
aseparatediskforeachvolumeandclickNext.
3TypetheIPaddressoftheVirtualCenterserverorthehostwhereyouwanttostoreyourvirtualmachine.
4Loginasadministrator,enteryouradministratorpassword,andclickNext.
5Typeanameforthenewmachine,selectthefolderlocationforthenewmachine,andclickNext.
6OntheHostorClusterpage,selectahost,cluster,orresourcepoolfromwhichthevirtualmachineisto
runandclickNext.
7OntheAdvancedDatastorepage,selecttheappropriatedatastoreforstoringeachdiskandclickNext.
Virtual Appliance Overview
ConvertersupportsinstallingandcreatingvirtualappliancesstoredinOVFversion0.9.Anapplianceisa
preconfiguredvirtualmachinethattypicallyincludesapreinstalledguestoperatingsystemandother
software.Importingvirtualappliancesallowsyoutoaddpreconfiguredvirtualmachinestoyour
VirtualCenter,ESX Server,orWorkstationinventory.
Importingavirtualappliance
issimilartodeployingavirtualmachinefromatemplate.However,youcan
importavirtualappliancefromanylocalfilesystemaccessiblefromthesourcemachineorfromaremoteWeb
server.Localfilesystemscanincludelocaldisks(suchasC:),removablemedia(suchasCDsorUSB
keychain
drives),andsharednetworkdrives.
OVFisnotabootableformat.Therefore,youcannotbootthefileinavirtualizationplatforminitscurrentstate.
Youmustimporttheappliancetoeitherahostedormanageddestinationtobootit.
InadditiontoimportingvirtualapplianceswithConverter,youcan
alsoimportOVFvirtualappliancestoESX
ServeroraVirtualCenterserverbyusingVIclient2.5.