Hello, I can confirm that the current -proposed package fixes the issue for Mitaka Cloud - Archive. libvirt
root@buneary:/home/ubuntu# time virsh start reproducer2 Domain reproducer2 started real 0m45.420s user 0m0.015s sys 0m0.012s 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 78ff00000000 bind:1 file=/dev/hugepages/libvirt/qemu/qemu_back_mem._objects_ram-node1.DBggwd\040(deleted) huge dirty=62 N1=62 kernelpagesize_kB=1048576 78d4c0000000 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 mitaka as done. ** Tags removed: verification-mitaka-needed ** Tags added: verification-mitaka-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705132 Title: Large memory guests, "error: monitor socket did not show up: No such file or directory" To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1705132/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
