virtualbox.org

I am running a WinXP 32bit host with a WinXP 32bit guest using Virtualbox 3.0.0. All is ok until I start the guest OS and then the CPU on the host goes to 50% and the CPU on the guest goes to 100%. Can barely if at all operate the guest. The guest is a VM from VB 2.2.2 and has VB additions installed. I've tried to install VBA 3.0.0 and also tried to uninstall VBA 2.2.2 both with no luck. Maybe they are working but because the VM is so slow and high on CPU it looks froze. Any help?

I have the same problem.

My host is windows XP (fully patched)
My guest is Redhat Enterprise server 5.1

Everything worked fine using virtualbox 2.2.4. The upgrade to 3.0 worked fine also.

Now if find that it takes 16mins to start the guest, and even when it has started, it is so slow it us unusable. shutting down is a little better, it only takes 6mins.

My set up as reported by system properties is
Model - Dell Dimension DM061,
processor is 2.66MHz Pentium D, Ram 2GB

Rgds
Bun

Did you try to Uncheck VT-x/AMD-V ? I keep this option always off and the emulated machines run perfectly.

J-Luc B wrote:Did you try to Uncheck VT-x/AMD-V ? I keep this option always off and the emulated machines run perfectly.

I do have these options checked, I will uncheck then as you suggest and see if that makes any difference.

Many thanks for your suggestion

I have the same problem with things running really slow in 3.0.0.

VMs in 2.2.4 worked great, same VMs run terribly under 3.0.0.

Created a new guest in 3.0.0, same problem, running really slow.

Disabled VT-x/AMD-V, for ones created in 2.2.4, same problems.

The xload graph in slitaz/puppy linux scrolls across like mad, top refreshes several times a second, eventually the hosts CPU rockets to nearly 100% and the fans go to maximum. Seems like theres a timing issue/CPU allocation somewhere that the guest/VBox is grabbing all the CPU. It makes the VMs unusable.

Running Dell XPS M1710, vista home premium 32 bit (came installed with it), 4g of Ram.

Unless there's an update/config alteration that can return it to normal, I'll reinstall 2.2.4 - this was working perfectly, and wait til 3.1 comes out.

I have the same problem, both with 2.2.4 and 3.0.0.

Host: WinXPsp3 32-bit
Guest: Solaris 10 u7 32-bit (VT-x disabled and IO APIC/ACPI/PAE-NX enabled)

If I enable VT-x, the guest runs fast both in 32- or 64-bit, but will inevitably hang (see bug #2258). In 2.2.4, the guest seemed to run better in 32-bit with PAE/NX disabled, but I need to test that more.

With 3.0.0, NAT networking is completely broken (bug #4343). At least for Windows hosts, it is recommended to revert to 2.2.4.

So, for 32-bit WinXP hosts, Solaris guests are completely unsupported as of 3.0.0.

I started a new bug for this:

http://www.virtualbox.org/ticket/4411

However, for those using non-Solaris guests, I would submit another bug.