marcinbojko/hv-packer marcinbojko/hv-packer

  • Stars
    star
    181
  • Rank 212,110 (Top 5 %)
  • Language
    PowerShell
  • Created about 7 years ago
  • Updated 6 months ago
Twitter logo Share LinkedIn logo Share Facebook logo Share
marcinbojko/hv-packer
github

marcinbojko

Reviews

There are no reviews yet. Be the first to send feedback to the community and the maintainers!

Repository Details

Hyper-V Generation 2 Packer Templates for Windows 2019/2022, AlmaLinux 8.x/AlmaLinux 9.x/RockyLinux 8.x/9.x/OracleLinux 8.x/9.x Ubuntu 20.04/Ubuntu 22.04/Ubuntu 24.04

Set of Hashicorp's Packer templates to create Microsoft Hyper-V virtual machines

RockyLinux OracleLinux AlmaLinux CentosLinux UbuntuLinux

Windows2016 Windows2019 Windows2022

Requirements

  • packer <=1.8.4. Do not use packer below 1.7.0 version. For previous packer versions use previous releases from this repository
  • Microsoft Hyper-V Server 2016/2019 or Microsoft Windows Server 2016/2019 (not 2012/R2) with Hyper-V role installed as host to build your images
  • firewall exceptions for packer http server (look down below)
  • [OPTIONAL] Vagrant >= 2.2.19 - for vagrant version of scripts. Boxes (prebuilt) are already available here: https://app.vagrantup.com/marcinbojko
  • be aware, for 2016 - VMs are in version 8.0, for 2019 - VMs are in version 9.0. There is no way to reuse higher version in previous operating system. If you need v8.0 - build and use only VHDX.
  • properly constructed virtual switch in Hyper-v allowing virtual machine to get IP from DHCP and contact Hyper-V server on mentioned packer ports. This is a must, if kickstart is reachable over the network.

Requirements - Quick Start

Install packer from Chocolatey

choco install packer --version=1.8.4 -y

Install required plugins

In root folder of a repository

packer init --upgrade config.pkr.hcl

Install vagrant from Chocolatey

choco install vagrant --version=2.3.2 -y

Use account with Administrator privileges for Hyper-V

Add firewal exclusions for TCP ports 8000-9000 (default range)

Remove-NetFirewallRule -DisplayName "Packer_http_server" -Verbose
New-NetFirewallRule -DisplayName "Packer_http_server" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 8000-9000

Adjust Hyper-V settings

To adjust to your Hyper-V, please check variables below and/or in ./variables files

  • (variable vlan_id in /variables/variables.*.pkvars.hcl) - proper VLAN ID . Look up to find your build server vEthernet setings.
  • (variable switch_name in /variables/variables.*.pkvars.hcl) - proper Hyper-V Virtual Switch name (access to Internet will be required). Make sure you're using pre-existing switch in your Hyper-V server - creation of new switch by packer, instead of reusing existing one can cause lack of Internet access, thus failing the build.
# example of mentioned variables
vlan_id = ""
switch_name = "vSwitch"

Default passwords

OS username password
Windows Administrator password
vagrant vagrant
CentOS/RHEL root password
vagrant vagrant
Ubuntu ubuntu password
vagrant vagrant

Enable Packer debug logging

Soon to be parametrized

In building script set packet_log variable to 1

$packer_log=1

Scripts

Windows Machines

  • all available updates will be applied (3 passes)

  • latest version of chocolatey

  • packages from a list below:

    Package Version
    conemu latest
    dotnetfx latest
    sysinternals latest
    puppet 7.14.0
    tabby latest

  • latest Nuget poweshell module

  • phase3.ps1 Puppet agent settings will be customized (server=foreman.example.com) with parameters:

    • Version - puppet chocolatey version, for example "6.26.0"
    • AddPrivateChoco ($true/$false) - if set to true, private MyGet repository will be added as public
    • PuppetMaster (foreman.example.com) - if set, in puppet.conf section server will point to that variable

    Example of usage:

    .\phase3.ps1 -Version 7.14.0 -AddPrivateChoco $true -PuppetMaster foreman.example.com

    Puppet is set to clear any temp SSL keys and to be stopped after generalize phase

  • phase5b-docker.ps1 - Docker settings can be customised

    • requiredVersion - which version of docker module to install - defaults to 19.03.1
    • installCompose ($true/$false) - install docker-compose from chocolatey packages
    • dockerLocation - of set, will default docker images and settings there. On empty, docker location is not being set.
    • configDockerLocation - default place for docker's config file

    Example of usage

    .\phase5b-docker.ps1 -requiredVersion "19.03.1" -installCompose $true -dockerLocation "d:\docker" -configDockerLocation "C:\ProgramData\Docker\config"

