Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update nested-virtualization.md #1833

Open
wants to merge 1 commit into
base: live
Choose a base branch
from
+2 −0
Open

Update nested-virtualization.md #1833

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions virtualization/hyper-v-on-windows/user-guide/nested-virtualization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,3 +108,5 @@ In contrast, the diagram below shows Hyper-V with nested virtualization enabled.
## 3rd Party Virtualization Apps

Virtualization applications other than Hyper-V are not supported in Hyper-V virtual machines, and are likely to fail. This includes any software that requires hardware virtualization extensions.

Third party hypervisors such as [Proxmox VE](https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_11_Bullseye) built on [Azure Debian](https://wiki.debian.org/Cloud/MicrosoftAzure) run with minimal issues (tested on [Proxmox VE 7.3](https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_7.3)), however [QEMU/KVM](https://pve.proxmox.com/wiki/Qemu/KVM_Virtual_Machines) guest VM's within the nested hypervisor have been seen to have stability issues when using virtio storage drivers. The Default (LSI 53C895A) SCSI controller is a suitable alternative.