[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libvirt (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
[Expired for virt-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: virt-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
So, it seems really working. Thank you so much Christian! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
So, I just rebooted and it seems fine. Puting in /etc/modules the line "kvm_amd" worked and I can start VM without restarting libvirt. So far said. So, what's up with that now? Is that bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
Hi. Under libvirt there are actually 2 processes: qemu-system-x86_64 -enable-kvm -S -no-user-config -nodefaults -nographic -machine none,accel=kvm:tcg -qmp unix:/var/lib/libvirt/qemu/qmp- 2NL5J0/qmp.monitor,server,nowait -pidfile /var/lib/libvirt/qemu/qmp- 2NL5J0 qemu-system-x86_64 -enable-kvm -S -no-user-config -nodefaults -nographic -machine none,accel=kvm:tcg -qmp unix:/var/lib/libvirt/qemu/qmp- 2NL5J0/qmp.monitor,server,nowait -pidfile /var/lib/libvirt/qemu/qmp- 2NL5J0/qmp.pid -daemonize -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
Ok, from 2.1 we can see that it is not just the socket that is up. It did indeed start your service at "2020-05-08 17:24:47". You have a qqemu process listed under libvirt, which is uncommon: 1745 [qemu-system-x86] That isn't a guest as those are not listed there. I'm wondering if this is the capability-probing step which happens when libvirt initializes and there is no cache for the capabilities. When you have the error case and you see a qemu under libvirt again in `systemctl status libvirtd` could you then check if that qemu is running fine. e..g does it consume cpu or is it hanging in a disabled state. Furthermore report its commandline via /proc//cmdline. I just want to find if that really is the capability probing. Further in your logs I found: Could not access KVM kernel module: No such file or directory qemu-system-x86_64: failed to initialize KVM: No such file or directory qemu-system-x86_64: Back to tcg accelerator This somewhat matches my assumption in comment #1 that for you libvirt might initialize out of order before kvm is ready. They would be auto-loaded, but just to be sure since it seems reproducible let us try to load kvm earlier to see if that resolves your situation. Put in /etc/modules the line "kvm_amd" Then: $ sudo update-initramfs -u $ sudo update-grub And reboot, let me know if this earlier loading of kvm_amd helped in your case. P.S. I rechecked some MAD systems, but they don't have the same issue to debug it over here ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
I did some tries as complete reinstall but it's still occcuring and now I'm also sure it stops system for proper shutdown. 2.1 $ virsh list --all is hanging 2.2 $ systemctl status libvirtd.service libvirtd-admin.socket libvirtd-ro.socket libvirtd.socket Report as attachment. ** Attachment added: "log1_systemctl status" https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1876266/+attachment/5368499/+files/log1_systemctl%20status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
2.2 $ cat /var/log/libvirtd.log As attachment ** Attachment added: "libvirtd.log" https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1876266/+attachment/5368500/+files/libvirtd.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
Ok, so your libvirt really isn't responsive It could be that it only has the socket up in systemd and not starting the service on a connection until you restart it. Or it really is started but not responsible. I'd recommend to: 1. enable logging in libvirt -> https://wiki.libvirt.org/page/DebugLogs That usually comes down to add to /etc/libvirt/libvirtd.conf: log_level = 1 log_outputs="1:file:/var/log/libvirtd.log" 2. Right after reboot then please: 2.1 check if it is hanging $ virsh list --all 2.2 if it is hanging please report the following $ systemctl status libvirtd.service libvirtd-admin.socket libvirtd-ro.socket libvirtd.socket $ cat /var/log/libvirtd.log P.S. Please consider putting that to text files and attach them to the bug instead of google-docs in a gdrive. It just is more accessible for more people. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
Third - does adding a new connection in virt-manager get it done as well? Via "File" -> "Add connection" I just tried this and it stucks on loading pointer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
Hi, I wasn't working recently. Yes, I restart quite regularly. What's the issue is that is is likely correlated with me unable to shutdown the system too. It hangs on and doesn't turn off even after 90s. I have to do hardreset. $ virsh list --all- is hanging on...as you predicted I posted all those logs after I boot up and uploaded to G Drive: https://drive.google.com/drive/folders/1MEc7-fq89JdujZInHuhxY451GvM-qZhp?usp=sharing Thanks you guys for helping me! Robin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
Here a few things I'd want you (@robin) to try and report how that works for you. First of all is this reproducible, e.g. if your reboot the computer do you get back into the same problem state? Second when in the state that virt-manager can't connect could you try on the command line to issue. $ virsh list --all Does that hang or work showing your guests? Does the virsh call maybe even unblock your waiting virt-manager? Third - does adding a new connection in virt-manager get it done as well? Via "File" -> "Add connection" Note: the warnings on restart are fine, libvirt keeps e.g. dnsmasq processes around and that is systemd notifying you that it found old processes and is regrouping it from before. Note II: the warning of no /dev/kvm is odd. Could you report the following two here if we might miss something (you could miss the module, or the qemu-system or such, not likely since it works later - but just to be sure): $ lsmod $ dpkg -l It almost seems like when libvirt initializes the first time KVM isn't really ready yet as it is missing /dev/kvm. Maybe that puts it into a bad state. Then later it is properly loaded and the libvirt restart makes it pick that up. Maybe providing these can help to time-corelate libvirt start and kvm module: $ dmesg $ journalctl -b 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876266] Re: virt-manager can't connect to libvirtd until the service is restarted
Incomplete waiting for further data for now as I could not reproduce it in several environments that I tried. ** Changed in: virt-manager (Ubuntu) Status: New => Incomplete ** Also affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876266 Title: virt-manager can't connect to libvirtd until the service is restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1876266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
