Error starting VM: start failed: QEMU exited with code 1 about boilerplates HOT 8 CLOSED

For me, this looks like an issue with starting the VM.
Can you check the following?

• Proxmox Logs
• Packer Debug logs, as described by @andrei-matei

from boilerplates.

Totally missed the reply to this. Sorry!

All resolved, there were some issues in choose q35 machine type.

I'll post my new config at some point once I get it working as I've managed to do away with the defined SSH key

from boilerplates.

Are your storage pools named "Proxmox"? They are usually called local-lvm if it's a basic install and you have no share storage.
Also, maybe you can try to use disk format raw instead of qcow2. I had issues with that.

from boilerplates.

Are your storage pools named "Proxmox"? They are usually called local-lvm if it's a basic install and you have no share storage. Also, maybe you can try to use disk format raw instead of qcow2. I had issues with that.

Aye, the storage pool is "Proxmox" (not very creative I know :P) - it's a single disk, not shared storage:

Hmmm, raw has its issues tbf, qcow is far more preferable due to the additional abilities it has.

Now, the only caveat I can see on my setup, is that I'm not running packer on the Proxmox install, but inside a VM as I'm not really looking to bog down the Proxmox install with other tools not directly related to it.

from boilerplates.

Hmm, the other part of the file looks the same as mine and they are fairly simple. What version of Proxmox do you use? I have 7.2-11.

packer build -debug -var-file=../credentials.pkr.hcl ubuntu-server-jammy.pkr.hcl

Maybe try to add -debug after Packer build and see if you can get more info.

Best ,
Andrei

from boilerplates.

I just added the network part as it seems qemu-guest-agent fails to install without it. And the disk config. But I guess that should not create those issues.

#cloud-config
autoinstall:
  version: 1
  locale: en_US
  keyboard:
    layout: en
  network:
    version: 2
    ethernets:
      ens18:
        dhcp4: true
  ssh:
    install-server: true
    allow-pw: false
    disable_root: true
    ssh_quiet_keygen: true
    allow_public_ssh_keys: true
  packages:
    - curl
    - qemu-guest-agent
    - sudo
  storage:
    swap:
      size: 0
    config:
      - {ptable: gpt, path: /dev/vda, preserve: false, name: '', grub_device: true, type: disk, id: disk-vda}
      - {type: partition, number: 1, device: disk-vda, flag: bios_grub, size: 1M, id: vda-grub}
      - {type: partition, number: 2, device: disk-vda, flag: boot, size: 1G, id: vda-boot}
      - {type: partition, number: 3, device: disk-vda, size: -1, id: vda-lvm}
      - {type: lvm_volgroup, name: vg-ubuntu, devices: [vda-lvm], id: vg-ubuntu}
      - {type: lvm_partition, volgroup: vg-ubuntu, id: lv-root, name: lv-root, size: -1}
      - {type: format, fstype: ext4, volume: vda-boot, id: vda-boot-fs}
      - {type: format, fstype: xfs, volume: lv-root, id: lv-root-fs}
      - {type: mount, path: /, id: m-root, device: lv-root-fs}
      - {type: mount, path: /boot, id: m-boot, device: vda-boot-fs}
  user-data:
    package_upgrade: true
    timezone: Europe/Bucharest
    users:
      - name: devops
        groups: [adm, sudo]
        lock-passwd: false
        sudo: ALL=(ALL) NOPASSWD:ALL
        shell: /bin/bash
        #passwd: myPass
        ssh_authorized_keys:
          - myPublicKey

from boilerplates.

I just added the network part as it seems qemu-guest-agent fails to install without it. And the disk config. But I guess that should not create those issues.

Cheers for the config! I'll give it a whirl. I'm on 7.2-11 btw, same as yourself.

Hmmm, I'm wondering if the issue is to do with the authorised keys part on my end, will give that a try as well.

The debug just shows:

Debug mode enabled. Builds will not be parallelized.
ubuntu-server-jammy.proxmox.ubuntu-server-jammy: output will be in this color.

==> ubuntu-server-jammy.proxmox.ubuntu-server-jammy: Pausing after run of step 'StepDownload'. Press enter to continue.
==> ubuntu-server-jammy.proxmox.ubuntu-server-jammy: Pausing after run of step 'stepUploadISO'. Press enter to continue.

==> ubuntu-server-jammy.proxmox.ubuntu-server-jammy: Creating VM
==> ubuntu-server-jammy.proxmox.ubuntu-server-jammy: Starting VM
==> ubuntu-server-jammy.proxmox.ubuntu-server-jammy: Error starting VM: start failed: QEMU exited with code 1
==> ubuntu-server-jammy.proxmox.ubuntu-server-jammy: Stopping VM
==> ubuntu-server-jammy.proxmox.ubuntu-server-jammy: Deleting VM
==> ubuntu-server-jammy.proxmox.ubuntu-server-jammy: Pausing before cleanup of step 'stepUploadISO'. Press enter to continue.

So it looks like the VM is created, starts, then Proxmox comes up with the errors:

Nov 12 01:44:16 proxmox pvedaemon[366147]: start failed: QEMU exited with code 1
Nov 12 01:44:16 proxmox pvedaemon[2060577]: <packer@pve!packer> end task UPID:proxmox:00059643:0B5B9B7B:636EFA6F:qmstart:100:packer@pve!packer: start failed: QEMU exited with code 1
Nov 12 01:44:21 proxmox pvedaemon[366182]: start failed: QEMU exited with code 1
Nov 12 01:44:21 proxmox pvestatd[2060612]: VM 100 qmp command failed - VM 100 not running
Nov 12 01:44:21 proxmox pvedaemon[2060578]: <packer@pve!packer> end task UPID:proxmox:00059666:0B5B9D38:636EFA73:qmstart:100:packer@pve!packer: start failed: QEMU exited with code 1
Nov 12 01:44:25 proxmox pvedaemon[366237]: start failed: QEMU exited with code 1
Nov 12 01:44:25 proxmox pvedaemon[2060578]: <packer@pve!packer> end task UPID:proxmox:0005969D:0B5B9ECC:636EFA77:qmstart:100:packer@pve!packer: start failed: QEMU exited with code 1

from boilerplates.

Issue gone cold

from boilerplates.