Hii
Okay, then let me see if I can reproduce this bug in a fresh Debian installation. If yes,
then could be a bug in the Debian side, else I will reinstall my system :)
Thank you!
-------- Original Message --------
On 6/10/24 12:19 PM, Michal Prívozník <mprivozn(a)redhat.com> wrote:
> On 6/9/24 07:54, Arun Mani J wrote:
> > 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.
>
> I haven't found anything wrong in the logs. The only thing that comes to
> my mind is NetworkManager on the host clashing with what libvirt does
> (which is supported by the fact that virbr0 link state was down in one
> of previous e-mails).
>
> Michal
>
>