blob: e90d077555c27028a8e9f7c7ce2ee82d6c826786 (
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
|
virtual: 0.972
mistranslation: 0.848
performance: 0.770
graphic: 0.760
device: 0.732
semantic: 0.667
VMM: 0.578
risc-v: 0.532
kernel: 0.529
hypervisor: 0.528
x86: 0.507
PID: 0.505
boot: 0.489
architecture: 0.484
i386: 0.483
user-level: 0.483
vnc: 0.469
network: 0.462
permissions: 0.456
ppc: 0.451
register: 0.449
socket: 0.441
debug: 0.436
TCG: 0.384
assembly: 0.359
files: 0.334
arm: 0.319
KVM: 0.306
peripherals: 0.270
qemu release memory to system
Qemu pre-allocates the maximum balloon amount which is inconvinient if all of the memory is used up and some other system needs to be added memory resource
eg:- I have 4GB RAM with 4 virtual systems to be run.
I want each of them to start with 1GB RAM with maximum 2GB possible. This is not achievable since qemu pre-allocates the maximum balloon amount which is 2GBx4 systems . So to start all 4 systems the system needs 8GB RAM rather than 4GB RAM to start with although I have told initial balloon amount to be 1GB.
Looking through old bug tickets... I think you should rather use hotpluggable memory here for the guests instead - or use a big swap partition on the host. Anyway, this is not a bug, so closing this ticket now.
|