[opensuse] Virtualbox load
I've noticed that lately a Windows 10 virtual machine has become a real hog. Top shows virtualbox taking well over 100% sometimes over 200% of CPU. Memory usage appears OK, but starting up W10 causes a real performance hit on Linux and even within W10. Has anyone else noticed this? I believe there was a recent update to Virtualbox on openSUSE and there was an update to W10 a couple of weeks ago, so I'm not sure where the problem may be. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/22/2018 07:34 AM, James Knott wrote:
I've noticed that lately a Windows 10 virtual machine has become a real hog. Top shows virtualbox taking well over 100% sometimes over 200% of CPU. Memory usage appears OK, but starting up W10 causes a real performance hit on Linux and even within W10. Has anyone else noticed this? I believe there was a recent update to Virtualbox on openSUSE and there was an update to W10 a couple of weeks ago, so I'm not sure where the problem may be.
I don't run any W10 Virtualboxes currently, but I have in the past. W10 can go into extended periods of high cpu usage while it is performing updates (or sending your private documents to Redmond, which ever you prefer to believe). Sometimes these can render your machine almost unusable, EVEN on bare metal machines. Often these are related to applying for preparing for updates. When you start digging into it you will find all sorts of processes and services running in the machine that you have to research to find out what they are, and start selectively killing them off. (Not all of these are Microsoft processes, but many are). I evaluate each one, and sometimes permanantly disable them if they are not essential. Start putting an execution cap on the VM so you can still get something done in the host. (Limiting it to one CPU does not really help as much as an execution cap). -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/22/2018 01:30 PM, John Andersen wrote:
I don't run any W10 Virtualboxes currently, but I have in the past.
W10 can go into extended periods of high cpu usage while it is performing updates (or sending your private documents to Redmond, which ever you prefer to believe).
Sometimes these can render your machine almost unusable, EVEN on bare metal machines. Often these are related to applying for preparing for updates.
When you start digging into it you will find all sorts of processes and services running in the machine that you have to research to find out what they are, and start selectively killing them off. (Not all of these are Microsoft processes, but many are). I evaluate each one, and sometimes permanantly disable them if they are not essential.
Start putting an execution cap on the VM so you can still get something done in the host. (Limiting it to one CPU does not really help as much as an execution cap).
On further testing, I suspect the problem is on W10, as it's slower even when run "bare metal" on my notebook computer. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-22 19:30, John Andersen wrote:
On 05/22/2018 07:34 AM, James Knott wrote:
I've noticed that lately a Windows 10 virtual machine has become a real hog. Top shows virtualbox taking well over 100% sometimes over 200% of CPU. Memory usage appears OK, but starting up W10 causes a real performance hit on Linux and even within W10. Has anyone else noticed this? I believe there was a recent update to Virtualbox on openSUSE and there was an update to W10 a couple of weeks ago, so I'm not sure where the problem may be.
I don't run any W10 Virtualboxes currently, but I have in the past.
W10 can go into extended periods of high cpu usage while it is performing updates (or sending your private documents to Redmond, which ever you prefer to believe).
Sometimes these can render your machine almost unusable, EVEN on bare metal machines. Often these are related to applying for preparing for updates.
Yes, this is true. Happens on my laptop, can last even days for the big updates, like the developer thing this winter - because I seldom boot it in Windows, there may be a month of updates waiting. Comparing to Linux, it is a real pain: downloads very slowly, and high CPU.
When you start digging into it you will find all sorts of processes and services running in the machine that you have to research to find out what they are, and start selectively killing them off. (Not all of these are Microsoft processes, but many are). I evaluate each one, and sometimes permanantly disable them if they are not essential.
Start putting an execution cap on the VM so you can still get something done in the host. (Limiting it to one CPU does not really help as much as an execution cap).
Ah. Interesting. I'll have to try that. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
participants (3)
-
Carlos E. R. -
James Knott -
John Andersen