On Tue, May 30, 2017 at 3:42 PM, <ovirt@fateknollogee.com> wrote:
Host: CentOS-7_v1611 (or Fedora 25 -my personal fav) VMs: oVirt nodes v4.1.2
To setup nested KVM, I follow these instructions(https://pve.proxm ox.com/wiki/Nested_Virtualization)
to check if is enabled do ("kvm_intel" for intel cpu, "kvm_amd" for AMD) -root@proxmox:~# cat /sys/module/kvm_intel/parameters/nested N (N means it's not, to enable ("kvm-intel" for intel, "kvm-amd" for AMD):)
# echo "options kvm-intel nested=Y" > /etc/modprobe.d/kvm-intel.conf and reboot or reload the kernel modul
modprobe -r kvm_intel modprobe kvm_intel check again
-root@proxmox:~# cat /sys/module/kvm_intel/parameters/nested Y
Question: what other settings need to be enabled in the guest vm? See "test nested virt" at https://fedoraproject.org/wiki /How_to_enable_nested_virtualization_in_KVM Do we need this setting in the vm? _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
But one of the questions already asked to you also throughout the other thread was: what hypervisor are you using? More precisely, as it is clear it is Qemu-KVM, what is the way you start your VMs that are the candidates to become hypervisors in oVirt? Is it with virt-manager, as described in one of the links you provided, or direct virsh commands or what? If you are using virt-manager, what did you specify in CPUs --> Configuration --> Model ? Did you choose the checkbox to "copy host cpu configuration"? Gianluca