How can I change the BIOS serial number in VirtualBox?
up vote
16
down vote
favorite
VirtualBox sets the BIOS serial number of every VM instance to 0. It seems to be possible to change some BIOS settings, but I haven't seen anything that directly references the serial number.
Can anyone suggest a way to do this?
virtualbox bios
asked Oct 14 '09 at 23:54
Roger
1,17231128
add a comment |
up vote
16
down vote
favorite
VirtualBox sets the BIOS serial number of every VM instance to 0. It seems to be possible to change some BIOS settings, but I haven't seen anything that directly references the serial number.
Can anyone suggest a way to do this?
virtualbox bios
asked Oct 14 '09 at 23:54
Roger
1,17231128
1
Any particular reason you want to do this?
– Jared Harley
Oct 15 '09 at 0:15
1
Yes. I have a PC inventory software tool that uses the BIOS serial number to uniquely identify computers. It works fine for physical hardware and for VMs from other vendors, but doesn't know how to handle multiple VirtualBox VMs.
– Roger
Oct 15 '09 at 0:52
edited my answer to reflect the error you caught.
– A Dwarf
Oct 15 '09 at 2:08
You have any news on this, Roger? Would love to know how it turned out.
– A Dwarf
Oct 31 '09 at 3:51
I never determined how to do it. I got a few responses on the VirtualBox forums, but found nothing that worked. If I run across the answer, I'll be sure to add an update here.
– Roger
Nov 4 '09 at 23:42
add a comment |
up vote
16
down vote
favorite
up vote
16
down vote
favorite
VirtualBox sets the BIOS serial number of every VM instance to 0. It seems to be possible to change some BIOS settings, but I haven't seen anything that directly references the serial number.
Can anyone suggest a way to do this?
virtualbox bios
asked Oct 14 '09 at 23:54
Roger
1,17231128
VirtualBox sets the BIOS serial number of every VM instance to 0. It seems to be possible to change some BIOS settings, but I haven't seen anything that directly references the serial number.
Can anyone suggest a way to do this?
virtualbox bios
virtualbox bios
asked Oct 14 '09 at 23:54
Roger
1,17231128
asked Oct 14 '09 at 23:54
Roger
1,17231128
asked Oct 14 '09 at 23:54
Roger
1,17231128
asked Oct 14 '09 at 23:54
Roger
1,17231128
asked Oct 14 '09 at 23:54
Roger
1,17231128
1,17231128
1
Any particular reason you want to do this?
– Jared Harley
Oct 15 '09 at 0:15
1
Yes. I have a PC inventory software tool that uses the BIOS serial number to uniquely identify computers. It works fine for physical hardware and for VMs from other vendors, but doesn't know how to handle multiple VirtualBox VMs.
– Roger
Oct 15 '09 at 0:52
edited my answer to reflect the error you caught.
– A Dwarf
Oct 15 '09 at 2:08
You have any news on this, Roger? Would love to know how it turned out.
– A Dwarf
Oct 31 '09 at 3:51
I never determined how to do it. I got a few responses on the VirtualBox forums, but found nothing that worked. If I run across the answer, I'll be sure to add an update here.
– Roger
Nov 4 '09 at 23:42
add a comment |
1
Any particular reason you want to do this?
– Jared Harley
Oct 15 '09 at 0:15
1
Yes. I have a PC inventory software tool that uses the BIOS serial number to uniquely identify computers. It works fine for physical hardware and for VMs from other vendors, but doesn't know how to handle multiple VirtualBox VMs.
– Roger
Oct 15 '09 at 0:52
edited my answer to reflect the error you caught.
– A Dwarf
Oct 15 '09 at 2:08
You have any news on this, Roger? Would love to know how it turned out.
– A Dwarf
Oct 31 '09 at 3:51
I never determined how to do it. I got a few responses on the VirtualBox forums, but found nothing that worked. If I run across the answer, I'll be sure to add an update here.
– Roger
Nov 4 '09 at 23:42
1
1
Any particular reason you want to do this?
– Jared Harley
Oct 15 '09 at 0:15
Any particular reason you want to do this?
– Jared Harley
Oct 15 '09 at 0:15
1
1
Yes. I have a PC inventory software tool that uses the BIOS serial number to uniquely identify computers. It works fine for physical hardware and for VMs from other vendors, but doesn't know how to handle multiple VirtualBox VMs.
– Roger
Oct 15 '09 at 0:52
Yes. I have a PC inventory software tool that uses the BIOS serial number to uniquely identify computers. It works fine for physical hardware and for VMs from other vendors, but doesn't know how to handle multiple VirtualBox VMs.
– Roger
Oct 15 '09 at 0:52
edited my answer to reflect the error you caught.
– A Dwarf
Oct 15 '09 at 2:08
edited my answer to reflect the error you caught.
– A Dwarf
Oct 15 '09 at 2:08
You have any news on this, Roger? Would love to know how it turned out.
– A Dwarf
Oct 31 '09 at 3:51
You have any news on this, Roger? Would love to know how it turned out.
– A Dwarf
Oct 31 '09 at 3:51
I never determined how to do it. I got a few responses on the VirtualBox forums, but found nothing that worked. If I run across the answer, I'll be sure to add an update here.
– Roger
Nov 4 '09 at 23:42
I never determined how to do it. I got a few responses on the VirtualBox forums, but found nothing that worked. If I run across the answer, I'll be sure to add an update here.
– Roger
Nov 4 '09 at 23:42
add a comment |
5 Answers
5
active
oldest
votes
up vote
19
down vote
accepted
http://www.virtualbox.org/manual/ch09.html#changedmi
Really has detailed answer for this.
You can set the bios serial number by doing this:
VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial" "System Serial"
The error you were getting is caused by the serial not being set as a string value, if you have a pure number you should prepend it with string: like so:
VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial" "string:1234"
Note: In case your VM is configured to use EFI firmware you need to replace pcbios by efi in the keys.
answered Jan 14 '12 at 11:56
Alex R
34525
1
Note that these instructions are for systems using BIOS. If your system uses EFI -- controlled by "Settings -> System -> Motherboard -> Enable EFI" -- then you need to replace "pcbios" with "efi" in the above commands.
– ntc2
Feb 15 at 20:01
add a comment |
up vote
8
down vote
Not from any external settings. But you can from the code and then build it yourself:
Source file: DevPcBios.cpp
Line: 1014 READCFGSTR("DmiSystemSerial", pszDmiSystemSerial, "0");
Change "0" to whatever value you need.
EDIT: You can apparently use VBoxManage setextradata. I have used it in the past for other type of configurations (not bios related) and didn't test this particular setting. Give it a go:
VBoxManage setextradata *YourVMName* VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial "*yourserial*"
Otherwise... revert back to source code editing and building.
Best of luck.
edited Jul 15 '17 at 1:19
Andrea Lazzarotto
682314
answered Oct 15 '09 at 0:33
A Dwarf
17k13665
1
Hmm. Thanks - so close, but not there yet. I tried this: "c:Program FilesSunVirtualBoxVBoxManage.exe" setextradata "Demo Server" VBoxInternal/Devices/pcbios/0/Config /DmiSerial "123" It seemed to work, but when I launched the VM I got this error message: Failed to start the virtual machine Demo Server. Invalid configuration for device pcbios device (VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES). Unknown error creating VM (VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES). Deleting and recreating the machine definition fixed it, so no harm done. I think you're really close - any other suggestions?
– Roger
Oct 15 '09 at 1:22
hmm... did you make a verbatim copy/paste of your command to the comment box? Because there's no spave between /Config and /DmiSerial. Regardless I'll explore this further. Guess I will have to install VirtualBox. So far was relying only on my notes :)
– A Dwarf
Oct 15 '09 at 1:45
Bah! This head of mine. I post the relevant code line and then don't even check it against my much older notes. It's not /DmiSerial. It has been renamed sometime between version 1.5 and now. It is now /DmiSystemSerial
– A Dwarf
Oct 15 '09 at 1:53
Thanks, A Dwarf, for all your help. I tried replacing DmiSerial with DmiSystemSerial, reran the command line (without the space, which was a typo), and got the same error.
– Roger
Oct 15 '09 at 12:06
To my knowledge it can only mean this isn't fully implemented yet and you can't do it this way. At this point I'm afraid I cease to be useful. You should go to the VirtualBox forums and try from there. They are excellent folks and you'll get a more informed answer. I would however love to know the end result, if you would be so kind and post an answer to your own question when that happens. All the best.
– A Dwarf
Oct 15 '09 at 17:52
add a comment |
up vote
3
down vote
If you run that command, and get the error referenced by Roger, you need to back out the command by running the command without the last parameter (VALUE).
This removes the entry causing the error.
If you are unsure of what the last offending command was, open the ~~~.vbox (XML) file in the root of the VirtualMachines folder of the specific VM and review the EXTRADATA section.
Running the command-line call to vboxmanage is the best way to modify these.
Editing the xml file does not stick 100% of the time.
answered Sep 6 '12 at 14:18
Alex
311
add a comment |
up vote
2
down vote
The accepted answer didn't update the serial number correctly for me; instead, I followed these steps to successfully update the serial number. Note the guest OS was macOS and the host was windows.
NOTE: You must close virtualbox before running this command for it to be saved.
- Open the windows command prompt as administrator
cd "C:Program FilesOracleVirtualBox"
VBoxManage.exe setextradata "VM NAME" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "SERIAL_HERE"see source.*
Not sure why the pcbios command didn't work but efi did.
HELPFUL LINKS
- If you have trouble finding a valid serial follow the instructions here.
- If you're not sure what your vm name is run
VBoxManage.exe list vms.
answered Jan 15 '17 at 2:29
josh7weaver
211
Re you needing "efi" and accepted answer using "pcbios", this is probably because you're using (U)EFI and that person was using traditional BIOS. Whether you're using EFI or BIOS is determined by the "Settings -> System -> Motherboard -> Enable EFI" check box in VirtualBox.
– ntc2
Feb 15 at 18:38
add a comment |
up vote
1
down vote
Try using a serial number that contains 20 byte hexadecimal string:
VBoxManage setextradata "VM name" "VBoxInternal/Devices/ahci/0/Config/Port0/SerialNumber" "serial"
(Reference)
edited Mar 9 '12 at 19:12
Diogo
21.8k54132209
answered Aug 16 '11 at 14:14
Ricardo Kiyoshi Batori
111
add a comment |
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
19
down vote
accepted
http://www.virtualbox.org/manual/ch09.html#changedmi
Really has detailed answer for this.
You can set the bios serial number by doing this:
VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial" "System Serial"
The error you were getting is caused by the serial not being set as a string value, if you have a pure number you should prepend it with string: like so:
VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial" "string:1234"
Note: In case your VM is configured to use EFI firmware you need to replace pcbios by efi in the keys.
answered Jan 14 '12 at 11:56
Alex R
34525
1
Note that these instructions are for systems using BIOS. If your system uses EFI -- controlled by "Settings -> System -> Motherboard -> Enable EFI" -- then you need to replace "pcbios" with "efi" in the above commands.
– ntc2
Feb 15 at 20:01
add a comment |
up vote
19
down vote
accepted
http://www.virtualbox.org/manual/ch09.html#changedmi
Really has detailed answer for this.
You can set the bios serial number by doing this:
VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial" "System Serial"
The error you were getting is caused by the serial not being set as a string value, if you have a pure number you should prepend it with string: like so:
VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial" "string:1234"
Note: In case your VM is configured to use EFI firmware you need to replace pcbios by efi in the keys.
answered Jan 14 '12 at 11:56
Alex R
34525
1
Note that these instructions are for systems using BIOS. If your system uses EFI -- controlled by "Settings -> System -> Motherboard -> Enable EFI" -- then you need to replace "pcbios" with "efi" in the above commands.
– ntc2
Feb 15 at 20:01
add a comment |
up vote
19
down vote
accepted
up vote
19
down vote
accepted
http://www.virtualbox.org/manual/ch09.html#changedmi
Really has detailed answer for this.
You can set the bios serial number by doing this:
VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial" "System Serial"
The error you were getting is caused by the serial not being set as a string value, if you have a pure number you should prepend it with string: like so:
VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial" "string:1234"
Note: In case your VM is configured to use EFI firmware you need to replace pcbios by efi in the keys.
answered Jan 14 '12 at 11:56
Alex R
34525
http://www.virtualbox.org/manual/ch09.html#changedmi
Really has detailed answer for this.
You can set the bios serial number by doing this:
VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial" "System Serial"
The error you were getting is caused by the serial not being set as a string value, if you have a pure number you should prepend it with string: like so:
VBoxManage setextradata "VM name"
"VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial" "string:1234"
Note: In case your VM is configured to use EFI firmware you need to replace pcbios by efi in the keys.
answered Jan 14 '12 at 11:56
Alex R
34525
edited Nov 19 at 11:58
answered Jan 14 '12 at 11:56
Alex R
34525
answered Jan 14 '12 at 11:56
Alex R
34525
answered Jan 14 '12 at 11:56
Alex R
34525
34525
1
Note that these instructions are for systems using BIOS. If your system uses EFI -- controlled by "Settings -> System -> Motherboard -> Enable EFI" -- then you need to replace "pcbios" with "efi" in the above commands.
– ntc2
Feb 15 at 20:01
add a comment |
1
Note that these instructions are for systems using BIOS. If your system uses EFI -- controlled by "Settings -> System -> Motherboard -> Enable EFI" -- then you need to replace "pcbios" with "efi" in the above commands.
– ntc2
Feb 15 at 20:01
1
1
Note that these instructions are for systems using BIOS. If your system uses EFI -- controlled by "Settings -> System -> Motherboard -> Enable EFI" -- then you need to replace "pcbios" with "efi" in the above commands.
– ntc2
Feb 15 at 20:01
Note that these instructions are for systems using BIOS. If your system uses EFI -- controlled by "Settings -> System -> Motherboard -> Enable EFI" -- then you need to replace "pcbios" with "efi" in the above commands.
– ntc2
Feb 15 at 20:01
add a comment |
up vote
8
down vote
Not from any external settings. But you can from the code and then build it yourself:
Source file: DevPcBios.cpp
Line: 1014 READCFGSTR("DmiSystemSerial", pszDmiSystemSerial, "0");
Change "0" to whatever value you need.
EDIT: You can apparently use VBoxManage setextradata. I have used it in the past for other type of configurations (not bios related) and didn't test this particular setting. Give it a go:
VBoxManage setextradata *YourVMName* VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial "*yourserial*"
Otherwise... revert back to source code editing and building.
Best of luck.
edited Jul 15 '17 at 1:19
Andrea Lazzarotto
682314
answered Oct 15 '09 at 0:33
A Dwarf
17k13665
1
Hmm. Thanks - so close, but not there yet. I tried this: "c:Program FilesSunVirtualBoxVBoxManage.exe" setextradata "Demo Server" VBoxInternal/Devices/pcbios/0/Config /DmiSerial "123" It seemed to work, but when I launched the VM I got this error message: Failed to start the virtual machine Demo Server. Invalid configuration for device pcbios device (VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES). Unknown error creating VM (VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES). Deleting and recreating the machine definition fixed it, so no harm done. I think you're really close - any other suggestions?
– Roger
Oct 15 '09 at 1:22
hmm... did you make a verbatim copy/paste of your command to the comment box? Because there's no spave between /Config and /DmiSerial. Regardless I'll explore this further. Guess I will have to install VirtualBox. So far was relying only on my notes :)
– A Dwarf
Oct 15 '09 at 1:45
Bah! This head of mine. I post the relevant code line and then don't even check it against my much older notes. It's not /DmiSerial. It has been renamed sometime between version 1.5 and now. It is now /DmiSystemSerial
– A Dwarf
Oct 15 '09 at 1:53
Thanks, A Dwarf, for all your help. I tried replacing DmiSerial with DmiSystemSerial, reran the command line (without the space, which was a typo), and got the same error.
– Roger
Oct 15 '09 at 12:06
To my knowledge it can only mean this isn't fully implemented yet and you can't do it this way. At this point I'm afraid I cease to be useful. You should go to the VirtualBox forums and try from there. They are excellent folks and you'll get a more informed answer. I would however love to know the end result, if you would be so kind and post an answer to your own question when that happens. All the best.
– A Dwarf
Oct 15 '09 at 17:52
add a comment |
up vote
8
down vote
Not from any external settings. But you can from the code and then build it yourself:
Source file: DevPcBios.cpp
Line: 1014 READCFGSTR("DmiSystemSerial", pszDmiSystemSerial, "0");
Change "0" to whatever value you need.
EDIT: You can apparently use VBoxManage setextradata. I have used it in the past for other type of configurations (not bios related) and didn't test this particular setting. Give it a go:
VBoxManage setextradata *YourVMName* VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial "*yourserial*"
Otherwise... revert back to source code editing and building.
Best of luck.
edited Jul 15 '17 at 1:19
Andrea Lazzarotto
682314
answered Oct 15 '09 at 0:33
A Dwarf
17k13665
1
Hmm. Thanks - so close, but not there yet. I tried this: "c:Program FilesSunVirtualBoxVBoxManage.exe" setextradata "Demo Server" VBoxInternal/Devices/pcbios/0/Config /DmiSerial "123" It seemed to work, but when I launched the VM I got this error message: Failed to start the virtual machine Demo Server. Invalid configuration for device pcbios device (VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES). Unknown error creating VM (VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES). Deleting and recreating the machine definition fixed it, so no harm done. I think you're really close - any other suggestions?
– Roger
Oct 15 '09 at 1:22
hmm... did you make a verbatim copy/paste of your command to the comment box? Because there's no spave between /Config and /DmiSerial. Regardless I'll explore this further. Guess I will have to install VirtualBox. So far was relying only on my notes :)
– A Dwarf
Oct 15 '09 at 1:45
Bah! This head of mine. I post the relevant code line and then don't even check it against my much older notes. It's not /DmiSerial. It has been renamed sometime between version 1.5 and now. It is now /DmiSystemSerial
– A Dwarf
Oct 15 '09 at 1:53
Thanks, A Dwarf, for all your help. I tried replacing DmiSerial with DmiSystemSerial, reran the command line (without the space, which was a typo), and got the same error.
– Roger
Oct 15 '09 at 12:06
To my knowledge it can only mean this isn't fully implemented yet and you can't do it this way. At this point I'm afraid I cease to be useful. You should go to the VirtualBox forums and try from there. They are excellent folks and you'll get a more informed answer. I would however love to know the end result, if you would be so kind and post an answer to your own question when that happens. All the best.
– A Dwarf
Oct 15 '09 at 17:52
add a comment |
up vote
8
down vote
up vote
8
down vote
Not from any external settings. But you can from the code and then build it yourself:
Source file: DevPcBios.cpp
Line: 1014 READCFGSTR("DmiSystemSerial", pszDmiSystemSerial, "0");
Change "0" to whatever value you need.
EDIT: You can apparently use VBoxManage setextradata. I have used it in the past for other type of configurations (not bios related) and didn't test this particular setting. Give it a go:
VBoxManage setextradata *YourVMName* VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial "*yourserial*"
Otherwise... revert back to source code editing and building.
Best of luck.
edited Jul 15 '17 at 1:19
Andrea Lazzarotto
682314
answered Oct 15 '09 at 0:33
A Dwarf
17k13665
Not from any external settings. But you can from the code and then build it yourself:
Source file: DevPcBios.cpp
Line: 1014 READCFGSTR("DmiSystemSerial", pszDmiSystemSerial, "0");
Change "0" to whatever value you need.
EDIT: You can apparently use VBoxManage setextradata. I have used it in the past for other type of configurations (not bios related) and didn't test this particular setting. Give it a go:
VBoxManage setextradata *YourVMName* VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial "*yourserial*"
Otherwise... revert back to source code editing and building.
Best of luck.
edited Jul 15 '17 at 1:19
Andrea Lazzarotto
682314
answered Oct 15 '09 at 0:33
A Dwarf
17k13665
edited Jul 15 '17 at 1:19
Andrea Lazzarotto
682314
edited Jul 15 '17 at 1:19
Andrea Lazzarotto
682314
edited Jul 15 '17 at 1:19
Andrea Lazzarotto
682314
682314
answered Oct 15 '09 at 0:33
A Dwarf
17k13665
answered Oct 15 '09 at 0:33
A Dwarf
17k13665
answered Oct 15 '09 at 0:33
A Dwarf
17k13665
17k13665
1
Hmm. Thanks - so close, but not there yet. I tried this: "c:Program FilesSunVirtualBoxVBoxManage.exe" setextradata "Demo Server" VBoxInternal/Devices/pcbios/0/Config /DmiSerial "123" It seemed to work, but when I launched the VM I got this error message: Failed to start the virtual machine Demo Server. Invalid configuration for device pcbios device (VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES). Unknown error creating VM (VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES). Deleting and recreating the machine definition fixed it, so no harm done. I think you're really close - any other suggestions?
– Roger
Oct 15 '09 at 1:22
hmm... did you make a verbatim copy/paste of your command to the comment box? Because there's no spave between /Config and /DmiSerial. Regardless I'll explore this further. Guess I will have to install VirtualBox. So far was relying only on my notes :)
– A Dwarf
Oct 15 '09 at 1:45
Bah! This head of mine. I post the relevant code line and then don't even check it against my much older notes. It's not /DmiSerial. It has been renamed sometime between version 1.5 and now. It is now /DmiSystemSerial
– A Dwarf
Oct 15 '09 at 1:53
Thanks, A Dwarf, for all your help. I tried replacing DmiSerial with DmiSystemSerial, reran the command line (without the space, which was a typo), and got the same error.
– Roger
Oct 15 '09 at 12:06
To my knowledge it can only mean this isn't fully implemented yet and you can't do it this way. At this point I'm afraid I cease to be useful. You should go to the VirtualBox forums and try from there. They are excellent folks and you'll get a more informed answer. I would however love to know the end result, if you would be so kind and post an answer to your own question when that happens. All the best.
– A Dwarf
Oct 15 '09 at 17:52
add a comment |
1
Hmm. Thanks - so close, but not there yet. I tried this: "c:Program FilesSunVirtualBoxVBoxManage.exe" setextradata "Demo Server" VBoxInternal/Devices/pcbios/0/Config /DmiSerial "123" It seemed to work, but when I launched the VM I got this error message: Failed to start the virtual machine Demo Server. Invalid configuration for device pcbios device (VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES). Unknown error creating VM (VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES). Deleting and recreating the machine definition fixed it, so no harm done. I think you're really close - any other suggestions?
– Roger
Oct 15 '09 at 1:22
hmm... did you make a verbatim copy/paste of your command to the comment box? Because there's no spave between /Config and /DmiSerial. Regardless I'll explore this further. Guess I will have to install VirtualBox. So far was relying only on my notes :)
– A Dwarf
Oct 15 '09 at 1:45
Bah! This head of mine. I post the relevant code line and then don't even check it against my much older notes. It's not /DmiSerial. It has been renamed sometime between version 1.5 and now. It is now /DmiSystemSerial
– A Dwarf
Oct 15 '09 at 1:53
Thanks, A Dwarf, for all your help. I tried replacing DmiSerial with DmiSystemSerial, reran the command line (without the space, which was a typo), and got the same error.
– Roger
Oct 15 '09 at 12:06
To my knowledge it can only mean this isn't fully implemented yet and you can't do it this way. At this point I'm afraid I cease to be useful. You should go to the VirtualBox forums and try from there. They are excellent folks and you'll get a more informed answer. I would however love to know the end result, if you would be so kind and post an answer to your own question when that happens. All the best.
– A Dwarf
Oct 15 '09 at 17:52
1
1
Hmm. Thanks - so close, but not there yet. I tried this: "c:Program FilesSunVirtualBoxVBoxManage.exe" setextradata "Demo Server" VBoxInternal/Devices/pcbios/0/Config /DmiSerial "123" It seemed to work, but when I launched the VM I got this error message: Failed to start the virtual machine Demo Server. Invalid configuration for device pcbios device (VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES). Unknown error creating VM (VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES). Deleting and recreating the machine definition fixed it, so no harm done. I think you're really close - any other suggestions?
– Roger
Oct 15 '09 at 1:22
Hmm. Thanks - so close, but not there yet. I tried this: "c:Program FilesSunVirtualBoxVBoxManage.exe" setextradata "Demo Server" VBoxInternal/Devices/pcbios/0/Config /DmiSerial "123" It seemed to work, but when I launched the VM I got this error message: Failed to start the virtual machine Demo Server. Invalid configuration for device pcbios device (VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES). Unknown error creating VM (VERR_PDM_DEVINS_UNKNOWN_CFG_VALUES). Deleting and recreating the machine definition fixed it, so no harm done. I think you're really close - any other suggestions?
– Roger
Oct 15 '09 at 1:22
hmm... did you make a verbatim copy/paste of your command to the comment box? Because there's no spave between /Config and /DmiSerial. Regardless I'll explore this further. Guess I will have to install VirtualBox. So far was relying only on my notes :)
– A Dwarf
Oct 15 '09 at 1:45
hmm... did you make a verbatim copy/paste of your command to the comment box? Because there's no spave between /Config and /DmiSerial. Regardless I'll explore this further. Guess I will have to install VirtualBox. So far was relying only on my notes :)
– A Dwarf
Oct 15 '09 at 1:45
Bah! This head of mine. I post the relevant code line and then don't even check it against my much older notes. It's not /DmiSerial. It has been renamed sometime between version 1.5 and now. It is now /DmiSystemSerial
– A Dwarf
Oct 15 '09 at 1:53
Bah! This head of mine. I post the relevant code line and then don't even check it against my much older notes. It's not /DmiSerial. It has been renamed sometime between version 1.5 and now. It is now /DmiSystemSerial
– A Dwarf
Oct 15 '09 at 1:53
Thanks, A Dwarf, for all your help. I tried replacing DmiSerial with DmiSystemSerial, reran the command line (without the space, which was a typo), and got the same error.
– Roger
Oct 15 '09 at 12:06
Thanks, A Dwarf, for all your help. I tried replacing DmiSerial with DmiSystemSerial, reran the command line (without the space, which was a typo), and got the same error.
– Roger
Oct 15 '09 at 12:06
To my knowledge it can only mean this isn't fully implemented yet and you can't do it this way. At this point I'm afraid I cease to be useful. You should go to the VirtualBox forums and try from there. They are excellent folks and you'll get a more informed answer. I would however love to know the end result, if you would be so kind and post an answer to your own question when that happens. All the best.
– A Dwarf
Oct 15 '09 at 17:52
To my knowledge it can only mean this isn't fully implemented yet and you can't do it this way. At this point I'm afraid I cease to be useful. You should go to the VirtualBox forums and try from there. They are excellent folks and you'll get a more informed answer. I would however love to know the end result, if you would be so kind and post an answer to your own question when that happens. All the best.
– A Dwarf
Oct 15 '09 at 17:52
add a comment |
up vote
3
down vote
If you run that command, and get the error referenced by Roger, you need to back out the command by running the command without the last parameter (VALUE).
This removes the entry causing the error.
If you are unsure of what the last offending command was, open the ~~~.vbox (XML) file in the root of the VirtualMachines folder of the specific VM and review the EXTRADATA section.
Running the command-line call to vboxmanage is the best way to modify these.
Editing the xml file does not stick 100% of the time.
answered Sep 6 '12 at 14:18
Alex
311
add a comment |
up vote
3
down vote
If you run that command, and get the error referenced by Roger, you need to back out the command by running the command without the last parameter (VALUE).
This removes the entry causing the error.
If you are unsure of what the last offending command was, open the ~~~.vbox (XML) file in the root of the VirtualMachines folder of the specific VM and review the EXTRADATA section.
Running the command-line call to vboxmanage is the best way to modify these.
Editing the xml file does not stick 100% of the time.
answered Sep 6 '12 at 14:18
Alex
311
add a comment |
up vote
3
down vote
up vote
3
down vote
If you run that command, and get the error referenced by Roger, you need to back out the command by running the command without the last parameter (VALUE).
This removes the entry causing the error.
If you are unsure of what the last offending command was, open the ~~~.vbox (XML) file in the root of the VirtualMachines folder of the specific VM and review the EXTRADATA section.
Running the command-line call to vboxmanage is the best way to modify these.
Editing the xml file does not stick 100% of the time.
answered Sep 6 '12 at 14:18
Alex
311
If you run that command, and get the error referenced by Roger, you need to back out the command by running the command without the last parameter (VALUE).
This removes the entry causing the error.
If you are unsure of what the last offending command was, open the ~~~.vbox (XML) file in the root of the VirtualMachines folder of the specific VM and review the EXTRADATA section.
Running the command-line call to vboxmanage is the best way to modify these.
Editing the xml file does not stick 100% of the time.
answered Sep 6 '12 at 14:18
Alex
311
answered Sep 6 '12 at 14:18
Alex
311
answered Sep 6 '12 at 14:18
Alex
311
answered Sep 6 '12 at 14:18
Alex
311
311
add a comment |
add a comment |
up vote
2
down vote
The accepted answer didn't update the serial number correctly for me; instead, I followed these steps to successfully update the serial number. Note the guest OS was macOS and the host was windows.
NOTE: You must close virtualbox before running this command for it to be saved.
- Open the windows command prompt as administrator
cd "C:Program FilesOracleVirtualBox"
VBoxManage.exe setextradata "VM NAME" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "SERIAL_HERE"see source.*
Not sure why the pcbios command didn't work but efi did.
HELPFUL LINKS
- If you have trouble finding a valid serial follow the instructions here.
- If you're not sure what your vm name is run
VBoxManage.exe list vms.
answered Jan 15 '17 at 2:29
josh7weaver
211
Re you needing "efi" and accepted answer using "pcbios", this is probably because you're using (U)EFI and that person was using traditional BIOS. Whether you're using EFI or BIOS is determined by the "Settings -> System -> Motherboard -> Enable EFI" check box in VirtualBox.
– ntc2
Feb 15 at 18:38
add a comment |
up vote
2
down vote
The accepted answer didn't update the serial number correctly for me; instead, I followed these steps to successfully update the serial number. Note the guest OS was macOS and the host was windows.
NOTE: You must close virtualbox before running this command for it to be saved.
- Open the windows command prompt as administrator
cd "C:Program FilesOracleVirtualBox"
VBoxManage.exe setextradata "VM NAME" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "SERIAL_HERE"see source.*
Not sure why the pcbios command didn't work but efi did.
HELPFUL LINKS
- If you have trouble finding a valid serial follow the instructions here.
- If you're not sure what your vm name is run
VBoxManage.exe list vms.
answered Jan 15 '17 at 2:29
josh7weaver
211
Re you needing "efi" and accepted answer using "pcbios", this is probably because you're using (U)EFI and that person was using traditional BIOS. Whether you're using EFI or BIOS is determined by the "Settings -> System -> Motherboard -> Enable EFI" check box in VirtualBox.
– ntc2
Feb 15 at 18:38
add a comment |
up vote
2
down vote
up vote
2
down vote
The accepted answer didn't update the serial number correctly for me; instead, I followed these steps to successfully update the serial number. Note the guest OS was macOS and the host was windows.
NOTE: You must close virtualbox before running this command for it to be saved.
- Open the windows command prompt as administrator
cd "C:Program FilesOracleVirtualBox"
VBoxManage.exe setextradata "VM NAME" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "SERIAL_HERE"see source.*
Not sure why the pcbios command didn't work but efi did.
HELPFUL LINKS
- If you have trouble finding a valid serial follow the instructions here.
- If you're not sure what your vm name is run
VBoxManage.exe list vms.
answered Jan 15 '17 at 2:29
josh7weaver
211
The accepted answer didn't update the serial number correctly for me; instead, I followed these steps to successfully update the serial number. Note the guest OS was macOS and the host was windows.
NOTE: You must close virtualbox before running this command for it to be saved.
- Open the windows command prompt as administrator
cd "C:Program FilesOracleVirtualBox"
VBoxManage.exe setextradata "VM NAME" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "SERIAL_HERE"see source.*
Not sure why the pcbios command didn't work but efi did.
HELPFUL LINKS
- If you have trouble finding a valid serial follow the instructions here.
- If you're not sure what your vm name is run
VBoxManage.exe list vms.
answered Jan 15 '17 at 2:29
josh7weaver
211
answered Jan 15 '17 at 2:29
josh7weaver
211
answered Jan 15 '17 at 2:29
josh7weaver
211
answered Jan 15 '17 at 2:29
josh7weaver
211
211
Re you needing "efi" and accepted answer using "pcbios", this is probably because you're using (U)EFI and that person was using traditional BIOS. Whether you're using EFI or BIOS is determined by the "Settings -> System -> Motherboard -> Enable EFI" check box in VirtualBox.
– ntc2
Feb 15 at 18:38
add a comment |
Re you needing "efi" and accepted answer using "pcbios", this is probably because you're using (U)EFI and that person was using traditional BIOS. Whether you're using EFI or BIOS is determined by the "Settings -> System -> Motherboard -> Enable EFI" check box in VirtualBox.
– ntc2
Feb 15 at 18:38
Re you needing "efi" and accepted answer using "pcbios", this is probably because you're using (U)EFI and that person was using traditional BIOS. Whether you're using EFI or BIOS is determined by the "Settings -> System -> Motherboard -> Enable EFI" check box in VirtualBox.
– ntc2
Feb 15 at 18:38
Re you needing "efi" and accepted answer using "pcbios", this is probably because you're using (U)EFI and that person was using traditional BIOS. Whether you're using EFI or BIOS is determined by the "Settings -> System -> Motherboard -> Enable EFI" check box in VirtualBox.
– ntc2
Feb 15 at 18:38
add a comment |
up vote
1
down vote
Try using a serial number that contains 20 byte hexadecimal string:
VBoxManage setextradata "VM name" "VBoxInternal/Devices/ahci/0/Config/Port0/SerialNumber" "serial"
(Reference)
edited Mar 9 '12 at 19:12
Diogo
21.8k54132209
answered Aug 16 '11 at 14:14
Ricardo Kiyoshi Batori
111
add a comment |
up vote
1
down vote
Try using a serial number that contains 20 byte hexadecimal string:
VBoxManage setextradata "VM name" "VBoxInternal/Devices/ahci/0/Config/Port0/SerialNumber" "serial"
(Reference)
edited Mar 9 '12 at 19:12
Diogo
21.8k54132209
answered Aug 16 '11 at 14:14
Ricardo Kiyoshi Batori
111
add a comment |
up vote
1
down vote
up vote
1
down vote
Try using a serial number that contains 20 byte hexadecimal string:
VBoxManage setextradata "VM name" "VBoxInternal/Devices/ahci/0/Config/Port0/SerialNumber" "serial"
(Reference)
edited Mar 9 '12 at 19:12
Diogo
21.8k54132209
answered Aug 16 '11 at 14:14
Ricardo Kiyoshi Batori
111
Try using a serial number that contains 20 byte hexadecimal string:
VBoxManage setextradata "VM name" "VBoxInternal/Devices/ahci/0/Config/Port0/SerialNumber" "serial"
(Reference)
edited Mar 9 '12 at 19:12
Diogo
21.8k54132209
answered Aug 16 '11 at 14:14
Ricardo Kiyoshi Batori
111
edited Mar 9 '12 at 19:12
Diogo
21.8k54132209
edited Mar 9 '12 at 19:12
Diogo
21.8k54132209
edited Mar 9 '12 at 19:12
Diogo
21.8k54132209
21.8k54132209
answered Aug 16 '11 at 14:14
Ricardo Kiyoshi Batori
111
answered Aug 16 '11 at 14:14
Ricardo Kiyoshi Batori
111
answered Aug 16 '11 at 14:14
Ricardo Kiyoshi Batori
111
111
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f55561%2fhow-can-i-change-the-bios-serial-number-in-virtualbox%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Any particular reason you want to do this?
– Jared Harley
Oct 15 '09 at 0:15
1
Yes. I have a PC inventory software tool that uses the BIOS serial number to uniquely identify computers. It works fine for physical hardware and for VMs from other vendors, but doesn't know how to handle multiple VirtualBox VMs.
– Roger
Oct 15 '09 at 0:52
edited my answer to reflect the error you caught.
– A Dwarf
Oct 15 '09 at 2:08
You have any news on this, Roger? Would love to know how it turned out.
– A Dwarf
Oct 31 '09 at 3:51
I never determined how to do it. I got a few responses on the VirtualBox forums, but found nothing that worked. If I run across the answer, I'll be sure to add an update here.
– Roger
Nov 4 '09 at 23:42