Win7 guest shows host CPU after setextradata cmd to change DMI strings executed

I am running Win7 guest/Win 8.1 host using virtualbox 5.0.14 r105127. I use the setextradata command listed in the virtualbox online manual here : (nevermind, I can't post links apparently, but it's oracle's online manual for virtualbox hosted on their site in section 9.12)

Which are:

Code:

VBoxManage setextradata "VM name"      "VBoxInternal/Devices/pcbios/0/Config/DmiProcManufacturer"  "GenuineIntel"
VBoxManage setextradata "VM name"       "VBoxInternal/Devices/pcbios/0/Config/DmiProcVersion"       "Pentium(R) III"

(But I used different input strings). The commands completes with no error messages, putting me back at the command prompt. But when I go in device manager and to My Compuer>About they both still show me the host's CPU, so obviously something isn't working. If someone could please help me I'd really appreciate it. Thanks in advance.

P.S.: Also, when you use setextradata to configure DMI and/or hardware details, are those changes persistent on a per VM basis until you modify them otherwise, or do you have to set them prior to each boot? Thanks again.

 

Thanks for the input. Is that also the case with regard to all setextradata changes? For example, I sometimes need to change the TSC handling mode, it's also persistent? Thanks again, and if anyone could take a crack at my original question, that would be sweeter than unicorn milk...

 

Yeah, I realized that, and entered it accordingly into the command string, to no avail. I still see the host cpu in system info. I'll give it another shot here in a moment just to make sure it wasn't 'operator error'.