VirtualBox

Ticket #12244 (closed defect: fixed)

Opened 6 months ago

Last modified 6 months ago

VirtualBox 4.3 - wrong hardwareuuid => Fixed in SVN

Reported by: www0815 Owned by:
Priority: major Component: other
Version: VirtualBox 4.3.0 Keywords: UUID, hardwareuuid
Cc: Guest type: Windows
Host type: Linux

Description (last modified by ramshankar) (diff)

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

comment:1 follow-up: ↓ 5 Changed 6 months ago by bluec0re

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

  <Machine uuid="{30761f24-1e22-49c8-a4a5-dedc4a7ed74c}" ...>
    ....
    <Hardware version="2">

After

  <Machine uuid="{30761f24-1e22-49c8-a4a5-dedc4a7ed74c}" ...>
    ....
    <Hardware version="2" uuid="{30761f24-1e22-49c8-a4a5-dedc4a7ed74c}">

comment:2 Changed 6 months ago by www0815

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 Changed 6 months ago by ramshankar

  • Description modified (diff)

comment:4 Changed 6 months ago by frank

  • Summary changed from VirtualBox 4.3 - wrong hardwareuuid to VirtualBox 4.3 - wrong hardwareuuid => Fixed in SVN

Thanks for the report! This bug will be fixed in the next maintenance release.

comment:5 in reply to: ↑ 1 Changed 6 months ago by RickG123

Replying to bluec0re:

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

  <Machine uuid="{30761f24-1e22-49c8-a4a5-dedc4a7ed74c}" ...>
    ....
    <Hardware version="2">

After

  <Machine uuid="{30761f24-1e22-49c8-a4a5-dedc4a7ed74c}" ...>
    ....
    <Hardware version="2" uuid="{30761f24-1e22-49c8-a4a5-dedc4a7ed74c}">

This workaround does not work for the issue of an invalid GUID for PXE boot as I described in https://www.virtualbox.org/ticket/12238

comment:6 Changed 6 months ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Thanks for the report! Fixed in 4.3.2.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use