4:25 a.m.
Hi, libvirt-users
How could I set up a memory-only and no-cpu NUMA node for the qemu-VM with
the XML file?
Seems each NUMA cell has to be bundled with some specific cpuids.
If I write the element like this, it is wrong.
<cpu mode='host-passthrough'>
<numa>
<cell id='0' cpus='0-3' memory='16'
unit='GiB'/>
<cell id='1' cpus='*null*' memory='16'
unit='GiB'/>
</numa>
</cpu>
Also if I ignore the cpus item, it is not acceptable for the virsh command.
The reason I want the memory-only node is that I want to set up multiple
memory tiers for the VM, just like
https://stevescargall.com/2022/06/10/using-linux-kernel-memory-tiering/
Thank You
Best
Jin Huang
7:34 a.m.
On 8/5/22 11:25, Jin Huang wrote:
Hi, libvirt-users
How could I set up a memory-only and no-cpu NUMA node for the qemu-VM
with the XML file?
Seems each NUMA cell has to be bundled with some specific cpuids.
If I write the element like this, it is wrong.
<cpu mode='host-passthrough'>
<numa>
<cell id='0' cpus='0-3' memory='16'
unit='GiB'/>
<cell id='1' cpus='*null*' memory='16'
unit='GiB'/>
</numa>
</cpu>
Also if I ignore the cpus item, it is not acceptable for the virsh command.
The reason I want the memory-only node is that I want to set up multiple
memory tiers for the VM, just
like https://stevescargall.com/2022/06/10/using-linux-kernel-memory-tiering/
<https://stevescargall.com/2022/06/10/using-linux-kernel-memory-tiering/>
What you want to configure is so called HMAT (Heterogeneous Memory
Attribute Table). It can be configured by leaving out the @cpus
attribute completely. For instance like this:
<cpu mode='host-model' check='partial'>
<numa>
<cell id='0' cpus='0-5' memory='512000'
unit='KiB' discard='yes'>
<distances>
<sibling id='0' value='10'/>
<sibling id='1' value='21'/>
</distances>
<cache level='3' associativity='direct'
policy='writeback'>
<size value='10' unit='KiB'/>
<line value='8' unit='B'/>
</cache>
<cache level='1' associativity='direct'
policy='writeback'>
<size value='8' unit='KiB'/>
<line value='5' unit='B'/>
</cache>
</cell>
<cell id='1' memory='512000' unit='KiB'>
<distances>
<sibling id='0' value='21'/>
<sibling id='1' value='10'/>
</distances>
</cell>
<interconnects>
<latency initiator='0' target='0' cache='1'
type='access'
value='5'/>
<bandwidth initiator='0' target='0' type='access'
value='204800'
unit='KiB'/>
</interconnects>
</numa>
</cpu>
This was introduced in libvirt-6.6.0 so you may need to upgrade.
Michal
9:10 p.m.
Hi, Michal
Thank you for your help.
After compiled and installed libvirt-6.7.0, when I try virsh define
xmlfile, it says "error: invalid argument: could not find capabilities for
arch=x86_64 domaintype=kvm".
The way I compiled and installed libvirt-6.7.0 is according to
https://libvirt.org/compiling.html
My system is Ubuntu20, originally I used apt to install the libvirt, it
works well, just not support HMAT.
Do you know how to fix my current issue?
Thank You
Best
Jin Huang
On Fri, Aug 5, 2022 at 5:34 AM Michal Prívozník <mprivozn(a)redhat.com> wrote:
On 8/5/22 11:25, Jin Huang wrote:
> Hi, libvirt-users
> How could I set up a memory-only and no-cpu NUMA node for the qemu-VM
> with the XML file?
>
> Seems each NUMA cell has to be bundled with some specific cpuids.
> If I write the element like this, it is wrong.
>
> <cpu mode='host-passthrough'>
> <numa>
> <cell id='0' cpus='0-3' memory='16'
unit='GiB'/>
> <cell id='1' cpus='*null*' memory='16'
unit='GiB'/>
> </numa>
> </cpu>
> Also if I ignore the cpus item, it is not acceptable for the virsh
command.
>
> The reason I want the memory-only node is that I want to set up multiple
> memory tiers for the VM, just
> like
https://stevescargall.com/2022/06/10/using-linux-kernel-memory-tiering/
> <https://stevescargall.com/2022/06/10/using-linux-kernel-memory-tiering/
>
>
What you want to configure is so called HMAT (Heterogeneous Memory
Attribute Table). It can be configured by leaving out the @cpus
attribute completely. For instance like this:
<cpu mode='host-model' check='partial'>
<numa>
<cell id='0' cpus='0-5' memory='512000'
unit='KiB' discard='yes'>
<distances>
<sibling id='0' value='10'/>
<sibling id='1' value='21'/>
</distances>
<cache level='3' associativity='direct'
policy='writeback'>
<size value='10' unit='KiB'/>
<line value='8' unit='B'/>
</cache>
<cache level='1' associativity='direct'
policy='writeback'>
<size value='8' unit='KiB'/>
<line value='5' unit='B'/>
</cache>
</cell>
<cell id='1' memory='512000' unit='KiB'>
<distances>
<sibling id='0' value='21'/>
<sibling id='1' value='10'/>
</distances>
</cell>
<interconnects>
<latency initiator='0' target='0' cache='1'
type='access'
value='5'/>
<bandwidth initiator='0' target='0' type='access'
value='204800'
unit='KiB'/>
</interconnects>
</numa>
</cpu>
This was introduced in libvirt-6.6.0 so you may need to upgrade.
Michal
5:55 a.m.
Hi, everyone
I built the libvirt 8.6.0 on my Ubuntu 20 system with the options like this:
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
(1)After installation, when I tried to start the libvirtd, I get this error
message:
error : virNetworkObjAssignDefLocked:576 : operation failed: network
'default' already exists with uuid 7477a9f5-02d3-4fbc-b0e8-d7229d39a6a2
(2)When try the virsh command, I get this error message:
virsh: /lib/x86_64-linux-gnu/libvirt-qemu.so.0: version
`LIBVIRT_QEMU_8.2.0' not found (required by virsh)
virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_8.0.0' not
found (required by virsh)
virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_8.5.0' not
found (required by virsh)
virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_6.10.0' not
found (required by virsh)
virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.7.0' not
found (required by virsh)
virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.8.0' not
found (required by virsh)
virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.2.0' not
found (required by virsh)
virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.1.0' not
found (required by virsh)
virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.3.0' not
found (required by virsh)
virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_PRIVATE_8.6.0'
not found (required by virsh)
Could anyone give me some suggestions to fix these issues?
Thank you
Jin Huang
6:26 a.m.
On 8/9/22 12:55, Jin Huang wrote:
Hi, everyone
I built the libvirt 8.6.0 on my Ubuntu 20 system with the options like this:
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
(1)After installation, when I tried to start the libvirtd, I get this
error message:
error : virNetworkObjAssignDefLocked:576 : operation failed: network
'default' already exists with uuid 7477a9f5-02d3-4fbc-b0e8-d7229d39a6a2
(2)When try the virsh command, I get this error message:
virsh: /lib/x86_64-linux-gnu/libvirt-qemu.so.0: version
`LIBVIRT_QEMU_8.2.0' not found (required by virsh)
virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_8.0.0' not
found (required by virsh)
virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_8.5.0' not
found (required by virsh)
virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_6.10.0' not
found (required by virsh)
virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.7.0' not
found (required by virsh)
virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.8.0' not
found (required by virsh)
virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.2.0' not
found (required by virsh)
virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.1.0' not
found (required by virsh)
virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.3.0' not
found (required by virsh)
virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version
`LIBVIRT_PRIVATE_8.6.0' not found (required by virsh)
Could anyone give me some suggestions to fix these issues?
This is pretty much expected if you had libvirt installed from your
package manager (which I believe is the case because of the network
error). I don't know what the correct way to build a .deb package is,
but on rpm based distros I usually build a .tar.xz (meson dist) from
which I build a .rpm (rpmbuild -ta) and then install it.
Michal
2:31 a.m.
Michal Prívozník <mprivozn(a)redhat.com> writes:
On 8/9/22 12:55, Jin Huang wrote:
> Hi, everyone
> I built the libvirt 8.6.0 on my Ubuntu 20 system with the options like this:
> 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
>
> (1)After installation, when I tried to start the libvirtd, I get this
> error message:
> error : virNetworkObjAssignDefLocked:576 : operation failed: network
> 'default' already exists with uuid 7477a9f5-02d3-4fbc-b0e8-d7229d39a6a2
>
> (2)When try the virsh command, I get this error message:
> virsh: /lib/x86_64-linux-gnu/libvirt-qemu.so.0: version
> `LIBVIRT_QEMU_8.2.0' not found (required by virsh)
> virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_8.0.0' not
> found (required by virsh)
> virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_8.5.0' not
> found (required by virsh)
> virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_6.10.0' not
> found (required by virsh)
> virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.7.0' not
> found (required by virsh)
> virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.8.0' not
> found (required by virsh)
> virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.2.0' not
> found (required by virsh)
> virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.1.0' not
> found (required by virsh)
> virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.3.0' not
> found (required by virsh)
> virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version
> `LIBVIRT_PRIVATE_8.6.0' not found (required by virsh)
>
> Could anyone give me some suggestions to fix these issues?
This is pretty much expected if you had libvirt installed from your
package manager (which I believe is the case because of the network
error). I don't know what the correct way to build a .deb package is,
The easiest way is to use a package from a newer Ubuntu version. I'd
suggest using the oldest good enough version available to avoid problems
with dependencies. You may still be forced to use a newer libc or so.
In such a case, you can either configure your system (in /etc/apt/) to
use some packages from a newer Ubuntu version, or to rebuild the newer
libvirt package using instructions from
https://wiki.debian.org/BuildingTutorial#The_packaging_workflow
but on rpm based distros I usually build a .tar.xz (meson dist) from
which I build a .rpm (rpmbuild -ta) and then install it.
Michal
4:17 a.m.
On Tue, Aug 09, 2022 at 01:26:55PM +0200, Michal Prívozník wrote:
On 8/9/22 12:55, Jin Huang wrote:
> Hi, everyone
> I built the libvirt 8.6.0 on my Ubuntu 20 system with the options like this:
> 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
>
> (1)After installation, when I tried to start the libvirtd, I get this
> error message:
> error : virNetworkObjAssignDefLocked:576 : operation failed: network
> 'default' already exists with uuid 7477a9f5-02d3-4fbc-b0e8-d7229d39a6a2
>
> (2)When try the virsh command, I get this error message:
> virsh: /lib/x86_64-linux-gnu/libvirt-qemu.so.0: version
> `LIBVIRT_QEMU_8.2.0' not found (required by virsh)
> virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_8.0.0' not
> found (required by virsh)
> virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_8.5.0' not
> found (required by virsh)
> virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_6.10.0' not
> found (required by virsh)
> virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.7.0' not
> found (required by virsh)
> virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.8.0' not
> found (required by virsh)
> virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.2.0' not
> found (required by virsh)
> virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.1.0' not
> found (required by virsh)
> virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.3.0' not
> found (required by virsh)
> virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version
> `LIBVIRT_PRIVATE_8.6.0' not found (required by virsh)
>
> Could anyone give me some suggestions to fix these issues?
This is pretty much expected if you had libvirt installed from your
package manager (which I believe is the case because of the network
error). I don't know what the correct way to build a .deb package is,
but on rpm based distros I usually build a .tar.xz (meson dist) from
which I build a .rpm (rpmbuild -ta) and then install it.
You could grab the source package for the latest version of libvirt
available in Debian, which would be
https://deb.debian.org/debian/pool/main/libv/libvirt/libvirt_8.5.0-1.dsc
right now, and then follow the instructions in
https://wiki.debian.org/BuildingTutorial#Get_the_source_package
to rebuild it locally targeting your release of Ubuntu. Since it's
not insanely old, I expect that would work just fine.
--
Andrea Bolognani / Red Hat / Virtualization
4:21 a.m.
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.
Thank You
Best
Jin Huang
On Wed, Aug 10, 2022 at 2:17 AM Andrea Bolognani <abologna(a)redhat.com>
wrote:
On Tue, Aug 09, 2022 at 01:26:55PM +0200, Michal Prívozník wrote:
> On 8/9/22 12:55, Jin Huang wrote:
> > Hi, everyone
> > I built the libvirt 8.6.0 on my Ubuntu 20 system with the options like
this:
> > 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
> >
> > (1)After installation, when I tried to start the libvirtd, I get this
> > error message:
> > error : virNetworkObjAssignDefLocked:576 : operation failed: network
> > 'default' already exists with uuid
7477a9f5-02d3-4fbc-b0e8-d7229d39a6a2
> >
> > (2)When try the virsh command, I get this error message:
> > virsh: /lib/x86_64-linux-gnu/libvirt-qemu.so.0: version
> > `LIBVIRT_QEMU_8.2.0' not found (required by virsh)
> > virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_8.0.0' not
> > found (required by virsh)
> > virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_8.5.0' not
> > found (required by virsh)
> > virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_6.10.0' not
> > found (required by virsh)
> > virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.7.0' not
> > found (required by virsh)
> > virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.8.0' not
> > found (required by virsh)
> > virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.2.0' not
> > found (required by virsh)
> > virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.1.0' not
> > found (required by virsh)
> > virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version `LIBVIRT_7.3.0' not
> > found (required by virsh)
> > virsh: /lib/x86_64-linux-gnu/libvirt.so.0: version
> > `LIBVIRT_PRIVATE_8.6.0' not found (required by virsh)
> >
> > Could anyone give me some suggestions to fix these issues?
>
> This is pretty much expected if you had libvirt installed from your
> package manager (which I believe is the case because of the network
> error). I don't know what the correct way to build a .deb package is,
> but on rpm based distros I usually build a .tar.xz (meson dist) from
> which I build a .rpm (rpmbuild -ta) and then install it.
You could grab the source package for the latest version of libvirt
available in Debian, which would be
https://deb.debian.org/debian/pool/main/libv/libvirt/libvirt_8.5.0-1.dsc
right now, and then follow the instructions in
https://wiki.debian.org/BuildingTutorial#Get_the_source_package
to rebuild it locally targeting your release of Ubuntu. Since it's
not insanely old, I expect that would work just fine.
--
Andrea Bolognani / Red Hat / Virtualization
8:55 a.m.
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
2:01 a.m.
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 "eof(a)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 <abologna(a)redhat.com>
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
2:36 a.m.
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 "eof(a)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
3:55 a.m.
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 <abologna(a)redhat.com>
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 "eof(a)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
4:48 a.m.
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
804
days inactive
821
days old
12 comments
4 participants
participants (4)
-
Andrea Bolognani -
Jin Huang -
Michal Prívozník -
Milan Zamazal