VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (865 - 867 of 16363)

Ticket Resolution Summary Owner Reporter
#13671 obsolete Application Error on guest VM requested power-off with Linux Guest Additions 4.3.20 Daniel.Glasser
Description

I recently upgraded my VirtualBox installation from 4.3.12 to 4.3.20 r96997 on a Windows 7 Enterprise. For full configuration details, please see the saved virtual box logs in attached .zip file. On the same day, I installed the 4.3.20 Guest Additions and some Ubuntu updates within the Ubuntu guest VM.

Now, whenever I shut down my guest VM from within the guest OS, I get a dialog titled "VirtualBox.exe - Application Error" with text similar to "The instruction at 0x69866f99 referenced memory at 0x00000000. The memory could not be read. Click on OK to terminate the program". The instruction address and referenced address are not always the same (usually all 0s or all Fs for the referenced address). When I start the guest VM and then select "shutdown" from the system menu on the login screen, without logging in, the VM shuts down cleanly, but if I've logged in and requested the shut-down from the system menu under the Unity desktop, the exception is always present for this VM, and that if I log back out before requesting shut-down, it still has the exception. When the Application Error dialog is displayed, the GUI "Oracle VM Virtual Box Manager" shows "Stopping" for the status of the VM, and once the dialog is dismissed, this becomes "Aborted".

I have found through experimentation that a VM running the same version of Ubuntu Linux that has not had the Guest Additions updated from 4.3.12 to 4.3.20 does not exhibit this problem at all.

In the attached .zip file, there are several files:

  • "ubuntu-14.04-x64-desktop-2014-11-26-12-33-39.log" - the VBox.log file for the last session of the guest before the update of VirtualBox and the Linux Guest Additions from 4.3.12 to 4.3.20. There was no application error dialog on exit.
  • "ubuntu-14.04-x64-desktop-2014-12-04-09-14-21.log" - a VBox.log file for a session of the guest after I had done the upgrade of both VirtualBox and the Linux Guest Additions to 4.3.20. This had been an extended session with several reboots within the guest VM. There was an application error dialog on exit.
  • "ubuntu-14.04-x64-desktop-2014-12-04-11-13-10.log" - a VBox.log file for a session of the updated guest where I didn't log in (described above). There was no application error dialog on exit.
  • "ubuntu-14.04-x64-desktop-2014-12-04-11-14-23.log" - a VBox.log file for a session of the updated guest where I logged in and immediately selected shutdown from the system menu. There was an application error dialog on exit.
  • "ubuntu-14.04-x64-desktop-2014-12-04-12-05-51.log" - a VBox.log file for a session of the updated guest where I logged in, immediately logged out, then selected shutdown from the system menu in the login screen. There was an application error dialog on exit.
  • "Freescale SDK-2014-12-04-10-36-58.log" - a VBox.log file for a different guest VM running under VirtualBox 4.3.20 that has not been upgraded to use Linux Guest Additions 4.3.20 (still using 4.3.12). I logged in and then selected shutdown. There was no application error dialog on exit.
  • "vbox-memexception.png" - a screenshot of one of the Application Error dialogs.

Note that the VM can reboot without exhibiting an error.

Each of the log files that resulted in a memory access exception ends at a line that reads: Console::powerDown(): A Request to power off the VM has been issued (mMachineState=Stopping, InUninit=0)

On the clean exits, there is a considerable amount of information logged following the matching line in the log file.

This problem appears to be only present when the guest VM has requested a power-down. The result is that my VM, after having been shut down, always says "Aborted".

This began as a posting in the forums: https://forums.virtualbox.org/viewtopic.php?f=6&t=64976

Site moderator "mpack" recommended raising a BugTracker ticket, so that's what I've done.

#16949 duplicate Share Folder Freezes DanielB
Description

I have a Windows 7 Professional 64 bits VM running on Virtual Box Version 5.1.24 r117012 (Qt5.6.2) on macOS Sierra Version 10.12.5 (16F73).

I use Share Folder in the Windows VM (auto-mount and permanent). I edit files directly on the Shared Folder. From time to time (and now more often than not) the Shared Folder freezes, even though it still shows as connected. When this happens, the Windows VM becomes unresponsive and doesn't even shut down (I have to force it by powering off the VM).

A similar ticket existed already (15662) but I was recommended to open a new one (?).

Attached the Vbox.log

#10404 wontfix udev rules want to access not mounted /usr -> can be solved with manual fix DanielDuesentrieb
Description

Hello,

I am using the Virtualbox Debian package for wheezy.

During boot I get the message from udev that the script

  • /usr/share/virtualbox/VBoxCreateUSBNode.sh

can not be found. At this moment the /usr partition is not mounted. I have contacted the Debian udev maintainer:

-http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666928

He suggests a solution similar to the bluez package described here:

It is planned to modify the appropriate Virtualbox postinstall script accordingly?

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy