Can not run an emulator

Once I execute the ./run_webos_emulator.sh script. It doesn’t seem to work properly and shows an error popup.

macOS Catalina 10.15.7
Virtualbox 6.1.40 r154048 (Qt5.6.3)

Sorry for the late reply. We checked it with several PCs, but the issue was not reproduced. Please reinstall the emulator. If the problem persists, please share your screenshot from the step 1 to 2 here. Thank you.

I’m having the exact same problem.

macOS Catalina 11.7 (20G817)
VirtualBox 6.1.40 r154048 (Qt5.6.3)

Have you figured out how to get around this?

Please check our reply above and share a screenshot if the problem persists. Thank you.

Running ./vm_register.command seems to work correctly, as it returns nothing. But ./run_webos_emulator.sh shows the exact same message OP posted.
Although I can launch the created image by double clicking the VM’s name on VirtualBox, I have no remote control.

Can we get a screenshot of the terminal? You can email us at developer@lge.com.

To run the remote control unit emulator, ./run_webos_emulator.sh must be completed. Please check the following.

  • Check if your Mac uses Apple Silicon. Currently, Intel chips are only supported.
  • Make sure vboxmanage is running. (You can check this using vboxmanage -v command.)
  • Try another version of VirtualBox. You can download the v6.1.30 at https://www.virtualbox.org/wiki/Download_Old_Builds_6_1.

I am having the exact same error, my specs:

  • MacOS Monterey 12.6.3
  • VirtualBox 6.1.30r148432
  • Processor 2,6 GHz 6-Core Intel Core i7

Did anyone find any solution?

Screenshot 2023-06-28 at 11.58.15

Have you checked the which vboxmanage command?

Same exact issue here.
VirtualBox version 6.1.46 r158378 (Qt5.6.3)
MacBook Pro 2019
2.6 GHz 6-Core Intel Core i7
Radeon Pro 555X 4 GB
Intel UHD Graphics 630 1536 MB

$ which vboxmanage
/usr/local/bin/vboxmanage
$ vboxmanage -v
6.1.46r158378

Please try a different version of VirtualBox. You can download the v6.1.30 at https://www.virtualbox.org/wiki/Download_Old_Builds_6_1.

hi. I have the exact same issue.

$ which vboxmanage
/usr/local/bin/vboxmanage
$ vboxmanage -v
vboxmanage -v 6.1.30r148432

Please make sure your PC meets the system requirements. Thank you.