blob: 70bea81f35b33208fb5edb11dae2f9b89116c043 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
device: 0.586
semantic: 0.548
performance: 0.472
PID: 0.462
other: 0.392
graphic: 0.346
vnc: 0.335
permissions: 0.292
boot: 0.281
files: 0.280
socket: 0.265
KVM: 0.247
network: 0.244
debug: 0.204
[Feature Request] Battery Status / Virtual Battery
When using virtualization on notebooks heavily then virtual machines do not realize that they're running on a notebook device causing high power consumption because they're not switching into a optimized "laptop mode". This leads to the circumstance that they are trying to do things like defragmentation / virtus scan / etc. while the host is still running on batteries.
So it would be great if QEMU / KVM would have support for emulating "Virtual Batteries" to guests causing them to enable power-saving options like disabling specific services / devices / file operations automatically by OS.
Optionally a great feature would be to set virtual battery's status manually. For example: Current charge rate / charging / discharging / ...
I'm trying to add virtual battery to QEMU. More specifically, if the HOST is running on battery power [laptop] I want to pass this knowledge to GUEST.
I have looked at ACPI folder within QEMU source code, however was unable to find the specific place where I can add this functionality.
Can someone provide me with general roadmap of what should I do and where I should start? I suspect that changing the QEMU source code will not be enough and I will also have to implement a driver for the GUEST.
I've started working on this issue and have some progress. Fedora 31 guest is already able to see a battery device but its state currently hardcoded. I think i will finish this in a few weeks.
Has there been any progress? I'm using KVM for ubuntu 20.04 and would love to have this feature.
The implementation could be similar to the temperature sensor interface proposed here:
https://<email address hidden>/msg65192.html
mizz,
I'm worked on it and got a working draft on pre-5.0 codebase. It can react on QMP property changes to trigger ACPI events on x86 and arm-virt.
However i've stuck on frontend/backend split. Keep calm, i'm still working on the task and will complete this soon.
Philippe, thanks for advice!
I just wanted to add that this would (probably) help solve the error 43 on mobile Nvidia GPU passthrough scenarios. While facing this myself I was able to get it working by simulating a battery and attaching it via an ACPI table.
Your work is greatly appreciated Sergey.
Thank you very much!
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'invalid' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/242
|