Bug 1971542
| Summary: | Rx and Tx drop not properly reported to the engine | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Aviv Litman <alitman> |
| Component: | BLL.Network | Assignee: | Ales Musil <amusil> |
| Status: | CLOSED NOTABUG | QA Contact: | Michael Burman <mburman> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.4.7 | CC: | ahadas, bugs, mperina, tgolembi |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-06-17 12:43:13 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1937714 | ||
The reported values are not from the guest. While it is possible to get the number of dropped packages from guest POV by qemu-ga, this is not what VDSM reports. When reporting network stats VDSM only gives libvirt stats as seen from domain POV (gathered with virConnectGetAllDomainStats()). Alright to sum up. Host statistics: vdsm collects statistics for all interfaces (nics/bonds/bridges), but engine aggregates and stores only physical nics and bonds. In case of this report the drop was on ovirtmgmt which is bridge. Physical interface ens3 has 0 drops for both RX and TX that's why engine DB has also 0. VM statistics: As Tomas explained, vdsm collects statistics from domain point of view, which might be slighlty different than guest point of view. This is considered as correct behavior. Closing as NOTABUG. |
Tomasi, can you please help us understand how guest agent reports drops? The VM has qemu-guest-agent-5.1.0 installed. UI show 0 dropped packets and the database has also 0, see the vm_interface_statistics screenshot. Kernel reports different drop statistics. # ip -s link show eth0 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 00:1a:4a:25:01:03 brd ff:ff:ff:ff:ff:ff RX: bytes packets errors dropped overrun mcast 26378082250 7194832 0 268134 0 0 TX: bytes packets errors dropped carrier collsns 1697312414 1065085 0 0 0 0 Any idea what might be missing here?