well, MACs are associated with interfaces, not IPs. As I said, having two IPs on the same interface is possible, a basic interfaces file for that would look something like this
iface enp6s18 inet manual
auto enp6s18:0
iface enp6s18:0 inet static...
Ohh, you can only have one as gateway. Generally it is not a problem a VM has multiple IPs on the same interface, as long as they are on the same subnet. This isn't something that should need any sort of configuration on the PVE host.
Hey,
the easiest is probably something like
pvesh get /cluster/replication --output-format=json | jq '.[].id' | xargs -I ID pvesr disable ID
- pvesh get /cluster/replication --output-format=json will give you a list of all replication jobs
- jq...
Hey,
did you change any configuration regarding kernel modules? Do the syslogs(journalctl -b) contain more information surrounding this, and could you also check dmesg?
Hey,
are those separate physical interfaces, or do those three come over the same one(this it what it look like based on your /etc/network/interfaces)? If they are on different interfaces, you can just pass through the whole interface to the VM...
Ohh, you mean mTLS. Generally there is no need to bind mount[1] it, you can just copy it from the host into your container, alternatively just generate them in the container. Is there a reason you have to have those directly on the PVE host...
Hey,
what is it you are trying to do? And how does it relate to bind mounting something in a LXC? Do you own the domain you want certificates for subdomain of? If yes, configuring NPM to use DNS challenge to obtain a certificate for something...