VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1225 - 1227 of 16363)

Ticket Resolution Summary Owner Reporter
#7526 obsolete VBox crashes within minutes of running Entegy
Description

I'm almost afraid to start any virtual machine now for fear of vm corruption because VB seems to crash just doing anything on my computer. Be it Starting a vm, stopping a vm, the vm just running (any guest) or even just trying to open/close the Virtual Media Manager, VB will crash. It doesn't happen instantly, but it will always happen within a few minutes of VB being launched. I can't seem to pinpoint a single reason as to why this happens.

My computer: MacBook Pro 5,5 (Mid-2009) 4GB of RAM Snow Leopard 10.6.4 with the 64-bit kernel activated VirtualBox 3.2.8

This has been happening since 3.1 (or whatever was recent in Jan. 2010)

Guests do not have to be running. The VirtualBox program itself can crash, a vm can crash, or they'll both crash.

Attached is a list of crashes from VirtualBox and VirtualBoxVM, along with the VBox.log of the last guest that crashed (Fedora 13 32-bit). Crashed happened when I tried to enter seamless mode. I can be doing anything to trigger a crash.

#7527 obsolete Slow client, possibly related to hardware(?) John D. West
Description

Hardware: Dell Precision WorkStation T5400, dual Xeon E5405 @ 2.0GHz Host: Ubuntu 10.04 64-bit or Red Hat Enterprise Linux Client release 5.3 Client: Ubuntu 10.04 64-bit

I have a web/database app on a Ubuntu 10.04 client in VirtualBox 3.2.8. When installed on either of two i7 processor boxes (one Ubuntu 10.04, one Windows 7) a given page (large) loads in 26-34 seconds. This is acceptable to my users.

When the same client is installed on the above Dell Workstation, the same page loads very slowly, 8-11 minutes. All processors are pegged during that time. I initially had the issue with RHEL (kernel 2.6.18-128.el5) on the host, then wiped the host and installed Ubuntu 10.04 (kernel 2.6.32-24-generic). No noticeable difference.

Reducing the client to only 1 processor speeded things up slightly, the page load then dropped to 3.5 minutes. Still unacceptable to my users, but better.

I installed VMware Workstation, and copied the client files into VMware. When I started the machine, I was presented with a message warning me that kernel.sched_compat_yield was turned off, and this would adversely affect performance. I turned it on, and the VMware client loads the page in 28 seconds. I left kernel.sched_compat_yield on and tried the VirtualBox client again, and it still takes 8+ minutes to load the same page.

Tentative conclusion: there is something with this hardware that VMware handles OK and VirtualBox does not.

#7529 obsolete VirtualBox.xml disappears upon exit VirtualBox Rony Shapiro
Description

Hi,

I've had this problem for the last few VBox releases, took me a while to narrow it down: When exiting VBox, the VirtualBox.xml disappears, to be replaced by VirtualBox.xml-tmp which has no read/write access. The workaround that I found (using cygwin) is: $ mv VirtualBox.xml-tmp VirtualBox.xml $ chmod 644 VirtualBox.xml

This is annoying, to say the least.

Attached please find the VirtualBox.xml I'm using. Let me know if there's anything else I can do to help resolve this.

Host is a Windows XP SP3 laptop.

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