VMWare slowly freezing whole system












0















Background:



I'm running Kubuntu 18.04 LTS and running Win 10 as guest for random MS specific apps OS on VMWare Workstation 15 Player. Everything appears to work really smooth and nice... for a while. After system has been up for a week or two, weird things start to happen.



At some point, I see various desktop features freezing/unresponsive, and by digging what's going on, it always seems to somehow point to vmware-vmx process. I.e. when I run simple ps aux at terminal, it gets frozen when printing details fof vmware-vmx. By doing strace ps aux I can see that it always gets stuck when reading from /proc/vmware-vmx-PID/cmdline file. The ps aux is frozen so hard that it can't be killed.



strace ps aux screenshot



Also killing the vmware-vmx process doesn't seem to fix the problem. After killing the process, system continues to behave weird and cause lots of lock-ups with many apps. Only reboot seems to recover from it (or actually hard-reset, because reboot also gets stuck waiting to shutdown snapd daemon forever).



What is most terrifying is that doing the system reboot at that state has tendency to corrupt files that I assume some apps are trying to write when closing. On next boot I see some files being empty (i.e. thunderbird passwords were once lost, another time eclipse workspace settings were lost because it contained an empty file, vmware disk image was crapped also once).



Any idea what's going on here?
OR any positive experiences with vmware with long uptimes?



Thanks for sharing your thoughts!



Sys specs:




  • VMWare Workstation 15 Player 15.0.2

  • 64 bit kernel 4.15.0-44

  • Core i5-6600

  • 24 GB RAM, memtest86 pass

  • Geforce 1060 with NVidia drivers 410.78 (390.xx also tried, no difference)

  • KDE 5

  • Ubuntu updates up to date

  • System should be stable, it's been used for 3 years on Win7 without stability issues (uptime several months between boots & active use, no problems)










share|improve this question

























  • As an experiment I have ran VMWare without 3D acceleration enabled and no stability issue occurred during 24 day uptime. Perhaps the freezing is related to VMware's 3D support OR nvidia drivers. Next test is to try with other display drivers/GPU.

    – Lahottaja
    Feb 22 at 16:26


















0















Background:



I'm running Kubuntu 18.04 LTS and running Win 10 as guest for random MS specific apps OS on VMWare Workstation 15 Player. Everything appears to work really smooth and nice... for a while. After system has been up for a week or two, weird things start to happen.



At some point, I see various desktop features freezing/unresponsive, and by digging what's going on, it always seems to somehow point to vmware-vmx process. I.e. when I run simple ps aux at terminal, it gets frozen when printing details fof vmware-vmx. By doing strace ps aux I can see that it always gets stuck when reading from /proc/vmware-vmx-PID/cmdline file. The ps aux is frozen so hard that it can't be killed.



strace ps aux screenshot



Also killing the vmware-vmx process doesn't seem to fix the problem. After killing the process, system continues to behave weird and cause lots of lock-ups with many apps. Only reboot seems to recover from it (or actually hard-reset, because reboot also gets stuck waiting to shutdown snapd daemon forever).



What is most terrifying is that doing the system reboot at that state has tendency to corrupt files that I assume some apps are trying to write when closing. On next boot I see some files being empty (i.e. thunderbird passwords were once lost, another time eclipse workspace settings were lost because it contained an empty file, vmware disk image was crapped also once).



Any idea what's going on here?
OR any positive experiences with vmware with long uptimes?



Thanks for sharing your thoughts!



Sys specs:




  • VMWare Workstation 15 Player 15.0.2

  • 64 bit kernel 4.15.0-44

  • Core i5-6600

  • 24 GB RAM, memtest86 pass

  • Geforce 1060 with NVidia drivers 410.78 (390.xx also tried, no difference)

  • KDE 5

  • Ubuntu updates up to date

  • System should be stable, it's been used for 3 years on Win7 without stability issues (uptime several months between boots & active use, no problems)










share|improve this question

























  • As an experiment I have ran VMWare without 3D acceleration enabled and no stability issue occurred during 24 day uptime. Perhaps the freezing is related to VMware's 3D support OR nvidia drivers. Next test is to try with other display drivers/GPU.

    – Lahottaja
    Feb 22 at 16:26
















0












0








0








Background:



I'm running Kubuntu 18.04 LTS and running Win 10 as guest for random MS specific apps OS on VMWare Workstation 15 Player. Everything appears to work really smooth and nice... for a while. After system has been up for a week or two, weird things start to happen.



