I run opnsense as a vm to use excess resources for hosting light services, this means until the vm has booted there is no network, but when booting IncusOS with this setup i get the following error:
if i reboot with regular non-vm hosted network it boots fine, and once booted the vm also starts without issue.
also: what is the correct method for nic passthrough on IncusOS, i added the following to opnsense yaml and it works but i’m unsure if it’s adding an extra layer between the nic and vm. on proxmox you would pass all functions of the nic pci id
devices:
nic-0:
nictype: physical
parent: enp1s0f0
type: nic
nic-1:
nictype: physical
parent: enp1s0f1
type: nic
nic-2:
nictype: physical
parent: enp1s0f2
type: nic
nic-3:
nictype: physical
parent: enp1s0f3
type: nic
Addressing the first part of your post, are you running opnsense as a VM hosted on IncusOS? I know a few people have experimented with that sort of a setup; this might be a good opportunity to improve that particular use case. We have support for a similar setup when IncusOS self-hosts Operations Center, but nothing generic to indicate that IncusOS should delay update checks for a specific duration or until some network endpoint becomes reachable.
The error you’re seeing is an update check error, which shouldn’t actually prevent IncusOS from starting up and becoming available. I tested booting one of my physical IncusOS machines with its ethernet cable unplugged; I see a similar error and then further message as Incus starts and IncusOS completes startup.
If routing for network access to IncusOS requires going through your opnsense VM, you may want to enable boot.autostart in the VM’s configuration (see Instance options - Incus documentation ).