virtualbox.org

Hello!

I'm having a huge problem with guest machines aborting for a reason that is yet unknown to me.

Most often it happens while Vagrant boxes are build and used by Jenkins and Ansible to perform certain actions. I've observed that boxes which are running but are not used by any process are affected as well and they abort seemingly for no reason at all. In both cases the following guests (Vagrant boxes of both architectures) are affected: CentOS 6, CentOS7, Debian Wheezy, Debian Jessie, Ubuntu Precise, Ubuntu Trusty and Ubuntu Xenial. I'm running VagrantBox on Ubuntu 16.04 64-bit remote host (I have no access to VB GUI).

I'm attaching three logs of different guests as well as VBoxSVC.log. I'm not sure what information more to provide.

I could only attach 3 file to the previous post, so I'm attaching another log to this one.

Vagrant is a program that relies on VirtualBox but modifies its configuration files in unknown ways to us. It is not supported on these VirtualBox user forums, they have their own vagrant support channels. If you are having this problem with a standalone version of VirtualBox, then we can continue this discussion.

The thing is, I use the same setup on two different machines, and it works on one, but not on the other.

Could you please at least take a look at the logs?

The logs don't really help all that much except to show the guest/s never achieve boot. Did they ever boot on this machine? By the way you can always look at the logs your self. Search for the lines where it shows the booting from and it should show hard drive. Other than that you would need to actually install a stand alone guest to do your diagnostics if you want help here. There are just too many differences in the way the setup is when using a specific tool like vagrant for a remote person to tell you what to try since there can be no hands on and none of us here uses or are familiar with vagrant.

Yes, all boxes always boot up.

Thank you for replies, I will approach this problem from the Vagrant side.

The source of my problem was Jenkins. When a Jenkins job ends, it also kills all processes that it starts. In this case, Jenkins started up Vagrant boxes, so when a Jenkins job ended the boxes were aborted. The solution was to set environment variable BUILD_ID=dontKillMe.

This information may be useful for someone with a similar problem, that's why I'm posting it.

Thank you again for assistance.

You should also post that information in the Jenkins/Vagrant forums, since it has more to do with Jenkins/Vagrant and way less with VirtualBox.