Shulou(Shulou.com)06/02 Report--

Some virtual machine applications are bound with hardware, and the UUID may be modified when Storage vMotion or vMotion is performed on the virtual machine, causing the application to recognize the hardware and fail to activate the application. After testing and understanding, the application host binds the ID of the hard disk and the network card MAC, so how does the virtual machine fix the relevant ID?

1. Fixed Nic MAC:

To shut down the virtual machine, directly modify the MAC to manually set the fixed MAC.

2. Fixed virtual machine UUID:

Use SSH to connect to the host where the virtual machine resides, go to the virtual machine storage directory, find the virtual machine configuration file .vmx for editing (backup before editing), and add the following:

Uuid.bios = "420b 3b 65 95 df 16 07-eb 0d 7f 2e 14 f7 1a d5"

Vc.uuid = "500b bb 2d 58 d8 3a f2-f3 a7 9e 6e b3 72 70 50"

3. Fixed virtual machine VMDK ID

Modify the virtual machine disk description file vm.vmdk (make no mistake, there is another vm-flat.vmdk this is the data file do not modify), confirm the following 2 items.

Ddb.longContentID = "5ed238cbc483babb2bd6c12367330ea0"

Ddb.uuid = "60 00 C29b 72 77 ee 66-9b 35 d5 d0a08b 71 ba"

4. Save the UUID/VMDK UUID record of the MAC/ virtual machine in the above 3 steps. If the migration of the virtual machine or the restore of the whole machine causes the application to be unable to bind the hardware, you can use the above method to restore.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.