The agent fails to start in a rockylinux-9 vm from the images remote.
incus init images:rockylinux/9/cloud test-rockylinux9-vm --vm
incus start test-rockylinux9-vm --console
[...]
Starting Incus - agent...
[ 3.444287] input: QEMU Virtio Keyboard as /devices/pci0000:00/0000:00:01.0/0000:01:00.2/virtio2/input/input5
[ 3.450145] virtio-fs: tag <config> not found
[ 3.451809] /dev/disk/by-id/scsi-0QEMU_QEMU_CD-ROM_incus_agent: Can't open blockdev
[FAILED] Failed to start Incus - agent.
See 'systemctl status incus-agent.service' for details.
I changed the root password by chrooting into the rootfs and restarting the vm.
journalctl prints the following traces:
[root@test-rockylinux9-vm ~]# journalctl -xae -u incus-agent
Mar 03 12:26:02 localhost systemd[1]: Starting Incus - agent...
░░ Subject: A start job for unit incus-agent.service has begun execution
░░ Defined-By: systemd
░░ Support: https://wiki.rockylinux.org/rocky/support
░░
░░ A start job for unit incus-agent.service has begun execution.
░░
░░ The job identifier is 257.
Mar 03 12:26:02 localhost incus-agent-setup[433]: Couldn't mount 9p or cdrom, failing
Mar 03 12:26:02 localhost systemd[1]: incus-agent.service: Control process exited, code=exited, status=1/FAILURE
There is no 9p filesystem in /proc/filesystems and no 9p.ko kernel module.
Is this the reason why the incus-agent fails to start?
Is there a workaround?
Hello,
The agent fails to start in a rockylinux-9 vm from the
images
remote.I changed the root password by chrooting into the rootfs and restarting the vm. journalctl prints the following traces:
There is no 9p filesystem in /proc/filesystems and no 9p.ko kernel module. Is this the reason why the incus-agent fails to start? Is there a workaround?
Thanks!