At some point, I see various desktop features freezing/unresponsive, and by digging what's going on, it always seems to somehow point to vmware-vmx process. I.e. when I run simple ps aux at terminal, it gets frozen when printing details fof vmware-vmx. By doing strace ps aux I can see that it always gets stuck when reading from /proc/vmware-vmx-PID/cmdline file. The ps aux is frozen so hard that it can't be killed.



strace ps aux screenshot



Also killing the vmware-vmx process doesn't seem to fix the problem. After killing the process, system continues to behave weird and cause lots of lock-ups with many apps. Only reboot seems to recover from it (or actually hard-reset, because reboot also gets stuck waiting to shutdown snapd daemon forever).



What is most terrifying is that doing the system reboot at that state has tendency to corrupt files that I assume some apps are trying to write when closing. On next boot I see some files being empty (i.e. thunderbird passwords were once lost, another time eclipse workspace settings were lost because it contained an empty file, vmware disk image was crapped also once).



Any idea what's going on here?
OR any positive experiences with vmware with long uptimes?



Thanks for sharing your thoughts!



Sys specs:




  • VMWare Workstation 15 Player 15.0.2

  • 64 bit kernel 4.15.0-44

  • Core i5-6600

  • 24 GB RAM, memtest86 pass

  • Geforce 1060 with NVidia drivers 410.78 (390.xx also tried, no difference)

  • KDE 5

  • Ubuntu updates up to date

  • System should be stable, it's been used for 3 years on Win7 without stability issues (uptime several months between boots & active use, no problems)










share|improve this question
















Background:



I'm running Kubuntu 18.04 LTS and running Win 10 as guest for random MS specific apps OS on VMWare Workstation 15 Player. Everything appears to work really smooth and nice... for a while. After system has been up for a week or two, weird things start to happen.



At some point, I see various desktop features freezing/unresponsive, and by digging what's going on, it always seems to somehow point to vmware-vmx process. I.e. when I run simple ps aux at terminal, it gets frozen when printing details fof vmware-vmx. By doing strace ps aux I can see that it always gets stuck when reading from /proc/vmware-vmx-PID/cmdline file. The ps aux is frozen so hard that it can't be killed.



strace ps aux screenshot



Also killing the vmware-vmx process doesn't seem to fix the problem. After killing the process, system continues to behave weird and cause lots of lock-ups with many apps. Only reboot seems to recover from it (or actually hard-reset, because reboot also gets stuck waiting to shutdown snapd daemon forever).



What is most terrifying is that doing the system reboot at that state has tendency to corrupt files that I assume some apps are trying to write when closing. On next boot I see some files being empty (i.e. thunderbird passwords were once lost, another time eclipse workspace settings were lost because it contained an empty file, vmware disk image was crapped also once).



Any idea what's going on here?
OR any positive experiences with vmware with long uptimes?



Thanks for sharing your thoughts!



Sys specs:




  • VMWare Workstation 15 Player 15.0.2

  • 64 bit kernel 4.15.0-44

  • Core i5-6600

  • 24 GB RAM, memtest86 pass

  • Geforce 1060 with NVidia drivers 410.78 (390.xx also tried, no difference)

  • KDE 5

  • Ubuntu updates up to date

  • System should be stable, it's been used for 3 years on Win7 without stability issues (uptime several months between boots & active use, no problems)







vmware freeze vmware-player uptime






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 30 at 15:33









Mr Shunz

2,49121922




2,49121922










asked Jan 30 at 13:16









LahottajaLahottaja

1




1













  • As an experiment I have ran VMWare without 3D acceleration enabled and no stability issue occurred during 24 day uptime. Perhaps the freezing is related to VMware's 3D support OR nvidia drivers. Next test is to try with other display drivers/GPU.

    – Lahottaja
    Feb 22 at 16:26





















  • As an experiment I have ran VMWare without 3D acceleration enabled and no stability issue occurred during 24 day uptime. Perhaps the freezing is related to VMware's 3D support OR nvidia drivers. Next test is to try with other display drivers/GPU.

    – Lahottaja
    Feb 22 at 16:26



















As an experiment I have ran VMWare without 3D acceleration enabled and no stability issue occurred during 24 day uptime. Perhaps the freezing is related to VMware's 3D support OR nvidia drivers. Next test is to try with other display drivers/GPU.

– Lahottaja
Feb 22 at 16:26







As an experiment I have ran VMWare without 3D acceleration enabled and no stability issue occurred during 24 day uptime. Perhaps the freezing is related to VMware's 3D support OR nvidia drivers. Next test is to try with other display drivers/GPU.

– Lahottaja
Feb 22 at 16:26












1 Answer
1






active

oldest

votes


















0














