Virtualboxvm.exe Application Error

[Joseph]

soI'm running Ubuntu 18.04 LTS on VirtualBox and I have windows 10 1903 running as host, and this error started happening since I installed the VM, I'll be working normally and all things going well, then this error shows up:

It is running the latest version of virtualbox and the latest extension pack. I assigned 3 cores and the execution cap to 100%, and it has 8GB of virtual memory, 128MB video memory, and 3D acceleration enabled.

A warning message appeared to say that a shutdown will commence and may affect any unsaved data from applications still open. (In my case, I only had the command line open so that was fine so I selected OK).

I'm trying to spin up a virtual box machine (ver 5.0.8 ) using vagrant set up.Whenever vagrant is trying to spin up virtualbox machine , the VirtualBox runs into an application error of referenced memory , stating memory could not be written.

Description of the issue:

I have installed brave browser in Ubuntu 16.04 guest, Windows 10 Pro Host using snap install brave in a Virtualbox 6.0 environment. Brave browser opens and works fine. But when I close Brave browser this crashes the whole Vbox with an application memory error.

Additional Information:

Same happens when I follow the installation on Brave website here: -browser.readthedocs.io/en/latest/installing-brave.html#linux with same crashing results when closing the browser after browsing 5seconds.

Yes. I just double checked my VM specs. Ubuntu 16.04 LTS requures VM with 1 processor, 4GB ram, 16GB disk. Did I overlooked something? It is running on a pretty new Dell laptop with Intel i5-8350U CPU which should be good enough, right?

Message boards : Questions and problems : BOINC and VirtualBox issues

Message board moderation To post messages, you must log in. "Oldest firstNewest firstHighest rated posts first 1 2 Next AuthorMessage Clark

I am running Lubuntu 16.04 LTS 64-bit (4.4.0-53-generic kernel)on my old PC and to better use it I installed BOINC on it using the apt-get method and it gave me the 7.6.31 boinc version. I also wanted to run VM applications on it and hence I downloaded and installed virtualbox from the oracle's site ver#5.1.10 with extension pack. Now when I add VM projects such as vLHC@home, ATLAS@home, Cosmology@home i receive an error stating that virtualbox is not installed.

I don't know how to resolve this as I have tried every method posted on troubleshooting forums.

Note: This error did not come when I was running 32bit version of the same OS on the same PC

Checked the Event Log and can't find any entry related to virtualbox.

I have checked the checklist, I am aware that I don't have a Vt-x enabled CPU (Core 2 Duo E7300) and have checked that thing in client_state.xml and it is set to zero.

The issue is that I was running 32bit Lubuntu 16.04 prior to my current installation and I received a task from vLHC@home and was able to run it.

Anyhow Vt-x capability of a CPU should not affect boinc's ability to scan for VirtualBox installation as I did not receive any error messages on the 32-bit installation.

VirtualBox requires VM extensions to run 64-bit VMs. Now that you have 64-bit OS the server may be only considering 64-bit VM versions which your machine can't run. The message you get from server could be just misleading in this case. So that puts Atlas out of the picture.

Edited after reading your message fully. How about reboot?

edit2: Try adding 'boinc' to 'vboxusers' group. I don't think you should have to do that but doesn't hurt to try.

I don't know why installing 32-bit BOINC and VirtualBox made any difference for detecting VirtualBox. All the client does is run "/usr/bin/VBoxManage --version" or if that fails "/usr/local/bin/VBoxManage --version".

32-bit client isn't helping getting 32-bit VM tasks. At startup the client checks what binaries the host OS can run. In your case it's both 64-bit and 32-bit with the 64-bit being primary platform. The server then checks what platforms the client supports and for VM tasks gives you only tasks that match the primary platform. VM tasks having to match primary platform is apparently some Windows limitation but it's applied for all operating systems. So the server is willing to give you only 64-bit tasks which your host can't run therefore you get no work.

Now there are some options to make things work but before we go into those maybe it would be best if you explained what you want to do with the host. What BOINC projects you want to run, what motivated the change to 64-bit OS and so forth.

I don't know why installing 32-bit BOINC and VirtualBox made any difference for detecting VirtualBox.

Lack of 32bit compatibility libraries, perhaps? _BOINC#64_Bit_Considerations

