Custom Query (16363 matches)
Results (2488 - 2490 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2419 | duplicate | Speed and Memory problems with Vista host | ||
| Description |
Am one of a few users who have noticed this issue with a Vista Host. I personally am using Vista64 Home Premium (with AMD Turion X2 TL-60 2.0 Ghz dual core), however, I have heard of people having the problem with Vista32. The issue appears when launching a vm with a Vista host. Once the vm is running, the host slows to a crawl, running so slowly that it is almost unusable. I personally have experienced this, and have also noticed that, even after I close the vm, the host continues to be unresponsive to an extreme degree, forcing a reboot to restore reasonable operation. It appears as if VBox is not properly releasing the memory used by the vm, but that is just a guess based upon the symptoms. It may simply be configuration, and something I have set wrong, but since, based upon the forum's I have reviewed, others seem to be experiencing it as well, I was advised by Terry to put in this ticket. Thank you |
|||
| #2420 | fixed | VBox Memory Leak in Windows XP SP2 (NAT/networking related) | ||
| Description |
Like Ticket #2242, I'm actually getting this exact same problem in Win XP. I start up Virtualbox, start working with a VM, and eventually all RAM is used up and my other programs (just Firefox for development) are moving sluggish because they've all been moved to virtual RAM. I look at my available physical memory and it's hovering near 30MB, even though the Virtualbox VM is set to use only 512 MB, and before starting the VM I had over 1.5GB free. What's weird is that the Virtualbox process is only using about 80MB, according to the Windows Task Manager. There's nothing to show in the task list what is using all the RAM, but in the "performance" tab of the Task Manager there is almost no physical memory free at all. This happened with both an Ubuntu VM and an OpenSolaris one, as the two log files I've included will hopefully show. |
|||
| #2421 | fixed | Can't boot VMs after host kernel upgrade (spawning session ...) => Fixed in 2.0.4 | ||
| Description |
In Ubuntu's kernel version 2.6.24-19, Virtual Box 2.0.2 works good. But today Ubuntu upgrade the kernel to 2.6.24-21 and Virtual Box stay in the message "Spawning session..." and don't open the guest OS. Occurs when I try open any guest OS (I have a Windows VM and a Ubuntu 8.10 VM). Virtual Box don't generate a log of this connection. |
|||

