VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1840 - 1842 of 16363)

Ticket Resolution Summary Owner Reporter
#9581 obsolete Display becomes corrupted when 3d acceleration is in use Sam Morris
Description

After running programs that use 3d acceleration for prolonged periods, the display becomes corrupted. Sometimes, but not always, VirtualBox will crash. If not then rebooting the guest does not fix the problem; as soon as a program uses OpenGL it will start again. It's necessary to power off the virtual machine to fix the problem.

I see the problem on two machines. It crops up much more often on one machine where I've installed GNOME 3 in the guest; I guess this is because gnome-shell (3.0.2) uses the 3d hardware a lot.

I'm unable to reproduce this on demand, but I can make it more likely by running Chromium (the web browser) and browsing to a page that it renders with GPU acceleration.

The first sign is that the desktop background goes black, then comes back. Eventually windows stop updating, or only update a cropped portion of themselves. Finally, the screen will go entirely black, with bits of the edges of windows occasionally appearing and being overlayed with white boxes.

The guest is running Debian with Linux 3.0.

Host is running Windows 7 x86_64; my graphics card is an ATI Radeon HD 5850.

#9583 obsolete WinXPHome guest resets upon starup David Relson
Description

environment: gentoo linux on an amd64 VirtualBox has successfully loaded a WinXPHome image created from vmware using vmware-converter Upon startup, the WinXP splash screen appears and, several seconds later, a blue screen appears with STOP: 0x0000008E (0xC0000005,0x8053A8E3,0xF779E610,0x00000000)

The virtual machine restarts and the cycle repeats. This continues until I close VirtualBox.

#9584 obsolete vboxmanage closemedium disk broken: "The object is not ready", worked in 3.x VirtualBoxBug
Description
VBoxManage closemedium disk deleteme.vdi --delete

gives

VBoxManage.exe: error: The object is not ready
VBoxManage.exe: error: Details: code E_ACCESSDENIED (0x80070005),
  component Medium, interface IMedium, callee IUnknown
Context: "FindMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType,
  pMedium.asOutParam())" at line 174 of file VBoxManageDisk.cpp

The same result with full path to the vdi or without the extension; in fact whatever I write as the disk name I get the same error. It worked in 3.x and the vdi can be removed using the GUI. I can't use --delete when unregistering the VM because I want to keep the OS disk.

MAYBE RELATED:

some other guy at http://daniel.hepper.net/blog/ got

$ VBoxManage list vms
"" {b68ed7a7-6e72-4f16-a438-8775cd80d9b3}
$ VBoxManage unregistervm {b68ed7a7-6e72-4f16-a438-8775cd80d9b3} --delete
VBoxManage: error: The object is not ready
VBoxManage: error: Details: code E_ACCESSDENIED (0x80070005),
  component Machine, interface IMachine, callee nsISupports
Context: "Delete(ComSafeArrayAsInParam(aMedia),
  pProgress.asOutParam())" at line 175 of file VBoxManageMisc.cpp
Segmentation fault

some other guy at http://forums.virtualbox.org/viewtopic.php?f=7&t=38150

Simply unregistering the machine without detaching the drives first seems to work, however unregistering the machine with the '--delete' flag gives:

Code: Select all   Expand viewCollapse view
    VBoxManage: error: The object is not ready
    VBoxManage: error: Details: code E_ACCESSDENIED (0x80070005),
  component Machine, interface IMachine, callee nsISupports
    Context: "Delete(ComSafeArrayAsInParam(aMedia),
  pProgress.asOutParam())" at line 167 of file VBoxManageMisc.cpp
    Segmentation fault (core dumped)
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