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

Currently this targets Proxmox VE 7.0.

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

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 $adapterName
$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

Start the example vagrant environment with:

cd example
vagrant up --provider=hyperv

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.