Hi,Can you spot whats wrong with this cluster in the picture?
View attachment 1923
No joke at all. This is for real. Yes it is a Virtualized Proxmox Cluster inside a Physical Proxmox Cluster. And it is fully functional without any major issue!should this be an joke?
I guess it's an cluster running on an kvm baremetal using nested virtualisation.
No joke at all. This is for real. Yes it is a Virtualized Proxmox Cluster inside a Physical Proxmox Cluster. And it is fully functional without any major issue!
No joke at all. This is for real. Yes it is a Virtualized Proxmox Cluster inside a Physical Proxmox Cluster. And it is fully functional without any major issue!
[...]
I wander if i can setup another nested Cluster inside this nested Cluster inside the Physical Cluster. LOL.
If you want to be able to run with nested kvm all you need is the following:
1) On each host add the following to /etc/modules :
Intel CPU: kvm-intel nested=1
AMD CPU: kvm-amd nested=1
2) Choose any CPU type for VM except kvm or qemu
3) In the VM add the following to /etc/modules :
Intel CPU: kvm-intel
AMD CPU: kvm-amd
yes, to both questions.
Nesting is not stable and not maintained or tested regularly here. (and does not work with 2.6.32 kernel anyways, use 3.10 in host and also guest).
It has been like this since pve-3.0. In pve-2.x you had to add a special argument to the vm.conf file.
And yes, this is quit stable and has been for years.
The physical Proxmox cluster has 4 nodes with Intel i7s.AMD or INTEL CPUs?
Nesting is not stable and not maintained or tested regularly here. (and does not work with 2.6.32 kernel anyways, use 3.10 in host and also guest).
It has been like this since pve-3.0. In pve-2.x you had to add a special argument to the vm.conf file.
And yes, this is quit stable and has been for years.
now, this is confusing...
please, can anyone explain/clarify? ....
I thought I did this already. As its not stable its unstable - that means it works for some, but not for me on latest Intel CPUs. If you want to test, use 3.10 kernel on the host and use amd cpu.
I suggest you try it by yourself and report results.
Agree with you there.btw, to me, unstable means that it should work in a defined way, but it often fails due to bugs.
If it works on some cpu vendors and not others, to me it means it is not supported everywhere, not that is unstable.
I have no amd cpu unfortunately, just intel and not latest.
just to report results so far on my servers (Intel(R) Xeon(R) CPU E5520 @ 2.27GHz)
running kernel 2.6.32-26-pve the /etc/modules modified with "kvm-intel nested=1"
does not work, in the nested pve it does not expose virt extensions.
Marco