HyperVDsc icon indicating copy to clipboard operation
HyperVDsc copied to clipboard

VMNetworkAdapter: Should support Device Naming and possibly other advanced options

Open nyanhp opened this issue 2 years ago • 0 comments

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 avatar Jan 17 '23 13:01 nyanhp