Opened 4 years ago
Last modified 3 years ago
#16700 new bug
iPv4: Networking In Virtual Machine Manager Broken By Multicast
| Reported by: | CodeforEvolution | Owned by: | axeld |
|---|---|---|---|
| Priority: | critical | Milestone: | Unscheduled |
| Component: | Network & Internet/IPv4 | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
I recently created a virtual Haiku install (within Virtual Machine Manager, which uses libvirt) using hrev54811, and found that any networking activity would come to a halt after just a few moments of usage. Eventually, I could simply not utilize any networking related functionality while using Haiku. Worse, while my Haiku virtual machine was running, I could not use the internet from my host operating system (Ubuntu 20.10).
Haiku would not give any information on what was going on with the networking. However, Ubuntu showed some suspicious messages regarding that "vnet0" was entering "promiscuous mode", which I believe has to do with multicast that was recently enabled in hrev54778.
If any further information is needed, just let me know!
Change History (5)
comment:1 by , 4 years ago
comment:3 by , 4 years ago
Yes, it sounds like bug #14982. My work-around in VirtualBox is to use the old "PCnet-PCI II (Am79C970A)" virtual hardware (which maxes out at 100Mb/s) rather than any of the other ones (all of which trigger that problem), from Intel Pro/1000s to virtio-net.
comment:4 by , 4 years ago
I'm using libvirt and the same GUI setup on my 20.04 (Mint Ulyssa) machine - but was able to download the sources and compile from inside last night. I don't know a great deal about how libvirt is plumbed inside, there are several modes and I looked into it before and it got complex quickly, but would you be able to export and attach the machine's setup as an XML file, and at the least I could diff this against mine to see what's changed between them?
comment:5 by , 3 years ago
CodeforEvaluation: Can you grab the file requested by stellarpower? Also, ny changes with Beta 3?
Researching this further, it seems that this may be a problem todo with libvirt. Worse, it seems it's one of those problems which hasn't been addressed for multiple years :(.
Semi-useful link: https://bugzilla.redhat.com/show_bug.cgi?id=1035253#c15 (The ticket was closed, however, there's still discussion ongoing as recently as November.)