<div dir="auto">We'll charge you for excessive bandwidth. <div dir="auto"><br><div data-smartmail="gmail_signature" dir="auto">--<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></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jun 1, 2020, 5:51 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">Well the solution was ridiculously easy.<br>
1. boot the normal kernel and make sure libvirtd is running<br>
2. run virt-manager; create a new virthost specifying the old .img file<br>
<br>
So all my concerns about converting the image file and salvaging details were unnecessary. The<br>
magic just works.<br>
<br>
I hope I did not burden you with excessive emails. Thanks for the moral support.<br>
<br>
On Mon, 2020-06-01 at 13:51 -0400, Tom Buskey wrote:<br>
> On my Fedora 31, I only have 2 xen rpms:<br>
> xen-licenses-4.12.2-3.fc31.x86_64<br>
> xen-libs-4.12.2-3.fc31.x86_64<br>
> <br>
> If you don't need xen specifically, you shouldn't use a xen kernel.<br>
> Everything is using KVM nowadays<br>
> <br>
> On Mon, Jun 1, 2020 at 9:17 AM Lloyd Kvam <<a href="mailto:lkvam@venix.com" target="_blank" rel="noreferrer">lkvam@venix.com</a>> wrote:<br>
> <br>
> > On Sun, 2020-05-31 at 20:10 -0400, Jerry Feldman wrote:<br>
> > > Why are you using the xen kernel.<br>
> > <br>
> > I had set this up years ago (2012??) using Xen and haven't tried to change<br>
> > it. Other than a<br>
> > brief problem a few years back, it has worked smoothly.<br>
> > <br>
> > I am reading up on the libvirt image handling now so that I can figure out<br>
> > my options for<br>
> > regaining access to the server data - or shifting my virtualization.<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, 8:08 PM Lloyd Kvam <<a href="mailto:lkvam@venix.com" target="_blank" rel="noreferrer">lkvam@venix.com</a>> wrote:<br>
> > > <br>
> > > > The key piece that I left out: libvirtd fails when I boot the XEN<br>
> > <br>
> > kernel.<br>
> > > > 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<br>
> > <br>
> > 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<br>
> > > > <br>
> > > > libvirtd manually. I<br>
> > > > > got<br>
> > > > > an error about virbr0 already existed. Poking through /etc I found an<br>
> > > > <br>
> > > > ancient qemu/networks<br>
> > > > > XML<br>
> > > > > file that defined virbr0 as well as a new XML file elsewhere that did<br>
> > > > <br>
> > > > 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<br>
> > <br>
> > rebooting<br>
> > > > <br>
> > > > 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<br>
> > <br>
> > output<br>
> > > > <br>
> > > > below<br>
> > > > > > > is from journalctl and<br>
> > > > > > > shows how libvirtd just recycles without end. I would greatly<br>
> > > > <br>
> > > > 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<br>
> > > > <br>
> > > > 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:<br>
> > > > <br>
> > > > Consumed<br>
> > > > > > > 2.011s CPU time.<br>
> > > > > > > May 31 17:48:39 vmhost.home.lan systemd[1]: libvirtd.service:<br>
> > > > <br>
> > > > Scheduled<br>
> > > > > > > restart job, restart counter is at 55.<br>
> > > > > > > May 31 17:48:39 vmhost.home.lan systemd[1]: Stopped<br>
> > <br>
> > Virtualization<br>
> > > > <br>
> > > > daemon.<br>
> > > > > > > May 31 17:48:39 vmhost.home.lan systemd[1]: libvirtd.service:<br>
> > > > <br>
> > > > Consumed<br>
> > > > > > > 2.011s CPU time.<br>
> > > > > > > May 31 17:48:39 vmhost.home.lan systemd[1]: Starting<br>
> > <br>
> > Virtualization<br>
> > > > > > > daemon...<br>
> > > > > > > May 31 17:48:44 vmhost.home.lan systemd[1]: Started<br>
> > <br>
> > Virtualization<br>
> > > > <br>
> > > > daemon.<br>
> > > > > > > May 31 17:49:18 vmhost.home.lan systemd[1]: libvirtd.service:<br>
> > <br>
> > Main<br>
> > > > <br>
> > > > process<br>
> > > > > > > exited, code=killed, status=11/SEGV<br>
> > > > > > > May 31 17:49:18 vmhost.home.lan systemd[1]: libvirtd.service:<br>
> > <br>
> > Failed<br>
> > > > <br>
> > > > with<br>
> > > > > > > result 'signal'.<br>
> > > > > > > May 31 17:49:18 vmhost.home.lan systemd[1]: libvirtd.service:<br>
> > > > <br>
> > > > Consumed<br>
> > > > > > > 2.378s CPU time.<br>
> > > > > > > May 31 17:49:19 vmhost.home.lan systemd[1]: libvirtd.service:<br>
> > > > <br>
> > > > Scheduled<br>
> > > > > > > restart job, restart counter is at 56.<br>
> > > > > > > May 31 17:49:19 vmhost.home.lan systemd[1]: Stopped<br>
> > <br>
> > Virtualization<br>
> > > > <br>
> > > > daemon.<br>
> > > > > > > May 31 17:49:19 vmhost.home.lan systemd[1]: libvirtd.service:<br>
> > > > <br>
> > > > Consumed<br>
> > > > > > > 2.378s CPU time.<br>
> > > > > > > May 31 17:49:19 vmhost.home.lan systemd[1]: Starting<br>
> > <br>
> > Virtualization<br>
> > > > > > > daemon...<br>
> > > > > > > May 31 17:49:22 vmhost.home.lan systemd[1]: Started<br>
> > <br>
> > Virtualization<br>
> > > > <br>
> > > > daemon.<br>
> > > > > > > May 31 17:49:47 vmhost.home.lan systemd[1]: libvirtd.service:<br>
> > <br>
> > Main<br>
> > > > <br>
> > > > process<br>
> > > > > > > exited, code=killed, status=11/SEGV<br>
> > > > > > > May 31 17:49:47 vmhost.home.lan systemd[1]: libvirtd.service:<br>
> > <br>
> > Failed<br>
> > > > <br>
> > > > with<br>
> > > > > > > result 'signal'.<br>
> > > > > > > May 31 17:49:47 vmhost.home.lan systemd[1]: libvirtd.service:<br>
> > > > <br>
> > > > Consumed<br>
> > > > > > > 1.931s CPU time.<br>
> > > > > > > May 31 17:49:47 vmhost.home.lan systemd[1]: libvirtd.service:<br>
> > > > <br>
> > > > 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>
> > > > --<br>
> > > > Lloyd Kvam<br>
> > > > 5 Foliage View<br>
> > > > Lebanon, NH 03766<br>
> > > > 802-448-0836<br>
> > > > <br>
> > > > <br>
> > > > <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>