Unable to Set volatile.vsock_id for LXD VM

[Gio2241]

LXD Version - 5.14
System: Ubuntu 22.04.2 LTS

I'm not able to set vsock_id for a VM.

Reproduce:

1. lxc init images:ubuntu/jammy machine --vm
2. lxc config set machine volatile.vsock_id=50
3. lxc config show machine --expanded

architecture: x86_64
config:
  image.architecture: amd64
  image.description: Ubuntu jammy amd64 (20230529_07:43)
  image.os: Ubuntu
  image.release: jammy
  image.serial: "20230529_07:43"
  image.type: disk-kvm.img
  image.variant: default
  volatile.apply_template: create
  volatile.base_image: d4443a83a55fbdfb4a87acc5a921fb999876a4a618fc46195f41f6bdaeb75aa2
  volatile.cloud-init.instance-id: 4c73fe89-28e9-496e-b4ef-4c5ee99bb52d
  volatile.eth0.hwaddr: 00:16:3e:5f:9c:0e
  volatile.uuid: cf0eba4d-3294-46a7-8df9-f55807eb4553
  volatile.uuid.generation: cf0eba4d-3294-46a7-8df9-f55807eb4553
  volatile.vsock_id: "50" <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

4. lxc start machine
5. lxc config show machine --expanded

architecture: x86_64
config:
  image.architecture: amd64
  image.description: Ubuntu jammy amd64 (20230529_07:43)
  image.os: Ubuntu
  image.release: jammy
  image.serial: "20230529_07:43"
  image.type: disk-kvm.img
  image.variant: default
  volatile.base_image: d4443a83a55fbdfb4a87acc5a921fb999876a4a618fc46195f41f6bdaeb75aa2
  volatile.cloud-init.instance-id: 4c73fe89-28e9-496e-b4ef-4c5ee99bb52d
  volatile.eth0.host_name: tap7f4041e0
  volatile.eth0.hwaddr: 00:16:3e:5f:9c:0e
  volatile.last_state.power: RUNNING
  volatile.uuid: cf0eba4d-3294-46a7-8df9-f55807eb4553
  volatile.uuid.generation: cf0eba4d-3294-46a7-8df9-f55807eb4553
  volatile.vsock_id: "22" <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Here 22 is just the next id, if we try it again it well be 23, etc. but not 50.

Am I doing something wrong?

[stgraber]

volatile keys aren't meant for end users to modify. In this case, it's always computed and stored on VM startup.

[stgraber]

Note that we have #11508 to handle what may be the source of your issue.

[Gio2241]

Note that we have #11508 to handle what may be the source of your issue.

So, there is no way to set it manually?
At least before you fix the issue?

[stgraber]

Correct, it's assigned by LXD at startup time and is only stored in a volatile config key for LXD's own use while the VM is running.