Moving a VM which has SetExtraData in.vbox file
Posted: 17. Dec 2018, 15:45
I have a slight issue which I have observed for several years whenever I have wanted to move a particular Win XP SP3 VM to another host.
I use the recommended method of copying the whole VM folder containing the VDI and vbox file to a new host and then use "Add machine" to register it on the new host.
This all works fine except that it seems to lose the 4 lines of SetExtraData which is contained in the vbox file.
Fortunately I have the 4 lines set up in a batch file which I can easily run to re-instate the missing lines into the vbox file and then everything works fine.
I'm just curious why this happens.
As I say, it's not a major problem, just a slight inconvenience.
For info, I have always moved the XP VM from a Windows Host to a different WIndows Host - currently Win10x64 Pro 1809, but I have observed this problem on Win7 and Win8.1 hosts.
I'm not sure a log file will help, but the SetExtraData lines in the vbox file are:
VboxManage setextradata %McName% "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSVendor" "Hewlett-Packard"
VboxManage setextradata %McName% "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSVersion" "A69"
VboxManage setextradata %McName% "VBoxInternal/Devices/pcbios/0/Config/DmiSystemProduct" "Pavilion Elite D5100T0"
VboxManage setextradata %McName% "VBoxInternal/Devices/pcbios/0/Config/DmiSystemVendor" "Hewlett-Packard"
I use the recommended method of copying the whole VM folder containing the VDI and vbox file to a new host and then use "Add machine" to register it on the new host.
This all works fine except that it seems to lose the 4 lines of SetExtraData which is contained in the vbox file.
Fortunately I have the 4 lines set up in a batch file which I can easily run to re-instate the missing lines into the vbox file and then everything works fine.
I'm just curious why this happens.
As I say, it's not a major problem, just a slight inconvenience.
For info, I have always moved the XP VM from a Windows Host to a different WIndows Host - currently Win10x64 Pro 1809, but I have observed this problem on Win7 and Win8.1 hosts.
I'm not sure a log file will help, but the SetExtraData lines in the vbox file are:
VboxManage setextradata %McName% "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSVendor" "Hewlett-Packard"
VboxManage setextradata %McName% "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSVersion" "A69"
VboxManage setextradata %McName% "VBoxInternal/Devices/pcbios/0/Config/DmiSystemProduct" "Pavilion Elite D5100T0"
VboxManage setextradata %McName% "VBoxInternal/Devices/pcbios/0/Config/DmiSystemVendor" "Hewlett-Packard"