On Sun, 2020-05-31 at 18:17 -0400, Jerry Feldman wrote: > I have not used libvirtd on fedora 32 directky but I do use gnome boxes > that does use libvirtd. > Did you try removing and reloading the packages.
Yes, dnf reinstall on the libvirt and xen packages. After disabling libvirtd and rebooting I was finally able to just run libvirtd manually. I got an error about virbr0 already existed. Poking through /etc I found an ancient qemu/networks XML file that defined virbr0 as well as a new XML file elsewhere that did the same. Since then, the manual runs simply dump core. I've deleted the ancient files (backed up by etckeeper) and am rebooting and trying things. Thanks for responding. > -- > Jerry Feldman <gaf.li...@gmail.com> > Boston Linux and Unix http://www.blu.org > PGP key id: 6F6BB6E7 > PGP Key fingerprint: 0EDC 2FF5 53A6 8EED 84D1 3050 5715 B88D 6F6 > B B6E7 > > On Sun, May 31, 2020, 6:11 PM Lloyd Kvam <lk...@venix.com> wrote: > > > This on my home server which runs a virtualized Ubuntu. The output below > > is from journalctl and > > shows how libvirtd just recycles without end. I would greatly appreciate > > any pointers for > > figuring out what's wrong with libvirtd. > > > > I suppose an alternative would be to turn the Ubuntu image into normal > > disk drive partition[s] > > and just run it directly. > > > > """ from journalctl libvirtd.service > > May 31 17:48:39 vmhost.home.lan systemd[1]: libvirtd.service: Consumed > > 2.011s CPU time. > > May 31 17:48:39 vmhost.home.lan systemd[1]: libvirtd.service: Scheduled > > restart job, restart counter is at 55. > > May 31 17:48:39 vmhost.home.lan systemd[1]: Stopped Virtualization daemon. > > May 31 17:48:39 vmhost.home.lan systemd[1]: libvirtd.service: Consumed > > 2.011s CPU time. > > May 31 17:48:39 vmhost.home.lan systemd[1]: Starting Virtualization > > daemon... > > May 31 17:48:44 vmhost.home.lan systemd[1]: Started Virtualization daemon. > > May 31 17:49:18 vmhost.home.lan systemd[1]: libvirtd.service: Main process > > exited, code=killed, status=11/SEGV > > May 31 17:49:18 vmhost.home.lan systemd[1]: libvirtd.service: Failed with > > result 'signal'. > > May 31 17:49:18 vmhost.home.lan systemd[1]: libvirtd.service: Consumed > > 2.378s CPU time. > > May 31 17:49:19 vmhost.home.lan systemd[1]: libvirtd.service: Scheduled > > restart job, restart counter is at 56. > > May 31 17:49:19 vmhost.home.lan systemd[1]: Stopped Virtualization daemon. > > May 31 17:49:19 vmhost.home.lan systemd[1]: libvirtd.service: Consumed > > 2.378s CPU time. > > May 31 17:49:19 vmhost.home.lan systemd[1]: Starting Virtualization > > daemon... > > May 31 17:49:22 vmhost.home.lan systemd[1]: Started Virtualization daemon. > > May 31 17:49:47 vmhost.home.lan systemd[1]: libvirtd.service: Main process > > exited, code=killed, status=11/SEGV > > May 31 17:49:47 vmhost.home.lan systemd[1]: libvirtd.service: Failed with > > result 'signal'. > > May 31 17:49:47 vmhost.home.lan systemd[1]: libvirtd.service: Consumed > > 1.931s CPU time. > > May 31 17:49:47 vmhost.home.lan systemd[1]: libvirtd.service: Scheduled > > restart job, restart counter is at 57. > > """ > > > > Any help or suggestions would be greatly appreciated. > > Thanks. > > > > -- > > Lloyd Kvam > > 5 Foliage View > > Lebanon, NH 03766 > > 802-448-0836 > > > > > > _______________________________________________ > > gnhlug-discuss mailing list > > gnhlug-discuss@mail.gnhlug.org > > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ > > -- Lloyd Kvam 5 Foliage View Lebanon, NH 03766 802-448-0836 _______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
