starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Support for nested virtualisation #11012

New Issue
Closed
opened 2025-12-29 21:39:08 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:39:08 +01:00
Owner
Copy Link

Originally created by @restena-sw on GitHub (Apr 11, 2025).

NetBox version

v4.2.7

Feature type

Data model extension

Proposed functionality

I'm aware of #1909 and the decision not to pursue this feature.

But I see that this was a discussion in 2018, seven years have passed, and nested virtualisation is much more common today than it was back then.

It would be nice if you could re-think this feature request considering today's reality.

In the end, this could be relatively simple to do: add a property to a Virtual Machine where one can select "Nested virtualisation host" - and VMs which are added to a cluster that have this property are considered as "Devices" in that cluster.

Use case

Nested virtualisation (hypervisor-in-hypervisor). Many hypervisors these days support this functionality.

Database changes

No response

External dependencies

No response

Originally created by @restena-sw on GitHub (Apr 11, 2025). ### NetBox version v4.2.7 ### Feature type Data model extension ### Proposed functionality I'm aware of #1909 and the decision not to pursue this feature. But I see that this was a discussion in 2018, seven years have passed, and nested virtualisation is much more common today than it was back then. It would be nice if you could re-think this feature request considering today's reality. In the end, this could be relatively simple to do: add a property to a Virtual Machine where one can select "Nested virtualisation host" - and VMs which are added to a cluster that have this property are considered as "Devices" in that cluster. ### Use case Nested virtualisation (hypervisor-in-hypervisor). Many hypervisors these days support this functionality. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closurestatus: under review labels 2025-12-29 21:39:09 +01:00
adam closed this issue 2025-12-29 21:39:09 +01:00
adam commented 2025-12-29 21:39:09 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 11, 2025):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jul 11, 2025): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md).
adam commented 2025-12-29 21:39:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 6, 2025):

Closing this out as it does not provide sufficient detail to be actionable.

If you are interested in this functionality, you are welcome to submit a new feature request including the detailed proposed implementation, including expected data model and workflow changes.

@jeremystretch commented on GitHub (Aug 6, 2025): Closing this out as it does not provide sufficient detail to be actionable. If you are interested in this functionality, you are welcome to submit a **new** feature request including the detailed proposed implementation, including expected data model and workflow changes.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label pending closure status: under review type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11012
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?