VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (277 - 279 of 16363)

Ticket Resolution Summary Owner Reporter
#9061 obsolete 3 VM servers all became unresponsive Jordie
Description

All three virtual machines were running on Win7 Host with 16 Gig of RAM:

VM Primary Domain Controller VM SQL Server 2008R2 VM SharePoint 2010 Foundation WFE Pod 0

  • I switched to VM SharePoint 2010 Foundation WFE Pod 0 server
  • I mounted an ISO disk - the virtual system became unresponsive
  • I waited close to 15 minutes - no change in response
  • I switched to VM SQL Server 2008R2, and "saved the machine state" - then this virtual system began not responding
  • I switched to the VM Primary Domain Controller to "pause it".
  • It Paused ok
  • Then un-paused VM Primary Domain Controller
  • This system then became unresponsive.
  • Attempted go to the Oracle VM Box Manager - it became unresponsive.
  • Waited close to 15 minutes - no change in response...
  • Finally killed them in Windows Task Manager.
  • Restarted each VM - Problem on VM Primary Domain Controller
#4355 fixed 3.0.0 Solaris guest additions graphics broken with OpenSolaris 2009.06 -> fixed in 3.0.6 beta 1 Constantin Gonzalez
Description

With OpenSolaris 2009.06, running on VirtualBox 3.0.0 running on Mac OS X "Leopard", guest additions installed, the display is garbled. Attached is a screenshot of the virtual machine window showing a broken login screen, as well as a copy of VBox.log.

This has been observed on VirtualBox 3.0.0B2 already, and there's also another case of a user who saw this effect with VirtualBox 3.0.0 on some flavour of Windows.

Looking at Xorg.0.log (attached), it seems that the VirtualBox display module can't connect to the dri device:

(==) VBoxVideo(0): Default visual is TrueColor drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: Open failed drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: open result is -1, (No such device or address) drmOpenDevice: Open failed [drm] failed to load kernel module "vboxvideo" (EE) [drm] drmOpen failed. (EE) VBoxVideo(0): DRIScreenInit failed, disabling DRI.

I get the impression that the vboxvideo Xorg module works, but somehow can't connect to the kernel module through dri and therefore there is no negotiation between the host and the guest re: display resolution. Therefore, X.org seems to render graphics under wrong assumptions over display resolution etc., resulting in the garbled screen. This is just my personal feeling, no hard facts on this one.

Resizing the window doesn't change anything, nor does switching between full-screen and window mode. When resizing the window, the canvas stays the same and scrollbars appear, indicating that the window-resize doesn't work. Mouse pointer integration and the rest of the guest additions seem to work ok.

Workaround:

  • Kill the X Server through Ctrl-Alt-Delete.
  • Log in quickly through the Solaris console (may need to kill X again to complete console login.
  • "svcadm disable gdm" (This disables X and login completely, may need to kill X again to be able to type this).
  • "pfexec mv /etc/xorg.conf /etc/xorg.conf.vboxguest"
  • "svcadm enable gdm"
  • Wait for X to start again, then log in.
  • This effectively disables the display and mouse portions of the guest additions, but the rest will work.

This issue has already been reported in the Beta forums, but with no response. It has also been reported in an Sun internal mail thread.

#4344 fixed 3.0.0 VBoxClient incompatible with Solaris 10 version of libX11.so.4 -> fixed in SVN Scott Barrett
Description

GUI login on Solaris 10 guest fails to successfully start XSession as VBoxClient requires SUNW_1.2 symbol from libX11.so.4. A copy of ~/.dt/startlog is attached.

Partial workaround is to define LD_NOVERSION in ~/.dtprofile to cause runtime linker to not perform version verification.

This workaround however leaves clipboard functionality broken, as the "VBoxClient --clipboard" process dies when an attempt is made to copy text from the guest.

Running "VBoxClient --clipboard -d" shows:

bash-3.00$ /opt/VirtualBoxAdditions/VBoxClient --clipboard -d
ld.so.1: VBoxClient: fatal: relocation error: file /opt/VirtualBoxAdditions/VBoxClient: symbol Xutf8TextPropertyToTextList: referenced symbol not found
Killed
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