[pve-devel] [PATCH] add hugepages option v5

Alexandre DERUMIER aderumier at odiso.com
Wed Jun 8 07:13:13 CEST 2016


>>One possibility would be adding an inotify handler onto the qemu.slice 
>>to pvestatd... 

another way, simply wrote a

/var/run/qemu-server/vmid.hugepages   when vm is starting, with hugepages topology

then in pvestatd, if vm is down and vmid.hugepages file is present, cleanup memory and remove file


Like this we can avoid inotify (in case of pvestatd was stopped/hanging)


----- Mail original -----
De: "aderumier" <aderumier at odiso.com>
À: "Wolfgang Bumiller" <w.bumiller at proxmox.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Mercredi 8 Juin 2016 06:00:16
Objet: Re: [pve-devel] [PATCH] add hugepages option v5

>>We really need a stop hook... but the question there is *how*... 
>>(Even if we added a hook to kvm, it would be nice to have something for 
>>the case where it gets SIGKILLed). 

For clean qemu stop (or shutdown in guest), we could use qmp-events 
https://projects.honeynet.org/svn/sebek/virtualization/qebek/trunk/QMP/qmp-events.txt 

But this need some kind of daemon/proxy which is always connected to qmp sockets (we can have only 1 connection by qmp socket), 
which can catch async events messages 
and then send qmp commands through this proxy. 

>>One possibility would be adding an inotify handler onto the qemu.slice 
>>to pvestatd... 

Seem to be more easy to implement (and should work with SIGKILLed) 

>>I've also looked quickly over the systemd dbus API but 
>>there was no obvious stop signal one could listen to... 

same here :( 
_______________________________________________ 
pve-devel mailing list 
pve-devel at pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 



More information about the pve-devel mailing list