Bug#1111240: cloud.debian.org: generic trixie amd64 qcow2 image unable to boot

[allddd <me@allddd.onl>]

The options you see in the log are mostly defaults, the config I use is prettybare-bones. I copy the qcow2 image from the cache to the designated folder,
resize it, and use the Ansible Jinja2 template below to define the VM:

# --- #
<domain type='kvm'>

  <name>{{ vm_num }}</name>
  <title>{{ vm_fqdn }}</title>
  <os>
    <type>hvm</type>
    <boot dev='hd'/>
  </os>
  <pm>
    <suspend-to-mem enabled='no'/>
    <suspend-to-disk enabled='no'/>
  </pm>
  <features>
    <acpi/>
  </features>

  <!-- cpu -->
  <vcpu>{{ vm_cpu }}</vcpu>

  <!-- ram -->
  <memory unit='GiB'>{{ vm_ram }}</memory>
  <currentMemory unit='GiB'>{{ vm_ram }}</currentMemory>

  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>

    <!-- image -->>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source file='{{ vm_dir }}/{{ vm_num }}/{{ vm_img }}'/>
      <target dev='vda' bus='virtio'/>
    </disk>

    <!-- cloud-init -->>
    <disk type="file" device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='{{ vm_cloudinit_data }}'/>
      <target dev='vdb' bus='sata'/>
      <readonly/>
    </disk>

    <!-- network -->>
    <interface type='bridge'>
      <mac address='{{ vm_mac }}'/>
      <source bridge='br0'/>
      <target dev='vmif{{ vm_num }}'/>
      <model type='virtio'/>
    </interface>

    <!-- console -->>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>

    <!-- guest-agent -->>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
    </channel>

  </devices>
</domain>
# --- #

Once the VM is defined, I enable autostart, start the VM, and wait until it’s
reachable.


18 Aug 2025, 00:14 by noahm@debian.org:

> Control: tags -1 + moreinfo
>
> On Sat, Aug 16, 2025 at 02:42:24AM +0200, allddd wrote:
>
>>
>> I’m deploying cloud images on a Libvirt/QEMU/KVM hypervisor using Ansible. After trixie hit stable, I replaced the bookworm image with a trixie one, but I am unable to get it to boot. The only change in the deployment process was switching from debian-12-generic-amd64.qcow2 to debian-13-generic-amd64.qcow2.
>> The process seems to hang during boot, and no errors are printed anywhere. I’m able to connect to the VM using virsh console, but I only see the first line "Booting Debian GNU/Linux" and nothing further happens.
>>
>
> Can you share more about your ansible and/or libvirt configuration that
> you're using to launch this VM?  I have no trouble launching VMs from
> our trixie images, but you've got a whole bunch of extra configuration
> passed by libvirt that I'm not using.  I suspect the issue is in there
> somewhere.
>
> noah
>