blob: ca65b9c3d95cd2c36169ced89b8227ae26aa4936 (
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
58
59
60
|
performance: 0.939
device: 0.930
peripherals: 0.891
graphic: 0.839
virtual: 0.804
hypervisor: 0.804
ppc: 0.792
architecture: 0.762
semantic: 0.727
PID: 0.716
vnc: 0.711
register: 0.707
risc-v: 0.707
debug: 0.699
VMM: 0.686
mistranslation: 0.658
network: 0.648
i386: 0.644
TCG: 0.632
files: 0.629
arm: 0.626
permissions: 0.610
x86: 0.607
socket: 0.606
boot: 0.579
KVM: 0.545
kernel: 0.545
user-level: 0.471
assembly: 0.262
Guest os=Windows , qemu. Shutdown very slow. Memory allocation issue.
Description of problem:
simplifiying - libvirt config:
```
<memory unit='KiB'>33554432</memory>
<currentMemory unit='KiB'>131072</currentMemory>
```
when use `<currentMemory>` less than `<memory>` - at/after shutdown of guest os cpu hangs on 100% and lasts long- approximately 3-5 minutes
if change to
```
<memory unit='KiB'>33554432</memory>
<currentMemory unit='KiB'>33554432</currentMemory>
```
then shutdown takes less some seconds
problem occurs not (shutdown of VM takes some seconds) in cases when not used balloon device:
1 `<currentMemory>` equal to `<memory>`
2 memballoon driver disabled in windows
3 memballoon disabled on libvirt with "model=none" (and therefore not passed to qemu command line)
Additional information:
on the guest :
* used drivers from virtio-win-0.1.262.iso - membaloon ver 100.95.104.26200
* possible combination of all or some components
monitored next:
`virsh dommemstat VMName` at shutdown time there grows "rss" till MaxMem, but very slowly.
aLso on `virsh setmem VMName --live --size 32G`
rss grows slow - but takes 2 times less than at simple shutdown time ( = at shutdown seems occurs memory allocation and deallocation at the same time)
so something with some or all libvirt/qemu/balloon parts not so nice
|