OK, I'll just have a go at the upgrade as-is and see how it goes. If anything breaks
and I can't fix it, I'll ask for advice. I hope to try this soon but not today.
On Mon, 13 Apr 2020, at 10:36 AM, Andy Smith wrote:
On Mon, Apr 13, 2020 at 10:18:32AM +0100, Alastair Sherringham wrote:
I am wanting to upgrade my server from Debian 9
to Debian 10. I
have done this on other systems without problems but have a
question about the Bitfolk VM and network interface name.
Since the MAC addresses and interface names are fixed in the config
on BitFolk's side, interface names are stable inside the VMs and
eth0 will always be eth0.
I've installed Debian 10 in BitFolk VMs many times and upgraded to
it many times and it's never changed away from eth0.
Here's something I wrote to another customer who asked:
Based on a Xen guest's device directory in sysfs being something
…then on second look it seems that here:
…it just doesn't fall into any of the existing categories except
for MAC-based, which as you say is disabled by default.
Specifically, it is not considered PCI because it's on a bus
called "vif-0" or whatever, not "pci".
I suppose it is possible that in future Xen could change
something here, or udev could add an extra test.
If you are worried about this then I think you could do one of
several things, such as:
- Use the net.ifnames=0 kernel command line option to
disable any future renaming.
- Enable the MAC-based device naming; your MAC address will not
change for the life of the account.
- Add a udev rule to rename based on MAC address to something
So I don't think you need to do anything at all.
On bare metal or a KVM guest it would probably be a different story.
-- No-nonsense VPS hosting
users mailing list