Linux

48220 readers

726 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

vSphere+Debian+KDE Plasma=Crash? (lemmy.world)

submitted 8 months ago* (last edited 8 months ago) by Infernal_pizza@lemmy.world to c/linux@lemmy.ml

8 comments fedilink hide all child comments

I needed a test VM at work the other day so I just went with Debian because why not, during the install I chose KDE plasma as the DE. I did nothing else with it after installing it and after leaving it alone for a while (somewhere between 20-60 minutes) the CPU useage shot up to the point vSphere sent out an alert and the VM was unresponsive (the web console just showed a blank console which I couldn't type in) It did this every time I booted the VM.

It seems to be the combination of vSphere Debian and KDE that causes this as I installed GNOME on the same VM and it was fine. I also created another Debian VM this time choosing GNOME during the install and that was also fine, until I installed KDE on that and then it started doing the same thing. I also created an Arch VM with KDE and that didn't have any issues.

Any idea why this combination causes issues? Journalctl output of the last boot from both Debian VMs below:

Original VM: https://text.is/032Z Secondary test VM: https://text.is/JR45

you are viewing a single comment's thread
view the rest of the comments

[+] catloaf@lemm.ee 2 points 8 months ago* (last edited 8 months ago) (1 children)

[removed by mod]

[–] Infernal_pizza@lemmy.world 1 points 8 months ago (1 children)

I just left it as default which is 1 display and 8mb video memory

[–] d3Xt3r@lemmy.nz 2 points 8 months ago* (last edited 8 months ago) (1 children)

8MB?! That is abysmally low for KDE. Depending on the apps you're using, I'd recommend allocating at least 256MB, if you're going to use it for actual productivity tasks.

Edit: Here's a screenshot from nvtop showing my VRAM usage on KDE 5.27:

As you can see, Plasma alone is using 209MB, and Kwin 175MB, and this is with nothing but just Plasma and Konsole running on a very basic desktop (no fancy widgets, just one panel). Now this is at 2880x1800, so if your VM is running at a lower resolution you'd need lesser VRAM, but you can use that as a reference to see how much VRAM KDE really needs.

[–] Infernal_pizza@lemmy.world 1 points 8 months ago

I just tried increasing it but the maximum I can set is 255 and that made no difference unfortunately. All the Windows VMs are also set at 8 and they don’t have any problems