Unless you're using it to test compatibility of 32 bit code in WoW, I don't think there'd be any benefit.
#Vmware fusion black screen windows 7 64 Bit#
Like Gabriel GR, I'm also curious why 64 bit Windows as a guest OS on VMware.
#Vmware fusion black screen windows 7 update#
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. 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). Within Windows 7, the CPU meters seem to be at 100% all the time (on OS X side, CPU load is hardly at 5%!).
0 kommentar(er)
