virtualbox.org

Hi,

Yesterday I upgraded to 4.3.28-10009. I updated the Virtual Box additions in the guest and also added the add-ons for 4.3.28. Since then the Windows guest seems unstable. (I'll leave it running on a virtual desktop and use it for Outlook), frequently when I go to switch to it, its not there anymore and the Virtual Box Manager lists it as "Aborted"

Has oneyone run into this problem, or have an idea for a solution?

thanks
James

Post the guests log file ( as an attachment )

Attached

What is the reason for storing guests in /root? I can see all kinds or strange things happening with permissions doing this.

Also is this a log just after an abort?

/root isn't a system directory, but simply the home directory of the user root.

If one has the bad habit of working as root,
what more strange things would happen because of this?

Root is in a different user space and the permissions are not the same as the user that is running the program. Now if you want to change the permission of the /root folder to allow for a normal user to operate in that space you can probably get around the permission issues that could apply but then the entire host would be vulnerable.

I'm running into the same issue.. I updated my Linux OS (Debian) and it crashes, I attach my log file for reference. Am I going to have to reinstall my Windows EVERYTIME I reinstall my main OS by the sounds of it??

I can't attach my log file cause its to big... I can't insert it cause its to many characters,, how the to upload???

gordon, just compress the log first.

Hi,

In my case Virtual Box runs as root so it can access the Windows partition on the HD (If needed I can reboot my box and select the Windows partition in grub and boot off it, but I prefer to boot into Linux and then run the Windows partition as a guest).

This was working fine before the update, so fairly sure this is NOT the issue.


(I'm attaching a more recent log, where I let the system run, then waited for it to crash, based on the Time Stamp on the file, it seems to happen consistently after approx 10 minutes of operation.

@james968,
OK so you are using root to access guests owned by hammett and running RAW access to the guest.

The log does not show any reason for the power down/abort so it must be coming from the guest AFAICT. If you reboot after a failure and look in the event viewer, does it show the power down or reason on the guests side?

As a side note it may be better to give user hammett access to mounting drives instead of fighting permission issues because you are running as root. Root is not all powerful and in some cases can cause this issue. Not to mention the security aspect and one reason I never talk about running as root. Another issue you need to watch is under no circumstance access the Windows partition in Linux while it is running as a guest. Bad things happen and even to the point of drastic.

Hi,

So the only error I see in the Windows Event Log is:

The name "XXXXX :1d" could not be registered on the interface with IP address 10.0.2.15. The computer with the IP address 10.0.2.2 did not allow the name to be claimed by this computer.

(This seems to happen fairly regularly in the log).

thanks
James

Hi,

The only error in the Windows Event log was a message about networking.

The name "XXXX :1d" could not be registered on the interface with IP address 10.0.2.15. The computer with the IP address 10.0.2.2 did not allow the name to be claimed by this computer.

I tried switching from NAT to Bridge networking and the box has been up for over an hour now. (Before it would abort after roughly 10 minutes).

thanks
James