Bottlerocket on Proxmox isn’t officially supported, but you can boot it by attaching a config drive with user-data. The official docs only cover VMware and cloud, so here’s the QEMU command that worked for me.

Grab the Bottlerocket image
Download the KVM image from the Bottlerocket releases page. You want the aws-k8s-1.24 variant or similar, not the VMware OVA. The file ends in .img.lz4.
Decompress it with lz4 -d bottlerocket-aws-k8s-1.24-x86_64.img.lz4. That gives you a raw disk image.
Create the VM in Proxmox
Create a new VM without any OS. Set the machine type to q35 and add a UEFI disk. Import the raw image as the main disk:
qm importdisk 100 bottlerocket-aws-k8s-1.24-x86_64.img local-lvm
Attach it as SCSI, then add a cloud-init drive. Proxmox will generate a config drive from the cloud-init settings.

Set the user-data
Bottlerocket expects TOML for user-data, not YAML. In the Proxmox cloud-init tab, put something like this in the custom user-data field:
[settings.kubernetes]
cluster-name = "proxmox-cluster"
api-server = "https://10.0.0.10:6443"
node-labels = { "role" = "worker" }
Set the network config to DHCP or static as needed. The config drive will be attached as a second CD-ROM.
Boot and troubleshoot
Start the VM. If it hangs at Booting Bottlerocket, check the serial console. You might need to add console=ttyS0 to the kernel args in the VM options.
Bottlerocket doesn’t have SSH by default. You interact through the control container or the admin container. To enable the admin container, add this to user-data:
[settings.host-containers.admin]
enabled = true
superpowered = true
Then you can apiclient exec admin bash from the host. The logs are in /var/log/bottlerocket.
My take
It’s doable but fiddly. The cloud-init drive is the key—without it, Bottlerocket just sits there. If you want a minimal container OS on Proxmox, Fedora CoreOS with Ignition is less of a fight. But for Bottlerocket’s security model, it’s worth the effort.