Bug 2231617

Summary: Latest kernel update breaks bridged networking in libvirt
Product: [Fedora] Fedora Reporter: Daniel Rusek <drusek>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 38CC: acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, hpa, jarod, josef, kernel-maint, lgoncalv, linville, mail, masami256, mchehab, ptalbert, steved
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg - regressed kernel
none
dmesg - correctly working kernel none

Description Daniel Rusek 2023-08-12 14:20:09 UTC 
1. Please describe the problem:
When running kernel-6.4.9-200.fc38, bridged networking inside a GNOME Boxes (Windows 10) VM shows "Network cable disconnected" + another (Windows XP) VM hangs on boot. Both VMs work fine when using older kernel-6.4.8-200.fc38.

2. What is the Version-Release number of the kernel:
kernel-6.4.9-200.fc38.x86_64

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
1. Install latest kernel-6.4.9-200.fc38.
2. Install Windows 10 VM in GNOME Boxes.
3. Check if there is a working network inside the VM.

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.
See the attachments.
(Ignore the Bluetooth driver issue - it is an unrelated hardware bug in my motherboard/uefi causing my BT dongle to randomly disappear when doing a reboot instead of cold start.)

Reproducible: Always
Comment 1 Daniel Rusek 2023-08-12 14:22:02 UTC 
Created attachment 1983144 [details]
dmesg - regressed kernel

dmesg with the regressed kernel version
Comment 2 Daniel Rusek 2023-08-12 14:22:41 UTC 
Created attachment 1983145 [details]
dmesg - correctly working kernel

dmesg with the correctly working kernel version
Comment 3 Daniel Rusek 2023-08-14 10:50:26 UTC 
It looks like that the recently released 6.4.10-200.fc38.x86_64 has the same problem.