Skip to content

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

@nyanhp

Description

@nyanhp

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions