Comment 16 for bug 1705132

Revision history for this message
Jorge Niedbalski (niedbalski) wrote :

Hello,

I can confirm that the current -proposed package fixes the issue for Xenial.

root@buneary:/home/ubuntu# dpkg -l | grep libvirt
ii libvirt-bin 1.3.1-1ubuntu10.12 amd64 programs for the libvirt library
ii libvirt0:amd64 1.3.1-1ubuntu10.12 amd64 library for interfacing with different virtualization systems
ii libvirt0-dbg 1.3.1-1ubuntu10.12 amd64 library for interfacing with different virtualization systems - debugging symbols
ii python-libvirt 1.3.1-1ubuntu1 amd64 libvirt Python
 bindings
ii uvtool-libvirt 0~bzr99-0ubuntu1 all Library and tools for using Ubuntu Cloud Images with libvirt

root@buneary:/home/ubuntu# time virsh start reproducer2
Domain reproducer2 started

real 0m35.450s
user 0m0.020s
sys 0m0.008s

It allocated all the available huge pages on both nodes (0, 1).

root@buneary:/home/ubuntu# sudo cat /proc/$(pidof qemu-system-x86_64)/numa_maps | grep huge
7f5500000000 bind:1 file=/dev/hugepages/libvirt/qemu/qemu_back_mem._objects_ram-node1.DBggwd\040(deleted) huge dirty=62 N1=62 kernelpagesize_kB=1048576

7f64c0000000 bind:0 file=/dev/hugepages/libvirt/qemu/qemu_back_mem._objects_ram-node0.AmusgD\040(deleted) huge dirty=60 N0=60 kernelpagesize_kB=1048576

root@buneary:/home/ubuntu# cat /sys/kernel/mm/hugepages/hugepages-1048576kB/free_hugepages
0

Marking the verification for xenial as done.