Closed rcambrj closed 2 weeks ago
Interesting, I don't have a server with EthernetServers anymore, but networkd works fine on my other OpenVZ nodes with nixos-unstable
. Could you try the following and see if networkd emits any interesting logs?
systemd.services.systemd-networkd = {
environment = {
SYSTEMD_LOG_LEVEL = "debug";
};
};
there are a bunch of failures in this log, but I don't know whether any of them are relevant 🤷
I'm now getting this failure when trying to nixos-rebuild switch
:
activating the configuration...
setting up /etc...
mount: /dev: mount(2) system call failed: Function not implemented.
dmesg(1) may have more information after failed mount system call.
mount: /dev/pts: mount(2) system call failed: Function not implemented.
dmesg(1) may have more information after failed mount system call.
mount: /dev/shm: mount(2) system call failed: Function not implemented.
Activation script snippet 'specialfs' failed (32)
dmesg(1) may have more information after failed mount system call.
mount: /proc: mount(2) system call failed: Function not implemented.
dmesg(1) may have more information after failed mount system call.
mount: /run: mount(2) system call failed: Function not implemented.
dmesg(1) may have more information after failed mount system call.
mount: /run/keys: mount(2) system call failed: Function not implemented.
dmesg(1) may have more information after failed mount system call.
reloading user units for root...
restarting sysinit-reactivation.target
warning: error(s) occurred while switching to the new configuration
Error: Process completed with exit code 1.
This might indeed be because I've misconfigured something, but from what I read, OpenVZ 7 runs on kernel 3.10 with Virtuozzo's patches to make it look like a more up to date one. That's pretty vague and obscure to me, so I'm going to abandon OpenVZ in favour of a KVM VPS. Not trying to steer anyone in any direction with this, only justifying that I won't investigate this any further.
Thanks again :) I hope what I put here helps someone at least.
For some reason the recommended configuration in the README didn't work for my OVZ VPS on ethernetservers.com.
The
venet0
interface should look like this:But after rebooting it would never gain an IP address. It would just always look like this:
Instead, and for those at a loss, I switched to whatever nixos uses when
networking.useNetworkd = false
:I don't get the
venet0:0
alias, but it works:Thanks for your hard work @zhaofengli 🙂