Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

xen-balloon consumes 15-30%+ CPU on idle in user qubes #9227

Open
jamke opened this issue May 14, 2024 · 2 comments
Open

xen-balloon consumes 15-30%+ CPU on idle in user qubes #9227

jamke opened this issue May 14, 2024 · 2 comments
Labels
affects-4.1 This issue affects Qubes OS 4.1. affects-4.2 This issue affects Qubes OS 4.2. C: Xen needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.

Comments

@jamke
Copy link

jamke commented May 14, 2024

Qubes OS release

R4.1
Used template is based on fedora-38-minimal.
Both OS and template are up to date.

Brief summary

xen-balloon command consumes 30%+ CPU on idle.
Happens with several qubes more often that others based on the same template.

Steps to reproduce

Use qube A while qube B shows no applications and should idle and do nothing.

Expected behavior

Qube B consumes 0% CPU

Actual behavior

Qube B consumes 15-35% CPU constantly or from time to time.
top shows that xen-balloon command is the only one that consumes this.

Additional

  • This problem of xen-balloon consuming CPU already happened in past but for dom0 (in 2021-2022):
    https://forum.qubes-os.org/t/high-dom0-cpu-usage-by-xen-balloon/6732/
    But I have everything up to date for R4.1, so it is expected to be fixed long time ago. i also have it in AppVMs, not dom0. Probably related, though.

  • It's probably a regression of the last year or so, before that I have never had this situation before, even with the same template.

@jamke jamke added P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists. labels May 14, 2024
@UndeadDevel
Copy link

UndeadDevel commented May 14, 2024

I've seen this symptom (~15-20% CPU usage in idle qubes) as well quite often (not sure about 4.1, but definitely in 4.2), but every time I launch a terminal in them and execute top, the CPU usage drops to very low (normal) levels again...did you use an admin console from a management disp VM to "catch" the xen-balloon process? The one thing that sometimes flashed for a moment with high-ish CPU usage in top was the Xorg process, but that may just be related to the fact that I just launched a terminal in that qube.

@jamke
Copy link
Author

jamke commented May 15, 2024

@UndeadDevel I use terminal (konsole), and top. Nothing fancy in my case. xen-balloon is shown as the top consumer. Can go to 0% in a few seconds, or can stay 15-35% for a longer time, for like minutes.

@andrewdavidwong andrewdavidwong added C: Xen needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. affects-4.1 This issue affects Qubes OS 4.1. affects-4.2 This issue affects Qubes OS 4.2. labels May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-4.1 This issue affects Qubes OS 4.1. affects-4.2 This issue affects Qubes OS 4.2. C: Xen needs diagnosis Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: bug Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
Projects
None yet
Development

No branches or pull requests

3 participants