summary refs log tree commit diff stats
path: root/results/classifier/zero-shot/111/review/680758
blob: a456a0c2b5d91eb033e97ad21c71c5358d0feb6a (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
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
PID: 0.120
graphic: 0.119
device: 0.097
KVM: 0.082
semantic: 0.077
other: 0.077
performance: 0.075
socket: 0.074
files: 0.055
network: 0.054
vnc: 0.050
boot: 0.047
debug: 0.039
permissions: 0.034
KVM: 0.546
performance: 0.215
debug: 0.192
files: 0.009
semantic: 0.007
device: 0.005
PID: 0.005
socket: 0.004
other: 0.004
network: 0.003
graphic: 0.003
vnc: 0.002
permissions: 0.002
boot: 0.002

balloon only resizes by 2M

when in monitor and running balloon 512 from a 1024M VM, the vm dropped the size to 1020 (this value changes), then every subsequent request to balloon 512 will drop it by another 2M.  The system was running at above 60% RAM free when these requests were made.  also requesting to up the ram results in no change above 1024 (I'm guessing this is intentional, but was unable to find any documentation)

Versions:

qemu-kvm 0.13.0
qemu-kvm.git b377474e589e5a1fe2abc7b13fafa8bad802637a


Qemu Command Line:

./x86_64-softmmu/qemu-system-x86_64 -ees/seven.base,if=virtio -net nic,model=virtio,macaddr=02:00:00:00:00:01 -net tap,script=/etc/qemu/qemu-ifup,downscript=/etc/qemu/qemu-ifdown -vga std -usb -usbdevice tablet -rtc base=localtime,clock=host -watchdog i6300esb -balloon virtio -m 1024 -no-quit -smp 2 -monitor stdio


Monitor Session:

QEMU 0.13.50 monitor - type 'help' for more information
(qemu) info balloon
balloon: actual=1024
(qemu) balloon 1536
(qemu) info balloon
balloon: actual=1024
(qemu) balloon 512
(qemu) info balloon
balloon: actual=1020
(qemu) info balloon
balloon: actual=1020
(qemu) balloon 512
(qemu) info balloon
balloon: actual=1018

the same here:

host debian squeeze: qemu-kvm-0.12.5
guest: windows 2008 server 
balloon driver: 6.1.7600.16385  10.8.2010




~# virsh  -c qemu:///system dominfo 9 | grep Used
Used memory:    2064384 kB
~# virsh  -c qemu:///system setmem 9 512000

~# virsh  -c qemu:///system dominfo 9 | grep Used
Used memory:    2062336 kB


the same host,  but winXP guest with the same balloon driver is working, looks like balloon driver issue... 

Triaging old bug tickets ... can you still reproduce this issue with the latest version of QEMU / the latest version of the balloon driver in the guest?

[Expired for QEMU because there has been no activity for 60 days.]