Issue with Nested Hyper V Network

[killmasta93]

Hi
I was wondering if someone could shed some light,
Currently i have Hyper V nested in proxmox, the issue is that the VM in the Hyper V is not getting IP, I already tried putting on the hyper V the option mac spoofing but not sure what else i need to do to fix this issue?

Thank you

 

[BobhWasatch]

This is not a Proxmox problem. The default setup for desktop hyper-v is NAT. The vm will get a private IP and is effectively behind a firewall. If you want the vm to get a public IP you will need to configure a hyper-v bridge in Windows.

 

[killmasta93]

oh gotcha didnt know going to take a look at

 

[TheBelgarion]

Hello guys,

it took me 2 days to figure out all the quirks and hoops i had to jump through - but now Proxmox 8.x is running nicely under Windows 11 Hyper-V.
The main issue i had was that I could ping internet from Proxmox but could not get it working on a vm/lxc - but I could ping the proxmox host all the time.

the main points I did.
* enable mac-spoofing on all network Adapters (Network Adapater => [+] Advanced Features)
* integration services => enable all hyper-v services
* Security => disable Secure Boot
* enable Intel-VM
in admin powershell run Set-VMProcessor -VMName proxmox.dev -ExposeVirtualizationExtensions $true

after install of proxmox
* apt-get install hyperv-daemons
* systemctl reboot


no everything runs fine and i can use lxc container and have full access.

(Im using a secondary network card which i don't share with the OS, but i guess it should also work with a shraed/bridged).

I think ExposeVirtualization, mac-spoofing and installing the hyper-v-daemons is the most important here to get it running.