![windows 7 64 bit slow in virtualbox windows 7 64 bit slow in virtualbox](http://4.bp.blogspot.com/-ThbE50zI0Aw/U8pUJlvJ9qI/AAAAAAAAATY/3cwj9OLMFTw/s1600/win7_ult64.jpg)
When I disabled the Hypervisor (and rebooted), I'm seeing a little bit improvement in performance, but not a lot. I know that VirtualBox and Hyper-V don't get along, and I had thought I had disabled it, although when I followed info from another discussion, I found that I had missed disabling the Windows Hypervisor, although I have disabled the other components, including Containers, Hyper-V, Virtual Machine Platform and Windows Sandbox. My host machine does have Hyper-V on it, as I was briefly running a VM there. For Windows, I have a variety of stuff installed, including a 32-bit Win 10, 2 64-bit Win 10, and a Win 11 installation. The Linux guests are fine, but all the Windows guests are struggling with slow performance. I have a number of guests defined, both Windows and Linux. I have VirtualBox running on 7.0.10, where the host is running Windows 10 Pro. I know that many disagree with my views on 圆4 vs x86 and I'm ok with that.I've seen other discussions about this, but details don't quite match my question. Based on this, all of my VM guest OSs are XP x86, because I'm looking for maximum performance and not maximum eye candy. XP 32 bit outperforms Win7 handily both in empirical benchmark results and in perceivable system responsiveness. On my PC, which has 8 gigs of physical RAM, I dual boot Win7 圆4 and XP x86. So, if an 圆4 guest OS is only being allocated 1 or 2 gigs of memory, then I can see how performance would suffer. It's my understanding that even if a machine has 4 gigs of physical ram (around 3 or whatever is addressable under x86 Windows), that the additional overhead of WoW in combination with the actual 64 bit system absorbs that extra memory for a net zero benefit. Since this was posted in the Macbook forum, I'm going to guess that the host machine has 4 gigs, there'd really be not benefit. Unless you're using it to test compatibility of 32 bit code in WoW, I don't think there'd be any benefit. Like Gabriel GR, I'm also curious why 64 bit Windows as a guest OS on VMware. Maybe a Win7 or VMWare update will solve this, eventually. Why this does not affect Linux (Ubuntu 9) client is not known. Using the image from regular OS X boot disk slows down. moving the image to an external USB disk speeds things up. There's basically nothing in there but Win7 RC.
![windows 7 64 bit slow in virtualbox windows 7 64 bit slow in virtualbox](https://content.spiceworksstatic.com/service.community/p/post_images/0000397882/5ec3460c/attached_image/VirtualBoxStartError.png)
it's actually expanded to above 20GB, which is alarming. Can work as a test bunny, if anyone has good ideas. I shall keep an eye on this issue, and maybe try moving the image to an external USB drive. When the slowdown hits, it's unusable though. I use Windows only occasionally and the current solution works fine enough. >And how about if you'd create a virtual machine with Win 7 32-bit instead of 64-bit? I'm running a 32-bit virtual machine and it's very responsive and all. >Is Fusion accessing the Bootcamp partition or did you create a virtual machine for Win 7? The hardware is Mac Mini (current model, with NVidia 9400GT), 2GB memory Looking at the Windows side task manager, I wasn't able to figure out who drinks all the juice, either. There's no timer on it, and I'm not using snapshots. I still need to try this out - get a USB drive for it. Some people seem to say, running from the OS X startup disk causes problems. Another thing to try is placing the VM image on an external (USB) disk or a second partition. One does not want it to start hybernating or anything as a guest OS. One thing worth doing is disable all sleep modes from Windows 7. The hard disk icon (or VMWare Fusion) remains blue most of the time - that looks strange.Īlso, the network icon (of Windows 7) shows not connected, and trouble, but browsing works just fine!?! I don't see any reason why it needs to be that way. Currently, Ubuntu is 100x more usable via virtualization than Windows 7 is. If anyone finds a cure to this - I'll be glad to know. Given enough time (say - 20 mins) the UI actually becomes responsive again. This may be some background indexing thingy or such. Anything is sluggish to say the least (actually - like dead - clicks take a minute to get through).
![windows 7 64 bit slow in virtualbox windows 7 64 bit slow in virtualbox](https://i.ytimg.com/vi/vnCk7VSeYuE/hqdefault.jpg)
Within Windows 7, the CPU meters seem to be at 100% all the time (on OS X side, CPU load is hardly at 5%!).