Re: NUMA node - Memory Only

2022-08-22 Thread Andrea Bolognani
On Mon, Aug 22, 2022 at 01:55:05AM -0700, Jin Huang wrote:
> Hi, Andrea
> After installing the debian-keyring package, no that issue. Thank you so
> much.
>
> But I tried this under libvirt-8.5.0/
> dpkg-buildpackage --no-sign
>
> dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper-compat (=
> 13) libc6-dev (>= 2.31-14~) meson (>= 0.54.0~) qemu-system-common:native
>
> But my meson version is 0.63.0, which should satisfy this dependency
> requirement;

You have probably installed that version using pip or some other
method, so dpkg doesn't know about it and can't use it to satisfy the
Build-Depends.

Anyway, it looks like Ubuntu 20.04 is much farther behind Debian sid
than I thought was the case. You could probably hammer the package
into a shape that can be built on that platform with enough effort,
but I'm not convinced it would be worth it.

Please consider moving to Ubuntu 22.04, the current LTS release. The
steps I provided will work there.

-- 
Andrea Bolognani / Red Hat / Virtualization



Re: NUMA node - Memory Only

2022-08-22 Thread Jin Huang
Hi, Andrea
After installing the debian-keyring package, no that issue. Thank you so
much.

But I tried this under libvirt-8.5.0/
dpkg-buildpackage --no-sign

dpkg-checkbuilddeps: error: Unmet build dependencies: debhelper-compat (=
13) libc6-dev (>= 2.31-14~) meson (>= 0.54.0~) qemu-system-common:native

But my meson version is 0.63.0, which should satisfy this dependency
requirement;
for the debhelper, libc6-dev, qemu-system-common, they are all the latest
version as for I use apt install in the Ubuntu20 system, I do not know how
to solve these dependency issues.

Plus, if I just add -d option in the dpkg-buildpackage command, it will
still fail in the end.




Thank You
Best
Jin Huang


On Mon, Aug 22, 2022 at 12:36 AM Andrea Bolognani 
wrote:

> On Mon, Aug 22, 2022 at 12:01:17AM -0700, Jin Huang wrote:
> > Hi, Andrea
> > When I tried
> >  $ dget
> > https://deb.debian.org/debian/pool/main/libv/libvirt/libvirt_8.5.0-1.dsc
> >
> > But failed, seems I did not have the public key? This is the message from
> > my system:
> >
> > dget: using existing libvirt_8.5.0.orig.tar.xz
> > dget: using existing libvirt_8.5.0.orig.tar.xz.asc
> > dget: using existing libvirt_8.5.0-1.debian.tar.xz
> > libvirt_8.5.0-1.dsc:
> > dscverify: libvirt_8.5.0-1.dsc failed signature check:
> > gpg: WARNING: no command supplied.  Trying to guess what you mean ...
> > gpg: Signature made Sun 17 Jul 2022 09:01:01 AM PDT
> > gpg:using RSA key
> 3B8F2DF67895CA9C771232DFF79E1FC5428583AC
> > gpg:issuer "e...@kiyuko.org"
> > gpg: Can't check signature: No public key
> > Validation FAILED!!
>
> Installing the debian-keyring package should take care of that.
>
> --
> Andrea Bolognani / Red Hat / Virtualization
>
>


Re: NUMA node - Memory Only

2022-08-22 Thread Andrea Bolognani
On Mon, Aug 22, 2022 at 12:01:17AM -0700, Jin Huang wrote:
> Hi, Andrea
> When I tried
>  $ dget
> https://deb.debian.org/debian/pool/main/libv/libvirt/libvirt_8.5.0-1.dsc
>
> But failed, seems I did not have the public key? This is the message from
> my system:
>
> dget: using existing libvirt_8.5.0.orig.tar.xz
> dget: using existing libvirt_8.5.0.orig.tar.xz.asc
> dget: using existing libvirt_8.5.0-1.debian.tar.xz
> libvirt_8.5.0-1.dsc:
> dscverify: libvirt_8.5.0-1.dsc failed signature check:
> gpg: WARNING: no command supplied.  Trying to guess what you mean ...
> gpg: Signature made Sun 17 Jul 2022 09:01:01 AM PDT
> gpg:using RSA key 3B8F2DF67895CA9C771232DFF79E1FC5428583AC
> gpg:issuer "e...@kiyuko.org"
> gpg: Can't check signature: No public key
> Validation FAILED!!

Installing the debian-keyring package should take care of that.

-- 
Andrea Bolognani / Red Hat / Virtualization



Re: NUMA node - Memory Only

2022-08-22 Thread Jin Huang
Hi, Andrea
When I tried
 $ dget
https://deb.debian.org/debian/pool/main/libv/libvirt/libvirt_8.5.0-1.dsc

But failed, seems I did not have the public key? This is the message from
my system:

dget: using existing libvirt_8.5.0.orig.tar.xz
dget: using existing libvirt_8.5.0.orig.tar.xz.asc
dget: using existing libvirt_8.5.0-1.debian.tar.xz
libvirt_8.5.0-1.dsc:
dscverify: libvirt_8.5.0-1.dsc failed signature check:
gpg: WARNING: no command supplied.  Trying to guess what you mean ...
gpg: Signature made Sun 17 Jul 2022 09:01:01 AM PDT
gpg:using RSA key 3B8F2DF67895CA9C771232DFF79E1FC5428583AC
gpg:issuer "e...@kiyuko.org"
gpg: Can't check signature: No public key
Validation FAILED!!




Thank You
Best
Jin Huang


On Thu, Aug 11, 2022 at 6:55 AM Andrea Bolognani 
wrote:

> On Thu, Aug 11, 2022 at 02:21:18AM -0700, Jin Huang wrote:
> > Hi, Andrea
> > Thank you for your help, but I did not figure out how to deal with the
> dsc
> > and rebuilding package stuff yet.
> >
> >
> > Also, I compiled and installed the libvirt-8.5.0 source code from
> > https://libvirt.org/sources/.
> > The build command I used is:
> > meson build -Dsystem=true -Ddriver_interface=enabled
> > -Ddriver_libvirtd=enabled -Ddriver_network=enabled -Ddriver_qemu=enabled
> > -Ddriver_remote=enabled -Dnumactl=enabled -Dnumad=enabled
> > -Dstorage_disk=enabled
> >
> > Now my question is how to start the libvird? My OS is Ubuntu20.
> > According to https://libvirt.org/compiling.html, when I tried # service
> > libvirtd stop (or systemctl stop libvirtd.service), under build/src
> > directory
> > The system reports error: Failed to start/stop libvirtd.service: Unit
> > libvirtd.service not found.
>
> As I said in the previous message, I'd rebuild the Debian package
> instead of building from source. That way, you should be able to
> seamlessly replace the version of libvirt that you had installed from
> Ubuntu 20.04's repositories with a newer one.
>
> The steps involved should be roughly
>
>   $ sudo apt-get update
>   $ sudo apt-get install -y build-essential
>   $ sudo apt-get build-dep -y libvirt
>
> to install the necessary build dependencies, and then
>
>   $ dget
> https://deb.debian.org/debian/pool/main/libv/libvirt/libvirt_8.5.0-1.dsc
>   $ cd libvirt-8.5.0/
>   $ dpkg-buildpackage --no-sign
>
> to actually build the package. Assuming there are no errors, you
> should end up with a bunch of .deb files that you can install on the
> system using apt-get.
>
> --
> Andrea Bolognani / Red Hat / Virtualization
>
>