answered
2020-02-19 11:02:06 +0200
tl;dr Sailfish SDK must be installed (somewhere) under user home directory. ~/.local/SailfishSDK
is likely to work well.
/opt
is a location for system-wide app installation. Sailfish SDK supports per-user installations only and as such it shouldn't use any system-wide location.
One reason for not supporting system-wide installations is that the issue of sharing VirtualBox VMs between users would have to be sorted out somehow. For each VM, there would have to be one system-wide template and per-user writable clones. In most cases there would be just one user on the machine, so all it would add would be wasting disk space a lot.
Furthermore, installing Sailfish SDK outside user home directory is not supported due to the limitations dictated by VirtualBox (in its default configuration).
You should be able to install Sailfish SDK e.g. under $HOME/.local/SailfishSDK
if you want to keep your home directory clean.
What does command "vboxmanage list vms" say?
Ville Nummela ( 2019-10-15 07:15:42 +0200 )editWhat version of Virtualbox are you using?
Related;
https://together.jolla.com/question/101886/solved-no-virtual-machine-with-the-name-mersdk-found-check-your-installation/
Spam Hunter ( 2019-10-15 12:52:35 +0200 )edit"exTern OS" {c2f5023a-88a9-444f-8808-5cb746c79e5f}
"Kubuntu" {e2c263b1-d39b-4f92-ae5b-a379a55f10bb}
Oracle VM VirtualBox Manager 5.2.34_Ubuntu
nshiell ( 2020-02-13 03:06:03 +0200 )editSo it's clear that neither the build engine or emulator vms are not there.
Could you paste the output of command 'grep -m 1 -A 10 "Build Engine" ~/SailfishOS/InstallationLog.txt" - it might give us some hint on what has went wrong?
Ville Nummela ( 2020-02-13 07:51:49 +0200 )editThanks for the reply, I did install sailfish to /opt/SailfishOS instead of ~/SailfishOS, could that be an issue?
Output of
grep -m 1 -A 10 "Build Engine" /opt/SailfishOS/InstallationLog.txt
[162997] - arguments: /usr/bin/VBoxManage, createvm, --name, Sailfish OS Build Engine, --register, --basefolder, /opt/SailfishOS/mersdk, UNDOEXECUTE, /usr/bin/VBoxManage, unregistervm, --delete, Sailfish OS Build Engine, errormessage=Please shutdown the "Sailfish OS Build Engine" VM
[162997] Done
[162998] perform org.merproject.mersdk operation: Execute
[162998] - arguments: /usr/bin/VBoxManage, createvm, --name, Sailfish OS Build Engine, --register, --basefolder, /opt/SailfishOS/mersdk, UNDOEXECUTE, /usr/bin/VBoxManage, unregistervm, --delete, Sailfish OS Build Engine, errormessage=Please shutdown the "Sailfish OS Build Engine" VM
[162998] /usr/bin/VBoxManage" started, arguments: "createvm --name Sailfish OS Build Engine --register --basefolder /opt/SailfishOS/mersdk
[163098] Done
[163098] backup org.merproject.mersdk operation: Execute
[163098] - arguments: /usr/bin/VBoxManage, modifyvm, Sailfish OS Build Engine, --description, ATTENTION: This virtual machine is managed by the Sailfish SDK. Do not try to alter it!
[163098] Done
[163098] perform org.merproject.mersdk operation: Execute
nshiell ( 2020-02-13 16:41:33 +0200 )edit[163098] - arguments: /usr/bin/VBoxManage, modifyvm, Sailfish OS Build Engine, --description, ATTENTION: This virtual machine is managed by the Sailfish SDK. Do not try to alter it!