Import in VirtualBox

[TerrorSource]

Hi,

I want to have the VDI created by the script directly in VirtualBox but i cannot get it to work properly.
When i create a new VM in VirtualBox and select the VDI as hdd it will not boot.
I've edited this in the VM:
Floppy: disabled
Memory: 4096
Processor: 2
Video Memory: 128mb
USB: USB 3.0 controller

Does anyone has an idea how i get this working?
now i need to run "sudo sh runMojaveVirtualbox.sh run" each time i want to start it.

[AlexanderWillner]

Hi,

the details how the VM is generated by the script can be seen at

runMacOSinVirtualBox/runMojaveVirtualbox.sh

Line 320 in 238ba21

VBoxManage createvm --register --name "$VM_NAME" --ostype MacOS1013_64

No need to use sudo to run the script with the parameter run.

You also can just start the VM in the VirtualBox GUI, as the VM should be visible there. The script is just setting up everything once. Afterwards you could also delete it.

[coolidm]

I also can't see the VM listed in virtual box or create a new one with the VDI. I would like to modify some settings on the config, but cant find the actual file.

[AlexanderWillner]

The default folder is:

runMacOSinVirtualBox/runMojaveVirtualbox.sh

Line 23 in 238ba21

readonly DST_DIR="${DST_DIR:-$HOME/VirtualBox VMs}"

It should look like this:

Not sure why you're not seeing the VM. Where are your others stored?

[coolidm]

It is not listed even when using "vboxmanage list vms", however I am still able to launch using the make process. Trying to register the vdi file shows an error "VBoxManage: error: Extra content at the end of the document. "

Is this the same issue as listed or should I create a new one?

[HigH-HawK]

I'm having the same issue as coolidm and noticed something which may be the cause of the VM not showing up in the list.

All manual setup VMs in VirtualBox are stored under /Users/your.username/VirtualBox VMs but the script moves the required .vbox to /var/root/VirtualBox VMs. This could however be caused by running make all with sudo but I am not sure of this yet.

On the other hand you have to run it as sudo because you get an error if you are not doing so.

[AlexanderWillner]

@HigH-HawK this could actually be the issue. @coolidm / @TerrorSource : can you verify? In that case we've to check in which case the root home is used (and not the user home)...

[HigH-HawK]

@AlexanderWillner I have done another test and can confirm that when running the make all command as sudo it puts the .vbox file in the above mentioned path /var/root/VirtualBox VMs

I guess the $HOME variable is being filled with the root home upon issuing the make ... command preceding with sudo

[HigH-HawK]

Hey Alex, I had a little thought about the $HOME issue. Would it be possible to create some sort of HOME variable right at the beginning of the script and filling this variable with the User HOME?

Example: readonly USER_HOME=$HOME

Since it is readonly it should not be possible for the script, to override this variable in case sudo needs to be used and the *.vbox files will still be saved in the right User HOME? My understanding of the readonly property could however be wrong at this time. It's just an idea to prevent the root HOME from being used.

[AlexanderWillner]

Actually, running a command via sudo should not change the $HOME variable, only when the parameter -H has been used. This is why the script works for me and many others, but not for those of you that are in this thread. Not sure yet what is special about your environment.

how can I fix my vm not showing in list? im not very technical

[AlexanderWillner]

Closing stalled issues.