virtualbox.org

found the answer to my own problem. splashy spins at startup. I am not sure if I have it configured incorrectly or not, but whatever the case, it spins and causes ridiculously long startup times.

I am finding that my VM is slower now with VT-x/AMD-V enabled in 2.1.4 than it was without in 2.1.0. I will test going back to no acceleration to see if I see a speed improvement.

I was correct in my thinking that disabling VT-x/AMD-V on my X2 5400+ sped up the guest by about 300% when doing anything that required processing power even if it was opening up a second browser window.

USING VBOX 2.2.2 This has been happening since 2.1.0 IIRC.

I can confirm this. Using VirtualBox 2.2.2, deactivating VT-X/AMD-V increases performance in my XP guest dramatically.

@megagram

AMD or Intel? I'll post a bug.

Still an issue in 2.2.4

How may I check the status of this issue? Is there a status available to the public?

I just loaded 2.2.4-47978 on a Windows Server 2008 64-bit host on an Intel quad core whitebox with 8Gb of memory. The hardware support for virtualization is enabled in the BIOS. I'll test with this disabled in the client and/or host this evening. XP seems extremely slow as a guest. I just happened to be loading XP on an old P4 physical machine for someone and it performed so much faster than the VM in VirtualBox on WS2008. Looking at the performance tab on the WS2008 host, it appeared that one processor core was much more heavily used than the other three.

I removed the Hyper-V role from Windows Server and this greatly improved performance.

i got the bsod after i disabled it :/

tried to delete the vm and use the disk image stored dindt realy help at all