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