From lkvam at venix.com  Mon Jun  1 09:15:59 2020
From: lkvam at venix.com (Lloyd Kvam)
Date: Mon, 01 Jun 2020 09:15:59 -0400
Subject: upgraded to Fedora 32 from Fedora 30 -- libvirtd no longer runs
In-Reply-To: <CAEvgogEiyE7a5DKONS_fEgjdf6HW8w+Ms2LpU6w8e_qOqWgsGg@mail.gmail.com>
References: <3a39213b4a2aa39e57383e142312f51bb09010f3.camel@venix.com>
	<CAEvgogGnxuQT5euQvWjwBAw83VeDgUBfhe66pEF_j2Mnk_ujzw@mail.gmail.com>
	<75776ae40f92c42000d3be5341ba5a73a394e973.camel@venix.com>
	<7ef05c9243109f52c7a849eaf9ae69e5840e50f5.camel@venix.com>
	<CAEvgogEiyE7a5DKONS_fEgjdf6HW8w+Ms2LpU6w8e_qOqWgsGg@mail.gmail.com>
Message-ID: <8edad52bead51c3c541bcda90b530a3f79d68414.camel@venix.com>

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



From tom at buskey.name  Mon Jun  1 13:51:59 2020
From: tom at buskey.name (Tom Buskey)
Date: Mon, 1 Jun 2020 13:51:59 -0400
Subject: upgraded to Fedora 32 from Fedora 30 -- libvirtd no longer runs
In-Reply-To: <8edad52bead51c3c541bcda90b530a3f79d68414.camel@venix.com>
References: <3a39213b4a2aa39e57383e142312f51bb09010f3.camel@venix.com>
	<CAEvgogGnxuQT5euQvWjwBAw83VeDgUBfhe66pEF_j2Mnk_ujzw@mail.gmail.com>
	<75776ae40f92c42000d3be5341ba5a73a394e973.camel@venix.com>
	<7ef05c9243109f52c7a849eaf9ae69e5840e50f5.camel@venix.com>
	<CAEvgogEiyE7a5DKONS_fEgjdf6HW8w+Ms2LpU6w8e_qOqWgsGg@mail.gmail.com>
	<8edad52bead51c3c541bcda90b530a3f79d68414.camel@venix.com>
Message-ID: <CAEHDbABHn5iqg9=SgA5JCkEdQ7GYgtj-bXUdm3=vbx9kQxrMTQ@mail.gmail.com>

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/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.gnhlug.org/pipermail/gnhlug-discuss/attachments/20200601/830744c1/attachment.html 

From lkvam at venix.com  Mon Jun  1 15:47:22 2020
From: lkvam at venix.com (Lloyd Kvam)
Date: Mon, 01 Jun 2020 15:47:22 -0400
Subject: upgraded to Fedora 32 from Fedora 30 -- libvirtd no longer runs
In-Reply-To: <CAEHDbABHn5iqg9=SgA5JCkEdQ7GYgtj-bXUdm3=vbx9kQxrMTQ@mail.gmail.com>
References: <3a39213b4a2aa39e57383e142312f51bb09010f3.camel@venix.com>
	<CAEvgogGnxuQT5euQvWjwBAw83VeDgUBfhe66pEF_j2Mnk_ujzw@mail.gmail.com>
	<75776ae40f92c42000d3be5341ba5a73a394e973.camel@venix.com>
	<7ef05c9243109f52c7a849eaf9ae69e5840e50f5.camel@venix.com>
	<CAEvgogEiyE7a5DKONS_fEgjdf6HW8w+Ms2LpU6w8e_qOqWgsGg@mail.gmail.com>
	<8edad52bead51c3c541bcda90b530a3f79d68414.camel@venix.com>
	<CAEHDbABHn5iqg9=SgA5JCkEdQ7GYgtj-bXUdm3=vbx9kQxrMTQ@mail.gmail.com>
Message-ID: <ef66be1a24bc3bc7da5ed8a1dda5ffd45d4800f7.camel@venix.com>

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

I have started trying to migrate. Unfortunately, virt-v2v requires a working libvirtd to move
things along. qemu-img is trying to convert the xen image right now.

