12:54 a.m.
Hii
Any help on this or is it just that my installation is messed up? 0_0.
Perhaps I can try reinstalling the packages after purging everything related to libvirt.
Thanks!
Arun Mani J
On Thursday, May 23rd, 2024 at 10:53 PM, Arun Mani J <J.ArunMani(a)proton.me> wrote:
> Yea I'm using qemu:///system.
>
> This should have the logs
https://gitlab.com/Arun-Mani-J/snippets/-/blob/main/virtlogs.
>
> Just to confirm that I got it right:
> 1. Found that my installation is a monolithic daemon.
> 2. Did sudo virt-admin -c libvirtd:///system daemon-log-outputs "3:journald
1:file:/home/arun-mani-j/virtd".
> 3. Did sudo virt-admin -c libvirtd:///system daemon-log-filters "3:remote
4:event 3:util.json 3:util.object 3:util.dbus 3:util.netlink 3:node_device 3:rpc 3:access
1:*"
> 4. Launched virt-manager.
> 5. Created and started a new guest that boots Debian 12 KDE Live.
> 6. Waited for the network-manager in guest to give up acquiring IP and reach
deactivated state (few minutes of waiting).
> 7. Shutdown the guest.
> 8. Closed virt-manager.
> 9. Did sudo virt-admin -c libvirtd:///system daemon-log-outputs ""
> 10. Did sudo virt-admin -c libvirtd:///system daemon-log-filters "3:remote
4:util.json 4:rpc"
>
> Please let me know if I have missed something, so that I can redo.
>
> Thanks for being so helpful, really awesome :)
> Arun Mani J
>
> On Thursday, May 23rd, 2024 at 1:11 PM, Michal Prívozník mprivozn(a)redhat.com wrote:
>
> > On 5/22/24 19:22, Arun Mani J wrote:
> >
> > > I have attached the screenshot of `nmcli` inside guest (clipboard
doesn't work, but that's for another day may be): https://imgur.com/NlDtDtc
> > >
> > > The guest is stuck in two states basically - connecting and after a few
seconds it reaches disconnected state.
> > >
> > > $ cat /proc/sys/net/ipv4/ip_forward
> > > 1
> > >
> > > (I'm using bridge instead of brctl because it is not available and
seems to be deprecated in favor of bridge, please let me know if that's not the case)
> > >
> > > $ sudo bridge link show virbr0
> > >
> > > The command gave no output, so I tried ip link (apologies if that
doesn't help)
> >
> > So, when I'm running a VM what I get is:
> >
> > # bridge link show virbr0
> > 18: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 master virbr0
> >
> > state forwarding priority 32 cost 2
> >
> > Something looks broken and vnet0 is not getting plugged into the bridge.
> >
> > > $ ip link show virbr0
> > > 4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN mode DEFAULT group default qlen 1000
> > > link/ether 52:54:00:78:76:0f brd ff:ff:ff:ff:ff:ff
> > >
> > > (It says state is DOWN ??)
> >
> > Yeah, this is suspicious too.
> >
> > > $ for i in nat filter mangle; do sudo iptables -t $i -L -v ; done
> >
> > Firewall rules look more or less the same.
> >
> > Now, I'm assuming your guest is under qemu:///system URI, right? Can you
> > enable debug logs, start the guest and then share the logs somewhere
> > (e.g. pastebin-like service) please? In the logs there should be a
> > section where libvirt creates vnetX interface and plugs it into the bridge.
> >
> > https://libvirt.org/kbase/debuglogs.html
> >
> > If you're running a monolithic daemon (libvirtd) then all the work
> > happens inside it and logs from it are sufficient. But if you're running
> > split daemons then I'd need to see logs from virtqemud and virtnetworkd.
> >
> > Michal