Is not seeing CPU usage on VM creation a bug?

I’m installing debian-13 on a VM from the debian Iso to incus (version 7.3) but as it’s installing I notice that incus doesn’t show CPU usage. See incus list below with some data redacted. The VM that’s installing right now is r7-vm and it’s loading from the iso (now at the step “Select and install software”)

+-----------+--------------+---------------+------------------+---------+-----------------------
| CPU USAGE | MEMORY USAGE | MEMORY USAGE% | NAME  |  STATE  |  IPV4      |        MAC         |
+-----------+--------------+---------------+------------------+---------+-----------------------
| 6412s     | 319.64MiB    |               | r1    | RUNNING | redacted   |  10:66:redacted    |
+-----------+--------------+---------------+------------------+---------+-----------------------
| 49364s    | 449.05MiB    |               | r2    | RUNNING | redacted   |  00:16:redacted    | 
+-----------+--------------+---------------+------------------+---------+-----------------------
| 69353s    | 928.91MiB    |               | r3    | RUNNING | redacted   |  00:16:redacted    | 
+-----------+--------------+---------------+------------------+---------+-----------------------
| 408459s   | 6.90GiB      |               | r4    | RUNNING | redacted   |  10:66:redacted    | 
+-----------+--------------+---------------+------------------+---------+-----------------------
| 2929833s  | 39.08GiB     |               | r5    | RUNNING | redacted   |  10:66:redacted    | 
+-----------+--------------+---------------+------------------+---------+-----------------------
| 7335507s  | 18.91GiB     | 78.8%         | r6-vm | RUNNING | redacted   |  10:66:redacted    |          
+-----------+--------------+---------------+------------------+---------+-----------------------
|           | 4.25GiB      | 53.1%         | r7-vm | RUNNING |            |  10:66:redacted    |
+-----------+--------------+---------------+------------------+---------+-----------------------

Should this be created as an issue in github?

Here’s the YAML configuration

architecture: x86_64
config:
  limits.cpu: '2'
  limits.memory: 8GiB
  volatile.cloud-init.instance-id: 1924566e-e444-4cdc-a3e4-e62cfaebd262
  volatile.eth0.host_name: tap4ec5127b
  volatile.eth0.hwaddr: 10:66:redacted
  volatile.iso-vol-1.io.bus: usb
  volatile.last_state.power: RUNNING
  volatile.uuid: 9f-redacted
  volatile.uuid.generation: 9f-redacted
  volatile.vm.needs_reset: 'true'
  volatile.vm.rtc_adjustment: '0'
  volatile.vm.rtc_offset: '-1'
  volatile.vsock_id: '1607561249'
devices:
  iso-vol-1:
    boot.priority: '10'
    io.bus: usb
    pool: default
    source: debian-13.6.0-amd64-netinst.iso
    type: disk
ephemeral: false
profiles:
  - default
  - bridge192
  - defaultDisk
stateful: false
description: Debian GUI for wine
created_at: '2026-08-11T04:37:54.873103142Z'
name: r7-vm
status: Running
status_code: 103
last_used_at: '2026-08-11T04:58:21.166929362Z'
location: none
type: virtual-machine
project: default

Expanded inherited values

devices:
  eth0: # inherited from profile: bridge192
    nictype: bridged
    parent: br0
    type: nic
  iso-vol-1:
    boot.priority: '10'
    io.bus: usb
    pool: default
    source: debian-13.6.0-amd64-netinst.iso
    type: disk
  root: # inherited from profile: defaultDisk
    path: /
    pool: default
    type: disk

Do you have the Incus agent running in the VM? (as in, does incus exec NAME bash work?

Nope.

$ incus exec r7-vm bash --
Error: VM agent isn't currently running

I used the GUI (:8443) for creating the VM and attaching the iso for booting, if that’s helpful for this question.

Update: I installed the agent after installation was complete

$ sudo su - 
# mkdir /run/incus_agent
# mount -t 9p config /run/incus_agent
# cd /run/incus_agent
# ./install.sh
# umount /run/incus_agent
# systemctl start incus-agent

and got CPU usage ( and IP address) info back into incus list

but was wondering if that was something that should be part of the iso installation?

I don’t understand. You used a clean Debian ISO to install your VM, how could that possibly include the Incus agent?

We have the agent loader pre-installed in all the images we publish, but if you’re installing something by hand from an outside source, there’s not much we can do :slight_smile:

Incus provides helpers to make it easy to install the agent into a VM: