Opened 10 years ago
Last modified 10 years ago
#12244 closed defect
VirtualBox 4.3 - wrong hardwareuuid — at Version 3
Reported by: | www0815 | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.3.0 |
Keywords: | UUID, hardwareuuid | Cc: | |
Guest type: | Windows | Host type: | Linux |
Description (last modified by )
If you run the following command:
VBoxManage --nologo showinfo --machinereadable "YOUR MACHINE NAME" | grep 'hardwareuuid'
You get the following result:
with Version 4.2.18: hardwareuuid="30761f24-1e22-49c8-a4a5-dedc4a7ed74c" (or anything similar)
with Version 4.3: hardwareuuid="00000000-0000-0000-0000-000000000000"
This is very annoying, because lot's of scripts use the variable hardwareuuid to start or modify a virtual machine. But with such a hardwareuuid all scripts won't work anymore. Please correct this.
By the way: The following command doesn't have any effect in version 4.3:
VBoxManage modifyvm "YOUR MACHINE NAME" --hardwareuuid "30761f24-1e22-49c8-a4a5-dedc4a7ed74c"
The hardware uuid is after this command still full of zeros.
Change History (3)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
That is a nice workaround. Thank you very much.
Could maybe anyone make a short comment here, when it is corrected in an upcoming maintenance release?
comment:3 by , 10 years ago
Description: | modified (diff) |
---|
Possible Workaround:
if the uuid (from the Machine tag in the vbox file) is added to the Hardware tag, the VBoxManage tool works as desired.
e.g. Before
After