I'll keep thrashing, but may windup installing Fedora30 to get back to a working system,
migrate to KVM and then upgrade Fedora.

> 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



From lkvam at venix.com  Mon Jun  1 17:51:42 2020
From: lkvam at venix.com (Lloyd Kvam)
Date: Mon, 01 Jun 2020 17:51:42 -0400
Subject: upgraded to Fedora 32 from Fedora 30 -- libvirtd no longer runs
In-Reply-To: <CAEHDbABHn5iqg9=SgA5JCkEdQ7GYgtj-bXUdm3=vbx9kQxrMTQ@mail.gmail.com>
References: <3a39213b4a2aa39e57383e142312f51bb09010f3.camel@venix.com>
	<CAEvgogGnxuQT5euQvWjwBAw83VeDgUBfhe66pEF_j2Mnk_ujzw@mail.gmail.com>
	<75776ae40f92c42000d3be5341ba5a73a394e973.camel@venix.com>
	<7ef05c9243109f52c7a849eaf9ae69e5840e50f5.camel@venix.com>
	<CAEvgogEiyE7a5DKONS_fEgjdf6HW8w+Ms2LpU6w8e_qOqWgsGg@mail.gmail.com>
	<8edad52bead51c3c541bcda90b530a3f79d68414.camel@venix.com>
	<CAEHDbABHn5iqg9=SgA5JCkEdQ7GYgtj-bXUdm3=vbx9kQxrMTQ@mail.gmail.com>
Message-ID: <66b1d4c8a917e96a00cd85b34ba7e711a1cb1be9.camel@venix.com>

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



From gaf.linux at gmail.com  Mon Jun  1 18:42:55 2020
From: gaf.linux at gmail.com (Jerry Feldman)
Date: Mon, 1 Jun 2020 18:42:55 -0400
Subject: upgraded to Fedora 32 from Fedora 30 -- libvirtd no longer runs
In-Reply-To: <66b1d4c8a917e96a00cd85b34ba7e711a1cb1be9.camel@venix.com>
References: <3a39213b4a2aa39e57383e142312f51bb09010f3.camel@venix.com>
	<CAEvgogGnxuQT5euQvWjwBAw83VeDgUBfhe66pEF_j2Mnk_ujzw@mail.gmail.com>
	<75776ae40f92c42000d3be5341ba5a73a394e973.camel@venix.com>
	<7ef05c9243109f52c7a849eaf9ae69e5840e50f5.camel@venix.com>
	<CAEvgogEiyE7a5DKONS_fEgjdf6HW8w+Ms2LpU6w8e_qOqWgsGg@mail.gmail.com>
	<8edad52bead51c3c541bcda90b530a3f79d68414.camel@venix.com>
	<CAEHDbABHn5iqg9=SgA5JCkEdQ7GYgtj-bXUdm3=vbx9kQxrMTQ@mail.gmail.com>
	<66b1d4c8a917e96a00cd85b34ba7e711a1cb1be9.camel@venix.com>
Message-ID: <CAEvgogE2Q8L3aPi29Wb1m77sBmB2+OuK5NGwmVOEMtMm3xP3Gw@mail.gmail.com>

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 

From dragonhawk at gmail.com  Tue Jun  2 19:57:20 2020
From: dragonhawk at gmail.com (Ben Scott)
Date: Tue, 2 Jun 2020 19:57:20 -0400
Subject: upgraded to Fedora 32 from Fedora 30 -- libvirtd no longer runs
In-Reply-To: <66b1d4c8a917e96a00cd85b34ba7e711a1cb1be9.camel@venix.com>
References: <3a39213b4a2aa39e57383e142312f51bb09010f3.camel@venix.com>
	<CAEvgogGnxuQT5euQvWjwBAw83VeDgUBfhe66pEF_j2Mnk_ujzw@mail.gmail.com>
	<75776ae40f92c42000d3be5341ba5a73a394e973.camel@venix.com>
	<7ef05c9243109f52c7a849eaf9ae69e5840e50f5.camel@venix.com>
	<CAEvgogEiyE7a5DKONS_fEgjdf6HW8w+Ms2LpU6w8e_qOqWgsGg@mail.gmail.com>
	<8edad52bead51c3c541bcda90b530a3f79d68414.camel@venix.com>
	<CAEHDbABHn5iqg9=SgA5JCkEdQ7GYgtj-bXUdm3=vbx9kQxrMTQ@mail.gmail.com>
	<66b1d4c8a917e96a00cd85b34ba7e711a1cb1be9.camel@venix.com>