Linux Machines

  • Repositories:

    Repository Package switch
    Epel 7/8/9 epel-release can be switched off by setting "install_epel" to false
    Zabbix 6.0 zabbix-agent can be switched on by setting "install_zabbix" to true
    Puppet 7 puppet-agent can be switched off by setting "install_puppet" to false
    Webmin webmin can be switched on by setting "install_webmin" to false
    Cockpit cockpit can be switched on by setting "install_zabbix" to true
    Hyper-V SCVMM Agent can be switched off by setting "install_hyperv" to false
    Neofetch neofetch can be switched off by setting "install_neofetch" to false

  • [Optional] Linux machine with separated disk for docker

  • [Optional] Linux machine for vagrant

    Be aware, turning off latest System Center Virtual Machine Agent will cause System Center fail to deploy machines

Ansible Playbooks (CentOS/AlmaLinux/RockyLinux/OracleLinux)

During deployment ansible-base and ansible are installed in operating system. After deployment ends, these packages are removed. Playbooks are held in /extra/playbooks folder, with proper OS variables.

  • adjust ./variables/*.yml files to achieve override for ansible
install_epel:                  true  # install Epel
install_webmin:                true  # install Webmin
install_hyperv:                true  # install Hyper-v and scvmm agent
install_zabbix:                false # install Zabbix-agent
install_zabbix_as_root:        false # install Zabbix-agent as root
install_cockpit:               false # install Cockpit
install_puppet:                true  # Install Puppet
install_docker_workaround:     true  # add `fsck.repair=yes` to grub
install_kubernetes_workaround: false # add `cgroup.memory=nokmem` to grub
remove_puppet_ssl_keys:        false # remove any ssl keys after puppet installation
install_neofetch:              true  # install neofetch
install_updates:               true  # install updates
install_extra_groups:          true  # install extra groups
docker_prepare:                false # prepare extra volumen for docker
extra_device:                  ""    # prepare mkfs and mount extra block device for docker
install_motd:                  true  # install motd (neofetch run)

Templates Windows 2022

Hyper-V Generation 2 Windows Server 2022 Standard Image

Run hv_win2022_std.ps1 (Windows)

Windows 2022 Standard Generation 2 Prerequisites

For Generation 2 prepare secondary.iso with folder structure:

  • ./extra/files/gen2-2022/std/Autounattend.xml => /Autounattend.xml
  • ./extra/scripts/hyper-v/bootstrap.ps1 => /bootstrap.ps1

This template uses this image name in Autounattendes.xml. If youre using different ISO you'll have to adjust that part in proper file and rebuild secondary.iso image.

<InstallFrom>
    <MetaData wcm:action="add">
        <Key>/IMAGE/NAME </Key>
        <Value>Windows Server 2022 SERVERSTANDARD</Value>
    </MetaData>
</InstallFrom>

Hyper-V Generation 2 Windows Server 2022 Datacenter Image

Run hv_win2022_dc.ps1 (Windows)

Windows 2022 Datacenter Generation 2 Prerequisites

For Generation 2 prepare secondary.iso with folder structure:

  • ./extra/files/gen2-2022/dc/Autounattend.xml => /Autounattend.xml
  • ./extra/scripts/hyper-v/bootstrap.ps1 => /bootstrap.ps1

This template uses this image name in Autounattendes.xml. If youre using different ISO you'll have to adjust that part in proper file and rebuild secondary.iso image.

<InstallFrom>
    <MetaData wcm:action="add">
        <Key>/IMAGE/NAME </Key>
        <Value>Windows Server 2022 SERVERDATACENTER</Value>
    </MetaData>
</InstallFrom>

[Experimental] Hyper-V generation 2 Windows Server 2022 Standard Vagrant support

hv_win2022_std_vagrant.ps1

[Experimental] Hyper-V generation 2 Windows Server 2022 Datacenter Vagrant support

hv_win2022_dc_vagrant.ps1

Templates Windows 2019

Hyper-V Generation 2 Windows Server 2019 Standard Image

Run hv_win2019_std.ps1 (Windows)

Windows 2019 Standard Generation 2 Prerequisites

For Generation 2 prepare secondary.iso with folder structure:

  • ./extra/files/gen2-2019/std/Autounattend.xml => /Autounattend.xml
  • ./extra/scripts/hyper-v/bootstrap.ps1 => /bootstrap.ps1

This template uses this image name in Autounattendes.xml. If youre using different ISO you'll have to adjust that part in proper file and rebuild secondary.iso image.

<InstallFrom>
    <MetaData wcm:action="add">
        <Key>/IMAGE/NAME </Key>
        <Value>Windows Server 2019 SERVERSTANDARD</Value>
    </MetaData>
</InstallFrom>

Hyper-V Generation 2 Windows Server 2019 Datacenter Image

Run hv_win2019_dc.ps1 (Windows)

Windows 2019 Datacenter Generation 2 Prerequisites

For Generation 2 prepare secondary.iso with folder structure:

  • ./extra/files/gen2-2019/dc/Autounattend.xml => /Autounattend.xml
  • ./extra/scripts/hyper-v/bootstrap.ps1 => /bootstrap.ps1

This template uses this image name in Autounattendes.xml. If youre using different ISO you'll have to adjust that part in proper file and rebuild secondary.iso image.

<InstallFrom>
    <MetaData wcm:action="add">
        <Key>/IMAGE/NAME </Key>
        <Value>Windows Server 2019 SERVERDATACENTER</Value>
    </MetaData>
</InstallFrom>

[Experimental] Hyper-V generation 2 Windows Server 2019 Standard Vagrant support

hv_win2019_std_vagrant.ps1

[Experimental] Hyper-V generation 2 Windows Server 2019 Datacenter Vagrant support

hv_win2019_dc_vagrant.ps1

Templates Windows 2016

Hyper-V Generation 2 Windows Server 2016 Standard Image

Run hv_win2016_std.ps1 (Windows)

Windows 2016 Standard Generation 2 Prerequisites

For Generation 2 prepare secondary.iso with folder structure:

  • ./extra/files/gen2-2016/Autounattend.xml => /Autounattend.xml
  • ./extra/scripts/hyper-v/bootstrap.ps1 => /bootstrap.ps1

This template uses this image name in Autounattendes.xml. If youre using different ISO you'll have to adjust that part in proper file and rebuild secondary.iso image.

<InstallFrom>
    <MetaData wcm:action="add">
        <Key>/IMAGE/NAME </Key>
        <Value>Windows Server 2016 SERVERSTANDARD</Value>
    </MetaData>
</InstallFrom>

Templates Ubuntu

Warnings - Ubuntu 20.x

  • if required change switch_name parameter to switch's name you're using. In most situations packer manages it fine but there were a cases when it created new 'internal' switches without access to Internet. By design this setup will fail to download and apply updates.
  • if needed - change iso_url variable to a proper iso name
  • packer generates v8 machine configuration files (Windows 2016/Hyper-V 2016 as host) and v9 for Windows Server 2019/Windows 10 1809
  • credentials for Windows machines: Administrator/password (removed after sysprep)
  • credentials for Linux machines: root/password
  • for Windows based machines adjust your settings in ./scripts/phase-2.ps1
  • for Linux based machines adjust your settings in ./files/gen2-{{os}}/provision.sh and ./files/gen2-{{os}}/puppet.conf

Hyper-V Generation 2 Ubuntu 20.04 Image

Run hv_ubuntu2004.ps1

Hyper-V Generation 2 Ubuntu 22.04 Image

Run hv_ubuntu2204.ps1

Templates RockyLinux 8.x

Warnings - RockyLinux 8

  • if required change switch_name parameter to switch's name you're using. In most situations packer manages it fine but there were a cases when it created new 'internal' switches without access to Internet. By design this setup will fail to download and apply updates.
  • if needed - change iso_url variable to a proper iso name
  • packer generates v8 machine configuration files (Windows 2016/Hyper-V 2016 as host) and v9 for Windows Server 2019/Windows 10 1809
  • credentials for Windows machines: Administrator/password (removed after sysprep)
  • credentials for Linux machines: root/password
  • for Windows based machines adjust your settings in ./scripts/phase-2.ps1
  • for Linux based machines adjust your settings in ./files/gen2-centos/provision.sh and ./files/gen2-centos/puppet.conf

Hyper-V Generation 2 RockyLinux 8.7 Image

Run hv_rockylinux87.ps1

Hyper-V Generation 2 RockyLinux 8.7 Vagrant support

Run hv_rockylinux87_vagrant.ps1 for RockyLinux 8.7

Hyper-V Generation 2 RockyLinux 8.6 image with extra docker volume

Run hv_rockylinux87_docker.ps1 for RockyLinux 8.7

Templates Rocky Linux 9

Warnings - RockyLinux 9

  • if required change switch_name parameter to switch's name you're using. In most situations packer manages it fine but there were a cases when it created new 'internal' switches without access to Internet. By design this setup will fail to download and apply updates.
  • if needed - change iso_url variable to a proper iso name
  • packer generates v8 machine configuration files (Windows 2016/Hyper-V 2016 as host) and v9 for Windows Server 2019/Windows 10 1809
  • credentials for Windows machines: Administrator/password (removed after sysprep)
  • credentials for Linux machines: root/password
  • for Windows based machines adjust your settings in ./scripts/phase-2.ps1
  • for Linux based machines adjust your settings in ./files/gen2-centos/provision.sh and ./files/gen2-centos/puppet.conf

Hyper-V Generation 2 RockyLinux 9.1 Image

Run hv_rockylinux91.ps1

Hyper-V Generation 2 RockyLinux 9.1 Vagrant support

Run hv_rockylinux91_vagrant.ps1 for RockyLinux 9.1

Hyper-V Generation 2 RockyLinux 9.0 image with extra docker volume

Run hv_rockylinux91_docker.ps1 for RockyLinux 9.1

Templates OracleLinux 8.x

Warnings - OracleLinux 8

  • if required change switch_name parameter to switch's name you're using. In most situations packer manages it fine but there were a cases when it created new 'internal' switches without access to Internet. By design this setup will fail to download and apply updates.
  • if needed - change iso_url variable to a proper iso name
  • packer generates v8 machine configuration files (Windows 2016/Hyper-V 2016 as host) and v9 for Windows Server 2019/Windows 10 1809
  • credentials for Windows machines: Administrator/password (removed after sysprep)
  • credentials for Linux machines: root/password
  • for Windows based machines adjust your settings in ./scripts/phase-2.ps1
  • for Linux based machines adjust your settings in ./files/gen2-centos/provision.sh and ./files/gen2-centos/puppet.conf

Hyper-V Generation 2 OracleLinux 8.6 Image

Run hv_oraclelinux86.ps1

Hyper-V Generation 2 OracleLinux 8.6 Vagrant support

Run hv_oraclelinux86_vagrant.ps1 for OracleLinux 8.5

Hyper-V Generation 2 OracleLinux 8.6 image with extra docker volume

Run hv_oraclelinux86_docker.ps1 for OracleLinux 8.6

Templates AlmaLinux 8.x

Warnings - AlmaLinux 8

  • if required change switch_name parameter to switch's name you're using. In most situations packer manages it fine but there were a cases when it created new 'internal' switches without access to Internet. By design this setup will fail to download and apply updates.
  • if needed - change iso_url variable to a proper iso name
  • packer generates v8 machine configuration files (Windows 2016/Hyper-V 2016 as host) and v9 for Windows Server 2019/Windows 10 1809
  • credentials for Windows machines: Administrator/password (removed after sysprep)
  • credentials for Linux machines: root/password
  • for Windows based machines adjust your settings in ./scripts/phase-2.ps1
  • for Linux based machines adjust your settings in ./files/gen2-centos/provision.sh and ./files/gen2-centos/puppet.conf

Hyper-V Generation 2 AlmaLinux 8.6 Image

Run hv_almalinux86.ps1

Hyper-V Generation 2 AlmaLinux 8.6 Vagrant support

Run hv_almalinux86_vagrant.ps1 for AlmaLinux 8.6

Hyper-V Generation 2 AlmaLinux 8.6 image with extra docker volume

Run hv_almalinux86_docker.ps1 for AlmaLinux 8.6

Templates CentOS 7.x

Warnings - CentOS Docker

  • if required change switch_name parameter to switch's name you're using. In most situations packer manages it fine but there were a cases when it created new 'internal' switches without access to Internet. By design this setup will fail to download and apply updates.
  • if needed - change iso_url variable to a proper iso name
  • packer generates v8 machine configuration files (Windows 2016/Hyper-V 2016 as host) and v9 for Windows Server 2019/Windows 10 1809
  • credentials for Windows machines: Administrator/password (removed after sysprep)
  • credentials for Linux machines: root/password
  • for Windows based machines adjust your settings in ./scripts/phase-2.ps1
  • for Linux based machines adjust your settings in ./values/centos7.yml or ./values/centos7_docker.yml
  • no docker repo will be added and no docker-related packages will be installed - this build only creates and mounts separated volume (size specified by variable) for docker

Hyper-V Generation 2 CentOS 7.9

Run hv_centos79.ps1

Hyper-V Generation 2 CentOS 7.9 Image with extra docker volume

Run hv_centos79_docker.ps1

Hyper-V Generation 2 CentOS 7.9 Vagrant support

Run hv_centos79_vagrant.ps1

Known issues

I have general problem not covered here

Please create an issue in github. There is slim chance I'll find the time to be your personal helpdesk ;)

I'd like to contribute

Sure. If I can ask - create your PR in smaller sizes, this is repo used for my work, so smaller changes - bigger chances to succeed.

Infamous UEFI/Secure boot WIndows implementation

During the deployment secure keys are stored in *.vmcx file and are separated from *.vhdx file. To countermeasure it - there is added extra step in a form of (/usr/local/bin/uefi.sh) script that will check for existence of CentOS folder in EFI and will add extra entry in UEFI. In manual setup you can run it as a part of your deploy. In SCVMM deployment I'd recommend using RunOnce feature.

On Windows Server 2019/Windows 10 1809 image boots to fast for packer to react

hashicorp/packer#7278 (comment)

Fixed in version 1.4.4. Do not use previous versions

When Hyper-V host has more than one interface Packer sets {{ .HTTPIP }} variable to inproper interface

Fixed in version 1.4.4. Do not use lower versions No resolution so far, template needs to be changed to pass real IP address, or there should be connection between these addresses. Limiting these, end with timeout errors.**

Packer version 1.3.0/1.3.1 have bug with windows-restart provisioner

hashicorp/packer#6733

Packer won't run until VirtualSwitch is created as shared

hashicorp/packer#5023 Will be fixed in 1.4.x revision

I have problem how to find a proper WIM name in Windows ISO to pick proper version

You can use number. If you have 4 images on the list of choice - use ImageIndex with proper Value

<ImageInstall>
    <OSImage>
        <InstallFrom>
            <MetaData wcm:action="add">
                <Key>/IMAGE/INDEX </Key>
                <Value>2</Value>
            </MetaData>
        </InstallFrom>
        <InstallTo>
            <DiskID>0</DiskID>
            <PartitionID>2</PartitionID>
        </InstallTo>
    </OSImage>
</ImageInstall>

On Windows machines, build break during updates phase, when update cycles are interfering with each other

Increase variable update_timeout in ./variables/*.json file - this will create longer pauses between stages, allowing cycles to complete before jumping to another one.

Why don't you use ansible instead of shell scripts for provisioning

I wish. In short - Windows. These builds should be done with minimum effort (Hyper-V role is enough). Building custom ansible station with lots of checks right now fails in my tryouts.

About

Work based on https://github.com/jacqinthebox/packer-templates.git

More Repositories

1

proxmox-kvm-packer

Proxmox and KVM Templates - Virtual Machines using packer
Shell
35
star
2

linux_mint

Ansible playbook for quick and painless DevOps/SysAdmin workstation, based on Linux Mint 21.x
Dockerfile
17
star
3

graylog

Simple one node Graylog setup with Traefik, Cloudflare/Let's Encrypt, Filebeat GELF/SYSLOG/BEATS support, and GeoIP updates
10
star
4

foreman_exporter

Small Foreman Prometheus exporter using API to ask hosts status
Python
7
star
5

vagrant-boxes

Set of Vagrant Boxes for different OS'es
PowerShell
4
star
6

mvmc

Microsoft Virtual Machine Converter
3
star
7

commvault_exporter

Commvault Backup and Recovery Prometheus Exporter
Python
3
star
8

foreman-template

Small Zabbix template for Foreman (1.16.x) with Grafana Dashboard
Shell
3
star
9

zabbix-agent

Zabbix-agent3 for chocolatey
PowerShell
2
star
10

sslvpn

Fortinet SSL VPN Small client
2
star
11

forticlient

Fortigate's Forticlient chocolatey package
PowerShell
2
star
12

upptime

Upptime monitoring
Markdown
1
star
13

hv_default

Powershell script for default settings in new Hyper-V 2012 R2/2016 instalations
PowerShell
1
star
14

doublecmd

Double Commander for Windows Chocolatey package
PowerShell
1
star
15

dive

Chocolatey package for https://github.com/wagoodman/dive
Shell
1
star
16

macbook-devops

Ansible repository for creating DevOps MacBook
1
star
17

az-packer

Azure set of VM using packer and 'extra' framework
Shell
1
star
18

puppet-manage_haproxy

Wrapper for puppetlabs-haproxy
Ruby
1
star
19

made2010

Microsoft Access Database Engine 2010 Redistributable Chocolatey package
PowerShell
1
star
20

marcinbojko

1
star