After installing QEMU/KVM my wired network connection keeps disconnecting or going into a limited connectivity state. It happens on both wired interfaces. I've had Arch installed for about a week now and never had a single issue until I installed QEMU/KVM. I've tried to -Rns QEMU but I still have issues. My wireless connection works fine, but I'd rather use wired.
#Network issues after installing QEMU/KVM
dreamy prism
agile hound
That sounds odd, how long does it stay disconnected for?
dreamy prism
That sounds odd, how long does it stay disconnected for?
maybe 10 seconds and then goes into limited connectivity for about 10-30 seconds and then goes normal
agile hound
If it happens for a decent amount of time, u should compare "ip addr" commands to see what's going on with your net interfaces
huh, alright
if you do "journalctl -b" and page down through the results does anything show up?
dreamy prism
If it happens for a decent amount of time, u should compare "ip addr" commands t...
The first ip addr is during normal operation. The second is during "limited connectivity"
agile hound
it all looks fine, i'm not sure what the problem is
dreamy prism
agile hound
there's definitely some weird stuff going on in there though let me see if I can find something
dreamy prism
Apr 07 22:05:09 TuxOnFire NetworkManager[629]: <info> [1712541909.7988] manager: NetworkManager state is now CONNECTED_SITE
Apr 07 22:05:09 TuxOnFire NetworkManager[629]: <info> [1712541909.7990] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 07 22:05:09 TuxOnFire NetworkManager[629]: <info> [1712541909.7991] manager: NetworkManager state is now CONNECTED_SITE
Apr 07 22:05:09 TuxOnFire NetworkManager[629]: <info> [1712541909.7991] policy: set 'Georgetown Meth Lab' (wlan0) as default for IPv4 routing and DNS
Apr 07 22:05:09 TuxOnFire systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 07 22:05:09 TuxOnFire systemd[1]: Started Network Manager Script Dispatcher Service.
Apr 07 22:05:19 TuxOnFire systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
it just happened again and thats the last entry
agile hound
So i can see that the dispatcher service is just continuously running and it's bringing your interface down
well it's not bringing it down, but ur losing connection
dreamy prism
I just stopped libvirtd service. I think it might be tied to it.
agile hound
yea there's a good chance of that
dreamy prism
Now its acting normal.
agile hound
That's good.
U could try tweaking the virtual network setting in libvirtd, that could help
U could also enable debug logging for NetworkManager to get clearer picture of what's going on
dreamy prism
Gotta figure out how to do that. It's been years since I used Linux.
agile hound
oh it's in that link
agile hound
lol all good, I'm CCNA certified and i'm still embarased by a lot of this stuff
dreamy prism
I haven't been in IT for years tho. I drive a semi
agile hound
I'm just trying to get my first support gig
dreamy prism
Well, you can use me as a reference.
agile hound
lol I may have to with the luck I've been getting
In that article though, the guy ended up disabling connectivity checking, which seemed to have fixed the issue for them
left cargo
Is this fixed?