Hello rpmurray
Thanks a lot for your help.
rpmurray wrote:You actually need to use double-quotes in the command, like so:
VBoxManage setextradata "MyXP_VM" "VBoxInternal/Devices/pcbios/0/Config/DmiSystemFamily" "<EMPTY>"
It's probably not necessary to use them around the VM name "MyXP_VM" but it's good practice to do it in case you have a space in the name. To reset to unknown or unspecified you need to use "<EMPTY>". You can find all this in the user manual, Section 9.12 Configuring the BIOS DMI information (page 177-178).
It works great. Thanks.
rpmurray wrote:You actually need to use double-quotes in the command, like so:
VBoxManage setextradata "MyXP_VM" "VBoxInternal/Devices/pcbios/0/Config/DmiSystemVersion" "7m`0213RE141EXPLO14"
It's probably not necessary to use them around the VM name "MyXP_VM" but it's good practice to do it in case you have a space in the name.
In this case, i don't have errors any longer, but when i run dmidecode on the guest, there is unfortunately no change. In fact after typing:
VBoxManage setextradata "MyXP_VM" "VBoxInternal/Devices/pcbios/0/Config/DmiSystemVersion" "7m`0213RE141EXPLO14"
i don't have the usual prompt showing me my current directory, but instead just ">". It looks as if the terminal is waiting for something else.
Maybe i should start another thread, but i was wondering if these commands do the same
VBoxManage setextradata "MyXP_VM" "VBoxInternal/Devices/pcbios/0/Config/DmiSystemUuid" "XXXXXXXXXXXXXXXXXXXX"
and
VBoxManage modifyvm "MyXP_VM" --hardwareuuid "XXXXXXXXXXXXXXXXXXX"
again, thanks a lot for your precious help.
Best regards,
Jeff_59