Re: ImportError: No module named libvirt

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

On Wed, 15 Sept 2021 at 13:59, Mario Marietto <marietto2008%gmail.com@localhost> wrote:
>
> Correct me if I'm wrong,but KVM is not supported by NetBSD,right ? So,it's not natural that on the virt-manager panel I see "QEMU-KVM not connected" and if I try to connect it gives the error : Client socket identity not available: Function not implemented ?
>
> Anyway I can't test if a different hypervisor works. I can choose between XEN / LXC / Bhyve / Virtuozzo,but :
>
> 1) I haven't installed and configured XEN and virtuozzo
>
> 2) Bhyve is not supported by NetBSD
>
> 3) I have configured NVMM but it is not on the list at all

NVMM is just a QEMU acceleration method; I thought I had to select
QEMU/local from the drop-down menu, but could not figure out the
authentication bit.

>
>
>
>
>
> Il giorno mer 15 set 2021 alle ore 13:54 Chavdar Ivanov <ci4ic4%gmail.com@localhost> ha scritto:
>>
>> On Wed, 15 Sept 2021 at 12:06, Mario Marietto <marietto2008%gmail.com@localhost> wrote:
>> >
>> > netbsd-marietto# service libvirtd start
>> >
>> > libvirtd already running? (pid=598).
>> >
>> >
>> > Unable to connect to libvirt qemu:///system.
>> >
>> > Client socket identity not available: Function not implemented
>> >
>> > Libvirt URI is: qemu:///system
>> >
>> > Traceback (most recent call last):
>> >   File "/usr/pkg/share/virt-manager/virtManager/connection.py", line 956, in _do_open
>> >     self._backend.open(connectauth.creds_dialog, self)
>> >   File "/usr/pkg/share/virt-manager/virtinst/connection.py", line 172, in open
>> >     conn = libvirt.openAuth(self._open_uri,
>> >   File "/usr/pkg/lib/python3.8/site-packages/libvirt.py", line 104, in openAuth
>>
>> That's what I reported earlier (albeit with python39).  I couldn't
>> figure it out quickly and haven't yet poked libvirt.py.
>>
>> >
>> > Il giorno mar 14 set 2021 alle ore 22:57 Chavdar Ivanov <ci4ic4%gmail.com@localhost> ha scritto:
>> >>
>> >> On Tue, 14 Sept 2021 at 21:33, Mario Marietto <marietto2008%gmail.com@localhost> wrote:
>> >> >
>> >> > You have a lot of experience with NetBSD,have you been able to pass through your graphic card using qemu and nvmm ? Is that possible ? Do you have a tutorial to suggest where I can learn how to do that ? I'm looking for a BSD os that can allows me to passthru my nvidia RTX 2080 ti to a linux guest os. I tried with freebsd and bhyve,but it didn't work. So,now I want to try try with qemu + nvmm. thanks very much.
>> >> >
>> >>
>> >> While I do use daily qemu+nvmm, I have never attempted to pass through
>> >> any device to any VM. I was tempted to say you can't do it, but I
>> >> can't say even that - qemu has a lot of trickeries I am not aware of.
>> >> I really don't know, sorry.
>> >>
>> >>
>> >> > Il giorno mar 14 set 2021 alle ore 20:37 Chavdar Ivanov <ci4ic4%gmail.com@localhost> ha scritto:
>> >> >>
>> >> >> On Tue, 14 Sept 2021 at 19:33, Mario Marietto <marietto2008%gmail.com@localhost> wrote:
>> >> >> >
>> >> >> > Great help from you. Finally I've been able to see the GUI of virt-manager. Now it wants that I make the installation of the libvirtd service. I'm learning how to do that. very thanks for your patience with a newbie.
>> >> >>
>> >> >> No worries. Do this:
>> >> >>
>> >> >> cp /usr/pkg/share/examples/rc.d/libvirtd /etc/rc.d/ && echo
>> >> >> libvirtd=YES >> /etc/rc.conf && /etc/rc.d/libvirtd start
>> >> >>
>> >> >> as root.
>> >> >>
>> >> >> >
>> >> >> > Il giorno mar 14 set 2021 alle ore 20:02 Chavdar Ivanov <ci4ic4%gmail.com@localhost> ha scritto:
>> >> >> >>
>> >> >> >> On Tue, 14 Sept 2021 at 18:50, Mario Marietto <marietto2008%gmail.com@localhost> wrote:
>> >> >> >> >
>> >> >> >> > Yes,I've already removed it. Did you read my previous message well ?
>> >> >> >> >
>> >> >> >> > netbsd-marietto# pkgin remove virtinst
>> >> >> >> >
>> >> >> >> > 1 packages to delete:
>> >> >> >> >   virtinst-0.600.3nb3
>> >> >> >> >
>> >> >> >> > proceed ? [Y/n] y
>> >> >> >> > removing virtinst-0.600.3nb3...
>> >> >> >> > pkg_install warnings: 0, errors: 0
>> >> >> >> > reading local summary...
>> >> >> >> > processing local summary...
>> >> >> >> > netbsd-marietto# make install
>> >> >> >> > => Bootstrap dependency digest>=20010302: found digest-20190127
>> >> >> >> > ===> Installing binary package of virt-manager-2.2.1
>> >> >> >> >
>> >> >> >> > netbsd-marietto# virt-manager
>> >> >> >> >
>> >> >> >> > Traceback (most recent call last):
>> >> >> >> >   File "/usr/pkg/share/virt-manager/virt-manager", line 19, in <module>
>> >> >> >> >     from virtinst import BuildConfig
>> >> >> >> >   File "/usr/pkg/share/virt-manager/virtinst/__init__.py", line 60, in <module>
>> >> >> >> >     from virtinst.install.installer import Installer
>> >> >> >> >   File "/usr/pkg/share/virt-manager/virtinst/install/installer.py", line 12, in <module>
>> >> >> >> >     from .installertreemedia import InstallerTreeMedia
>> >> >> >> >   File "/usr/pkg/share/virt-manager/virtinst/install/installertreemedia.py", line 10, in <module>
>> >> >> >> >     from . import urlfetcher
>> >> >> >> >   File "/usr/pkg/share/virt-manager/virtinst/install/urlfetcher.py", line 16, in <module>
>> >> >> >> >     import requests
>> >> >> >> > ModuleNotFoundError: No module named 'requests'
>> >> >> >>
>> >> >> >> Another missing run-time dependency - devel/py-requests
>> >> >> >>
>> >> >> >>  >
>> >> >> >> >
>> >> >> >> > Il giorno mar 14 set 2021 alle ore 19:29 Chavdar Ivanov <ci4ic4%gmail.com@localhost> ha scritto:
>> >> >> >> >>
>> >> >> >> >> virtinst that is...
>> >> >> >> >>
>> >> >> >> >> On Tue, 14 Sept 2021 at 18:28, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:
>> >> >> >> >> >
>> >> >> >> >> > vistinst is an old package you can remove. I last built it in about
>> >> >> >> >> > 2019 and don't remember using it.
>> >> >> >> >> >
>> >> >> >> >> > On Tue, 14 Sept 2021 at 18:01, Mario Marietto <marietto2008%gmail.com@localhost> wrote:
>> >> >> >> >> > >
>> >> >> >> >> > > netbsd-marietto# pwd
>> >> >> >> >> > >
>> >> >> >> >> > > /usr/pkgsrc/wip/virt-manager
>> >> >> >> >> > >
>> >> >> >> >> > > netbsd-marietto# make install
>> >> >> >> >> > >
>> >> >> >> >> > > ....
>> >> >> >> >> > >
>> >> >> >> >> > > compiling gsettings schemas
>> >> >> >> >> > > glib-compile-schemas /usr/pkgsrc/wip/virt-manager/work/.destdir/usr/pkg/share/glib-2.0/schemas
>> >> >> >> >> > > running install_egg_info
>> >> >> >> >> > > => Automatic manual page handling
>> >> >> >> >> > > => Generating post-install file lists
>> >> >> >> >> > > => Checking file-check results for virt-manager-2.2.1
>> >> >> >> >> > > => Creating binary package /usr/pkgsrc/wip/virt-manager/work/.packages/virt-manager-2.2.1.tgz
>> >> >> >> >> > > ===> Building binary package for virt-manager-2.2.1
>> >> >> >> >> > > => Creating binary package /usr/pkgsrc/packages/All/virt-manager-2.2.1.tgz
>> >> >> >> >> > > ===> Installing binary package of virt-manager-2.2.1
>> >> >> >> >> > > pkg_add: Conflicting PLIST with virtinst-0.600.3nb3: bin/virt-clone
>> >> >> >> >> > > pkg_add: 1 package addition failed
>> >> >> >> >> > > *** Error code 1
>> >> >> >> >> > >
>> >> >> >> >> > > netbsd-marietto# pkgin remove virtinst
>> >> >> >> >> > >
>> >> >> >> >> > > 1 packages to delete:
>> >> >> >> >> > >   virtinst-0.600.3nb3
>> >> >> >> >> > >
>> >> >> >> >> > > proceed ? [Y/n] y
>> >> >> >> >> > > removing virtinst-0.600.3nb3...
>> >> >> >> >> > > pkg_install warnings: 0, errors: 0
>> >> >> >> >> > > reading local summary...
>> >> >> >> >> > > processing local summary...
>> >> >> >> >> > > netbsd-marietto# make install
>> >> >> >> >> > > => Bootstrap dependency digest>=20010302: found digest-20190127
>> >> >> >> >> > > ===> Installing binary package of virt-manager-2.2.1
>> >> >> >> >> > >
>> >> >> >> >> > > netbsd-marietto# virt-manager
>> >> >> >> >> > >
>> >> >> >> >> > > Traceback (most recent call last):
>> >> >> >> >> > >   File "/usr/pkg/share/virt-manager/virt-manager", line 19, in <module>
>> >> >> >> >> > >     from virtinst import BuildConfig
>> >> >> >> >> > >   File "/usr/pkg/share/virt-manager/virtinst/__init__.py", line 60, in <module>
>> >> >> >> >> > >     from virtinst.install.installer import Installer
>> >> >> >> >> > >   File "/usr/pkg/share/virt-manager/virtinst/install/installer.py", line 12, in <module>
>> >> >> >> >> > >     from .installertreemedia import InstallerTreeMedia
>> >> >> >> >> > >   File "/usr/pkg/share/virt-manager/virtinst/install/installertreemedia.py", line 10, in <module>
>> >> >> >> >> > >     from . import urlfetcher
>> >> >> >> >> > >   File "/usr/pkg/share/virt-manager/virtinst/install/urlfetcher.py", line 16, in <module>
>> >> >> >> >> > >     import requests
>> >> >> >> >> > > ModuleNotFoundError: No module named 'requests'
>> >> >> >> >> > >
>> >> >> >> >> > >
>> >> >> >> >> > >
>> >> >> >> >> > >
>> >> >> >> >> > > Il giorno mar 14 set 2021 alle ore 18:40 Chavdar Ivanov <ci4ic4%gmail.com@localhost> ha scritto:
>> >> >> >> >> > >>
>> >> >> >> >> > >> On Tue, 14 Sept 2021 at 17:11, Thomas Klausner <wiz%netbsd.org@localhost> wrote:
>> >> >> >> >> > >> >
>> >> >> >> >> > >> > On Tue, Sep 14, 2021 at 06:04:49PM +0200, Mario Marietto wrote:
>> >> >> >> >> > >> > > ERROR: [depends.mk] The directory \`../../wip/vte'' does not exist.`
>> >> >> >> >> > >> >
>> >> >> >> >> > >> > If you see this, your checkout is not up-to-date.
>> >> >> >> >> > >> > There is no reference to wip/vte in the latest version. Please update.
>> >> >> >> >> > >> >  Thomas
>> >> >> >> >> > >>
>> >> >> >> >> > >> That's true. In the latest wip/virt-manager Makefile, the reference to
>> >> >> >> >> > >> wip/vte has been replaced with x11/vte3; that's obvious; however, in
>> >> >> >> >> > >> order to be sure everything is current, one has to update the whole
>> >> >> >> >> > >> pkgsrc tree ( cd /usr/pkgsrc && cvs up -dPA ) - which then will
>> >> >> >> >> > >> require 'pkg_rolling-replace' etc. I do the latter all the time, once
>> >> >> >> >> > >> or twice a week, first 'git pull' in pkgsrc/wip, then the pkgsrc
>> >> >> >> >> > >> update, then 'pkg_rolling-replace -uvk', followed by manually chasing
>> >> >> >> >> > >> all possible failures of the latter; also, before running the rolling
>> >> >> >> >> > >> replace command, I run 'pkg_admin rebuild-tree', making sure it
>> >> >> >> >> > >> returns nothing (or something I expect and have decided not to
>> >> >> >> >> > >> correct), followed by a 'pkg_chk -uq' - which I expect to finish to
>> >> >> >> >> > >> the end (which is the complain that there is no
>> >> >> >> >> > >> /usr/pkgsrc/pkgchk_update-{build-hostname}.conf present in my case).
>> >> >> >> >> > >>
>> >> >> >> >> > >> Just stating my usual workflow for pkgsrc+wip updates, in case it is useful.
>> >> >> >> >> > >>
>> >> >> >> >> > >>
>> >> >> >> >> > >> --
>> >> >> >> >> > >> ----
>> >> >> >> >> > >
>> >> >> >> >> > >
>> >> >> >> >> > >
>> >> >> >> >> > > --
>> >> >> >> >> > > Mario.
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> >
>> >> >> >> >> > --
>> >> >> >> >> > ----
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> --
>> >> >> >> >> ----
>> >> >> >> >
>> >> >> >> >
>> >> >> >> >
>> >> >> >> > --
>> >> >> >> > Mario.
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> ----
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > Mario.
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> ----
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Mario.
>> >>
>> >>
>> >>
>> >> --
>> >> ----
>> >
>> >
>> >
>> > --
>> > Mario.
>>
>>
>>
>> --
>> ----
>
>
>
> --
> Mario.



-- 
----