A better way to do it would be to modify libvirt to create a directory
on the hugetlbfs for the vm (not just for itself), then pass that as the
mem-path to kvm and tell the sVirt driver about it somehow.
--
Apparmor deny when trying to use hugetlbfs
https://bugs.launchpad.net/bugs/646468
You rece
Just a follow-up...
This actually does work, and since qemu seems to unlink() right after
the mkstemp() there's only a small race condition there, and after that
the only way to steal another VMs memory is via procfs.
Is it worth writing a small doc (or debconf option?) to help people
setup huget
Ok, that was closer, but this time I get the message:
[84836.383289] type=1400 audit(1285366835.469:59): apparmor="DENIED"
operation="open" parent=1 profile="libvirt-
e2420e79-06d6-f8d0-0523-7c52b3650191"
name="/dev/hugepages/libvirt/qemu/kvm.3Ag3N7" pid=1149 comm="kvm"
requested_mask="r" denied_m
Public bug reported:
When starting a VM with hugepages support, I get an apparmor deny
message and the VM starts with normal pages.
dmesg shows:
[ 449.428584] type=1400 audit(1285282448.505:47): apparmor="DENIED"
operation="mknod" parent=1
profile="libvirt-e2420e79-06d6-f8d0-0523-7c52b3650191"
