32fd88726b
While switching NixOS configurations with both networking.useNetworkd = true; virtualisation.virtualbox.host.enable; You often end up waiting for systemd-networkd-wait-online.service. This happens because the vboxnet0 device doesn't have a carrier until virtualbox machines are started, so networkd gets stuck in "Configuring": ⇒ networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 wlp2s0 wlan routable unmanaged 3 vboxnet0 ether no-carrier configuring This updates the NixOS virtualbox host module to include a RequiredForOnline=no statement in the generated 40-vboxnet0.network file, so networkd doesn't consider it necessary for systemd-networkd-wait-online.service to finish. |
||
|---|---|---|
| .. | ||
| amazon-image.nix | ||
| amazon-init.nix | ||
| amazon-options.nix | ||
| anbox.nix | ||
| azure-agent-entropy.patch | ||
| azure-agent.nix | ||
| azure-bootstrap-blobs.nix | ||
| azure-common.nix | ||
| azure-config-user.nix | ||
| azure-config.nix | ||
| azure-image.nix | ||
| azure-images.nix | ||
| brightbox-config.nix | ||
| brightbox-image.nix | ||
| cloudstack-config.nix | ||
| container-config.nix | ||
| containers.nix | ||
| cri-o.nix | ||
| docker-containers.nix | ||
| docker-image.nix | ||
| docker-preloader.nix | ||
| docker.nix | ||
| ec2-amis.nix | ||
| ec2-data.nix | ||
| ec2-metadata-fetcher.nix | ||
| ecs-agent.nix | ||
| gce-images.nix | ||
| google-compute-config.nix | ||
| google-compute-image.nix | ||
| grow-partition.nix | ||
| hyperv-guest.nix | ||
| kvmgt.nix | ||
| libvirtd.nix | ||
| lxc-container.nix | ||
| lxc.nix | ||
| lxcfs.nix | ||
| lxd.nix | ||
| openstack-config.nix | ||
| openvswitch.nix | ||
| parallels-guest.nix | ||
| qemu-guest-agent.nix | ||
| qemu-vm.nix | ||
| railcar.nix | ||
| rkt.nix | ||
| virtualbox-guest.nix | ||
| virtualbox-host.nix | ||
| virtualbox-image.nix | ||
| vmware-guest.nix | ||
| xe-guest-utilities.nix | ||
| xen-dom0.nix | ||
| xen-domU.nix | ||