Thank you for your time. I have deleted all but the 1st snapshot and the VM does now start. Output from 3 commands provided below. When I created the VM I allowed 80GiB.
$ sudo zfs list -t all
NAME USED AVAIL REFER MOUNTPOINT
default 25.8G 2.81G 24K legacy
default/buckets 24K 2.81G 24K legacy
default/containers 24K 2.81G 24K legacy
default/custom 24K 2.81G 24K legacy
default/deleted 144K 2.81G 24K legacy
default/deleted/buckets 24K 2.81G 24K legacy
default/deleted/containers 24K 2.81G 24K legacy
default/deleted/custom 24K 2.81G 24K legacy
default/deleted/images 24K 2.81G 24K legacy
default/deleted/virtual-machines 24K 2.81G 24K legacy
default/images 24K 2.81G 24K legacy
default/virtual-machines 25.7G 2.81G 24K legacy
default/virtual-machines/win11d 7.73M 192M 63.5K legacy
default/virtual-machines/win11d@snapshot-clean_install 7.67M - 7.68M -
default/virtual-machines/win11d.block 25.7G 2.81G 22.3G -
default/virtual-machines/win11d.block@snapshot-clean_install 3.47G - 16.0G -
$ lxc storage info default
info:
description: ""
driver: zfs
name: default
space used: 25.77GiB
total space: 28.58GiB
used by:
instances:
- win11d
profiles:
- default
$ lxc config show win11d --expanded
architecture: x86_64
config:
limits.cpu: "4"
limits.memory: 8GiB
volatile.cloud-init.instance-id: 800ceedf-7c56-409d-b03a-f0a1fcece579
volatile.eth0.host_name: tapea63755d
volatile.eth0.hwaddr: 00:16:3e:67:83:8d
volatile.last_state.power: RUNNING
volatile.uuid: 9fb7e78f-3746-42c1-ac14-d4975f9f05c0
volatile.uuid.generation: 8f7a7c84-9c30-4847-b17b-3d0f05862fad
volatile.vsock_id: "2881689457"
devices:
eth0:
name: eth0
network: lxdbr0
type: nic
root:
path: /
pool: default
size: 80GiB
size.state: 200MiB
type: disk
vtpm:
path: /dev/tpm0
type: tpm
ephemeral: false
profiles:
- default
stateful: false
description: ""