Author Topic: Failed to start virtual machine "MerSDK"  (Read 4067 times)

0 Members and 1 Guest are viewing this topic.

Offline jolle

  • Newbie
  • *
  • Posts: 3
    • View Profile
  • Phone model: Nokia N9
Failed to start virtual machine "MerSDK"
« on: December 11, 2014, 10:00:42 PM »
Hello everybody,

recently I bought a jolla phone, after using the N9 for 4 years.
The system impressed me so much, that I want to try developping an app. Unfortunately I couldnt get it done.
I didnīt even manage to start the MerSDK:

 >Error connecting to "MerSDK" virtual machine: Failed to start virtual machine "MerSDK"<

Can anybody help me?


Offline Vistaus

  • Hero Member
  • *****
  • Posts: 668
    • View Profile
  • Phone model: The Jolla phone!
Re: Failed to start virtual machine "MerSDK"
« Reply #1 on: December 11, 2014, 11:05:32 PM »
You need to have Virtualbox installed. Could you ensure that and then run Virtualbox and start MerSDK from the Virtualbox interface and see if that outputs any errors?

Offline jolle

  • Newbie
  • *
  • Posts: 3
    • View Profile
  • Phone model: Nokia N9
Re: Failed to start virtual machine "MerSDK"
« Reply #2 on: December 12, 2014, 01:34:38 PM »
Sorry, that I wasnīt so specific. I was already sleeping, when I wrote the question yesterday.

First I installed the newest Oracle VM and the newest Sailfish SDK:
> The Emulator started but didnīt work. There was some kid of problem with the BIOS.

The removed both an installed it again with an older version of Oracle VM (because I read something like that anyhwere):
> Didnīt work again.

The I installed the newest versions of VM and SDK:
> The MerSDK neither can be started from the Qt-IDE nor from the Oracle VM. I always get the Error:
Quote
The virtual machine 'MerSDK' has terminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\SailfishOS\mersdk\MerSDK\Logs\VBoxStartup.log'.

Fehlercode:E_FAIL (0x80004005)
Komponente:Machine
Interface:IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

Offline ShaneQful

  • Newbie
  • *
  • Posts: 2
    • View Profile
  • Phone model: Jolla
Re: Failed to start virtual machine "MerSDK"
« Reply #3 on: January 03, 2015, 02:55:56 AM »
I had a a similar issue and fixed it. I had VT-x disabled in my BIOS.

VT-x is an Intel virtualization technology which the MerSDK VM seems to rely on you should be able to find the option in your BIOS. You can checkout my blog post on the issue for more details:

http://www.softwareontheside.info/2015/01/mersdk-not-starting-enabled-vt-x-in.html

Offline jolle

  • Newbie
  • *
  • Posts: 3
    • View Profile
  • Phone model: Nokia N9
Re: Failed to start virtual machine "MerSDK"
« Reply #4 on: January 18, 2015, 07:53:48 PM »
Thank you for the help. I will try getting it to work.

Offline Javi

  • Newbie
  • *
  • Posts: 4
    • View Profile
  • Phone model: Jolla
Re: Failed to start virtual machine "MerSDK"
« Reply #5 on: January 25, 2015, 09:16:34 PM »
I had a a similar issue and fixed it. I had VT-x disabled in my BIOS.

VT-x is an Intel virtualization technology which the MerSDK VM seems to rely on you should be able to find the option in your BIOS. You can checkout my blog post on the issue for more details:

http://www.softwareontheside.info/2015/01/mersdk-not-starting-enabled-vt-x-in.html

I had the same problem and this solved it for me, thank you!

These were the error messages I was getting, for anyone else having the same problem:

Quote
Failed to open a session for the virtual machine MerSDK.

AMD-V is disabled in the BIOS (or by the host OS). (VERR_SVM_DISABLED).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

AND

Failed to open a session for the virtual machine SailfishOS Emulator.

AMD-V is disabled in the BIOS (or by the host OS). (VERR_SVM_DISABLED).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

Offline hsjpekka

  • Newbie
  • *
  • Posts: 3
    • View Profile
  • Phone model: Jolla
Re: Failed to start virtual machine "MerSDK"
« Reply #6 on: February 09, 2015, 07:09:05 PM »
I disabled VT-x/AMD-V (vbox: settings - system - acceleration).

MerSDK and sailfishOS emulator seem to work.

Offline Objectifnul

  • Newbie
  • *
  • Posts: 8
  • Mainly professional user.
    • View Profile
  • Phone model: Jolla
Re: Failed to start virtual machine "MerSDK"
« Reply #7 on: June 14, 2015, 08:51:45 PM »
Hi.
My Oracle Virtualbox (4.3.28) is unable to start MERsdk and SailfishOS Emulator on my Thinkpad X201.

("The virtual machine 'SailfishOS Emulator' has terminated unexpectedly during startup with exit code 1 (0x1).
Error code : E_FAIL (0x80004005)
Component : Machine
Interface : IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}")

According to some sources, that's because of Intel TXT (Trusted eXecution Technology) embedded in Lenovo BIOS.
See here => https://forums.virtualbox.org/viewtopic.php?f=6&t=43943

So I disabled TXT in my BIOS setup, but this didn't fix the issue.

Any other hint?

Offline frbelotto

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: Failed to start virtual machine "MerSDK"
« Reply #8 on: June 15, 2015, 05:33:27 AM »
Lol! Same error here!
I am such a great developer! I cant event make the SDK works! lol

Kidding, I am not a developer but I am trying to use the SDK to become familiar to system environment.

I tried to disable de "VT-X" option as said before but still get

"No virtual machine with name MerSDK found".

I can run it directly from virtual box, even the emulator, but I cant connect to qt-creator.

Offline frbelotto

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: Failed to start virtual machine "MerSDK"
« Reply #9 on: June 18, 2015, 03:15:50 AM »
for those who had the same trouble, the new SDK is the solution!

Offline jebradl

  • Newbie
  • *
  • Posts: 1
    • View Profile
Re: Failed to start virtual machine "MerSDK"
« Reply #10 on: June 30, 2015, 03:06:16 AM »
The new SDK (1506) isn't the answer to all the problems of the SDK failing to work. I get a message, "AttachedDevice/Image element is missing" regarding the MerSDK.vbox file (which is where it should be).

Offline deFender

  • Newbie
  • *
  • Posts: 1
    • View Profile
Re: Failed to start virtual machine "MerSDK"
« Reply #11 on: July 22, 2015, 11:44:26 AM »
I might be kicking in open doors, but try a Virtualbox of version 4.x instead.