[libvirt PATCH] rpm: switch to using %mingw_find_lang
by Daniel P. Berrangé
We currently list the locale file paths via a wildcard in %files, but the
normal pattern for mingw RPMs in Fedora is to use %mingw_find_lang.
Signed-off-by: Daniel P. Berrangé <berrange(a)redhat.com>
---
libvirt.spec.in | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/libvirt.spec.in b/libvirt.spec.in
index 562baea52e..31ff8ea01e 100644
--- a/libvirt.spec.in
+++ b/libvirt.spec.in
@@ -1355,6 +1355,8 @@ rm -rf $RPM_BUILD_ROOT%{mingw64_libexecdir}/libvirt-guests.sh
%mingw_debug_install_post
+%mingw_find_lang %{name}
+
%endif
%check
@@ -2181,7 +2183,7 @@ exit 0
%{_datadir}/libvirt/api/libvirt-lxc-api.xml
%if %{with_mingw}
-%files -n mingw32-libvirt
+%files -n mingw32-libvirt -f mingw32-libvirt.lang
%dir %{mingw32_sysconfdir}/libvirt/
%config(noreplace) %{mingw32_sysconfdir}/libvirt/libvirt.conf
%config(noreplace) %{mingw32_sysconfdir}/libvirt/libvirt-admin.conf
@@ -2212,7 +2214,6 @@ exit 0
%{mingw32_datadir}/libvirt/api/libvirt-admin-api.xml
%{mingw32_datadir}/libvirt/cpu_map/*.xml
%{mingw32_datadir}/libvirt/test-screenshot.png
-%{mingw32_datadir}/locale/*/LC_MESSAGES/libvirt.mo
%dir %{mingw32_includedir}/libvirt
%{mingw32_includedir}/libvirt/libvirt.h
%{mingw32_includedir}/libvirt/libvirt-common.h
@@ -2239,7 +2240,7 @@ exit 0
%{mingw32_mandir}/man1/virt-pki-validate.1*
%{mingw32_mandir}/man7/virkey*.7*
-%files -n mingw64-libvirt
+%files -n mingw64-libvirt -f mingw64-libvirt.lang
%dir %{mingw64_sysconfdir}/libvirt/
%config(noreplace) %{mingw64_sysconfdir}/libvirt/libvirt.conf
%config(noreplace) %{mingw64_sysconfdir}/libvirt/libvirt-admin.conf
@@ -2270,7 +2271,6 @@ exit 0
%{mingw64_datadir}/libvirt/api/libvirt-admin-api.xml
%{mingw64_datadir}/libvirt/cpu_map/*.xml
%{mingw64_datadir}/libvirt/test-screenshot.png
-%{mingw64_datadir}/locale/*/LC_MESSAGES/libvirt.mo
%dir %{mingw64_includedir}/libvirt
%{mingw64_includedir}/libvirt/libvirt.h
%{mingw64_includedir}/libvirt/libvirt-common.h
--
2.38.1
2 years, 4 months
[libvirt PATCH 0/3] Actually do secure erase with explicit_bzero
by Daniel P. Berrangé
If we're going to have a virSecureErase function, we
might as well make it do secure erasure with currently
available explicit_bzero in FreeBSD/Linux.
While we're here, we should use it from the RPC code.
The remaining hole in the RPC code is xdr_free which
does not securely erase buffers. That's not easily
fixed without dropping the RPC impl in favour of a
custom one.
Daniel P. Berrangé (3):
util: implement secure erase with explicit_bzero
rpc: fix buffer offset updates after decoding payload
rpc: securely erase the message buffers
meson.build | 1 +
src/rpc/virnetmessage.c | 4 +++-
src/util/virsecureerase.c | 6 ++++++
3 files changed, 10 insertions(+), 1 deletion(-)
--
2.38.1
2 years, 4 months
[PATCH] formatcaps: Update capabilities example
by Michal Privoznik
In the formatcaps.rst we give an example output of capabilities.
Well, there are couple of issues with it:
1) We show <features/> nested under /capabilities/host/cpu.
There's no such element and never was.
2) The ordering of elements is corrupted.
3) There is plenty of elements missing.
Fix these by showing an actual output of 'virsh capabilities' as
obtained on my machine.
Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com>
---
docs/formatcaps.rst | 230 +++++++++++++++++++++++++++++++++-----------
1 file changed, 176 insertions(+), 54 deletions(-)
diff --git a/docs/formatcaps.rst b/docs/formatcaps.rst
index 39b1fb78ac..f7e5342654 100644
--- a/docs/formatcaps.rst
+++ b/docs/formatcaps.rst
@@ -143,60 +143,182 @@ capabilities enabled in the chip and BIOS you will see:
::
- <capabilities>
- <host>
- <cpu>
- <arch>x86_64</arch>
- <features>
- <vmx/>
- </features>
- <model>core2duo</model>
- <vendor>Intel</vendor>
- <topology sockets="1" dies="1" cores="2" threads="1"/>
- <feature name="lahf_lm"/>
- <feature name='xtpr'/>
- <pages unit='KiB' size='4'/>
- <pages unit='KiB' size='2048'/>
- <pages unit='KiB' size='1048576'/>
- <microcode version='36'/>
- <maxphysaddr mode='emulate' bits='46'/>
- ...
- </cpu>
- <power_management>
- <suspend_mem/>
- <suspend_disk/>
- <suspend_hybrid/>
- </power_management>
- </host>
+ <capabilities>
- <!-- xen-3.0-x86_64 -->
- <guest>
- <os_type>xen</os_type>
- <arch name="x86_64">
- <wordsize>64</wordsize>
- <domain type="xen"></domain>
- <emulator>/usr/lib64/xen/bin/qemu-dm</emulator>
- </arch>
- <features>
- </features>
- </guest>
+ <host>
+ <uuid>7b55704c-29f4-11b2-a85c-9dc6ff50623f</uuid>
+ <cpu>
+ <arch>x86_64</arch>
+ <model>Skylake-Client-noTSX-IBRS</model>
+ <vendor>Intel</vendor>
+ <microcode version='236'/>
+ <signature family='6' model='142' stepping='12'/>
+ <counter name='tsc' frequency='2303997000' scaling='no'/>
+ <topology sockets='1' dies='1' cores='4' threads='2'/>
+ <maxphysaddr mode='emulate' bits='39'/>
+ <feature name='ds'/>
+ <feature name='acpi'/>
+ <feature name='ss'/>
+ <feature name='ht'/>
+ <feature name='tm'/>
+ <feature name='pbe'/>
+ <feature name='dtes64'/>
+ <feature name='monitor'/>
+ <feature name='ds_cpl'/>
+ <feature name='vmx'/>
+ <feature name='smx'/>
+ <feature name='est'/>
+ <feature name='tm2'/>
+ <feature name='xtpr'/>
+ <feature name='pdcm'/>
+ <feature name='osxsave'/>
+ <feature name='tsc_adjust'/>
+ <feature name='sgx'/>
+ <feature name='clflushopt'/>
+ <feature name='intel-pt'/>
+ <feature name='md-clear'/>
+ <feature name='stibp'/>
+ <feature name='arch-capabilities'/>
+ <feature name='ssbd'/>
+ <feature name='xsaves'/>
+ <feature name='sgx1'/>
+ <feature name='sgx-debug'/>
+ <feature name='sgx-mode64'/>
+ <feature name='sgx-provisionkey'/>
+ <feature name='sgx-tokenkey'/>
+ <feature name='pdpe1gb'/>
+ <feature name='invtsc'/>
+ <feature name='rdctl-no'/>
+ <feature name='ibrs-all'/>
+ <feature name='skip-l1dfl-vmentry'/>
+ <feature name='mds-no'/>
+ <feature name='tsx-ctrl'/>
+ <pages unit='KiB' size='4'/>
+ <pages unit='KiB' size='2048'/>
+ <pages unit='KiB' size='1048576'/>
+ </cpu>
+ <power_management>
+ <suspend_mem/>
+ </power_management>
+ <iommu support='yes'/>
+ <migration_features>
+ <live/>
+ <uri_transports>
+ <uri_transport>tcp</uri_transport>
+ <uri_transport>rdma</uri_transport>
+ </uri_transports>
+ </migration_features>
+ <topology>
+ <cells num='1'>
+ <cell id='0'>
+ <memory unit='KiB'>32498112</memory>
+ <pages unit='KiB' size='4'>6813808</pages>
+ <pages unit='KiB' size='2048'>2048</pages>
+ <pages unit='KiB' size='1048576'>1</pages>
+ <distances>
+ <sibling id='0' value='10'/>
+ </distances>
+ <cpus num='8'>
+ <cpu id='0' socket_id='0' die_id='0' core_id='0' siblings='0,4'/>
+ <cpu id='1' socket_id='0' die_id='0' core_id='1' siblings='1,5'/>
+ <cpu id='2' socket_id='0' die_id='0' core_id='2' siblings='2,6'/>
+ <cpu id='3' socket_id='0' die_id='0' core_id='3' siblings='3,7'/>
+ <cpu id='4' socket_id='0' die_id='0' core_id='0' siblings='0,4'/>
+ <cpu id='5' socket_id='0' die_id='0' core_id='1' siblings='1,5'/>
+ <cpu id='6' socket_id='0' die_id='0' core_id='2' siblings='2,6'/>
+ <cpu id='7' socket_id='0' die_id='0' core_id='3' siblings='3,7'/>
+ </cpus>
+ </cell>
+ </cells>
+ </topology>
+ <cache>
+ <bank id='0' level='3' type='both' size='8' unit='MiB' cpus='0-7'/>
+ </cache>
+ <secmodel>
+ <model>none</model>
+ <doi>0</doi>
+ </secmodel>
+ <secmodel>
+ <model>dac</model>
+ <doi>0</doi>
+ <baselabel type='kvm'>+77:+77</baselabel>
+ <baselabel type='qemu'>+77:+77</baselabel>
+ </secmodel>
+ </host>
- <!-- hvm-3.0-x86_32 -->
- <guest>
- <os_type>hvm</os_type>
- <arch name="i686">
- <wordsize>32</wordsize>
- <domain type="xen"></domain>
- <emulator>/usr/lib/xen/bin/qemu-dm</emulator>
- <machine>pc</machine>
- <machine>isapc</machine>
- <loader>/usr/lib/xen/boot/hvmloader</loader>
- </arch>
- <features>
- <cpuselection/>
- <deviceboot/>
- </features>
- </guest>
+ <guest>
+ <os_type>hvm</os_type>
+ <arch name='x86_64'>
+ <wordsize>64</wordsize>
+ <emulator>/usr/bin/qemu-system-x86_64</emulator>
+ <machine maxCpus='255'>pc-i440fx-7.1</machine>
+ <machine canonical='pc-i440fx-7.1' maxCpus='255'>pc</machine>
+ <machine maxCpus='288'>pc-q35-5.2</machine>
+ <machine maxCpus='255'>pc-i440fx-2.12</machine>
+ <machine maxCpus='255'>pc-i440fx-2.0</machine>
+ <machine maxCpus='255'>pc-i440fx-6.2</machine>
+ <machine maxCpus='288'>pc-q35-4.2</machine>
+ <machine maxCpus='255'>pc-i440fx-2.5</machine>
+ <machine maxCpus='255'>pc-i440fx-4.2</machine>
+ <machine maxCpus='255'>pc-i440fx-5.2</machine>
+ <machine maxCpus='255' deprecated='yes'>pc-i440fx-1.5</machine>
+ <machine maxCpus='255'>pc-q35-2.7</machine>
+ <machine maxCpus='288'>pc-q35-7.1</machine>
+ <machine canonical='pc-q35-7.1' maxCpus='288'>q35</machine>
+ <machine maxCpus='255'>pc-i440fx-2.2</machine>
+ <machine maxCpus='255'>pc-i440fx-2.7</machine>
+ <machine maxCpus='288'>pc-q35-6.1</machine>
+ <machine maxCpus='255'>pc-q35-2.4</machine>
+ <machine maxCpus='288'>pc-q35-2.10</machine>
+ <machine maxCpus='1'>x-remote</machine>
+ <machine maxCpus='288'>pc-q35-5.1</machine>
+ <machine maxCpus='255' deprecated='yes'>pc-i440fx-1.7</machine>
+ <machine maxCpus='288'>pc-q35-2.9</machine>
+ <machine maxCpus='255'>pc-i440fx-2.11</machine>
+ <machine maxCpus='288'>pc-q35-3.1</machine>
+ <machine maxCpus='255'>pc-i440fx-6.1</machine>
+ <machine maxCpus='288'>pc-q35-4.1</machine>
+ <machine maxCpus='255'>pc-i440fx-2.4</machine>
+ <machine maxCpus='255'>pc-i440fx-4.1</machine>
+ <machine maxCpus='255'>pc-i440fx-5.1</machine>
+ <machine maxCpus='255'>pc-i440fx-2.9</machine>
+ <machine maxCpus='1'>isapc</machine>
+ <machine maxCpus='255' deprecated='yes'>pc-i440fx-1.4</machine>
+ <machine maxCpus='255'>pc-q35-2.6</machine>
+ <machine maxCpus='255'>pc-i440fx-3.1</machine>
+ <machine maxCpus='288'>pc-q35-2.12</machine>
+ <machine maxCpus='288'>pc-q35-7.0</machine>
+ <machine maxCpus='255'>pc-i440fx-2.1</machine>
+ <machine maxCpus='288'>pc-q35-6.0</machine>
+ <machine maxCpus='255'>pc-i440fx-2.6</machine>
+ <machine maxCpus='288'>pc-q35-4.0.1</machine>
+ <machine maxCpus='255'>pc-i440fx-7.0</machine>
+ <machine maxCpus='255' deprecated='yes'>pc-i440fx-1.6</machine>
+ <machine maxCpus='288'>pc-q35-5.0</machine>
+ <machine maxCpus='288'>pc-q35-2.8</machine>
+ <machine maxCpus='255'>pc-i440fx-2.10</machine>
+ <machine maxCpus='288'>pc-q35-3.0</machine>
+ <machine maxCpus='255'>pc-i440fx-6.0</machine>
+ <machine maxCpus='288'>pc-q35-4.0</machine>
+ <machine maxCpus='288'>microvm</machine>
+ <machine maxCpus='255'>pc-i440fx-2.3</machine>
+ <machine maxCpus='255'>pc-i440fx-4.0</machine>
+ <machine maxCpus='255'>pc-i440fx-5.0</machine>
+ <machine maxCpus='255'>pc-i440fx-2.8</machine>
+ <machine maxCpus='288'>pc-q35-6.2</machine>
+ <machine maxCpus='255'>pc-q35-2.5</machine>
+ <machine maxCpus='255'>pc-i440fx-3.0</machine>
+ <machine maxCpus='288'>pc-q35-2.11</machine>
+ <domain type='qemu'/>
+ <domain type='kvm'/>
+ </arch>
+ <features>
+ <acpi default='on' toggle='yes'/>
+ <apic default='on' toggle='no'/>
+ <cpuselection/>
+ <deviceboot/>
+ <disksnapshot default='on' toggle='no'/>
+ </features>
+ </guest>
- ...
- </capabilities>
+ </capabilities>
--
2.37.4
2 years, 4 months
[PATCH] docs: Add missing elements to formatcaps.rst
by Nobuhiro MIKI
Signed-off-by: Nobuhiro MIKI <nmiki(a)yahoo-corp.jp>
---
docs/formatcaps.rst | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/docs/formatcaps.rst b/docs/formatcaps.rst
index 9d7932a6a8..39b1fb78ac 100644
--- a/docs/formatcaps.rst
+++ b/docs/formatcaps.rst
@@ -155,6 +155,11 @@ capabilities enabled in the chip and BIOS you will see:
<topology sockets="1" dies="1" cores="2" threads="1"/>
<feature name="lahf_lm"/>
<feature name='xtpr'/>
+ <pages unit='KiB' size='4'/>
+ <pages unit='KiB' size='2048'/>
+ <pages unit='KiB' size='1048576'/>
+ <microcode version='36'/>
+ <maxphysaddr mode='emulate' bits='46'/>
...
</cpu>
<power_management>
--
2.38.1
2 years, 4 months
[PATCH RFC 0/6] spec: Decompose the daemon subpackage
by Jim Fehlig
Currently it is not possible to install a modular daemon subpackage without
also installing the monolithic daemon
https://listman.redhat.com/archives/libvir-list/2022-September/234554.html
This series is an initial attempt at moving common daemons, utilities, and
files from the daemon subpackage to a new daemon-core subpackage. The
monolithic and modular daemons can then depend on the new subpackage.
libvirt-guests is moved to a new libvirt-guests subpackage, which is
recommended by the daemon subpackage to provide smoother upgrade.
I've likely overlooked several items, but before continuing down this
path too far I first wanted to gauge interest and see if this work is
worth pursuing. If so, any comments on the RFC are appreciated!
Note that patches 1-3 are things I noticed while working on the others
and could be pushed independently.
Jim Fehlig (6):
spec: Remove redundant with_libxl
spec: Use more %{name} macro
spec: Remove daemon postun trigger
spec: Move common daemons to a separate subpackage
spec: Move more files to the daemon-core subpackage
spec: Move libvirt-guests to guests subpackage
libvirt.spec.in | 406 ++++++++++++++++++++++++++----------------------
1 file changed, 219 insertions(+), 187 deletions(-)
--
2.37.3
2 years, 4 months
[libvirt PATCH] tools: Fix style issues in virt-qemu-sev-validate
by Andrea Bolognani
The script had an incorrect interpreter line until commit
f6a19d7264bb, so the flake8 check would not realize it needed
to pick it up and these issues, some of which were present it
the very first version that was committed, were not being
reported.
Signed-off-by: Andrea Bolognani <abologna(a)redhat.com>
---
tools/virt-qemu-sev-validate | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/tools/virt-qemu-sev-validate b/tools/virt-qemu-sev-validate
index 46a92aa7a0..3d8b292fef 100755
--- a/tools/virt-qemu-sev-validate
+++ b/tools/virt-qemu-sev-validate
@@ -849,7 +849,7 @@ class ConfidentialVM(abc.ABC):
secret64 = b64encode(secret_table_ciphertext).decode('utf8')
log.debug("Header: %s (%d bytes)", header64, len(header))
log.debug("Secret: %s (%d bytes)",
- secret64, len(secret_table_ciphertext))
+ secret64, len(secret_table_ciphertext))
return header64, secret64
@@ -955,7 +955,7 @@ class LibvirtConfidentialVM(ConfidentialVM):
self.dom = self.conn.lookupByName(id_name_uuid)
log.debug("VM: id=%d name=%s uuid=%s",
- self.dom.ID(), self.dom.name(), self.dom.UUIDString())
+ self.dom.ID(), self.dom.name(), self.dom.UUIDString())
if not self.dom.isActive():
raise InvalidStateException(
@@ -1331,5 +1331,6 @@ def main():
print("ERROR: %s" % e, file=sys.stderr)
sys.exit(6)
+
if __name__ == "__main__":
main()
--
2.38.1
2 years, 4 months
[PATCH] virnetdevtap.c: Disallow pre-existing TAP devices
by Michal Privoznik
When starting a guest with <interface/> which has the target
device name set (i.e. not generated by us), it may happen that
the TAP device already exists. This then may lead to all sorts of
problems. For instance: for <interface type='network'/> the TAP
device is plugged into the network's bridge, but since the TAP
device is persistent it remains plugged there even after the
guest is shut off. We don't have a code that unplugs TAP devices
from the bridge because TAP devices we create are transient, i.e.
are removed automatically when QEMU closes their FD.
The only exception is <interface type='ethernet'/> with <target
managed='no'/> where we specifically want to let users use
pre-created TAP device and basically not touch it at all.
There's another reason for denying to use a pre-created TAP
devices: if we ever have bug in TAP name generation, we may
re-use a TAP device from another domain.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2144738
Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com>
---
src/qemu/qemu_interface.c | 2 ++
src/util/virnetdevtap.c | 31 ++++++++++++++++++++++++++++++-
src/util/virnetdevtap.h | 2 ++
3 files changed, 34 insertions(+), 1 deletion(-)
diff --git a/src/qemu/qemu_interface.c b/src/qemu/qemu_interface.c
index 4cc76e07a5..264d5e060c 100644
--- a/src/qemu/qemu_interface.c
+++ b/src/qemu/qemu_interface.c
@@ -461,6 +461,8 @@ qemuInterfaceEthernetConnect(virDomainDef *def,
if (!net->ifname)
template_ifname = true;
+ tap_create_flags |= VIR_NETDEV_TAP_CREATE_ALLOW_EXISTING;
+
if (virNetDevTapCreate(&net->ifname, tunpath, tapfd, tapfdSize,
tap_create_flags) < 0) {
goto cleanup;
diff --git a/src/util/virnetdevtap.c b/src/util/virnetdevtap.c
index 112a1e8b99..406339c583 100644
--- a/src/util/virnetdevtap.c
+++ b/src/util/virnetdevtap.c
@@ -148,12 +148,15 @@ virNetDevTapGetRealDeviceName(char *ifname G_GNUC_UNUSED)
* @tunpath: path to the tun device (if NULL, /dev/net/tun is used)
* @tapfds: array of file descriptors return value for the new tap device
* @tapfdSize: number of file descriptors in @tapfd
- * @flags: OR of virNetDevTapCreateFlags. Only one flag is recognized:
+ * @flags: OR of virNetDevTapCreateFlags. Only the following flags are
+ * recognized:
*
* VIR_NETDEV_TAP_CREATE_VNET_HDR
* - Enable IFF_VNET_HDR on the tap device
* VIR_NETDEV_TAP_CREATE_PERSIST
* - The device will persist after the file descriptor is closed
+ * VIR_NETDEV_TAP_CREATE_ALLOW_EXISTING
+ * - The device creation fails if @ifname already exists
*
* Creates a tap interface. The caller must use virNetDevTapDelete to
* remove a persistent TAP device when it is no longer needed. In case
@@ -182,6 +185,19 @@ int virNetDevTapCreate(char **ifname,
if (virNetDevGenerateName(ifname, VIR_NET_DEV_GEN_NAME_VNET) < 0)
return -1;
+ if (!(flags & VIR_NETDEV_TAP_CREATE_ALLOW_EXISTING)) {
+ int rc = virNetDevExists(*ifname);
+
+ if (rc < 0) {
+ return -1;
+ } else if (rc > 0) {
+ virReportError(VIR_ERR_OPERATION_INVALID,
+ _("The %s interface already exists"),
+ *ifname);
+ return -1;
+ }
+ }
+
if (!tunpath)
tunpath = "/dev/net/tun";
@@ -319,6 +335,19 @@ int virNetDevTapCreate(char **ifname,
if (virNetDevGenerateName(ifname, VIR_NET_DEV_GEN_NAME_VNET) < 0)
return -1;
+ if (!(flags & VIR_NETDEV_TAP_CREATE_ALLOW_EXISTING)) {
+ int rc = virNetDevExists(*ifname);
+
+ if (rc < 0) {
+ return -1;
+ } else if (rc > 0) {
+ virReportError(VIR_ERR_OPERATION_INVALID,
+ _("The %s interface already exists"),
+ *ifname);
+ return -1;
+ }
+ }
+
/* As FreeBSD determines interface type by name,
* we have to create 'tap' interface first and
* then rename it to 'vnet'
diff --git a/src/util/virnetdevtap.h b/src/util/virnetdevtap.h
index 197ea10f94..c9d29c0384 100644
--- a/src/util/virnetdevtap.h
+++ b/src/util/virnetdevtap.h
@@ -56,6 +56,8 @@ typedef enum {
VIR_NETDEV_TAP_CREATE_USE_MAC_FOR_BRIDGE = 1 << 2,
/* The device will persist after the file descriptor is closed */
VIR_NETDEV_TAP_CREATE_PERSIST = 1 << 3,
+ /* The device is allowed to exist before creation */
+ VIR_NETDEV_TAP_CREATE_ALLOW_EXISTING = 1 << 4,
} virNetDevTapCreateFlags;
int
--
2.37.4
2 years, 4 months
[libvirt PATCH 00/21] meson: remove many obsolete checks
by Daniel P. Berrangé
We have alot of checks for Linux kernel features that are obsolete since
our supported platform matrix lets us assume new enough kernel versions.
Removing the checks will speed up the meson phase and reduce the tangle
of #ifdefs in the code.
I thought I could remove the check for linux/kvm.h but for some reason
our code in virhostpcu.c / cpu_x86.c is enabling the codebases even
on FreeBSD, which I find kind of odd. Does FreeBSD really ship a
linux/kvm.h ?
Daniel P. Berrangé (21):
meson: remove obsolete check for LOOP_CTL_GET_FREE
meson: remove obsolete check for EPOLL_CLOEXEC
meson: remove obsolete check for LO_FLAGS_AUTOCLEAR
meson: drop check for unshare()
netdev: simplify check for ethtool functionality
meson: remove obsolete check for ETHTOOL_GGSO
meson: remove obsolete check for ETHTOOL_GGRO
meson: remove obsolete check for ETHTOOL_GFLAGS
meson: remove obsolete check for ETH_FLAG_LRO
meson: remove obsolete check for ETH_FLAG_TXVLAN/RXVLAN
meson: remove obsolete check for ETH_FLAG_NTUPLE
meson: remove obsolete check for ETH_FLAG_RXHASH
meson: remove obsolete check for ETHTOOL_GFEATURES
meson: remove obsolete check for ETHTOOL_GCOALESCE
meson: remove obsolete check for GET_VLAN_VID_CMD
meson: simplify check for virnetdevbridge.c headers
meson: remove obsolete check for DEVLINK_CMD_ESWITCH_GET
meson: remove obsolete check for linux/magic.h
meson: remove obsolete check for VHOST_VSOCK_SET_GUEST_CID
meson: remove obsolete check for BPF_PROG_QUERY
meson: remove obsolete check for BPF_CGROUP_DEVICE
meson.build | 82 +++--------------------------------
src/util/virbpf.c | 6 +--
src/util/virbpf.h | 6 +--
src/util/vircgroupv2devices.c | 10 ++---
src/util/virfile.c | 15 ++-----
src/util/virnetdev.c | 65 ++++-----------------------
src/util/virvsock.c | 4 +-
tests/securityselinuxhelper.c | 4 +-
tests/virfilemock.c | 2 +-
9 files changed, 32 insertions(+), 162 deletions(-)
--
2.38.1
2 years, 4 months
[libvirt PATCH 0/2] virt-qemu-sev-validate: A couple of small fixes
by Andrea Bolognani
Andrea Bolognani (2):
docs: Fix typo in virt-qemu-sev-validate(1)
tools: Fix interpreter for virt-qemu-sev-validate
docs/manpages/virt-qemu-sev-validate.rst | 2 +-
tools/virt-qemu-sev-validate | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.38.1
2 years, 4 months