VMware on Linux host causes regular freezes
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
1
down vote
favorite
When running a virtual machine in VMware (Ubuntu 16.04 host), both the guest system (Windows 10 at the moment) and the host system regularly become unresponsive for several seconds, e.g. when starting Atom or Visual Studio in the guest VM.
RAM usage reports look normal (16 GB total, 6.5 GB used by the VM as “shared memoryâ€Â, some GB free), but while the system is unresponsive, IO tasks are either suspended or very slow, for example copy/paste of text takes several seconds.
Changing settings (virtualisation settings, VM’s RAM, …) in VMware does not have any effect.
performance vmware
asked Jul 27 at 16:35
Simon A. Eugster
1596
add a comment |Â
up vote
1
down vote
favorite
When running a virtual machine in VMware (Ubuntu 16.04 host), both the guest system (Windows 10 at the moment) and the host system regularly become unresponsive for several seconds, e.g. when starting Atom or Visual Studio in the guest VM.
RAM usage reports look normal (16 GB total, 6.5 GB used by the VM as “shared memoryâ€Â, some GB free), but while the system is unresponsive, IO tasks are either suspended or very slow, for example copy/paste of text takes several seconds.
Changing settings (virtualisation settings, VM’s RAM, …) in VMware does not have any effect.
performance vmware
asked Jul 27 at 16:35
Simon A. Eugster
1596
Even though you've found the solution, I am surprised you are fine with 5GB of RAM used for your VM, as from my experience W10 allocates 5+ GB just when it starts, and VS 2017 takes about 500MB, so 5.5GB used under W10 on a physical host with 16GB RAM is a normality. Adding AV and other minor corporate stuff brings up initial RAM allocation on my current machine to 9.5 GB right after fresh start.
– ajeh
Jul 27 at 17:28
You are right. The VM is configured with 6.5 GB currently. Infree -h, the memory used by VMware does not show up in “used memory†but only in “shared†(for example, it shows 2 GB used and 3 GB free currently). Will update the question to clarify that :)
– Simon A. Eugster
Jul 30 at 6:55
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
When running a virtual machine in VMware (Ubuntu 16.04 host), both the guest system (Windows 10 at the moment) and the host system regularly become unresponsive for several seconds, e.g. when starting Atom or Visual Studio in the guest VM.
RAM usage reports look normal (16 GB total, 6.5 GB used by the VM as “shared memoryâ€Â, some GB free), but while the system is unresponsive, IO tasks are either suspended or very slow, for example copy/paste of text takes several seconds.
Changing settings (virtualisation settings, VM’s RAM, …) in VMware does not have any effect.
performance vmware
asked Jul 27 at 16:35
Simon A. Eugster
1596
When running a virtual machine in VMware (Ubuntu 16.04 host), both the guest system (Windows 10 at the moment) and the host system regularly become unresponsive for several seconds, e.g. when starting Atom or Visual Studio in the guest VM.
RAM usage reports look normal (16 GB total, 6.5 GB used by the VM as “shared memoryâ€Â, some GB free), but while the system is unresponsive, IO tasks are either suspended or very slow, for example copy/paste of text takes several seconds.
Changing settings (virtualisation settings, VM’s RAM, …) in VMware does not have any effect.
performance vmware
asked Jul 27 at 16:35
Simon A. Eugster
1596
edited Jul 30 at 10:29
asked Jul 27 at 16:35
Simon A. Eugster
1596
asked Jul 27 at 16:35
Simon A. Eugster
1596
asked Jul 27 at 16:35
Simon A. Eugster
1596
1596
Even though you've found the solution, I am surprised you are fine with 5GB of RAM used for your VM, as from my experience W10 allocates 5+ GB just when it starts, and VS 2017 takes about 500MB, so 5.5GB used under W10 on a physical host with 16GB RAM is a normality. Adding AV and other minor corporate stuff brings up initial RAM allocation on my current machine to 9.5 GB right after fresh start.
– ajeh
Jul 27 at 17:28
You are right. The VM is configured with 6.5 GB currently. Infree -h, the memory used by VMware does not show up in “used memory†but only in “shared†(for example, it shows 2 GB used and 3 GB free currently). Will update the question to clarify that :)
– Simon A. Eugster
Jul 30 at 6:55
add a comment |Â
Even though you've found the solution, I am surprised you are fine with 5GB of RAM used for your VM, as from my experience W10 allocates 5+ GB just when it starts, and VS 2017 takes about 500MB, so 5.5GB used under W10 on a physical host with 16GB RAM is a normality. Adding AV and other minor corporate stuff brings up initial RAM allocation on my current machine to 9.5 GB right after fresh start.
– ajeh
Jul 27 at 17:28
You are right. The VM is configured with 6.5 GB currently. Infree -h, the memory used by VMware does not show up in “used memory†but only in “shared†(for example, it shows 2 GB used and 3 GB free currently). Will update the question to clarify that :)
– Simon A. Eugster
Jul 30 at 6:55
Even though you've found the solution, I am surprised you are fine with 5GB of RAM used for your VM, as from my experience W10 allocates 5+ GB just when it starts, and VS 2017 takes about 500MB, so 5.5GB used under W10 on a physical host with 16GB RAM is a normality. Adding AV and other minor corporate stuff brings up initial RAM allocation on my current machine to 9.5 GB right after fresh start.
– ajeh
Jul 27 at 17:28
Even though you've found the solution, I am surprised you are fine with 5GB of RAM used for your VM, as from my experience W10 allocates 5+ GB just when it starts, and VS 2017 takes about 500MB, so 5.5GB used under W10 on a physical host with 16GB RAM is a normality. Adding AV and other minor corporate stuff brings up initial RAM allocation on my current machine to 9.5 GB right after fresh start.
– ajeh
Jul 27 at 17:28
You are right. The VM is configured with 6.5 GB currently. In
free -h, the memory used by VMware does not show up in “used memory†but only in “shared†(for example, it shows 2 GB used and 3 GB free currently). Will update the question to clarify that :)– Simon A. Eugster
Jul 30 at 6:55
You are right. The VM is configured with 6.5 GB currently. In
free -h, the memory used by VMware does not show up in “used memory†but only in “shared†(for example, it shows 2 GB used and 3 GB free currently). Will update the question to clarify that :)– Simon A. Eugster
Jul 30 at 6:55
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
The solution is to disable khugepaged defragmenting:
echo never | sudo tee /sys/kernel/mm/transparent_hugepage/defrag
echo 0 | sudo tee /sys/kernel/mm/transparent_hugepage/khugepaged/defrag
See this answer from the question Arch Linux becomes unresponsive from khugepaged.
Also, it is probably a good idea to limit the amount of RAM which VMware can use for running VMs to reserve some for the host system (Edit > Preferences).
Note: I am re-posting this answer under this question because the answer is very hard to find – it literally took me years.
answered Jul 27 at 16:35
Simon A. Eugster
1596
1
alternatively, you can add to the kernel options in grubtransparent_hugepage=never
– Rui F Ribeiro
Jul 27 at 16:48
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
The solution is to disable khugepaged defragmenting:
echo never | sudo tee /sys/kernel/mm/transparent_hugepage/defrag
echo 0 | sudo tee /sys/kernel/mm/transparent_hugepage/khugepaged/defrag
See this answer from the question Arch Linux becomes unresponsive from khugepaged.
Also, it is probably a good idea to limit the amount of RAM which VMware can use for running VMs to reserve some for the host system (Edit > Preferences).
Note: I am re-posting this answer under this question because the answer is very hard to find – it literally took me years.
answered Jul 27 at 16:35
Simon A. Eugster
1596
1
alternatively, you can add to the kernel options in grubtransparent_hugepage=never
– Rui F Ribeiro
Jul 27 at 16:48
add a comment |Â
up vote
2
down vote
The solution is to disable khugepaged defragmenting:
echo never | sudo tee /sys/kernel/mm/transparent_hugepage/defrag
echo 0 | sudo tee /sys/kernel/mm/transparent_hugepage/khugepaged/defrag
See this answer from the question Arch Linux becomes unresponsive from khugepaged.
Also, it is probably a good idea to limit the amount of RAM which VMware can use for running VMs to reserve some for the host system (Edit > Preferences).
Note: I am re-posting this answer under this question because the answer is very hard to find – it literally took me years.
answered Jul 27 at 16:35
Simon A. Eugster
1596
1
alternatively, you can add to the kernel options in grubtransparent_hugepage=never
– Rui F Ribeiro
Jul 27 at 16:48
add a comment |Â
up vote
2
down vote
up vote
2
down vote
The solution is to disable khugepaged defragmenting:
echo never | sudo tee /sys/kernel/mm/transparent_hugepage/defrag
echo 0 | sudo tee /sys/kernel/mm/transparent_hugepage/khugepaged/defrag
See this answer from the question Arch Linux becomes unresponsive from khugepaged.
Also, it is probably a good idea to limit the amount of RAM which VMware can use for running VMs to reserve some for the host system (Edit > Preferences).
Note: I am re-posting this answer under this question because the answer is very hard to find – it literally took me years.
answered Jul 27 at 16:35
Simon A. Eugster
1596
The solution is to disable khugepaged defragmenting:
echo never | sudo tee /sys/kernel/mm/transparent_hugepage/defrag
echo 0 | sudo tee /sys/kernel/mm/transparent_hugepage/khugepaged/defrag
See this answer from the question Arch Linux becomes unresponsive from khugepaged.
Also, it is probably a good idea to limit the amount of RAM which VMware can use for running VMs to reserve some for the host system (Edit > Preferences).
Note: I am re-posting this answer under this question because the answer is very hard to find – it literally took me years.
answered Jul 27 at 16:35
Simon A. Eugster
1596
answered Jul 27 at 16:35
Simon A. Eugster
1596
answered Jul 27 at 16:35
Simon A. Eugster
1596
answered Jul 27 at 16:35
Simon A. Eugster
1596
1596
1
alternatively, you can add to the kernel options in grubtransparent_hugepage=never
– Rui F Ribeiro
Jul 27 at 16:48
add a comment |Â
1
alternatively, you can add to the kernel options in grubtransparent_hugepage=never
– Rui F Ribeiro
Jul 27 at 16:48
1
1
alternatively, you can add to the kernel options in grub
transparent_hugepage=never– Rui F Ribeiro
Jul 27 at 16:48
alternatively, you can add to the kernel options in grub
transparent_hugepage=never– Rui F Ribeiro
Jul 27 at 16:48
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f458893%2fvmware-on-linux-host-causes-regular-freezes%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Even though you've found the solution, I am surprised you are fine with 5GB of RAM used for your VM, as from my experience W10 allocates 5+ GB just when it starts, and VS 2017 takes about 500MB, so 5.5GB used under W10 on a physical host with 16GB RAM is a normality. Adding AV and other minor corporate stuff brings up initial RAM allocation on my current machine to 9.5 GB right after fresh start.
– ajeh
Jul 27 at 17:28
You are right. The VM is configured with 6.5 GB currently. In
free -h, the memory used by VMware does not show up in “used memory†but only in “shared†(for example, it shows 2 GB used and 3 GB free currently). Will update the question to clarify that :)– Simon A. Eugster
Jul 30 at 6:55