Try rolling back the kernel to 4.15.0-43 (or -42). There's known issues around external displays (though I've had the same lock-up symptoms you described the last two days). My kernel updated to 4.15.0-44 yesterday (check with grep 4.15.0-44 /var/log/dpkg.log). I suggest installing ukuu to manage kernels.



I'm also running Kubuntu 18.04 LTS, 64 bit on an i7-8850h, 32 GB RAM.



Links:




  • Redit link about the kernel bug

  • Ukuu Kernal Manager - FOSS Mint






share|improve this answer
























  • Thanks for hint! However I'm not certain that these kernel version would solve this. The lockups have been haunting me since I installed Ubuntu, over two months ago, and it has gone thru few kernel versions on that time. All of them had same issue.

    – Lahottaja
    Jan 31 at 20:19











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1114108%2fvmware-slowly-freezing-whole-system%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Try rolling back the kernel to 4.15.0-43 (or -42). There's known issues around external displays (though I've had the same lock-up symptoms you described the last two days). My kernel updated to 4.15.0-44 yesterday (check with grep 4.15.0-44 /var/log/dpkg.log). I suggest installing ukuu to manage kernels.



I'm also running Kubuntu 18.04 LTS, 64 bit on an i7-8850h, 32 GB RAM.



Links:




  • Redit link about the kernel bug

  • Ukuu Kernal Manager - FOSS Mint






share|improve this answer
























  • Thanks for hint! However I'm not certain that these kernel version would solve this. The lockups have been haunting me since I installed Ubuntu, over two months ago, and it has gone thru few kernel versions on that time. All of them had same issue.

    – Lahottaja
    Jan 31 at 20:19
















0














Try rolling back the kernel to 4.15.0-43 (or -42). There's known issues around external displays (though I've had the same lock-up symptoms you described the last two days). My kernel updated to 4.15.0-44 yesterday (check with grep 4.15.0-44 /var/log/dpkg.log). I suggest installing ukuu to manage kernels.



I'm also running Kubuntu 18.04 LTS, 64 bit on an i7-8850h, 32 GB RAM.



Links:




  • Redit link about the kernel bug

  • Ukuu Kernal Manager - FOSS Mint






share|improve this answer
























  • Thanks for hint! However I'm not certain that these kernel version would solve this. The lockups have been haunting me since I installed Ubuntu, over two months ago, and it has gone thru few kernel versions on that time. All of them had same issue.

    – Lahottaja
    Jan 31 at 20:19














0












0








0







Try rolling back the kernel to 4.15.0-43 (or -42). There's known issues around external displays (though I've had the same lock-up symptoms you described the last two days). My kernel updated to 4.15.0-44 yesterday (check with grep 4.15.0-44 /var/log/dpkg.log). I suggest installing ukuu to manage kernels.



I'm also running Kubuntu 18.04 LTS, 64 bit on an i7-8850h, 32 GB RAM.



Links:




  • Redit link about the kernel bug

  • Ukuu Kernal Manager - FOSS Mint






share|improve this answer













Try rolling back the kernel to 4.15.0-43 (or -42). There's known issues around external displays (though I've had the same lock-up symptoms you described the last two days). My kernel updated to 4.15.0-44 yesterday (check with grep 4.15.0-44 /var/log/dpkg.log). I suggest installing ukuu to manage kernels.



I'm also running Kubuntu 18.04 LTS, 64 bit on an i7-8850h, 32 GB RAM.



Links:




  • Redit link about the kernel bug

  • Ukuu Kernal Manager - FOSS Mint







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 31 at 3:49









tvealtveal

1




1













  • Thanks for hint! However I'm not certain that these kernel version would solve this. The lockups have been haunting me since I installed Ubuntu, over two months ago, and it has gone thru few kernel versions on that time. All of them had same issue.

    – Lahottaja
    Jan 31 at 20:19



















  • Thanks for hint! However I'm not certain that these kernel version would solve this. The lockups have been haunting me since I installed Ubuntu, over two months ago, and it has gone thru few kernel versions on that time. All of them had same issue.

    – Lahottaja
    Jan 31 at 20:19

















Thanks for hint! However I'm not certain that these kernel version would solve this. The lockups have been haunting me since I installed Ubuntu, over two months ago, and it has gone thru few kernel versions on that time. All of them had same issue.

– Lahottaja
Jan 31 at 20:19





Thanks for hint! However I'm not certain that these kernel version would solve this. The lockups have been haunting me since I installed Ubuntu, over two months ago, and it has gone thru few kernel versions on that time. All of them had same issue.

– Lahottaja
Jan 31 at 20:19


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1114108%2fvmware-slowly-freezing-whole-system%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Human spaceflight

Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

File:DeusFollowingSea.jpg