
27 Sep
2015
27 Sep
'15
1:15 a.m.
As a followup to my last e-mail, I grepped the '/var/log/vdsm/vdsm.log' file for the name of my VM so I could see what CPU options (and options in general) were being passed, and I definitely see that "hyperVenable" is being set to "true" I could try a full reboot of my host, in case the "kvm_intel" module didn't get properly (re-)loaded with the "nested" option....? Regards, Alan