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.

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

VMNetworkAdapter: Should support Device Naming and possibly other advanced options #206

Open
nyanhp opened this issue Jan 17, 2023 · 0 comments · May be fixed by #208
Open

VMNetworkAdapter: Should support Device Naming and possibly other advanced options #206

nyanhp opened this issue Jan 17, 2023 · 0 comments · May be fixed by #208

Comments

@nyanhp
Copy link

nyanhp commented Jan 17, 2023

Problem description

Currently, the resource VMNetworkAdapter does not allow configuration of advanced properties like Device Naming. Without device naming, additional DSC configurations inside the virtual machines are more complicated. While implementing this, other settings like MacAddressSpoofing etc. could be implemented as well.

I am not a Hyper-V expert, but I will at least add MacAddressSpoofing and DeviceNaming

Verbose logs

None, this is not implemented yet

DSC configuration

VMNetworkAdapter netty
{
  Id         = "$($node.NodeName)-$($nic.InterfaceAlias)"
  Name       = "$($node.NodeName)-$($nic.InterfaceAlias)"
  SwitchName = $nic.InterfaceAlias -replace '-en0'
  VMName     = $node.NodeName
  DependsOn  = "[VMHyperV]$($node.NodeName)"
}

Suggested solution

VMNetworkAdapter netty
{
Id = "$($node.NodeName)-$($nic.InterfaceAlias)"
Name = "$($node.NodeName)-$($nic.InterfaceAlias)"
SwitchName = $nic.InterfaceAlias -replace '-en0'
VMName = $node.NodeName
DependsOn = "[VMHyperV]$($node.NodeName)"
DeviceNaming = "On" # On, Off
}

Operating system the target node is running

Available with 2016 and newer

PowerShell version and build the target node is running

5.1

HyperVDsc version

4.0.0
@nyanhp nyanhp linked a pull request Jan 17, 2023 that will close this issue
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant