centos 7 build error about hv-packer

[marcinbojko]

Thanks. Looks like your VM doesn't get an IP, and it's unable to reach hyper-v host for kickstart file
Can you confirm (when in VM dracut fails), what IP is assigned, if any?

[marcinbojko]

My guess (guess as you did't paste any logs) is - no rule for firewall or wrong switch name/van used.
Check the readme for guidance.

[marcinbojko]

Logs:
Get-NetAdapter
Get-VMSwitch |fl
Get-NetFirewallRule -Displayname "Packer_http_server"

[ykravch]

@marcinbojko

Name                      InterfaceDescription                    ifIndex Status       MacAddress             LinkSpeed
----                      --------------------                    ------- ------       ----------             ---------
vEthernet (vSwitch)       Hyper-V Virtual Ethernet Adapter             14 Up           00-22-48-1E-77-01        50 Gbps
Ethernet 6                Microsoft Hyper-V Network Adapter #6         17 Up           00-22-48-1E-77-01        50 Gbps

Name                                             : vSwitch
Id                                               : a49cb013-4cc5-4e5a-9315-8af9347c1d98
Notes                                            :
Extensions                                       : {Microsoft Windows Filtering Platform, Microsoft Azure VFP Switch
                                                   Extension, Microsoft NDIS Capture}
BandwidthReservationMode                         : Absolute
PacketDirectEnabled                              : False
EmbeddedTeamingEnabled                           : False
IovEnabled                                       : False
SwitchType                                       : External
AllowManagementOS                                : True
NetAdapterInterfaceDescription                   : Microsoft Hyper-V Network Adapter #6
NetAdapterInterfaceDescriptions                  : {Microsoft Hyper-V Network Adapter #6}
NetAdapterInterfaceGuid                          : {178a7cfe-dbde-46f1-a8e2-fdce64ea7d27}
IovSupport                                       : False
IovSupportReasons                                : {Ensure that the system has chipset support for SR-IOV and that I/O
                                                   virtualization is enabled in the BIOS., To use SR-IOV on this
                                                   system, the system BIOS must be updated to allow Windows to control
                                                   PCI Express. Contact your system manufacturer for an update.,
                                                   SR-IOV cannot be used on this system as the PCI Express hardware
                                                   does not support Access Control Services (ACS) at any root port.
                                                   Contact your system vendor for further information., This network
                                                   adapter does not support SR-IOV.}
AvailableIPSecSA                                 : 0
NumberIPSecSAAllocated                           : 0
AvailableVMQueues                                : 0
NumberVmqAllocated                               : 0
IovQueuePairCount                                : 0
IovQueuePairsInUse                               : 0
IovVirtualFunctionCount                          : 0
IovVirtualFunctionsInUse                         : 0
PacketDirectInUse                                : False
DefaultQueueVrssEnabledRequested                 : True
DefaultQueueVrssEnabled                          : False
DefaultQueueVmmqEnabledRequested                 : True
DefaultQueueVmmqEnabled                          : False
DefaultQueueVrssMaxQueuePairsRequested           : 16
DefaultQueueVrssMaxQueuePairs                    : 0
DefaultQueueVrssMinQueuePairsRequested           : 1
DefaultQueueVrssMinQueuePairs                    : 0
DefaultQueueVrssQueueSchedulingModeRequested     : StaticVrss
DefaultQueueVrssQueueSchedulingMode              : Dynamic
DefaultQueueVrssExcludePrimaryProcessorRequested : False
DefaultQueueVrssExcludePrimaryProcessor          : False
SoftwareRscEnabled                               : True
BandwidthPercentage                              : 10
DefaultFlowMinimumBandwidthAbsolute              : 5000000000
DefaultFlowMinimumBandwidthWeight                : 0
CimSession                                       : CimSession: .
ComputerName                                     : PACKER-AGENT-02
IsDeleted                                        : False
DefaultQueueVmmqQueuePairs                       : 0
DefaultQueueVmmqQueuePairsRequested              : 16

Name                  : {fcb7b443-301c-42fe-a6b4-e89288eb0dcd}
DisplayName           : Packer_http_server
Description           :
DisplayGroup          :
Group                 :
Enabled               : True
Profile               : Any
Platform              : {}
Direction             : Inbound
Action                : Allow
EdgeTraversalPolicy   : Block
LooseSourceMapping    : False
LocalOnlyMapping      : False
Owner                 :
PrimaryStatus         : OK
Status                : The rule was parsed successfully from the store. (65536)
EnforcementStatus     : NotApplicable
PolicyStoreSource     : PersistentStore
PolicyStoreSourceType : Local

[marcinbojko]

Looks ok. Can you switch PACKER_LOGS to 1 and paste a gist?

[ykravch]

https://gist.github.com/ykravch/c79e83b473116ab03c9c3512b6686d00

[ykravch]

Thank you. You're right, the problem is that VM doesn't get an IP address.

[marcinbojko]

Hi @ykravch , thanks for info. I'll update documentation as it seems quite popular these days ;)