Ask / Submit

Unable to connect to build server, emulator [Win10, SDK2.24]

asked 2019-09-17 07:43:05 +0300

bongo gravatar image

SDK launches these OK, but never connects

  • Tried turning off windows firewall
  • tried running virtualbox manager as admin, and starting vms from there
  • virtualbox was warning about error in configuration (no hardware virtualization), so fixed that.
edit retag flag offensive close delete


Facing the same issue

Timeout connecting to the "Sailfish OS Build Engine" virtual machine. Failed to connect to the 'Sailfish OS Build Engine' virtual machine: Failed to establish SSH connection with virtual machine "Sailfish OS Build Engine": SSH connection failure. ssh_exchange_identification: read: Connection reset by peer

santhoshmanikandan ( 2019-09-17 08:00:39 +0300 )edit

More or less the same problem for me, just haven't got round to detailing a report, you've done it though, so thanks and voted +1

I did what you have listed and a few other adjustments, nothing helped, neither connect. Tried full clean install of both SDK and Vbox, made no difference.

I did note than when SDK was newly installed, it first failed to open any of my previously running projects, upon selecting OK to close the dialog, my project opens!, but the qml/pages are strewn in red error messages, with things like PageHeader is not in this scope (words to the effect) - stuff that had been compiling beforehand. All of the problems began when accepting YES to updating the SDK from an installation that was.....well, ok if a bit flaky on connecting to build machine, but got there eventually, mostly.

Edz ( 2019-09-17 08:05:41 +0300 )edit

What OS are you guys trying?

bongo ( 2019-09-17 14:23:23 +0300 )edit

@bongo Windows 10 in my case

santhoshmanikandan ( 2019-09-17 20:37:00 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2019-09-17 14:45:08 +0300

Edz gravatar image

updated 2019-09-17 15:08:09 +0300

I post this as an answer simply because it worked for me, hopefully it may work for you also;

@bongo @Ingvix @martyone @santhoshmanikandan - I think I have solved the problem! (at least for myself).

For your information, usually I use Windows 7 64bit Ultimate, on another hdd in my laptop I have a newly installed copy of Windows 10, both OS'es have fresh installs of VB and SFOS SDK.

Regarding starting problems for SailfishOS build engine and emulator:

I had to boot to BIOS (haven't had to do that in years!) and select "ENABLE VIRTUALISATION TECHNOLOGY" (words to the effect, didn't make a note!, sorry) and after booting back into Windows 7 and undoing all the options in Sailfish virtualbox settings I had previously , I am now up and running......but with problems that I'll list in a fresh question.

RECAP: Reboot PC/laptop, go to BIOS and look for a setting similar words to Enable virtualisation technology; enable it, save that to BIOS boot back into windows, use SDK, compile, enjoy.

NOTE* - None of this sht appeared to be necessary prior to the last SDK update. I now note these very problems are mentioned here;

edit flag offensive delete publish link more



@Edz congrats! The requirements on SDK side have not changed for years in this respect. VirtualBox or even OS update might be to blame.

martyone ( 2019-09-17 15:24:22 +0300 )edit

Unfortunately I couldn't find any similar setting in my BIOS. But it's not a huge issue as I'm mainly doing the developing on linux machine anyway.

Ingvix ( 2019-09-17 16:50:27 +0300 )edit

@Edz If I enable Virtualization in BIOS I get this error. That's the reason I switched it off in the last SDK version

Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED).

Will try to remove Hyper-V and other workarounds given to solve above problem.

Edit: Running the following command after disabling HyperV, Container, WSL, Virtualization Platform fixed the issue for me.

RUN > CMD > bcdedit /set hypervisorlaunchtype off then reboot host machine.

santhoshmanikandan ( 2019-09-17 20:21:30 +0300 )edit

@Edz Thanks that got that going.

Now I have to work out why I get " RPM Validation: RPM File: [Userbuild-play1c-SailfishOS_3_1_0_12_i486_in_Sailfish_OS_Build_Engine-DebugRPMSplay1c-0.1-1.noarch.rpm] Only one RPM file can be specified"

bongo ( 2019-09-18 02:11:12 +0300 )edit

@bongo, then check the contents of your spec file.

Edz ( 2019-09-18 15:40:48 +0300 )edit
Login/Signup to Answer

Question tools



Asked: 2019-09-17 07:43:05 +0300

Seen: 144 times

Last updated: Sep 17 '19