all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Roland <devzero@web.de>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
	Atila Vasconcelos <atilav@lightspeed.ca>
Subject: Re: [PVE-User] linux idle cpu overhead in kvm - old issue, but still there in 2020...
Date: Sat, 18 Jul 2020 15:02:38 +0200	[thread overview]
Message-ID: <936489cc-8971-5e21-f25f-eafd4bb3795e@web.de> (raw)
In-Reply-To: <79fb6f58-0d41-80da-4bfa-2cdc344a3245@web.de>

apparently, this issue will get fixed upstream (in systemd package):

https://github.com/systemd/systemd/pull/353#issuecomment-658810289
https://github.com/systemd/systemd/pull/16476

roland

Am 15.07.20 um 19:18 schrieb Roland:
>
> >if i change VMs machine type from i440fx(default) to q35 the problem
> >goes away.
> >
> >the same applies when running "powertop --auto-tune" inside the guest
> >(with i440fx type - enable autosuspend for usb-controller + tablet
> device).
>
> third option (for VMs without gui):
>
> set "use tablet for pointer " to "No" in VM's options
>
> https://forum.proxmox.com/threads/high-cpu-usage-of-usb-tablet-device-in-debian.45307/
>
> https://forum.proxmox.com/threads/use-tablet-for-pointer-option-causing-cpu-usage-on-linux.54084/
>
> roland
>
>
> Am 14.07.20 um 19:16 schrieb Roland:
>> nice :)
>>
>> what guest OS do you use and which showed the problem ?
>>
>> as i think that q35 will not be default in kvm or proxmox anytime
>> soon, shouldn't we perhaps file a bug report for every distro affected ?
>>
>> is there someone who likes to work with this (help testing,
>> writing/tracking bug reports...) ?
>>
>> could perhaps save some tons of CO2 ....
>>
>> roland
>>
>>
>> Am 14.07.20 um 18:05 schrieb Atila Vasconcelos:
>>> Wow, I just tried this at my servers (very old Dell PowerEdge 2950);
>>>
>>> The results are impressive!
>>>
>>> 8o
>>>
>>>
>>> ABV
>>>
>>>
>>> On 2020-07-13 3:15 a.m., Roland wrote:
>>>> hello,
>>>>
>>>> i have found that there is an old bug still around in linux, which is
>>>> causing quite an amount of unnecessary cpu consumption in kvm/proxmox,
>>>> and thus, wasting precious power.
>>>>
>>>> i run some proxmox installations on older systems and on those, it's
>>>> quite significant difference.
>>>>
>>>> on the slowest system, a single debian 10 VM , kvm process is at
>>>> 20% cpu
>>>> (VM is 100% idle) when this issue is present.
>>>>
>>>> if i change VMs machine type from i440fx(default) to q35 the problem
>>>> goes away.
>>>>
>>>> the same applies when running "powertop --auto-tune" inside the guest
>>>> (with i440fx type - enable autosuspend for usb-controller + tablet
>>>> device).
>>>>
>>>> on some L5630 machine, in proxmox summary i see "CPU usage" drop from
>>>> 10% to <1%.
>>>>
>>>> see:
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=478317
>>>> https://bugzilla.redhat.com/show_bug.cgi?id=949547
>>>>
>>>> i guess this information could make a difference for people who run a
>>>> large amount of virtual machines or use older systems/cpu's.
>>>>
>>>> on most recent cpu's, i think the difference is not that big.
>>>>
>>>> anyway, i really wonder how linux bugs have such great survival
>>>> capability....
>>>>
>>>> regards
>>>> roland
>>>>
>>>> more references:
>>>> https://lists.gnu.org/archive/html/qemu-devel/2010-04/msg00149.html
>>>> https://www.redhat.com/archives/vfio-users/2015-November/msg00159.html
>>>>
>>>>
>>>> _______________________________________________
>>>> pve-user mailing list
>>>> pve-user@lists.proxmox.com
>>>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>>>
>>>
>>> _______________________________________________
>>> pve-user mailing list
>>> pve-user@lists.proxmox.com
>>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>>>



      parent reply	other threads:[~2020-07-18 13:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13 10:15 Roland
2020-07-14 16:05 ` Atila Vasconcelos
2020-07-14 17:16   ` Roland
     [not found]     ` <79fb6f58-0d41-80da-4bfa-2cdc344a3245@web.de>
2020-07-18 13:02       ` Roland [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=936489cc-8971-5e21-f25f-eafd4bb3795e@web.de \
    --to=devzero@web.de \
    --cc=atilav@lightspeed.ca \
    --cc=pve-user@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal