I'm using Windows, I've started to use VMware recently and when I installed Ubuntu on it, it stopped responding. I ended the VMware workstation with Windows Task Manager, and when I restarted it, the VM appeared to be powered off in the VMware station, but the VMware Tray Process still displayed the Virtual Machines are running. They captured a lot of CPU usages and memory, especially the VMware Workstation VMX.
The processes seem to be unkillable though I'd tried to kill them in many ways: task manager, taskkill, process explorer, even deleting the virtual machine from the disk (but the only file had been deleted is the vmd file, others still stay and cannot be removed because another process is using it).
I've tried reinstalling the OS 3 times and the same problem still occurs, except for the last time when I booted CD-ROM first with default hardware settings. However, when I changed the memory and the disk space, it stopped responding when I started it, and that problem occured.
Now I've had 3 virtual machine running and always occupies more than 95% CPU usage and I've got no idea how to shut them down and delete them completely. Please show me how, thank you.
Problem solved:
I restarted my computer
When the services hadn't started yet, I deleted the folders which had the running virtual machines, and it works because no process is using them.
Finally, no virtual machine is running in the background and the CPU usage is back to normal.
Related
For the last two months I've (tried to) embraced WSL2 as my main development environment. It works fine with most small projects, but when it comes to complex ones, things start to slow down, making working on WSL2 impossible. With complex one I mean a monorepo with React, node, different libraries, etc. This same monorepo, on the same machine, works just fine when running it from Windows itself.
Please note that, when working on WSL2, all my files are in the linux environment; I'm not trying to access Windows files from WSL2.
I've the latest Docker Desktop installed, with WSL2 integration and kubernetes enabled. But the issue persists even with Docker completely stopped.
I've also tried to limit the memory consumption for WSL2, but that doesn't seems to fix the problem.
My machine is an Aero 15X with 16GB of ram. A colleague suggested upgrading to 32GB of ram. But before trying this, or "switching back" to Windows for now, I'd like to see if someone has any suggestions I could test out.
Thanks.
The recent Kernel version Linux MSI-wsl 5.10.16.3 starts slower than previous overall.But the root cause can be outside WSL: if you have a new NVIDIA GeForce card installed Windows gives it to eat as much memory as it can, i.e 6-16 Gb without using it. I had to limit WSL memory to 8Gb to start WSL service without OoM. Try to play with this parameter in .wslconfig in your home directory and look at the WSL_Console_Log in the same place. If the timestamps in this file are in ms my Kernel starts in 55 ms and then hangs on Networking(!!!).
I'm afraid that WSL Kernel network driver
lshw -c network
*-network
description: Ethernet interface
physical id: 1
logical name: eth0
serial: 00:15:5d:52:c5:c0
size: 10Gbit/s
capabilities: ethernet physical
configuration: autonegotiation=off broadcast=yes driver=hv_netvsc driverversion=5.10.16.3-microsoft-standard-WS duplex=full firmware=N/A ip=172.20.186.108 link=yes multicast=yes speed=10Gbit/s
is not so fast how it is expected to be
Background
I run a Mac OS X Catalina, Apache, PHP 7.3, SQL Server 2012 stack on my mac.
Obviously SQL Server will not run on a mac so it is run on a Virtual Box Windows 10 Professional machine with network routing on port 1433.
The Problem
My local host website moves very fast most of the time. However if the Virtual Box has not been accessed for a certain amount of time (as in physically opening the vm window and manipulating something in the OS the site slows from ~1sec loads to as high as 30sec loads. I select the VM and it immediately speeds up again to normal speed. This issue is exaggerated when I run on battery power and in about 30sec after I leave the VM window the performance drop occurs.
The Question: What is happening and how do I stop it?
I suspect Mac OS is throttling background processes to protect battery life and free up resources. It could be doing this to hard drive access or processor access to achieve the same effect. Is this a fair evaluation? Is their a setting in Virtual Box or Mac OS or service I can use to prevent this specific process from being back-burnered?
So turns out the issue was completely unrelated to virtual box. I was using a custom domain name for the local copy of the website. "mysite.local" Mac has reserved the ".local" domain extension for internal use. So while it works it has very inconsistent performance sometimes responding to the dns request in moments other times taking up to 30sec. The issue is indeed more pronounced while on battery and more pronounced when I have virtual box running I assume whatever dns service is running is being throttled or overworked.
The solution: Change the ".local" domain to just about anything else.
I changed it to ".dson" and have not had the issue since. I read this solution in another stack exchange question but I have been unable to re-locate it
I'm working on a project for a client to install HMI application on the client servers. The client has requested to install the application inside Hyper-v virtual machine so that in case the operating system crashes then it will be easy to restore it back through the virtual machine drive back-up.
However, the customer is asking me to lock the virtual machine so that the machine's operator should not be able to go to the host operating system and only work through the virtual machine alone.
If it is not possible with Hyper-v options, then is there any free 3rd party tool which can do the same job.
I will really appreciate any advice on this issue.
Ok I wasn't able to prevent computer users from closing the virtual machine application. However I did manage to mitigate the effect of closing the virtual machine.
First thing I did was setting up Remote Desktop to connect the host to the VM remotely through hyper-v virtual switch. Then I installed Allen Bradley DeskLock tool (It is a free tool that comes together with their FTView CD). Through DeskLock I have prevented the user from doing anything over the host (Locked the desktop) and I provided him with only one button to run Remote Desktop and open the VM whenever he closes it by mistake.
I don't think that this answers the question completely, but it was the only solution I found without touching the computer Registry
I've been having a lot of trouble over the past couple of days. I set up a Win7 work environment in Virtualbox and everything has been running smoothly until I tried to use Remote Desktop. I can log in to the remote machine normally and everything works for a while but then all of a sudden, my guest Win7 machine restarts due to a BSOD. I thought it might be a memory or space issue so I upped the VM's RAM to 4GB (Host system is 8GB) and the HDD to 45 GB. I also enabled I/O APIC and PAE/NX which improved performance on the guest machine but running RDP for a few minutes still triggers a BSOD. I also increased video memory from 128MB to 256MB. I don't know what else to do and I don't know how to analyze dump files. I was able to see that the last 4 error check strings were the following:
KERNEL_MODE_EXCEPTION_NOT_HANDLED
IRQL_NOT_LESS_OR_EQUAL
MEMORY_MANAGEMENT
KERNEL_MODE_EXCEPTION_NOT_HANDLED
I'm attaching the last 4 minidumps in here:
https://drive.google.com/file/d/0B-hWzWXaH29hZXVVbjVmTkV4Vkk/edit?usp=sharing
Any help would be immensely helpful. Thank you all in advance.
Cheers,
Luis
The problem was that virtualization was disabled on the host machine's BIOS which prevented me from accessing the Acceleration tab in the VM's settings. Once I changed the host machine's BIOS settings to enable virtualization, I was able to enable Hardware virtualization in the VirtualBox settings and the problem went away. I also added extra disk space for good measure.
I run VPC 2007 on my Vista business laptop with 4 gig RAM. I use VPC to run windows XP and maintain a VS2003 web project. At first everything was great. I assigned the VPC 512MB and did my work as usual. I also run Resharper and Visual SVN. Lately, the act of scrolling in a page causes the CPU to spike above 50, sometimes near 100. This freezes my machine occasionally and is frustrating. Typing code sometimes does the same thing.
I have experimented with changing allocated memory, disk space, turning on/off the paging file, uninstalling ReSharper and Visual SVN. There should be no reason this thing is slow with all the memory I have on this laptop! I don't have anything running on it but VPC at any one time.
I'm wondering if I should just install VS2003 on my Vista machine and deal with any incompatibility problems.
Any suggestions?
Try VirtualBox.
VirtualBox is a family of powerful x86
virtualization products for enterprise
as well as home use. Not only is
VirtualBox an extremely feature rich,
high performance product for
enterprise customers, it is also the
only professional solution that is
freely available as Open Source
Software under the terms of the GNU
General Public License (GPL).
If it were me, I'd run the VS.NET 2003 IDE on Vista natively. Just check out this page with the problems you might have:
http://msdn.microsoft.com/en-us/vs2005/bb188244.aspx
As far as your CPU goes, it could be a video driver/display issue. Have you tried turning Aero Glass on/off on your vista machine to see if that changes things? Are your number of colors for your desktop the same both in the VPC and on your host? Have you updated your video drivers recently?
I recommend VirtualBox. Every time I use VPC I soon give up because the performance is terrible. I run VirtualBox with a Vista virtual PC allocated 1.5gb ram and it runs really well. In fact I don't really notice much slow down from running natively.
First thing I'd suggest doing is run Process Explorer and Process Monitor to find out whats really eating the cpu. If it used to run fine, switching to another VM might not fix anything.
I'd bet VisualSVN is the problem. I had the same problem on a dual-core system with 6GB of RAM. I eventually just uninstalled it because it kept crashing the IDE.
BTW, I'm running Server2003 64-bit.
You probably have VPC07 runnning the active vhd at maximum speed. Go to options on the console menu and change this setting to divide CPU time equally among all vhd's and your problems will disappear!