If you are running 64 bit Linux, you might have a problem with projects that issue 32 bit applications rather than 64 bit applications. To allow 32 bit applications to run on 64 bit Linux you must install 32 bit versions of certain shared libraries. The names of the packages containing the 32 bit libraries is different for each distro.

Are you connecting using the old address or are you connecting using the new one for the newly combined LHC?

The newly combined LHC uses

Just checking in case they didn't shut off the old servers yet. I haven't kept up recently. May check more on it later.

I really would like to run a VM project on my machine (vLHC@home) and for the 64-bit OS I never gave a thought to it the only thing I wanted was to run latest software on my old PC to get the most of it.

If you could help me to get 32-bit tasks from the vLHC@home server on my current installation it would be great, also just for your information I recently got a 32-bit task from SETI@home, don't know if it helps but thought of mentioning it.

P.S. I have activated the 32-bit libraries in my 64-bit Lubuntu. It seems newer versions of ubuntu are multiarch and don't need to specifically install 32-bit libraries which is I think proved by the fact that I got a 32-bit task from SETI.

But what link are you using to attach to LHC? They recently merged all of the projects into one and are slowly phasing out their servers at the other projects. You may not be getting work if you are still attached to the old server. Please verify that you are using the new combined project link above. They are sending out work for each of the LHC projects now. You may have to go into your preferences and check which apps you want to run if you already had an account at Six Track.

Ok. Since you run other projects too you'll want to keep the 64-bit OS. At least on my old host 64-bit apps have a small but noticeable performance advantage.

I think you have two choices. You can use Anonymous platform mechanism. Instead of asking the server for an application you'd tell server what application you already have. To set things up you need to know and have all the files that the 32-bit app version needs. If you have a backup of the 32-bit OS installation the files and info should be there. Otherwise you need to ask someone who runs the 32-bit app version to tell you what files you need and their download location. Downside is that the app wouldn't be automatically updated any more. After setting up anon platform you are responsible for updates.

The other option is to use a modified BOINC client. I think all that needs to be done is swap the platforms. This way the vLHC server would think 32-bit is primary platform and other servers would still see 64-bit platform as well. Downside to this is that the tweaked client isn't automatically updated when new versions are released.

Notice that vLHC is/has merging with the original LHC. While the old site still has 32-bit app versions they have not been copied to LHC.

Ageless wrote:I don't know why installing 32-bit BOINC and VirtualBox made any difference for detecting VirtualBox.

Lack of 32bit compatibility libraries, perhaps?

No. 32-bit client and VirtualBox worked. It was 64-bit that didn't.

Coleslaw wrote:Are you connecting using the old address or are you connecting using the new one for the newly combined LHC?

From the log he's still connecting to the old vLHC. According to their server status page vLHC still works and has work available. Since the 32-bit app versions have not been copied to the combined LHC Clark shouldn't connect to it.

The other option is to use a modified BOINC client. I think all that needs to be done is swap the platforms.

How to do this? What I did was that I changed paltform in the sched_request for vLHC@home from x86_64 to i686 and still didn't make any difference.

I tried to follow this thread loosely and I'm now kind of confused what you did and what you expect. Please correct me if I'm wrong.

You are running Lubuntu 16.04 LTS 64-bit and installed BOINC via package manager (which usually gives you the 64-bit version). You then downloaded VirtualBox from the website and installed in manually. Why didn't you install it also via apt? The version in 16.04 should be recent enough.

installing 32-bit versions of the apps would solve my issues and after doing that

I don't understand what you mean by "apps". Do you mean BOINC? Do you mean VBox? You should use the 64bit Version for both.

In your latest log snippet BOINC was detecting the correct VirtualBox version which may have been a simple client restart issue which fixed itself by whatever you did to "install 32-bit versions of the apps". The BOINC client is still 64 bit as is stated in the logfile.

Juha: Can you point me to where this Vbox pinning to the primary platform happens?

Clark: you could try to swap platforms in your client_state.xml (stop boinc-client before changing the file!) For me the config is at the bottom of the file and looks like this:

x86_64-pc-linux-gnui686-pc-linux-gnu

Just swap the content of those tags and start boinc-client again. It's possible that info is regenerated at startup and this won't work but I think it's worth a try.

3a8082e126