hi,

I'm trying to set up a KVM on my RHEL 7.3 installation through VB/VMW (I have same issue on both) on a windows 10 i7 laptop. The svm/vmx flags never appear on cpuinfo. Virtualization is already enabled in the BIOS, but I always get the below error message:

"KVM is not available. This may mean the KVM package is not installed, or the KVM kernel modules are not loaded. Your virtual machines may perform poorly."

I ran # yum group install "Virtualization Host" "Virtualization Client" for the prerequisites

"modprobe kvm_intel" says operation not supported

Any ideas what I might be missing?

Thanks!!

Try this link: https://access.redhat.com/documentat...ux_system.html

Thanks for the link but I already have those packages. I'm still not able to build the KVM.

So you're trying to build kvm to run VM's on a VM running in VBox? Am I understanding correctly?

yes

Have you tried https://wiki.archlinux.org/index.php...irtualization?

I've tried most of the things listed in that doc. The issue is with this part:

$ egrep --color=auto 'vmx|svm|0xc0f' /proc/cpuinfo

I don't have any of those flags, so I cannot use KVM, apparently. I have Virtualization enabled from the BIOS, plus all 7 of the needed packages for Virtualization. I have an Intel i7 6700HQ, which shows up under lscpu, so there shouldn't be any issues there I don't believe.

I have same question, and a guess at answer:
ONLY 32bit guest, on 64bit VMguest-'host', on 64bit physical host.
(I need to readup on why! So could any 'superb student'!)
Something about 2nd Layer of virtualization not possible for 64bitL2Guest, but 32bitL2Guest works.
(I have 32bit XPhost, so no. But you have 64bit Win10Host+LinuxGuest)

I wish I understood. I need to searchLQ too. I'll be back. &3+ layers of VMs?

Sidenote (as LQpolice say): Commercial software, so call their support. I'd use CentOS7+VB.
Update1:
link in #2 says you have "a valid Red Hat account", but Idk if support included.
link in #6 says: host (Win10 in your case) needs "Nested virtualization"
I'm lost here. M$Win cmds? LinuxGuest==2ndLevelHost? Time for more web-research.
Update2: (a minute later! Proves www-search faster than asking people!)
https://www.interfacett.com/blogs/ne...-to-enable-it/
(discusses Build10565+ host & nested VM must run same build of Win 10 & ...&)
Better search: "Nested virtualization" enable on win10 host linux guest
Studying... (3rd+ levels of VMs???) Update3: confusing; other LQers?
http://www.linuxquestions.org/questi...on-4175558228/ (dual-boot CentOS?)
http://www.linuxquestions.org/questi...4/#post5643049 ?? WHY?:LQblog/wiki?

As far as I am aware, VirtualBox still doesn't support nested virtualisation:

https://www.virtualbox.org/ticket/4032

Thanks. I saw that, but the 'obvious' just 'dawned' on me:
that means: the VBguestCPU doesn't receive (VB doesn't pass) the VT-x,
noting #1 where OP says: "The svm/vmx flags never appear on cpuinfo."

This is probably for RHCE, like the setup in beginning of Jang book (chapter 2).

Sorry, I get really lost on concepts that I don't "thoroughly understand, bottom-up"!

To OP: *let us know*, and mark thread as '[SOLVED]', *once all done* here.

p.s. Does Commercial VMware support this? [Yes?] I guess kvm does, on physical host.
So, what does Win10 need to allow VMware (OP:which product?) to 'work' here?
So, IF bare-metal-booted OS with kvm, can multiple layers of VMs w/kvm be done? [yes?]

I used to run VirtualBox, but I always had to remove the intel_kvm kernel module manually before I started a VM. I decided that since KVM and VirtualBox didn't play nice together, I'd use the one that's built into Linux. That's been years ago.

Right, but even if VB doesn't support nested virtualization, I believe that VMware does. However, I'm facing the same issue even on VMW.

Jjanel, indeed it is an exercise from Jang's 2nd chapter. The instructions are clear enough but the dang flags never show up. :-/

Years ago I made nested VMs on VMware Workstation. But that was before virtualization CPU extensions. And it was 32-bit.

You probably need to post your (exact) version of VMware, and guest VMware 'config'.
Like is req. for a (complete) 'bug report'! (So others can reproduce problem)