Enable vSphere Nested Virtualization
Bug #2037566 reported by
Adam Dyess
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
The juju vsphere provider can launch VMs by first building with `buildConfigSpe
This flag would allow vsphere instances to be started which could also host VMs by passing `/dev/kvm` through to the host machine.
[0] https:/
[1] https:/
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
To post a comment you must log in.
Proposal of a new machine constraint:
nested- virtualization= [true|false]
My expectation is that one would want to add machines in a model, some with this enabled, and others without. This would facilitate something like Charmed Kubernetes with kubevirt enabled. The worker machines in the model could be started with a constraint like `nested- virtualization= true' which would allow `/dev/kvm` from the metal to be passed through and used to start VMs inside the workers without adding `/dev/kvm` the machines that host kubernetes- control- plane, etcd, vault, kubeapi- load-balancer and other Charmed Kubernetes machines