Message-ID: <CAE=no6FbEud3b-JR+HQMvf_+=LzOijKopnE0k8wCsJUSY6Sc4w@mail.gmail.com>

On Mon, Jun 1, 2020 at 5:54 PM Lloyd Kvam <lkvam at venix.com> wrote:
> I hope I did not burden you with excessive emails.

This is the most interesting thread we've had on this list for months.  ;-)

-- Ben

From ken at jots.org  Fri Jun  5 00:16:48 2020
From: ken at jots.org (Ken D'Ambrosio)
Date: Fri, 05 Jun 2020 00:16:48 -0400
Subject: Access public IP from NAT.
Message-ID: <ba3f7d668385b577943bd4ecc0bec0b3@jots.org>

Hey, all.  So I finally yanked my Comcast modem ("for reasons," largely
having to do with lack of static routes), and put in my own cable modem,
a WAP, and a RasPi-4 that's doing routing/NAT.  It all works great. 
But... I have services exposed that I want to access on the public IP. 
It works *great* from out there, but if I try to access the public IP
from my NATted network, no dice.  And, sadly, if there's one Linux place
where there's a truck-sized hole in my knowledge, it's IP Tables.  I've
googled the Interwebs to no avail on what magic IPTables stuff would be
needed to make it work.  Here's my current script:

root at ubuntu:/usr/local/bin# cat start-NAT.sh 
#!/bin/bash
export PUBLIC=eth1
export PRIVATE=eth0

echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -t nat -A POSTROUTING -o $PUBLIC -j MASQUERADE
iptables -A FORWARD -i $PUBLIC -o $PRIVATE -m state --state
RELATED,ESTABLISHED -j ACCEPT
iptables -A FORWARD -i $PRIVATE -o $PUBLIC -j ACCEPT

=====================================================================================================
root at ubuntu:/usr/local/bin# cat start-port-forwarding.sh 
#!/bin/bash

export PRIVATE=eth0
export PRIV_IP=192.168.10.1
export PUBLIC=eth1 
export JELLYFIN=192.168.10.12 

iptables -A FORWARD -i $PUBLIC -o $PRIVATE -p tcp --syn --dport 8096 -m
conntrack --ctstate NEW -j ACCEPT
iptables -A FORWARD -i $PUBLIC -o $PRIVATE -m conntrack --ctstate
ESTABLISHED,RELATED -j ACCEPT
iptables -A FORWARD -i $PRIVATE -o $PUBLIC -m conntrack --ctstate
ESTABLISHED,RELATED -j ACCEPT
iptables -P FORWARD DROP
iptables -t nat -A PREROUTING -i $PUBLIC -p tcp --dport 8096 -j DNAT
--to-destination $JELLYFIN
iptables -t nat -A POSTROUTING -o $PRIVATE -p tcp --dport 8096 -d
$JELLYFIN -j SNAT --to-source $PRIV_IP
=====================================================================================================
If anyone could be kind enough to let me know what extra magic(tm) I
need to employ to get at my public IP from inside, I'd be most
interested to hear. 

Thanks! 

-Ken
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.gnhlug.org/pipermail/gnhlug-discuss/attachments/20200605/091ebd84/attachment.html 

From lkvam at venix.com  Fri Jun  5 08:04:19 2020
From: lkvam at venix.com (Lloyd Kvam)
Date: Fri, 05 Jun 2020 08:04:19 -0400
Subject: Access public IP from NAT.
In-Reply-To: <ba3f7d668385b577943bd4ecc0bec0b3@jots.org>
References: <ba3f7d668385b577943bd4ecc0bec0b3@jots.org>
Message-ID: <a52a9646aa6202a6f83c557d310895eef0a7e9d8.camel@venix.com>

My approach has been to provide the external names to dnsmasq so that the names are attached to
the correct IP address at home and away.

I'm using an IQrouter (runs openWRT) which makes this pretty painless to setup.

To be clear:
from outside my office on the net
   $ host www.venix.com
www.venix.com has address 68.238.56.186

from in my office (I'm using the 172.x.x.x private address space as a holdover from running
Lede and the buffer bloat software)

   $ host www.lan
www.lan has address 172.30.42.28

$ host www.venix.com
www.venix.com has address 172.30.42.28

That's not what you asked for, but it might fit your needs. With my openWRT based router, the
advanced menu provide Network / Hostnames which supplements the DHCP name/address resolution in
dnsmasq. You can figure out the setup on your RasPi to add the required host entries.

(For those hosts that need to be visible to the broader Internet, I use port forwarding through
the firewall.)

On Fri, 2020-06-05 at 00:16 -0400, Ken D'Ambrosio wrote:
> Hey, all.  So I finally yanked my Comcast modem ("for reasons," largely
> having to do with lack of static routes), and put in my own cable modem,
> a WAP, and a RasPi-4 that's doing routing/NAT.  It all works great. 
> But... I have services exposed that I want to access on the public IP. 
> It works *great* from out there, but if I try to access the public IP
> from my NATted network, no dice.  And, sadly, if there's one Linux place
> where there's a truck-sized hole in my knowledge, it's IP Tables.  I've
> googled the Interwebs to no avail on what magic IPTables stuff would be
> needed to make it work.  Here's my current script:
> 
> root at ubuntu:/usr/local/bin# cat start-NAT.sh 
> #!/bin/bash
> export PUBLIC=eth1
> export PRIVATE=eth0
> 
> echo 1 > /proc/sys/net/ipv4/ip_forward
> iptables -t nat -A POSTROUTING -o $PUBLIC -j MASQUERADE
> iptables -A FORWARD -i $PUBLIC -o $PRIVATE -m state --state
> RELATED,ESTABLISHED -j ACCEPT
> iptables -A FORWARD -i $PRIVATE -o $PUBLIC -j ACCEPT
> 
> =============================================================================================
> ========
> root at ubuntu:/usr/local/bin# cat start-port-forwarding.sh 
> #!/bin/bash
> 
> export PRIVATE=eth0
> export PRIV_IP=192.168.10.1
> export PUBLIC=eth1 
> export JELLYFIN=192.168.10.12 
> 
> iptables -A FORWARD -i $PUBLIC -o $PRIVATE -p tcp --syn --dport 8096 -m
> conntrack --ctstate NEW -j ACCEPT
> iptables -A FORWARD -i $PUBLIC -o $PRIVATE -m conntrack --ctstate
> ESTABLISHED,RELATED -j ACCEPT
> iptables -A FORWARD -i $PRIVATE -o $PUBLIC -m conntrack --ctstate
> ESTABLISHED,RELATED -j ACCEPT
> iptables -P FORWARD DROP
> iptables -t nat -A PREROUTING -i $PUBLIC -p tcp --dport 8096 -j DNAT
> --to-destination $JELLYFIN
> iptables -t nat -A POSTROUTING -o $PRIVATE -p tcp --dport 8096 -d
> $JELLYFIN -j SNAT --to-source $PRIV_IP
> =============================================================================================
> ========
> If anyone could be kind enough to let me know what extra magic(tm) I
> need to employ to get at my public IP from inside, I'd be most
> interested to hear. 
> 
> Thanks! 
> 
> -Ken
> _______________________________________________
> 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



From mkomarinski at wayga.org  Fri Jun  5 08:13:10 2020
From: mkomarinski at wayga.org (Mark Komarinski)
Date: Fri, 05 Jun 2020 08:13:10 -0400
Subject: Access public IP from NAT.
In-Reply-To: <a52a9646aa6202a6f83c557d310895eef0a7e9d8.camel@venix.com>
References: <ba3f7d668385b577943bd4ecc0bec0b3@jots.org>
	<a52a9646aa6202a6f83c557d310895eef0a7e9d8.camel@venix.com>
Message-ID: <308EF915-19EE-4257-8377-16CD95676834@wayga.org>

I think that's the problem.  Check your DNS and see which IP you're getting when you put the external name in.

On June 5, 2020 8:04:19 AM EDT, Lloyd Kvam <lkvam at venix.com> wrote:
>My approach has been to provide the external names to dnsmasq so that
>the names are attached to
>the correct IP address at home and away.
>
>I'm using an IQrouter (runs openWRT) which makes this pretty painless
>to setup.
>
>To be clear:
>from outside my office on the net
>   $ host www.venix.com
>www.venix.com has address 68.238.56.186
>
>from in my office (I'm using the 172.x.x.x private address space as a
>holdover from running
>Lede and the buffer bloat software)
>
>   $ host www.lan
>www.lan has address 172.30.42.28
>
>$ host www.venix.com
>www.venix.com has address 172.30.42.28
>
>That's not what you asked for, but it might fit your needs. With my
>openWRT based router, the
>advanced menu provide Network / Hostnames which supplements the DHCP
>name/address resolution in
>dnsmasq. You can figure out the setup on your RasPi to add the required
>host entries.
>
>(For those hosts that need to be visible to the broader Internet, I use
>port forwarding through
>the firewall.)
>
>On Fri, 2020-06-05 at 00:16 -0400, Ken D'Ambrosio wrote:
>> Hey, all.  So I finally yanked my Comcast modem ("for reasons,"
>largely
>> having to do with lack of static routes), and put in my own cable
>modem,
>> a WAP, and a RasPi-4 that's doing routing/NAT.  It all works great. 
>> But... I have services exposed that I want to access on the public
>IP. 
>> It works *great* from out there, but if I try to access the public IP
>> from my NATted network, no dice.  And, sadly, if there's one Linux
>place
>> where there's a truck-sized hole in my knowledge, it's IP Tables. 
>I've
>> googled the Interwebs to no avail on what magic IPTables stuff would
>be
>> needed to make it work.  Here's my current script:
>> 
>> root at ubuntu:/usr/local/bin# cat start-NAT.sh 
>> #!/bin/bash
>> export PUBLIC=eth1
>> export PRIVATE=eth0
>> 
>> echo 1 > /proc/sys/net/ipv4/ip_forward
>> iptables -t nat -A POSTROUTING -o $PUBLIC -j MASQUERADE
>> iptables -A FORWARD -i $PUBLIC -o $PRIVATE -m state --state
>> RELATED,ESTABLISHED -j ACCEPT
>> iptables -A FORWARD -i $PRIVATE -o $PUBLIC -j ACCEPT
>> 
>>
>=============================================================================================
>> ========
>> root at ubuntu:/usr/local/bin# cat start-port-forwarding.sh 
>> #!/bin/bash
>> 
>> export PRIVATE=eth0
>> export PRIV_IP=192.168.10.1
>> export PUBLIC=eth1 
>> export JELLYFIN=192.168.10.12 
>> 
>> iptables -A FORWARD -i $PUBLIC -o $PRIVATE -p tcp --syn --dport 8096
>-m
>> conntrack --ctstate NEW -j ACCEPT
>> iptables -A FORWARD -i $PUBLIC -o $PRIVATE -m conntrack --ctstate
>> ESTABLISHED,RELATED -j ACCEPT
>> iptables -A FORWARD -i $PRIVATE -o $PUBLIC -m conntrack --ctstate
>> ESTABLISHED,RELATED -j ACCEPT
>> iptables -P FORWARD DROP
>> iptables -t nat -A PREROUTING -i $PUBLIC -p tcp --dport 8096 -j DNAT
>> --to-destination $JELLYFIN
>> iptables -t nat -A POSTROUTING -o $PRIVATE -p tcp --dport 8096 -d
>> $JELLYFIN -j SNAT --to-source $PRIV_IP
>>
>=============================================================================================
>> ========
>> If anyone could be kind enough to let me know what extra magic(tm) I
>> need to employ to get at my public IP from inside, I'd be most
>> interested to hear. 
>> 
>> Thanks! 
>> 
>> -Ken
>> _______________________________________________
>> 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
>
>
>_______________________________________________
>gnhlug-discuss mailing list
>gnhlug-discuss at mail.gnhlug.org
>http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.gnhlug.org/pipermail/gnhlug-discuss/attachments/20200605/53620367/attachment.html 

From r270 at mrt4.com  Sat Jun  6 11:35:32 2020
From: r270 at mrt4.com (r270 at mrt4.com)
Date: Sat, 6 Jun 2020 11:35:32 -0400
Subject: Access public IP from NAT.
In-Reply-To: <ba3f7d668385b577943bd4ecc0bec0b3@jots.org>
References: <ba3f7d668385b577943bd4ecc0bec0b3@jots.org>
Message-ID: <20200606113532.000f494f7fe9b60ab8e23eab@mrt4.com>

Try removing "-i $PUBLIC" from the first nat table spec in "start-port-forwarding.sh" so it reads:
iptables -t nat -A PREROUTING -p tcp --dport 8096 -j DNAT --to-destination $JELLYFIN

Also, if any of your inside clients use UDP for DNS, you'll need to create specific rules for that.

If that doesn't fix it, let us know what your exact physical network topology is (which device is connected to which and to which interface each is connected).

Also, use iptables -L -n to verify that everything you put in your scripts are actually being applied to Netfilter and that nothing else is in there. (As a sanity check, you should flush the tables (iptables -F) and reset policies for each (iptables -P <tablename> DROP) at the beginning of your first script.)

Ron
r270 at mrt4.com

--------------

On Fri, 05 Jun 2020 00:16:48 -0400
"Ken D'Ambrosio" <ken at jots.org> wrote:

> Hey, all.  So I finally yanked my Comcast modem ("for reasons," largely
> having to do with lack of static routes), and put in my own cable modem,
> a WAP, and a RasPi-4 that's doing routing/NAT.  It all works great. 
> But... I have services exposed that I want to access on the public IP. 
> It works *great* from out there, but if I try to access the public IP
> from my NATted network, no dice.  And, sadly, if there's one Linux place
> where there's a truck-sized hole in my knowledge, it's IP Tables.  I've
> googled the Interwebs to no avail on what magic IPTables stuff would be
> needed to make it work.  Here's my current script:
> 
> root at ubuntu:/usr/local/bin# cat start-NAT.sh 
> #!/bin/bash
> export PUBLIC=eth1
> export PRIVATE=eth0
> 
> echo 1 > /proc/sys/net/ipv4/ip_forward
> iptables -t nat -A POSTROUTING -o $PUBLIC -j MASQUERADE
> iptables -A FORWARD -i $PUBLIC -o $PRIVATE -m state --state
> RELATED,ESTABLISHED -j ACCEPT
> iptables -A FORWARD -i $PRIVATE -o $PUBLIC -j ACCEPT
> 
> =====================================================================================================
> root at ubuntu:/usr/local/bin# cat start-port-forwarding.sh 
> #!/bin/bash
> 
> export PRIVATE=eth0
> export PRIV_IP=192.168.10.1
> export PUBLIC=eth1 
> export JELLYFIN=192.168.10.12 
> 
> iptables -A FORWARD -i $PUBLIC -o $PRIVATE -p tcp --syn --dport 8096 -m
> conntrack --ctstate NEW -j ACCEPT
> iptables -A FORWARD -i $PUBLIC -o $PRIVATE -m conntrack --ctstate
> ESTABLISHED,RELATED -j ACCEPT
> iptables -A FORWARD -i $PRIVATE -o $PUBLIC -m conntrack --ctstate
> ESTABLISHED,RELATED -j ACCEPT
> iptables -P FORWARD DROP
> iptables -t nat -A PREROUTING -i $PUBLIC -p tcp --dport 8096 -j DNAT
> --to-destination $JELLYFIN
> iptables -t nat -A POSTROUTING -o $PRIVATE -p tcp --dport 8096 -d
> $JELLYFIN -j SNAT --to-source $PRIV_IP
> =====================================================================================================
> If anyone could be kind enough to let me know what extra magic(tm) I
> need to employ to get at my public IP from inside, I'd be most
> interested to hear. 
> 
> Thanks! 
> 
> -Ken

From gaf.linux at gmail.com  Wed Jun 10 08:43:56 2020
From: gaf.linux at gmail.com (Jerry Feldman)
Date: Wed, 10 Jun 2020 08:43:56 -0400
Subject: Boston Linux VIRTUAL Meeting Wednesday, June 17, 2020 How Many Ways
	Can You Fail? A Taxonomy of Corporate (in)Decision
Message-ID: <7400a567-b157-6227-0f82-e91fa69772c2@gmail.com>



When: June 17, 2020 7:00PM (6:30PM for Q&A)
Topic: How Many Ways Can You Fail? A Taxonomy of Corporate (in)Decision
Moderators: Federico Lucifredi
Location: Via Bluejeans Meeting ID TBA
Meeting will be streamed on YouTube; TBA


We will be using the Bluejeans Conferencing system. We will
also be streaming through YouTube as listed above.


*Summary*

Federico shares battle stories from fifteen years in technology management


*Abstract*

Details to follow


Bio
Federico Lucifredi is The Ceph Storage Product Management Director at 
Red Hat, formerly the Ubuntu Server PM at Canonical, and the Linux 
?Systems Management Czar? at SUSE.For further information and directions 
please consult the BLU Web site:
http://www.blu.org
--
Jerry Feldman <gaf.linux at gmail.com <mailto: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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.gnhlug.org/pipermail/gnhlug-discuss/attachments/20200610/1fa200a0/attachment.html 

From gaf.linux at gmail.com  Tue Jun 16 12:53:20 2020
From: gaf.linux at gmail.com (Jerry Feldman)
Date: Tue, 16 Jun 2020 12:53:20 -0400
Subject: Boston Linux VIRTUAL Meeting Reminder Wednesday, June 17, 2020 How
	Many Ways Can You Fail? A Taxonomy of Corporate (in)Decision
Message-ID: <CAEvgogFVq6f0k09dzR1wGq-PG3PxVssxZk9eag=umTY0-csrYQ@mail.gmail.com>

When: Wednesday June 17, 2020 6:30 Q&A, 7:00 Speaker
Topic: How Many Ways Can You Fail? A Taxonomy of Corporate (in)Decision
Moderator:  Federico Lucifredi
Location: online via BlueJeans
Link to Wednesday's BlueJeans meeting: *https://bluejeans.com/654265524
<https://bluejeans.com/654265524>*
Note: We will post the recording within 24 to 48 hours after the meeting


*Summary:*
Federico shares battle stories from fifteen years in technology management

*Abstract:*
Decision-making in the modern corporation is riddled with paradox: the
outward declared objective of the organization, has to contend with all too
human realities ranging from the Peter Principle to having too many cooks
in the kitchen, to the individual's perfectionism, indecision, or even
straight up cowardice. Decisions that are the lifeblood of your project can
be deferred, avoided, or derailed in perfectly legitimate and even
well-meaning ways. This can spell death for what you were tasked to build,
as success depends on implementation as much as on a good idea. You cannot
execute if decisions are not prompt, mostly correct, and accepted by the
team.

We dissect how decisions do *not* happen, and what you can do about it.
Success in business depends on getting things done. Join us as we explore
the lost art of thinking in the corporation, and what you as a tiny but
revolutionary-minded cog can do about it.

*Bio:*
Federico Lucifredi is The Ceph Storage Product Management Director at Red
Hat, formerly the Ubuntu Server PM at Canonical, and the Linux ?Systems
Management Czar? at SUSE.
-- 
--
Jerry Feldman <gaf.linux at gmail.com>
Boston Linux and Unix
PGP key id: 6F6BB6E7
Key fingerprint: 0EDC 2FF5 53A6 8EED 84D1  3050 5715 B88D 6F6B B6E7
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.gnhlug.org/pipermail/gnhlug-discuss/attachments/20200616/488b8835/attachment.html 

From dan at garthwaite.org  Tue Jun 23 14:58:52 2020
From: dan at garthwaite.org (Dan Garthwaite)
Date: Tue, 23 Jun 2020 14:58:52 -0400
Subject: $5/mo to sponsor linux multitouch touchpad support
Message-ID: <CAGrNZ+=QwMmjONd6RFsPSuk1K3tKCE--CbhWvx_EXxJFdE6+_w@mail.gmail.com>

I just saw on hacker news that this project has some legs and I signed up
as a $5 sponsor.

https://github.com/sponsors/gitclear

It's just one of those things standing in the way of widespread linux
adoption.  I'm a lifelong vim user, don't even own a mouse, and for me the
lack of multitouch gestures are galling. Everyone benefits if more people
pick linux for their daily driver and I perceive this outstanding issue as
a blocker.  If in a year I'm still making payments I'll reconsider but in
the meantime it is an easy decision for me to kick in a coffee to these
folks every month to coordinate the effort.

  Dan Garthwaite, Manchester, NH
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.gnhlug.org/pipermail/gnhlug-discuss/attachments/20200623/b81bd635/attachment.html 

From rozzin at hackerposse.com  Fri Jun 26 19:41:41 2020
From: rozzin at hackerposse.com (Joshua Judson Rosen)
Date: Fri, 26 Jun 2020 19:41:41 -0400
Subject: $5/mo to sponsor linux multitouch touchpad support
In-Reply-To: <CAGrNZ+=QwMmjONd6RFsPSuk1K3tKCE--CbhWvx_EXxJFdE6+_w@mail.gmail.com>
References: <CAGrNZ+=QwMmjONd6RFsPSuk1K3tKCE--CbhWvx_EXxJFdE6+_w@mail.gmail.com>
Message-ID: <92d1a3e2-a70b-b4f9-371c-8a7e2c06ff1c@hackerposse.com>

On 6/23/20 2:58 PM, Dan Garthwaite wrote:
> I just saw on hacker news that this project has some legs and I signed up as a $5 sponsor.
> 
> https://github.com/sponsors/gitclear
> 
> It's just one of those things standing in the way of widespread linux adoption.? I'm a lifelong vim user,?don't even own a mouse, and for me the lack of multitouch gestures are galling.

What specifically does "multitouch" or "multitouch gesters" mean in this context?

I've only skimmed through that series of articles/comments, but it looks like that term that people
*use* repeatedly but never bother to define or explain.

Does it mean something like... "pinch-zooming + 3-finger-slide to go back/forward in web-browsers"?
Or is it something like "2-finger tap for right-click"? (because apparently the author thinks
that functionality doesn't exist with synaptics, referring to some
"need to click in the bottom right corner to effect a right click"?)
Some combination of all of those things?

(I'm not asking from the perspective of ignorance/oblivion; I've been using a TouchStream for almost 20 years,
  and watching as various touch technologies, techniques, UIs, and featuresets have gone in and out of fashion
  in that time..., so when I say "what do you mean by `multitouch'?", it's because I just can't guess anymore at
  which particular tiny subset of multitouch functionality people think they're clever or exalted for knowing about...).

Also..., I really don't get this "if only we could make it as good as Mac OS!" angles. At all--really;
someone explain it to me? This is going to sound like indignation..., and maybe it is?
I think it's actually just remembering frustration, and getting cynical after too many years of "splaining"...:

It's been maybe 5 years since I actually tried to use Mac OS..., but I remember basically
being blown over by how so much in Mac OS just felt like "cheap and chintzy"--
in a lot of ways, but specifically *including the touchpad input*.

This was relative to the synaptics Xorg driver at the time--if libinput even existed, I didn't have it yet..., though now that
everything seems to be moving to libinput and dropping support for synaptics, touchpad support on Linux systems does seem
to finally be getting bad enough to be comparable with what I remember from Mac OS....

IIRC Mac OS had no support for *any* of...:

	* circular scrolling?
	* locked drags?
	* edge motion?
	* pressure-sensitive pointer speed?

Does it have any of those today? A quick websearch turns up stuff like this:

	https://apple.stackexchange.com/questions/85882/how-to-right-drag-using-trackpad-only-for-windows-on-macbook

... which seems to indicate that there's actually not even a way to secondary-click-and-drag in Mac OS?

Whaaat? And I'm guessing the whole idea of "middle-drag" is just complete crazytalk to Mac users?

Though..., I don't know--most of the reason I care about secondary and tertiary drag
is for window-management, which which was another whole chapter of the
"you have got to be kidding me where are my affordances" saga...; if I could accept the
overall lack of window-management affordances, I guess maybe I wouldn't notice
the little thing being missing?

-- 
Connect with me on the GNU social network! <https://status.hackerposse.com/rozzin>
Not on the network? Ask me for more info!