Communication with VM Hypervisor failed.


Advanced search

Questions and Answers : Unix/Linux : Communication with VM Hypervisor failed.

Author Message
UnionJack
Send message
Joined: 3 May 15
Posts: 15
Credit: 422,299
RAC: 0
    
Message 4049 - Posted: 20 Apr 2016, 16:17:01 UTC

I have a new 12-core i7 machine with a UEFI interface and an M.2 SSD. It was built by Armari with an Asus X99-A motherboard. The graphics card is a Radeon R9 M295X Mac Edition (I hope that last isn't a problem). I'm running Gentoo Linux with sys-kernel/gentoo-sources-4.4.6 and sys-firmware/amdgpu-ucode-20160331 installed via the kernel config and I have no display problems as far as I know.

VirtualBox is running at version 5.0.16-r1; it has one Windows XP client already which runs as expected, but ATLAS@home complains with the error message in the title above. Virtualisation is enabled in both places in the UEFI BIOS ("Virtualization" and "VT-d"). My other projects are Asteroids@home, Cosmology@Home, Einstein@Home, LHC@home and pogs, all of which run as expected, some of them using the GPU.

I have the boinc and .VirtualBox directories under my home directory, and both my user and, now, the boinc user are in the vboxusers directory. Adding the boinc user made no discernible difference.

Dmesg doesn't show anything to suggest a cause of this. What else can I try?

UnionJack
Send message
Joined: 3 May 15
Posts: 15
Credit: 422,299
RAC: 0
    
Message 4051 - Posted: 21 Apr 2016, 15:49:42 UTC - in response to Message 4049.

In fact the graphics card is a Sapphire Radeon R9 380 Nitro. It was misidentified by lspci, part of sys-apps/pciutils.

UnionJack
Send message
Joined: 3 May 15
Posts: 15
Credit: 422,299
RAC: 0
    
Message 4052 - Posted: 22 Apr 2016, 12:25:12 UTC

I've solved my problem by finding versions of BOINC, Radeon microcode, VirtualBox and the kernel that work together. I have this:

sci-misc/boinc-7.4.42-r1
sys-firmware/amdgpu-ucode-20160331
app-emulation/virtualbox-5.0.18
sys-kernel/gentoo-sources-4.5.0-r1

This is now an apparently stable setup for use with my Radeon R9 380X Nitro 4G D5 graphics card. (Time will tell...)

I hope someone finds this useful.

UnionJack
Send message
Joined: 3 May 15
Posts: 15
Credit: 422,299
RAC: 0
    
Message 4054 - Posted: 24 Apr 2016, 8:35:18 UTC - in response to Message 4052.

Time has told. It only appeared to work.

After trying every available version of BOINC, kernel, GPU microcode and VirtualBox, ATLAS@home still cannot communicate with VirtualBox.

Something is still wrong with BOINC, and my only option now is to disconnect from all projects that use VirtualBox.

UnionJack
Send message
Joined: 3 May 15
Posts: 15
Credit: 422,299
RAC: 0
    
Message 4065 - Posted: 29 Apr 2016, 9:36:26 UTC
Last modified: 29 Apr 2016, 10:05:16 UTC

Has no-one any idea about this? It seems a pity to be unable to contribute to what is likely to be a growing proportion of projects.

I also find that I have four copies of the .vdi file: one under the project directory and three under slot directories. That's 4 x 1.4 GB!

So I copy the one from under the project, detach from the project, make a directory for it, copy the .vdi file back in, reattach to the project and it starts downloading it again!

This can't be proper behaviour. Where do I go to report a bug?

UnionJack
Send message
Joined: 3 May 15
Posts: 15
Credit: 422,299
RAC: 0
    
Message 4081 - Posted: 7 May 2016, 9:56:08 UTC - in response to Message 4065.

SOLVED!

The problem was in the startup script in the Gentoo BOINC package, which was not using the standard start-stop-daemon method to start the client.

That has now been fixed and I have no difficulty running ATLAS@home.

Questions and Answers : Unix/Linux : Communication with VM Hypervisor failed.