this post was submitted on 03 Mar 2026
7 points (100.0% liked)

linux4noobs

3976 readers
4 users here now

linux4noobs


Noob Friendly, Expert Enabling

Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.


Seeking Support?

Community Rules

founded 2 years ago
MODERATORS
 

Moved to Mint months back. I had to install Win10 in a kvm for a couple of things impossible on Linux. I allocated 16 gig of ram to the kvm. I can't really find anything on how that works, exactly. According to Stacer, I have a consistent 16 gig of ram being used, but that's between a running Win10 kvm and all of my other running Linux programs. I've never seen my system memory use move higher or lower than 16 gig of ram when the vm is running. Again, that's the kvm + normal Linux programs.

If I allocated 16 gig of ram to the kvm, shouldn't my memory usage be over 16 gig or ram with other Linux programs running?


About once a week, maybe two weeks, I open a new tab on a browser and it hangs my system. Nothing works but the mouse pointer.

I initially thought of a memory leak with Firefox, but it will also do it opening a new tab in Chrome.

The last time it hung up, I think I noticed the virtual machine manager icon was missing from the menu bar. I'm waiting for it to hang up again to verify this.

Anyone have any thoughts on this?

you are viewing a single comment's thread
view the rest of the comments
[–] refalo@programming.dev 1 points 11 hours ago

If you can still switch to the console, then check dmesg and/or journalctl -eb for any issues. But this at least tells you the system itself is not frozen. The kernel still works.

I would try to restart your login manager/desktop environment and see if that brings you back to a working desktop. If so then it sounds like a software bug in your DE. You could try switching to a different one and see if that helps anything. As a last resort you could also try a completely different Linux distro.