VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1828 - 1830 of 16363)

Ticket Resolution Summary Owner Reporter
#10650 obsolete Solaris 10 Host reboot - after kernel panic... JensMR
Description

After patching our Solaris System 10 with the actual patch cluster (21.5.2012) and updating VirtualBox to version 4.1.16 our server crashes. In the system messages we always find the attached message ahead of the crash. The referenced CPU number varies and so do the addresses. But the rest is 'stable'.

Since January we used VirtualBox v4.1.8 without any crashes. And after having troubles with version 4.1.16 I reinstalled v4.1.8 but the crashes persist.

System is a SunFire X4600M2 with 8 sockets (Opteron 8356) and 256GB ECC memory. No hardware changes between the running and the crashing system.

The guest systems did not change (predominant is WinXP, but linux systems are also running -- sometimes). The logfiles of the users VMs do not show additional messages. It does not seem to be load-dependent - right now only a small number of users is working on the system (load < 20%).

Did somebody else experience this? Any ideas? Please let me know, if you need additional logfiles, stats or data.

#11825 obsolete Host send network speed slow when VM is running with bridged adapter Jerad
Description

We're using VB to run Linux guests on some of our machines. These use Bridged Adapters to allow the whole network to access them, and for years it's been working fine. With the 4.2.10 update, and also in 4.2.12, the Host's network send speed is severely reduced when the VM is running. This is tested just using normal Windows shares from the Host to any other machine on the network. Normal transfer speeds are upwards of 90MB/s, but when the VMs are running, it's around 20MB/s. Turn the VM off and the speed returns to normal. Turn it back on and speed is reduced again. Receive speed is fine, only send speed is affected.

When we downgrade to 4.2.8, the issue disappears entirely. We've got several machines that all have the same issue.

The hosts are all windows 7 x64 Ultimate. The guests are a mix of Debian 7 and Ubuntu 12.04, and all they do is run Apache or MySql. The guests are not under any load during these tests, and are generally idle.

#11303 obsolete memory leak: host system crashes after prolonged use with jack Jeremy
Description

While utilizing jack (www.jackaudio.org) on the host, and virtualbox on the host, the system can becoe unusable because of a memory leak.

how to reproduce:

On the host machine, in this case running Linux I386 Debian Wheezy, start jack and the following clients:

ecasound (for transporting audio from jack to a remote server) mpg123 (for ingesting audio)

Next start the virtualbox guest. As long as mpg123 is providing content into the jack system, there is a small memory leak, about 100k a second. No process takes ownership of the loss of memory, but total memory ithat is used in 'top' reports the leak. The memory does not appear in the buffers or cache columns, and after a few hours several processes are killed with OOM killer, rendering the host machine unusable if dhcpd or bind is terminated. Eventually, the machine becomes unresponsive to all network traffic and requires a hard-reset to bring it back to life.

If mpg123 is connected to the jack system, but not providing audio, the machine can run for days without incident and no apparent memory leak. If the guest is never started, and if mpg123 is providing content, the system is stable.

If Virtualbox is running, but jack and friends are not, the system runs fine for days at a time--it is only when mpg123 is providing content. I also tried this with jack_simple_client, various versions of jack, the alsa and dummy backend drivers, but the problem is still present--only when the virtual guest is running and when an audio client is providing audio for jack does this problem appear.

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