Local image identification problem

[BurlyLuo]

hello:
there is an issue about the local image.
with

[root@rowan> 01-vpp-testbed]# kcli version 
version: 99.0 commit: 97b2bd3 2024/12/10 Available Updates: True

if create a file at: /var/lib/libvirt/images. the image will shown at: kcli list image

[root@rowan> images]# touch test_cx_image_xxxxxx
[root@rowan> images]# kcli list image| grep test_cx_image_xxxxxx
| /var/lib/libvirt/images/test_cx_image_xxxxxx                               |
[root@rowan> images]# 

but with: 1f45ada

root@vm0:/var/lib/libvirt/images# kcli version 
version: 99.0 commit: 1f45ada 2025/04/13 Available Updates: False
root@vm0:/var/lib/libvirt/images# 

the great feature seems not support.
would you pls revert this func due to, if there is a self-image. we can use kcli tools to setup a vm quickly.
As you know, not all the official image can support all the packages, if we install the image and then export as a shel-image. it should be a great func.
Thanks.

[BurlyLuo]

seems if the image is export with kcli. it can be control by kcli.

root@vm:/var/lib/libvirt/images# history | grep export
  126  kcli export vm vppu

root@vm:/var/lib/libvirt/images# kcli list image 
+------------------------------------------------------------------+
| Images                                                           |
+------------------------------------------------------------------+
| /root/snap                                                       |
| /var/lib/libvirt/images/1.qcow2                                  |
| /var/lib/libvirt/images/cc                                       |
| /var/lib/libvirt/images/ubuntu-22.04-server-cloudimg-amd64.qcow2 |
| /var/lib/libvirt/images/vppu.qcow2                               |
+------------------------------------------------------------------+

so we need load a fresh image with

virt-install --name vppu --memory=2048 --vcpus=2 --disk /var/lib/libvirt/images/ubuntu-22.04-server-cloudimg-amd64.img,device=disk,bus=virtio --disk size=20 --os-variant ubuntu22.04 --virt-type kvm --graphics none --network=bridge=virbr0,model=virtio --import

and then use kcli export vm -h
and them the image can be re-used by kcli

so. my suggestion is: if all the image can be aware. it's great.