Disk size mismatch

[diablinux]

I am using the latest version 0.9.4 to create VMs.
This is the terraform code snippet.
From main.tf module

resource "libvirt_volume" "vm_disk" {
  for_each = toset(var.vm_names)
  name     = "${each.key}-disk.qcow2"
  pool     = "default"

  target   = { format = { type = "qcow2" } }
  capacity = var.disk_size

  create = {
    content = {
      url = local.vm_image_paths[each.key]
    }
  }
}

From main.tf I am specifying a 40GB disk

disk_size = 40 * 1024 * 1024 * 1024

After terraform apply: ssh into the vm:

core@ubuntu:~$ sudo su -
root@ubuntu:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           392M  5.9M  386M   2% /run
/dev/vda1       2.4G  1.9G  500M  80% /
tmpfs           2.0G     0  2.0G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/vda16      881M   64M  756M   8% /boot
/dev/vda15      105M  6.2M   99M   6% /boot/efi
tmpfs           392M   12K  392M   1% /run/user/1000
root@ubuntu:~# fdisk -l
GPT PMBR size mismatch (7340031 != 20971519) will be corrected by write.
The backup GPT table is not on the end of the device.
Disk /dev/vda: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 2927B9F0-3C3C-42B2-A1BE-106306237EC4

Device       Start     End Sectors  Size Type
/dev/vda1  2099200 7339998 5240799  2.5G Linux filesystem
/dev/vda14    2048   10239    8192    4M BIOS boot
/dev/vda15   10240  227327  217088  106M EFI System
/dev/vda16  227328 2097152 1869825  913M Linux extended boot

Disk /dev/vda: 10 GiB

Terraform plan snippet:

# module.vms_cluster.libvirt_volume.vm_disk["worker03"] will be created
  + resource "libvirt_volume" "vm_disk" {
      + allocation = (known after apply)
      + capacity   = 42949672960
      + create     = {
          + content = {
              + url = "/home/acabrera/libvirt/images/ubuntu-base.qcow2"
            }
        }
      + id         = (known after apply)
      + key        = (known after apply)
      + name       = "worker03-disk.qcow2"
      + path       = (known after apply)
      + physical   = (known after apply)
      + pool       = "default"
      + target     = {
          + format = {
              + type = "qcow2"
            }
          + path   = (known after apply)
        }

}

But, when I create the VM with virt-install (using the same source image) I got the 40 GB disk.

$ virt-install -n worker03 --ram 4096 --os-variant=ubuntu24.04  --disk=size=40,backing_store="/home/acabrera/libvirt/images/ubuntu-base.qcow2" --vcpus=4 --noautoconsole --import --network bridge=nm-bridge,model=virtio

Starting install...
Allocating 'worker03.qcow2' |  40 GB  00:00:00
Creating domain...                  |         00:00:00
Domain creation completed.
acabrera@server:~$ virsh list --all
 Id   Name             State
--------------------------------
 14   worker03         running

acabrera@server:~$ virsh console worker03
Connected to domain 'worker03'
Escape character is ^] (Ctrl + ])

ubuntu login: core
Password:

core@ubuntu:~$ sudo su -
root@ubuntu:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           392M  6.0M  386M   2% /run
/dev/vda1       2.4G  1.9G  500M  80% /
tmpfs           2.0G     0  2.0G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/vda16      881M   64M  756M   8% /boot
/dev/vda15      105M  6.2M   99M   6% /boot/efi
tmpfs           392M   12K  392M   1% /run/user/1000

root@ubuntu:~# fdisk -l
GPT PMBR size mismatch (7340031 != 83886079) will be corrected by write.
The backup GPT table is not on the end of the device.
Disk /dev/vda: 40 GiB, 42949672960 bytes, 83886080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 2927B9F0-3C3C-42B2-A1BE-106306237EC4

Device       Start     End Sectors  Size Type
/dev/vda1  2099200 7339998 5240799  2.5G Linux filesystem
/dev/vda14    2048   10239    8192    4M BIOS boot
/dev/vda15   10240  227327  217088  106M EFI System
/dev/vda16  227328 2097152 1869825  913M Linux extended boot

Partition table entries are not in disk order.
root@ubuntu:~#

What am I missing here?