VBoxManage Question

Temporary forum to discuss issues and problems during a VirtualBox Beta or Release Candidate phase.
Post Reply
multiOS
Volunteer
Posts: 1348
Joined: 14. Sep 2019, 16:51
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux, BSD
Location: United Kingdom

VBoxManage Question

Post by multiOS »

NOT a 'bug' report just a query. Is there an undocumented command which completely reverses the effects of the unsupported command?

Code: Select all

VBoxManage setextradata global VBoxInternal2/EnableX86OnArm 1
Neither of the following appears to work, but do disable the ability to run existing VMs:

Code: Select all

VBoxManage setextradata global VBoxInternal2/EnableX86OnArm 0
VBoxManage setextradata global VBoxInternal2/EnableX86OnArm
Admin edit: added the missing "global" and fixed the quotes by removing them all because they're not needed.
klaus
Oracle Corporation
Posts: 1736
Joined: 10. May 2007, 14:57

Re: VBoxManage Question

Post by klaus »

If you do it right then it works ;) The "VBoxManage setextradata" command is quite well documented. Run it as is to get short help output. If you want the full documentation use "VBoxManage help setextradata". This works for all VBoxManage commands. For some of them you'll get a lot of documentation.

The first one enables x86-on-arm (the value for the extradata key must be 1, nothing else enables it).

The second command sets the value differently which disables x86-on-arm. You could put pretty much anything other than 1 in this place.

The third command deletes the extradata key by not giving any value, also disabling x86-on-arm and making the VM config file a little smaller again.
Post Reply