[pve-devel] ballon initializing bug

[Alexandre DERUMIER]

adding a sleep seem to fix it. (execute the balloon command when guest driver is already loaded)


            if (!$statefile && (!defined($conf->{balloon}) || $conf->{balloon})) {
+                sleep 30;
                vm_mon_cmd_nocheck($vmid, "balloon", value => $conf->{balloon}*1024*1024)
                    if $conf->{balloon};
            }


Seem to be related to guest kernel.

guest kernel 3.16 works fine,  guest kernel 4.7,4.8 don't see the value at start. (maybe balloon driver don't read the value at boot)


----- Mail original -----
De: "aderumier" <aderumier at odiso.com>
À: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Mercredi 16 Novembre 2016 16:59:25
Objet: [pve-devel] ballon initializing bug

Hi, 

I have detected something strange with ballooning and qemu 2.7 and 2.6.2 (not sure about old version). 
maybe it's a recent proxmox update ? 


vmid.conf 
--------- 
memory: 16384 
shares: 0 
balloon: 4096 


at start, qmp command seem to be sent the qmp command 

{ 
'arguments' => { 
'value' => 4294967296 
}, 
'execute' => 'balloon' 
}; 


but info balloon give me: 

# info balloon 
balloon: actual=16384 max_mem=16384 total_mem=16049 free_mem=15913 mem_swapped_in=0 mem_swapped_out=0 major_page_faults=255 minor_page_faults=62558 last_update=1479311697 



Then if I set manually in monitor: 

# balloon 4096 
# info balloon 
balloon: actual=4096 max_mem=16384 total_mem=4317 free_mem=3956 mem_swapped_in=0 mem_swapped_out=0 major_page_faults=964 minor_page_faults=205397 last_update=1479311871 
_______________________________________________ 
pve-devel mailing list 
pve-devel at pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel