I have recently been creating Windows Server 2019 VMs from an image. However, due to testing purposes I had to delete the Windows VM image from LXD and import it again, after which I have not been able to iniate a VM with the same image:
Fingerprint: cee305252934f842b4d9422ba378221bde8e893d35e1a62c40269823ec9b963c
Size: 5357.71MB
Architecture: x86_64
Type: virtual-machine
Public: no
Timestamps:
Created: 2020/11/10 12:04 UTC
Uploaded: 2020/11/24 18:52 UTC
Expires: never
Last used: 2020/11/24 18:52 UTC
Properties:
Aliases:
- wserver19
Cached: no
Auto update: disabled
Profiles:
- default
config: {}
description: Profile to be used when creating container instances through the UI.
devices:
eth0:
name: eth0
nictype: bridged
parent: br0
type: nic
root:
path: /
pool: lxd-pool
type: disk
name: bridge
used_by: []
Ah I know what this is, its an issue related to the new reference counting for mounts, and for ZFS the protection we added to prevent resizing image volumes, but in the case of unpacking images into initial image volumes we need to allow unrestricted resizing of volumes by the unpacker. I’ll add a fix.
You can run the edge snap, although please note that due to a schema change between edge and LXD 4.8 you won’t be able to downgrade until the next release, so be sure to run this on a separate system when testing. I think @stgraber will cherry-pick this fix into the LXD 4.8 snap version soon anyway.