My virtual machine hangs on after starting rstudio-quickstart-18.04-amd64-20190209. I can stop it in manager of Windows only.
The one mistake I found in the VBox.log:
ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={ab4164db-c13e-4dab-842d-61ee3f0c1e87} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=-37
Very strange! Do you see anything like this in the logs?
TM: Host/VM is not suitable for using TSC mode 'RealTscOffset',
request to change TSC mode ignored
This is an issue we have seen before that manifests in this way. Unfortunately, we have not found the solution yet, as it seems to be a configuration issue on the Host / VM.
Alternatively, you might copy/paste more of the logs to see if there is anything else that might be related? The error about taking a screenshot seems (hopefully) unrelated. The behavior you are seeing is just no activity / nothing shows up in the browser at http://localhost:5000 ?
Very strange!! Everything looks healthy!! And honestly, it looks like it is running! Do you mind sending a screenshot of what http://localhost:5000 looks like in your browser?
This is a bit more advanced, but another thing you might try is going to Settings -> Network -> Advanced -> Port Forwarding.
This allows SSHing into the VirtualBox image with something like the following. If the box is hung somehow, this should fail, otherwise you should get a password prompt.
Very strange!! It does look like basically nothing is happening on the VM. I did a cursory search for this type of issue within VirtualBox. It looks like tinkering with the Settings for the image might help? Disabling audio / ensuring that you have enough RAM available / etc.? Do any of these help?
Do you have another computer that you could try the QuickStart on, perchance? It seems that the issue is almost certainly with your computer / VirtualBox configuration, as the QuickStart cannot even get off the ground
after setting EFI on the VM doesn't hang on but still I don't have connection to de server.
Aby other change havn't got any positive result. I'll try on VM in GCP but it's my last idea.
When you say it "doesn't hang on," what do you mean? Does it get started, do you get access to a terminal, etc.? And what EFI setting change did you make?
It might be good for someone else to hear a bit more about what you did to see if it helps them! Unfortunately, I am pretty much out of ideas as well Maybe this is something you could post on the virtualbox forums? Are you able to start any other types of virtualbox images? (i.e. a bare Ubuntu VM?).
I am suspicious that the GCP instance might not work because of hypervisor-in-a-hypervisor shenanigans (I lost a few days to that last year). But hopefully I am wrong! Would definitely love to get you up and running here! I'm honestly thinking the best bet may be to try with a bare Ubuntu image and post on the virtualbox forum, where more virtualbox-savvy folks may be lurking!
If the server is started successfully, though, then perhaps I can help in debugging what is keeping you from connecting!
Any more updates here? I'm hopeful that you had great success, but suspicious that there may not have been a breakthrough This Virtualization stuff can be very painful