starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Nested Proxmox VM #666

New Issue
Closed
opened 2026-02-04 20:37:35 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-04 20:37:35 +03:00
Owner
Copy Link

Originally created by @Ingraved on GitHub (Mar 19, 2025).

🌟 Briefly describe the feature

Install Proxmox Virtual Environment on a VM

📝 Detailed description

I think it would be very useful for testing to have Proxmox installed on a VM (or LXC?).
It would also be nice if the script had options to run 'post install' automatically.

💡 Why is this useful?

I probably don't need to explain why VMs are better for testing than bare metal installs.
I couldn't find a guide on how to install PVE in a VM and I think it would really benefit the community.

Originally created by @Ingraved on GitHub (Mar 19, 2025). ### 🌟 Briefly describe the feature Install Proxmox Virtual Environment on a VM ### 📝 Detailed description I think it would be very useful for testing to have Proxmox installed on a VM (or LXC?). It would also be nice if the script had options to run 'post install' automatically. ### 💡 Why is this useful? I probably don't need to explain why VMs are better for testing than bare metal installs. I couldn't find a guide on how to install PVE in a VM and I think it would really benefit the community.
OVERLORD added the enhancement label 2026-02-04 20:37:35 +03:00
OVERLORD commented 2026-02-04 20:37:50 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Mar 19, 2025):

i'm not really sure you understand how these things work

@tremor021 commented on GitHub (Mar 19, 2025): i'm not really sure you understand how these things work
OVERLORD commented 2026-02-04 20:37:53 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 19, 2025):

  • Resource Waste – Running a full Proxmox instance inside a VM consumes unnecessary CPU, RAM, and disk space.
  • Nested Virtualization Required – Without it, you can't run VMs inside the Proxmox VM, limiting its functionality.
  • Performance Issues – nested virtualization significantly reduces performance, especially for VMs inside of proxmox

By the way, here are not the right section for script requests.

Image
@MickLesk commented on GitHub (Mar 19, 2025): - Resource Waste – Running a full Proxmox instance inside a VM consumes unnecessary CPU, RAM, and disk space. - Nested Virtualization Required – Without it, you can't run VMs inside the Proxmox VM, limiting its functionality. - Performance Issues – nested virtualization significantly reduces performance, especially for VMs inside of proxmox By the way, here are not the right section for script requests. <img width="672" alt="Image" src="https://github.com/user-attachments/assets/e34c8239-c905-40a6-b856-516d627544fe" />
OVERLORD commented 2026-02-04 20:37:56 +03:00
Author
Owner
Copy Link

@Ingraved commented on GitHub (Mar 19, 2025):

i'm not really sure you understand how these things work

@tremor021, Would you mind clarifying what you believe I do not understand?

@Ingraved commented on GitHub (Mar 19, 2025): > i'm not really sure you understand how these things work @tremor021, Would you mind clarifying what you believe I do not understand?
OVERLORD commented 2026-02-04 20:38:00 +03:00
Author
Owner
Copy Link

@Ingraved commented on GitHub (Mar 19, 2025):

@MickLesk, The use case was for testing PVE. This use case is backed by Proxmox documentation. https://pve.proxmox.com/wiki/Nested_Virtualization#:~:text=it%20could%20let%20you%20test%20(or%20learn)%20how%20to%20manage%20hypervisors%20before%20actual%20implementation

Proxmox Devs use nested setups for development.
https://forum.proxmox.com/threads/running-proxmox-inside-a-proxmox-vm.40144/#post-338280:~:text=We%20use%20nested%20virtualization%20for%20development%20here%2C%20by%20the%20way.

I understand that PVE in a VM in PVE is not ideal for production. I will not open another ticket. I accept your decision. However, I do feel that the request was dismissed too quickly. Have a great day.

@Ingraved commented on GitHub (Mar 19, 2025): @MickLesk, The use case was for testing PVE. This use case is backed by Proxmox documentation. https://pve.proxmox.com/wiki/Nested_Virtualization#:~:text=it%20could%20let%20you%20test%20(or%20learn)%20how%20to%20manage%20hypervisors%20before%20actual%20implementation Proxmox Devs use nested setups for development. https://forum.proxmox.com/threads/running-proxmox-inside-a-proxmox-vm.40144/#post-338280:~:text=We%20use%20nested%20virtualization%20for%20development%20here%2C%20by%20the%20way. I understand that PVE in a VM in PVE is not ideal for production. I will not open another ticket. I accept your decision. However, I do feel that the request was dismissed too quickly. Have a great day.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#666
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?