Hello
This is not a support request, it's just a post to explain my experience hoping it will help someone.
After several hours (days) investigating, I have been able to have a windows 11 machine with Virtual Box nested virtualization. First of all I'm going to put my configuration and later I'll share my experience:
Of course, I followed this document: https://pve.proxmox.com/wiki/Nested_Virtualization
But it was not enough because I got blue and autorepair screens, as many other people in this forum
Now, i got this config working:
My experience was that I had a W11 machine working fine, and suddenly it was not able to boot. It showed a blus screen autorepair screen. I tried tons of solutions and configurations in .conf files with many "args:" opctions that appears to work for others. I also changed CPU from HOST to x86-64-vs-AES and other options like turn KVM off.
The strange behavior was that when I changed to default CPU (KVM64), windows was able to run, but Virtual Box reported:
Then I changed the CPU to HOST again, windows starts and Virtualbox worked... until next boot. After shutdown and boot, it fails again. I had to change CPU to default, start windows, shutdown Windows, change CPU, start windows... and it works... until next restart.
I tried clean installations, different CPU, Graphic cards, tips, .conf configuration, args, flags... nothing worked.
Until I decided to write this post and I tried to get all the information that could be useful. I that point, I checked all the setups in Proxmox and Windows in order to explain the problem and I realized that with the configuration I have posted at the beginning, IT WORKS!.
Don't ask me why. The only thing I did different was
Because all the previous tries were done with Windows Feature: Virtual Machine Patform -> ON
I leave this here with the hope that it will be useful for someone.
And... of course, if it suddenly fails again, I'll be back here
Regards,
Carlos
This is not a support request, it's just a post to explain my experience hoping it will help someone.
After several hours (days) investigating, I have been able to have a windows 11 machine with Virtual Box nested virtualization. First of all I'm going to put my configuration and later I'll share my experience:
Of course, I followed this document: https://pve.proxmox.com/wiki/Nested_Virtualization
But it was not enough because I got blue and autorepair screens, as many other people in this forum
Now, i got this config working:
- CPU -> host
- Windows features:
- Windows features:
- Windows feater Hyper-v ON
- Virtual Machine Patform off
- Windows hypervisor Plarform off
My experience was that I had a W11 machine working fine, and suddenly it was not able to boot. It showed a blus screen autorepair screen. I tried tons of solutions and configurations in .conf files with many "args:" opctions that appears to work for others. I also changed CPU from HOST to x86-64-vs-AES and other options like turn KVM off.
The strange behavior was that when I changed to default CPU (KVM64), windows was able to run, but Virtual Box reported:
- WHvCapabilityCodeHypervisorPresent is FALSE! Make sure you have enabled the 'Windows Hypervisor Platform' feature.
Then I changed the CPU to HOST again, windows starts and Virtualbox worked... until next boot. After shutdown and boot, it fails again. I had to change CPU to default, start windows, shutdown Windows, change CPU, start windows... and it works... until next restart.
I tried clean installations, different CPU, Graphic cards, tips, .conf configuration, args, flags... nothing worked.
Until I decided to write this post and I tried to get all the information that could be useful. I that point, I checked all the setups in Proxmox and Windows in order to explain the problem and I realized that with the configuration I have posted at the beginning, IT WORKS!.
Don't ask me why. The only thing I did different was
- Windows feater Hyper-v ON
- Virtual Machine Patform off
- Windows hypervisor Plarform off
Because all the previous tries were done with Windows Feature: Virtual Machine Patform -> ON
I leave this here with the hope that it will be useful for someone.
And... of course, if it suddenly fails again, I'll be back here
Regards,
Carlos