0 votes
Hello,

I would like to test Dataiku on Windows via a virtual machine.

I have followed all the steps of the following link:

https://www.dataiku.com/dss/trynow/virtualbox/

Yet, at the end, it doesn't work when I open the URL in my Firefow browser. The web page is like I wouldn't have access to internet (while I have, since I can log on other websites).

Do you know which problems can happen at this step?

Thanks
asked by anonymous
retagged by

1 Answer

+1 vote

So, I have been struggling with some of the same issues.  Here are the things that I had to change in order to get things going.

1. The OS on the VM is a 64bit version.  On importation of the virtual machine the Operating system selected was a 32bit Ubuntu.  I had to change to a 64bit Unbuntu.

2. Then I go an error that my bios was not set up for virtualization.  Using the VirtualBox Documentation. Once I found the right spot in my bios, then the virtual machine started.

Once I go through that the start up screen eventual came up on the VM looking like this.

Once I got to that screen I was able in my browser to go to http://127.0.0.1:10000 and go to the web site.  Then I had to figure out the startup password for the site.  The documentation is fairly clear at that point.

 

answered by
edited by
Hi,

Can you please share more details about step#2 - bios not set up for virtualization.

Following the steps listed here - https://www.dataiku.com/dss/trynow/virtualbox/

I am able to follow till step#3 whereafter I am unable to start the machine (using normal start from the start menu), getting the following error:

Failed to open a session for the virtual machine dataiku-dss-4.0.1.

VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

I was able to find conflicting advice on internet regarding the following:
Virtual Box "Settings" > System Settings > Processor > PAE/NX option
Some say to enable it, others to disable it, and some to disable and then enable it back again.

SOLUTION: I reduced the RAM allocation and get past the above error without requiring any changes to BIOS

Thanks /
598 questions
608 answers
445 comments
330 users