linux4noobs

4026 readers

1 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?

Mention your Linux distro and relevant system details.
Describe what you've tried so far.
Share your solution even if you found it yourself.
Do not delete your post. This allows other people to see possible solutions if they have a similar problem.
Properly format any scripts, code, logs, or error messages.
Be mindful to omit any sensitive information such as usernames, passwords, IP addresses, etc.

Community Rules

Keep discussions respectful and amiable. This community is a space where individuals may freely inquire, exchange thoughts, express viewpoints, and extend help without encountering belittlement. We were all a noob at one point. Differing opinions and ideas is a normal part of discourse, but it must remain civil. Offenders will be warned and/or removed.
Posts must be Linux oriented
Spam or affiliate links will not be tolerated.

founded 2 years ago

MODERATORS

PlutoParty@programming.dev

qemu/kvm memory question (programming.dev)

submitted 2 weeks ago by transporter_ii@programming.dev to c/linux4noobs@programming.dev

13 comments fedilink hide all child comments

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

[–] DeltaWingDragon@sh.itjust.works 1 points 1 week ago* (last edited 1 week ago) (1 children)

Do you have any SWAP partition or swapfile? That will allow the host operating system to use parts of the disk as memory. Instead of completely locking up when it runs out of memory, it will get slow first, and buy you more time.

[–] transporter_ii@programming.dev 1 points 1 week ago (1 children)

That question has a lot of ways to go in. A swap file on Linux or Windows running in my vm? Also, I have a new PC with 32 gig of RAM. I allocated half to the vm when it is running. This kind of brings me to why I asked this question to begin with. I have Stacer installed and I've never seen my memory usage go over halfway (Stacer graph) when I have the vm running. I pretty much always have my vm running, because I need it running. I shouldn't be running out of memory. If it shows my 16ish gigs of ram used when the vm is fired up, then I should have 16ish gigs of ram that I've never seen being used.

I really wouldn't think the vm is running out of memory. There is 16 gig allocated and all it has running is IIS server, VisualStudio, and Firefox. I rarely open much more than that on it. I never browse on Windows' Firefox. It's just open because VisualStudio opens a browser while I'm debugging. At most, the only other programs running on the vm are File Manager and Notepad.

If I close the vm, Stacer shows my memory usage at 11 Gig. That means the vm should be using close to 6ish gig when it is fired up (according to Stacer).

Note: Yeah, I'm not able to check Stacer after it hangs up. I do spot checks with it from time to time. Like I said, about 50% of the ram is being used when my vm is fired up. No matter what I'm doing, I've never seen more than that used.

Thanks,

[–] DeltaWingDragon@sh.itjust.works 1 points 1 week ago (2 children)

It might actually be running out of memory. 16GB are used, and the other 16GB are unusable somehow. Could be a bad RAM stick or bad connection (as mentioned by others), or it could be a memory quota. Run ulimit -a to check the quota.

However, on my second read, the symptoms do not match up with running out of memory. (can drop to the console, can move the mouse) It could be a problem with the desktop environment. Which DE do you use?

[–] transporter_ii@programming.dev 1 points 1 week ago

It's pretty much a default install of Linux Mint, with Cinnamon. I haven't even installed that many programs, yet. Pretty much a vm, vscode, 4 browsers, gimp, and some small utilities.

[–] transporter_ii@programming.dev 1 points 1 week ago

OK, I just did some testing, and it was not exactly what I was expecting. For one, it's kind of hard to intentionally use a lot of memory. The best thing I found was opening a large amount of tabs in Firefox. I maybe could increase my swap space, but I never hung my system up. I shut down the vm and used about 18 gig of ram. I then started the vm.

The deal is, Stacer isn't exactly accurate when the VM starts. For some reason, memory usage (on Stacer) drops when the vm starts up. Checking the system resource monitor, memory usage briefly jumped to 28 gig in it. It never reflected this on Stacer. However, without the full 16 gig of ram allocated to the vm, Windows boots up, and then shuts back down after a brief period.

I stopped and started Windows numerous times. It would actually make Linux stutter as the memory maxed out, but it never froze up to the point I had to reboot to fix it.

The swap space did about max out during some of this. I do think I will increase the swap space a little.