![]() BIOS maybe your VT-x support is disabled? If so please be aware that upon changing it to enabled you will have to completely remove power before the motherboard will actually reward the change. If I'm reading your SSD remark correctly you now moved the VM to a dedicated new 64GB SSD and are still experiencing the same delay? Please also beware that while it is a pretty decent CPU, the Q9650 is from 2008 which isn't helping for virtualisation either. Also heavy CPU load doesn't tell me much besides the comment, busy doing what? Which process is running at a high percentage? Writing to disk triggers interrupts, without any details on what interrupts you are seeing it is difficult to comment on that. ![]() Sysinternals has many tools, I think you are referring to the Process Explorer? trying to boot a 1GB VM on a Win7 host with only 3.5 GB RAM) and if the VM runs OK after the initial boot delay, it is mostly just an annoyance. Indeed things like an antivirus might be biting you if it tries to scan all files (including virtual disks) upon opening them.įWIW, I also understand the answer from support as it might be expected if your host is a little thin on resources (eg. No I do not consider it normal behavior for the boot to be slow and unresponsive, it is an indication that the hypervisor is trying to get some resources but is not getting them quick enough. Then I have also seen it on Fusion 4/5 when my host OS was running out of memory and I was trying to boot yet another guest OS anyways. I have also seen this on older versions of Workstation under linux (IIRC version 7) where the host had an atom based CPU, there I updated to more RAM and a newer version of Workstation and the problem disappeared. For example I saw this on an ESX host (yes I know different product) where there was a problem with storage not supplying enough IOPS. But mostly on older hardware or if there are problems with regards to particular resources. I know what you mean as I have seen it occasionally as well. VirtualHW.productCompatibility = "hosted" Sound.fileName = "Speakers (SoundMAX Integrated D" ![]() Guest OS: Windows 7 Professional SP1 32-bit Host OS: Windows 7 Professional SP1 32-bit Installed memory: 4.00GB (3.25 GB usable)īoot disk C: Intel SSD, 180GB (where VMware is installed)ĭata disk F: Seagate 1TB (where the VM resides) Host PC: Dell Optiplex, Intel Core2 Quad PU Q9650 3.00GHz VMware Player version 6.0.1 build-1379776 See the the log excerpt below at time 09:54:28.619 where the delay occurs followed by the entry for time 09:55:11.625 when startup resumes, a 43 second delay during which nothing seems to happen and the system is unresponsive. During the startup delay, the entire system is unresponsive, both host and guest OS. Once it appears, the OS starts booting (or the suspend state is resumed) quickly and performance is normal after that. The symptom is that when starting the VM, either from fresh boot or suspend, there is a significant delay before the VMware power on/startup screen appears. Set up a virtual machine, installed Windows 7 SP1 32-bit, everything works fine. Evaluating VMWare to set up VM for legacy software maintenance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |