Fcos 39 kernel 6.7.5-200.fc39.x86_64 unable to find virtio_net module, network fails

hi colleagues.
After zincati update 39.20240309.3.0 suddenly failed to connect VM to network. The VM run in an exotic cloud for 5 months with regular updates. The normal network device detected by kernel and started up by NetworkManager:

 grep -I4 virtio_net dmesg
[    3.255062] systemd[1]: Stopping systemd-vconsole-setup.service - Virtual Console Setup...
[    3.263331] systemd[1]: Starting systemd-vconsole-setup.service - Virtual Console Setup...
[    3.273083]  sda: sda1 sda2 sda3 sda4
[    3.273758] sd 6:0:0:0: [sda] Attached SCSI disk
[    3.301597] virtio_net virtio0 enp3s0: renamed from eth0
[    3.357120] systemd[1]: Finished systemd-vconsole-setup.service - Virtual Console Setup.
[    3.674456] systemd[1]: Found device dev-disk-by\x2duuid-728bb1ea\x2d3e79\x2d424d\x2d9105\x2df60cb0cbb329.device - QEMU_HARDDISK root.
[    3.676298] systemd[1]: Reached target initrd-root-device.target - Initrd Root Device.
[    3.709100] systemd[1]: Finished systemd-udev-settle.service - Wait for udev To Complete Device Initialization.

normal network config should be

enp3s0: connected to Wired connection 1
        "Red Hat Virtio 1.0"
        ethernet (virtio_net), 02:C4:DA:11:5B:A5, hw, mtu 1500
        ip4 default
        route4 metric 100
        route4 default via metric 100
        inet6 fe80::4bfe:57e:adb2:685c/64
        route6 fe80::/64 metric 1024

lo: connected (externally) to lo
        loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
        inet6 ::1/128

The latter net status from other fcos39 VM, restored from old image and updated to the current version. It seems that cloud DHCP service failed, or other networking issue put the subj. VM in a useless state.

I’m trying to restore networking manually, loaded the modprobe virtio_net, but nmcli doesn’t see the ethernet device. Is there any way to set net up ??

Bad news that rollback to the previous version of ostree 39.20240225.3.0 didn’t help, kernel doesn’t see virtio_net, nmcli status shows only lo

Since you booted other VMs and they don’t have the problem and a rollback to the old software on the problematic VM doesn’t recover the issue I’d suspect the hardware is somehow bad for this particular VM.