Hello,
On Sun, Jan 16, 2022 at 04:35:51PM -0500, Greg Wooledge wrote:
> On Sun, Jan 16, 2022 at 10:11:30PM +0100, Felix Odenkirchen wrote:
> > A udev update changed the interface name for virtual network devices
> > from "eth0" to "enX0" (using persistent block device naming scheme),
>
>
On Sun, Jan 16, 2022 at 10:11:30PM +0100, Felix Odenkirchen wrote:
> A udev update changed the interface name for virtual network devices
> from "eth0" to "enX0" (using persistent block device naming scheme),
https://wiki.debian.org/NewInBuster#Network_interface_name_migration
Which version of
Hi Felix,
It looks to me like a change in one of the systemd or udev packages in
vm-sid is causing the trouble here. In my experience with Debian, the
networking startup stuff is not so straightforward, but I do know that
systemd and udev are the software components responsible for setting
up
On 1/16/2022 7:16 AM, Felix Odenkirchen wrote:
Dear all,
I'm running a stock Debian SID vm on xen, hostname "vm-sid".
Dom0 is on stock Debian Bullseye, hostname "bigiron-one".
apt updating vm-sid packages on 2022-01-13 08:11:00 UTC rendered vm-sid
unaccessible over network upon reboot.
Updated
Dear all,
I'm running a stock Debian SID vm on xen, hostname "vm-sid".
Dom0 is on stock Debian Bullseye, hostname "bigiron-one".
apt updating vm-sid packages on 2022-01-13 08:11:00 UTC rendered vm-sid
unaccessible over network upon reboot.
Updated packages:
bsdutils bsdextrautils dbus eject
5 matches
Mail list logo
