Revision history [back]

Installing the latest Sailfish SDK (Beta-1602) on Linux 64bit with Virtual Box 5.1.0 leaves the Virtual Machines MerSDK and Emulator not connected to the local network due to an error in the default VM configuration.

This problem surfaces as a MerSDK timeout, as the VM starts and runs but never appears on the network for ssh connection.

The fix is to go to Settings > Network > Adapter 1 & 2 > Advanced, and check the Cable Connected checkbox.

It would be nice if this was fixed, or put into the Known Issues for anyone who might come across this in the future.

Installing the latest Sailfish SDK (Beta-1602) on Linux 64bit with Virtual Box 5.1.0 leaves the Virtual Machines MerSDK and Emulator not connected to the local network due to an error in the default VM configuration.

This problem surfaces as a MerSDK timeout, as the VM starts and runs but never appears on the network for ssh connection.

The fix is to go to Settings > Network > Adapter 1 & 2 > Advanced, and check the Cable Connected checkbox.checkbox for each VM in Virtual Box Manager.

It would be nice if this was fixed, or put into the Known Issues for anyone who might come across this in the future.

Installing the latest Sailfish SDK (Beta-1602) on Linux 64bit with Virtual Box 5.1.0 leaves the Virtual Machines MerSDK and Emulator not connected to the local network due to an error in the default VM configuration.

This problem surfaces as a MerSDK timeout, as the VM starts and runs but never appears on the network for ssh connection.

The fix is to go to Settings > Network > Adapter 1 & 2 > Advanced, and check the Cable Connected checkbox for each VM in Virtual Box Manager.

It would be nice if this was fixed, or put into the Known Issues for anyone who might come across this in the future.