VMware, Inc. 143
Chapter 6 Creating a Virtual Machine from a System Image or Another Virtual Machine
Migration Issues Caused by Hardware Changes
MostmigratedapplicationsfunctioncorrectlyintheVMwarevirtualmachinebecause
theirconfigurationanddatafileshavethesamelocationasthesourcevirtualmachine.
However,applicationsmightnotworkiftheydependonspecific characteristicsofthe
underlyinghardwaresuchastheserialnumberorthedevicemanufacturer.
Whentroubleshootingaftervi
rtualmachinemigration,considerthefollowing
potentialhardwarechanges:
TheCPUmodelandserialnumbers(ifactivated)canbedifferentafterthe
migration.TheycorrespondtothephysicalcomputerhostingtheVMwarevirtual
machine.
Thenetworkadaptercanbedifferent(AMDPCNetorVMXnet)withadifferent
MACaddress.Eachinterface’sIPaddressmustbeindividuallyreconfigured.
Thegraphicscardcanbedifferent(VMwareSVGAcard).
Thenumbersofdisksandpartitionsarethesame,buteachdiskdevicecanhavea
differentmodelanddifferentmanufacturerstrings.
Theprimarydiskcontrollerscanbedifferentfromthesourcemachine’s
controllers.
Applicationsmightnotworkiftheydependondevicesthatarenotavailablefrom
withinavirtualmachine.
Open a Third-Party Virtual Machine or System Image
TheFile>Opencommandletsyouconvertavirtualappliance,systemimage,orvirtual
machinecreatedwithsoftwarefromanothercompanyintoaVMwarevirtualmachine.
To open a third-party virtual machine or system image
1FromtheWorkstationmenubar,chooseFile>Open.
2IntheFilenamefield,browsetoandopentheconfiguration(.vmx,.vmc,.s
pf,
.ovf,.o
va,or.sv2i)fileforthevirtualappliance,virtualmachine,orsystem
imagetoconvert.
YoucanusethefieldFilesoftypetofilterthefilesdisplayedbyfileextension.
Comentarios a estos manuales