Windows 10 VM crashes 5.2.2r1 on Ubuntu 17.10
Posted: 7. Dec 2017, 19:18
I'm on Ubuntu 17.10 x64 running 5.2.2r1 for 17.04. The system has SSD and 16GB RAM.
My Windows 10 VM (64-bit) crashes the VM and VBox.
It was created with default settings, but now some are different because of my experimenting to see if some non-default settings help.
The VM has 4GB RAM, 2 CPU, and I just use it to open 1-2 tabs in Chrome and play slide-shows from PowerPoint 2016.
The way it crashes doesn't coincide with high workload, sometimes it happens when I'm typing in the guest CLI, for example.
The VM becomes unresponsive for about 10-15 seconds, and then both the VM and VBox crash and I have to restart VBox.
It seems some logs get collected but can't be uploaded to Ubuntu because my VBox DEB package is not from the distro. I don't know what parts of the binary may contain sensitive work data, so I'd like to share relevant parts of VBox.log. I looked at the file and couldn't find anything like "error", "crash" or "stop". Now I'm tailing to log to see if I can see what happens when it crashes, but it hasn't crashed yet.
What else may be helpful to debug this?
My Windows 10 VM (64-bit) crashes the VM and VBox.
It was created with default settings, but now some are different because of my experimenting to see if some non-default settings help.
The VM has 4GB RAM, 2 CPU, and I just use it to open 1-2 tabs in Chrome and play slide-shows from PowerPoint 2016.
The way it crashes doesn't coincide with high workload, sometimes it happens when I'm typing in the guest CLI, for example.
The VM becomes unresponsive for about 10-15 seconds, and then both the VM and VBox crash and I have to restart VBox.
It seems some logs get collected but can't be uploaded to Ubuntu because my VBox DEB package is not from the distro. I don't know what parts of the binary may contain sensitive work data, so I'd like to share relevant parts of VBox.log. I looked at the file and couldn't find anything like "error", "crash" or "stop". Now I'm tailing to log to see if I can see what happens when it crashes, but it hasn't crashed yet.
What else may be helpful to debug this?