On 12/13/18 8:29 AM, Michal Privoznik wrote:
> On 11/29/18 2:55 AM, John Ferlan wrote:
>> Support for nested KVM is handled via a kernel module configuration
>> parameters values for kvm_intel, kvm_amd, kvm_hv (PPC), or kvm (s390).
>> While it's possible to fetch the kmod config values via
On 11/29/18 2:55 AM, John Ferlan wrote:
> Support for nested KVM is handled via a kernel module configuration
> parameters values for kvm_intel, kvm_amd, kvm_hv (PPC), or kvm (s390).
> While it's possible to fetch the kmod config values via virKModConfig,
> unfortunately that is the static value
ping?
Thanks -
John
On 11/28/18 8:55 PM, John Ferlan wrote:
> Support for nested KVM is handled via a kernel module configuration
> parameters values for kvm_intel, kvm_amd, kvm_hv (PPC), or kvm (s390).
> While it's possible to fetch the kmod config values via virKModConfig,
> unfortunately
Support for nested KVM is handled via a kernel module configuration
parameters values for kvm_intel, kvm_amd, kvm_hv (PPC), or kvm (s390).
While it's possible to fetch the kmod config values via virKModConfig,
unfortunately that is the static value and we need to get the
current/dynamic value from