Ladi Prosek a765e3094d hyperv: Map Limit to max_memory and VirtualQuantity to cur_balloon ...

Hyper-V uses its own specific memory management so no mapping is going to
be perfect. However, it is more correct to map Limit to max_memory (it
really is the upper limit of what the VM may potentially use) and keep
cur_balloon equal to total_memory.

The typical value returned from Hyper-V in Limit is 1 TiB, which is not
really going to work if interpreted as "startup memory" to be ballooned
away later.

Signed-off-by: Ladi Prosek <lprosek@redhat.com>

2017-10-16 10:29:32 -04:00

..

hyperv_driver.c

hyperv: Map Limit to max_memory and VirtualQuantity to cur_balloon

2017-10-16 10:29:32 -04:00

hyperv_driver.h

Don't leave empty first line in C source files

2014-03-18 12:17:12 +01:00

hyperv_private.h

hyperv: store WMI version in hypervPrivate.

2017-04-08 14:14:15 +02:00

hyperv_util.c

Remove unnecessary curly brackets in src/hyperv/

2014-11-14 17:13:01 +01:00

hyperv_util.h

Don't leave empty first line in C source files

2014-03-18 12:17:12 +01:00

hyperv_wmi_classes.c

Don't leave empty first line in C source files

2014-03-18 12:17:12 +01:00

hyperv_wmi_classes.h

hyperv: Generate object property type information

2017-07-08 13:44:59 +02:00

hyperv_wmi_generator.input

hyperv: Add support for virDomainSetMemory

2017-07-08 13:45:07 +02:00

hyperv_wmi_generator.py

python: Don't hardcode interpreter path

2017-09-19 16:04:53 +02:00

hyperv_wmi.c

hyperv: Escape WQL queries

2017-10-16 10:29:32 -04:00

hyperv_wmi.h

hyperv: Add support for virDomainSetMemory

2017-07-08 13:45:07 +02:00

openwsman.h

hyperv: add hypervInvokeMethod

2017-07-08 13:45:02 +02:00