I was trying to perform GPU passthrough on a virtual machine and it never started… I tried deleting it by using the --force option but no luck. I set up the autostart on boot flag so it doesn’t matter if I reboot the server, the instance will always try to come back and I won’t be able to remove it
It doesn’t matter if I let incus instance delete gaming --force
forever, it won’t delete. The instance won’t start either
There’s no operations too
hypervisor@hypervisor:~$ incus operation ls
+----+------+-------------+-------+------------+---------+
| ID | TYPE | DESCRIPTION | STATE | CANCELABLE | CREATED |
+----+------+-------------+-------+------------+---------+
I also tried incus config set game-server boot.autostart=false
but it is also stuck forever
journalctl doesn’t show anything useful
May 01 23:29:50 hypervisor systemd[1]: Starting incus.service - Incus - Main daemon...
░░ Subject: A start job for unit incus.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit incus.service has begun execution.
░░
░░ The job identifier is 643.
May 01 23:29:50 hypervisor startup[2780]: time="2025-05-01T23:29:50-05:00" level=warning msg="AppArmor support has been disabled because of lack of kernel support"
May 01 23:29:50 hypervisor startup[2780]: time="2025-05-01T23:29:50-05:00" level=warning msg=" - AppArmor support has been disabled, Disabled because of lack of kernel support"
May 01 23:29:56 hypervisor startup[2780]: time="2025-05-01T23:29:56-05:00" level=warning msg="Unable to use virtio-fs for device, using 9p as a fallback" device=data driver=disk err="Virtiofsd missing" instance=gaming project=default
May 01 23:29:56 hypervisor startup[2780]: time="2025-05-01T23:29:56-05:00" level=warning msg="Unable to use virtio-fs for device, using 9p as a fallback" device=library driver=disk err="Virtiofsd missing" instance=gaming project=default
Here’s the instance config
architecture: x86_64
config:
boot.autostart: "true"
cloud-init.user-data: <hidden>
limits.cpu: "2"
limits.memory: 8GiB
security.nesting: "true"
volatile.cloud-init.instance-id: a3903009-f568-489a-8cd6-9791dfc00cf7
volatile.eth0.host_name: tap4db9ef03
volatile.eth0.hwaddr: 10:66:6a:53:66:02
volatile.eth0.last_state.ip_addresses: 10.0.8.13,fd42:6111:b330:eb74:1266:6aff:fe53:6602
volatile.gpu.last_state.pci.driver: amdgpu
volatile.gpu.last_state.pci.slot.name: "0000:01:00.0"
volatile.last_state.power: RUNNING
volatile.uuid: 1c65d753-7ea8-4ad8-8890-1dd8e005cff1
volatile.uuid.generation: 1c65d753-7ea8-4ad8-8890-1dd8e005cff1
volatile.vm.definition: pc-q35-9.2
volatile.vsock_id: "331660789"
devices:
data:
path: /home
pool: virt-main
source: gaming-data
type: disk
eth0:
ipv4.address: 10.0.8.13
network: untrusted
security.acls: gaming-svc
type: nic
gpu:
pci: "01:00.0"
type: gpu
library:
path: /library
pool: virt-spin0
source: gaming-library
type: disk
root:
path: /
pool: virt-main
type: disk
ephemeral: false
profiles:
- default
stateful: false
description: ""
How can I force delete this instance?