Can't start any VM or do anything. VirtualBox keeps closing

[ArnoldRimmer]

I tried to create some new VMs and there were problems.

When I start VB now I get told that there are problems with my disks and there are two yellow warning icons by the drives for the new VMs that I tried to make.

I want to delete the new VMs but can't do anything - clicking anywhere on anything in VirtualBox cause the app to close.

Has anyone else had this problem? I think it is connected to the two new VMs that I tried to create as before this everything worked out fine.

Thanks for any help.

[ArnoldRimmer]

I keep seeing these log entries but have no idea what it means or how to fix it.

[Perryg]

Minimal information needed to be able to help

[mpack]

When I start VB now I get told that there are problems with my disks and there are two yellow warning icons by the drives for the new VMs that I tried to make.

You only get that if you have been manually moving or deleting files after registering them with VirtualBox.

Perhaps you should delete the contents of $HOME/.VirtualBox and $HOME/"VirtualBox VMs", which will give you a clean slate in order to begin again - and I'd suggest reading the early chapters of the user manual before you do that.

[ArnoldRimmer]

I hope this is enough. No guests are running and I can't start any as the GUI closes as soon as I try and interact with it.

[Perryg]

OK so what changed since this was working? I would forget about the new guests for now since they would not have much to do with your actual issue.

[ArnoldRimmer]

Nothing that I know of. I only make updates once every few weeks.

I have also today installed all updates and updated to the current version of VB to see if this fixes the issue but it doesn't help. Everything was working fine. What about those segfaults in the gnome log application - what does that indicate?

[Perryg]

It means that something has changed and all of your adding and changing is making it more difficult to help. Now we don't have a base line to go back to. It looks like your QT was updated since that is the message in your screen shot ( please post text instead. images are not searchable and no copy paste )

Start VirtualBox from a terminal as normal user and this will bring up the main manager. Try using it and see what happens. If it fails look in the terminal and see if anything is indicated and post the text if there is.

[ArnoldRimmer]

If start VB via terminal, when VB closes I see the following in the terminal :

Speicherzugriffsfehler (Speicherabzug geschrieben)

[Perryg]

Since 5.1.14 was released three days ago is it possible that this all worked in a previous version, and if so which did you have installed before?

[ArnoldRimmer]

It was the same version as now (Version: 5.1.14 r112924) but just the revision number was lower. I installed VB about 1 month ago and everything was fine. It's only been about 2 days that I have had this problem

[Perryg]

That is impossible since the version 5.1.14 regardless the revision number was only released on Tuesday. 5.1.12 was the previous version.

Let's look at one of the guests log file. Since you can not use the main manager look in the folder where you have these guests stored. Usually /home/<user>/VirtualBox VMs/<guest>/logs/

Post one as an attachment here.

[ArnoldRimmer]

Hi thanks for your help. I shant be able to provide any more information now until Monday. I do appreciate your help though and will update this ticket next week.

Thank you

[Perryg]

Very well. Enjoy the weekend.

[ArnoldRimmer]

Hi,

here is the log file from the only guest I can start - as it is highlighted when I start vb.