upgraded to Fedora 32 from Fedora 30 -- libvirtd no longer runs

Mon Jun 1 18:42:55 EDT 2020

We'll charge you for excessive bandwidth.

--
Jerry Feldman <gaf.linux at 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 Mon, Jun 1, 2020, 5:51 PM Lloyd Kvam <lkvam at venix.com> wrote:

> Well the solution was ridiculously easy.
>    1. boot the normal kernel and make sure libvirtd is running
>    2. run virt-manager; create a new virthost specifying the old .img file
>
> So all my concerns about converting the image file and salvaging details
> were unnecessary. The
> magic just works.
>
> I hope I did not burden you with excessive emails. Thanks for the moral
> support.
>
> On Mon, 2020-06-01 at 13:51 -0400, Tom Buskey wrote:
> > On my Fedora 31, I only have 2 xen rpms:
> > xen-licenses-4.12.2-3.fc31.x86_64
> > xen-libs-4.12.2-3.fc31.x86_64
> >
> > If you don't need xen specifically, you shouldn't use a xen kernel.
> > Everything is using KVM nowadays
> >
> > On Mon, Jun 1, 2020 at 9:17 AM Lloyd Kvam <lkvam at venix.com> wrote:
> >
> > > On Sun, 2020-05-31 at 20:10 -0400, Jerry Feldman wrote:
> > > > Why are you using the xen kernel.
> > >
> > > I had set this up years ago (2012??) using Xen and haven't tried to
> change
> > > it. Other than a
> > > brief problem a few years back, it has worked smoothly.
> > >
> > > I am reading up on the libvirt image handling now so that I can figure
> out
> > > my options for
> > > regaining access to the server data - or shifting my virtualization.
> > >
> > > > --
> > > > Jerry Feldman <gaf.linux at 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, 8:08 PM Lloyd Kvam <lkvam at venix.com> wrote:
> > > >
> > > > > The key piece that I left out: libvirtd fails when I boot the XEN
> > >
> > > kernel.
> > > > > It's OK with the
> > > > > regular kernel.
> > > > >
> > > > >
> > > > > On Sun, 2020-05-31 at 19:38 -0400, Lloyd Kvam wrote:
> > > > > > 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.linux at 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 <lkvam at 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 at mail.gnhlug.org
> > > > > > > > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
> > > > > > > >
> > > > >
> > > > > --
> > > > > Lloyd Kvam
> > > > > 5 Foliage View
> > > > > Lebanon, NH 03766
> > > > > 802-448-0836
> > > > >
> > > > >
> > > > >
> > >
> > > --
> > > Lloyd Kvam
> > > 5 Foliage View
> > > Lebanon, NH 03766
> > > 802-448-0836
> > >
> > >
> > > _______________________________________________
> > > gnhlug-discuss mailing list
> > > gnhlug-discuss at mail.gnhlug.org
> > > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
> > >
> --
> Lloyd Kvam
> 5 Foliage View
> Lebanon, NH 03766
> 802-448-0836
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.gnhlug.org/pipermail/gnhlug-discuss/attachments/20200601/2b84425d/attachment.html 