virtualbox.org

Howdy!

I am running a Windows 10 guest on my laptop, which runs Linux Mint 19. I installed VirtualBox from the main website via a DEB package and not through apt. I'm running into an issue that soon after boot, my VM will crash under very light load (usually just playing music). The VMs status is changed to "aborted". As for the VM it's self, I've configured it with the recommended specs, as well as changed the USB controller from 1.0 to 3.0, as well as failed back to IDE from ACHI. Prior to re-installing with IDE, I would receive a message in the logs regarding "ACHI:0 Port 0 reset", or something similar. On IDE, at 1:18, it seems all goes to hell
I do have the PV tools installed, and it didn't seem to occur prior to the PV tools. Out of best habbit, I generally install those first.

Attached is the log. Any help would be wonderful!

00:00:01.127569 NumCPUs <integer> = 0x0000000000000002 (2)
00:00:01.362038 CPUM: Physical host cores: 2
00:00:01.362866 Full Name: "Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz"

You have assigned all your CPUs to the VM. The host is going to run low on resources, since VirtualBox cares about physical processors (cores), not logical ones (threads). Your i5-2430M CPU has 2 cores and 4 threads.

00:00:01.042759 File system of '/home/ngl/VirtualBox VMs/Windows 10/Windows 10.vhd' is ext4

Why a VHD file and not the default VDI?

Other than that, your configuration looks pretty benign...

nateleduc wrote:I do have the PV tools installed, and it didn't seem to occur prior to the PV tools

What are the "PV tools". A quick web search didn't reveal anything of interest. Could you explain that part?

And, just to make it clear, you say that if you install these tools, that's when you start seeing the crashes?

PS. For future reference you should ZIP your logs. It helps you, it helps us, it helps save a (virtual) tree or two...

Thanks for the reply,

I'm currently using a VDI disk on an IDE controller (previous was VHD because Windows). I'll drop it down to one core for the time being. I purchased a quad core i7 on Ebay, so we'll see if that changes anything.

PV=ParaVirtulization , aka guest tools. I THINK the issues started afterward. I let the VM sit for about an hour without any issues before i installed the guest tools. I'll also remove them to see if it changes anything.

nateleduc wrote:PV=ParaVirtulization , aka guest tools.

Ah, those "tools" are called "Guest Additions", or GAs for short. There's another thing called "Paravirtualization Interface" (VM Settings » System » Acceleration), you're running into a potential confusing situation, either for you, or for us...

00:00:01.127946   VMSVGA3dEnabled  <integer> = 0x0000000000000000 (0)
00:00:01.127947   VMSVGAEnabled    <integer> = 0x0000000000000001 (1)
00:00:01.345804 GUI: 2D video acceleration is disabled

Another thing that you could try would be to change the vGPU from VBoxSVGA to VBoxVGA (without the "S") in the VM Settings » Display » Screen. And since you're there, please enable 2D/3D acceleration. See if that makes a difference...

I would call this fixed, since dropping to a single core, I have not had any issues

Great, thanks for the feedback. Marking as [Solved].