virtualbox.org

My host is Ubuntu Linux 64-bt 14.04.05 and the same guest OS also. I am not sure what's causing it, but it crashes typically after I try to start terminal or some terminal app a while after it starts (or even save the program a while later). I'm attaching my .vbox file and the logs for reference. The same happens with VirtualBox 5.1.4 also and then I thought I'll upgrade but to no use. The guest OS disappears and I get the 'aborted' red icon on the Virtualbox control panel for that guest OS.

Interestingly I have two bootable drives for this physical machine (intel i3, 2nd Gen, 12GB RAM) both using 14.04.05, one with a SATA disk and another with a SSD. This happens only when I boot using the SSD. The SATA was working too slow and hence I wanted to upgrade, but ran into this problem. The same VirtualBox image works fine on the SATA machine.

Can anyone help please ? I'm stuck on this.

Thanks,
Ravi

Does it work properly on the machine that you took this log from if you set the CPU core count to one (1)?

No, it still crashes.

One last test if you would before raising a ticket at bugtracker.
Can you install a new Linux guest to the ssd and see if it behaves differently?

Hi Ravi,
I had similar crashes (VM window just disappeared) on Win10 guests.
But only at one single day. Now it is gone since many days.

viewtopic.php?f=7&t=79708&p=372629#p372629

There's another VM which is a fresh install & which works fine. It may probably be an application I installed, it shouldn't crash Linux ? The app may be Synology Cloud Station drive (https://global.download.synology.com/do ... x86_64.deb). This may have a kernel access as it's like Dropbox (for my local NAS storage though, syncs storage from multiple computers on to the same file system structure). But I wonder why it should crash Linux - the Linux Window just disappears! The same VM works perfectly well on my other Virtualbox installation.

If in fact you remove this application and your problem subsides than it is a good indicator that it is doing something different than when on metal. I would ask Synology if they know of any reason this would be happening and of course you are always able to raise a ticket at bugtracker

I uninstalled the Synology application. The VM still crashes. I see the Ubuntu logo upside down and strangely my screen - it first appears almost inverted of something with some crazy tiling of the texture. It's a strange thing why the host OS is killing the VM.

Am reattaching logs to see if it makes any sense. If it doesn't then we open a bug. Is there any workaround? Or my SSD investment has gone down the drain !

Ubuntu logo upside down

This would indicate something corrupt in the graphics. Try disabling 3D acceleration for now and then see if you can get the guest to boot up. Then try updating the OS and see if it finds something note worthy.

After reading your log file I do have one more bit of advice. If you can get this guest to boot and run with the acceleration off, or even dropping to a tty instead of log in, remove Version 4.3.14 r95030 and install the ones of your current VBox version. Some changes may have something to do with your issue.

Disabled the 3D acceleration and it's doesn't seem to be crashing at least as of now. I wonder what's happening here, why doesn't the same VM crash - it's the same physical machine and the same two OS's running the same VM (just the installations are different, one is on a SATA disk and the other on a SSD) - crashes in one not in the other. It's sounds funny, but it's a nightmare. Thank you for the workaround. Should a bug be filed?

I would read my previous post and proceed there first. Since it is unique to that one guest a bug ticket will not help much unless you can pinpoint the real cause.

I'm not sure how I can point out the cause. But if someone can give me a way/instrumentation to collect information which can help do that, I'll be happy to do it as this can possibly help save others from this terrible problem. It was a showstopper for me actually, almost took my entire day today.

remove Version 4.3.14 r95030 and install the ones of your current VBox version. Some changes may have something to do with your issue.

Did you do this?