This builds an up-to-date Proxmox VE Vagrant Base Box.

Currently this targets Proxmox VE 7.

Create the base box as described in the section corresponding to your provider.

If you want to troubleshoot the packer execution see the .log file that is created in the current directory.

After the example vagrant enviroment is started, you can access the Proxmox Web Interface with the default root user and password vagrant.

For a cluster example see rgl/proxmox-ve-cluster-vagrant.

Create the base box:

make build-libvirt # or build-virtualbox

Add the base box as suggested in make output:

vagrant box add -f proxmox-ve-amd64 proxmox-ve-amd64-libvirt.box # or proxmox-ve-amd64-virtualbox.box

Start the example vagrant environment with:

cd example
vagrant up --no-destroy-on-error --provider=libvirt # or --provider=virtualbox

Follow the rgl/debian-vagrant Hyper-V Usage section.

Create a vSwitch for proxmox:

PowerShell -NoLogo -NoProfile -ExecutionPolicy Bypass <<'EOF'
$switchName = 'proxmox'
$networkAdapterName = "vEthernet ($switchName)"
$networkAdapterIpAddress = '10.10.10.1'
$networkAdapterIpPrefixLength = 24

# create the vSwitch.
New-VMSwitch -Name $switchName -SwitchType Internal | Out-Null

# assign it an host IP address.
$networkAdapter = Get-NetAdapter $networkAdapterName
$networkAdapter | New-NetIPAddress `
    -IPAddress $networkAdapterIpAddress `
    -PrefixLength $networkAdapterIpPrefixLength `
    | Out-Null

# remove all virtual switches from the windows firewall.
Set-NetFirewallProfile `
    -DisabledInterfaceAliases (
            Get-NetAdapter -name "vEthernet*" | Where-Object {$_.ifIndex}
        ).InterfaceAlias
EOF

Create the base box:

make build-hyperv

Add the base box as suggested in make output:

vagrant box add -f proxmox-ve-amd64 proxmox-ve-amd64-hyperv.box

Start the example vagrant environment with:

cd example
vagrant up --provider=hyperv

To improve the build performance you can use the following options.

To speed up package downloads, you can specify an apt caching proxy (e.g. apt-cacher-ng) by defining the environment variables APT_CACHE_HOST (default: undefined) and APT_CACHE_PORT (default: 3124).

Example:

APT_CACHE_HOST=10.10.10.100 make build-libvirt

To decrease disk wear (and potentially reduce io times), you can use /dev/shm (temporary memory file-system) as output_directory for Packer builders. Your system must have enough available memory to store the created virtual machine.

Example:

PACKER_OUTPUT_BASE_DIR=/dev/shm make build-libvirt

Remember to also define PACKER_OUTPUT_BASE_DIR when you run make clean afterwards.

Some properties of the virtual machine and the Proxmox VE installation can be overridden. Take a look at proxmox-ve.json, object variables, to get an idea which values can be overridden. Do not override iso_url and iso_checksum as the boot_commands might be tied to a specific Proxmox VE version. Also take care when you decide to override country.

Create the base box:

make build-libvirt VAR_FILE=example.vars.json  # or build-virtualbox or build-hyperv

The following content of example.vars.json:

• sets the initial disk size to 128 GB

• sets the initial memory to 4 GB

• sets the Packer output base directory to /dev/shm

• sets the country to Germany (timezone is updated by Proxmox VE installer) and changes the keyboard layout back to "U.S. English" as this is needed for the subsequent boot_command statements

• sets the hostname to pve-test.example.local

• uses all default shell provisioners (see ./provisioners) and a custom one for german localisation

  {
      "disk_size": "131072",
      "memory": "4096",
      "output_base_dir": "/dev/shm",
      "step_country": "Ger<wait>m<wait>a<wait>n<wait><enter>",
      "step_hostname": "pve-test.example.local",
      "step_keyboard_layout": "<end><up><wait>",
      "shell_provisioner_scripts": "provisioners/apt_proxy.sh,provisioners/upgrade.sh,provisioners/network.sh,localisation-de.sh,provisioners/reboot.sh,provisioners/provision.sh"
  }

As Proxmox does not have any way to be pre-seeded, this environment has to answer all the installer questions through the packer boot_command interface. This is quite fragile, so be aware when you change anything. The following table describes the current steps and corresponding answers.

NB Do not change the keyboard layout. If you do, the email address will fail to be typed.