2012-06-15 20:13:11 +04:00
%{?mingw_package_header}
2018-03-19 20:04:34 +03:00
# This spec file assumes you are building on a Fedora version
# that's still supported by the vendor. It may work on other distros
# or versions, but no effort will be made to ensure that going forward.
2019-05-07 13:10:58 +03:00
%define min_fedora 29
2018-03-19 20:04:34 +03:00
%if 0%{?fedora} && 0%{?fedora} >= %{min_fedora}
%define supported_platform 1
%else
%define supported_platform 0
%endif
2012-06-15 20:13:11 +04:00
# Default to skipping autoreconf. Distros can change just this one line
# (or provide a command-line override) if they backport any patches that
# touch configure.ac or Makefile.am.
%{!?enable_autotools:%define enable_autotools 0}
# The mingw build is client only. Set up defaults for hypervisor drivers
# that talk via a native remote protocol, and for which prereq mingw
# libraries exist.
%define with_phyp 0%{!?_without_phyp:1}
%define with_esx 0%{!?_without_esx:1}
# missing libwsman, so can't build hyper-v
%define with_hyperv 0%{!?_without_hyperv:0}
%define with_xenapi 0%{!?_without_xenapi:1}
2015-06-10 10:50:00 +03:00
%define with_vz 0%{!?_without_vz:0}
2012-06-15 20:13:11 +04:00
# RHEL ships ESX but not PowerHypervisor, HyperV, or libxenserver (xenapi)
%if 0%{?rhel}
2013-01-10 00:50:03 +04:00
%define with_phyp 0
%define with_xenapi 0
%define with_hyperv 0
2012-06-15 20:13:11 +04:00
%endif
Name : mingw-libvirt
Version : @VERSION@
2019-01-21 15:55:15 +03:00
Release : 1%{?dist}
2012-06-15 20:13:11 +04:00
Summary : MinGW Windows libvirt virtualization library
License : LGPLv2+
2017-05-11 19:31:08 +03:00
URL : https://libvirt.org/
2017-05-11 19:28:00 +03:00
%if %(echo %{version} | grep -q "\.0$"; echo $?) == 1
%define mainturl stable_updates/
%endif
2017-05-11 19:31:08 +03:00
Source : https://libvirt.org/sources/%{?mainturl} libvirt-%{version} .tar.xz
2012-06-15 20:13:11 +04:00
BuildRequires : mingw32-filesystem >= 95
BuildRequires : mingw64-filesystem >= 95
BuildRequires : mingw32-gcc
BuildRequires : mingw64-gcc
BuildRequires : mingw32-binutils
BuildRequires : mingw64-binutils
2019-07-30 12:13:36 +03:00
BuildRequires : mingw32-glib2 >= 2.48
BuildRequires : mingw64-glib2 >= 2.48
2012-06-15 20:13:11 +04:00
BuildRequires : mingw32-libgpg-error
BuildRequires : mingw64-libgpg-error
BuildRequires : mingw32-libgcrypt
BuildRequires : mingw64-libgcrypt
BuildRequires : mingw32-gnutls
BuildRequires : mingw64-gnutls
BuildRequires : mingw32-gettext
BuildRequires : mingw64-gettext
BuildRequires : mingw32-libxml2
BuildRequires : mingw64-libxml2
BuildRequires : mingw32-portablexdr
BuildRequires : mingw64-portablexdr
2017-08-02 13:21:12 +03:00
BuildRequires : mingw32-dlfcn
BuildRequires : mingw64-dlfcn
2012-06-15 20:13:11 +04:00
BuildRequires : pkgconfig
# Need native version for msgfmt
BuildRequires : gettext
2017-09-04 14:42:46 +03:00
BuildRequires : libxslt
2018-03-19 20:06:09 +03:00
BuildRequires : python3
2017-08-02 12:51:36 +03:00
BuildRequires : perl-interpreter
2016-07-01 16:11:15 +03:00
BuildRequires : perl(Getopt::Long)
2012-06-15 20:13:11 +04:00
%if 0%{?enable_autotools}
BuildRequires : autoconf
BuildRequires : automake
BuildRequires : gettext-devel
BuildRequires : libtool
%endif
BuildRequires : mingw32-libssh2
BuildRequires : mingw64-libssh2
%if %{with_esx}
BuildRequires : mingw32-curl
BuildRequires : mingw64-curl
%endif
BuildArch : noarch
%description
MinGW Windows libvirt virtualization library.
# Mingw32
%package -n mingw32-libvirt
Summary : %{summary}
%description -n mingw32-libvirt
MinGW Windows libvirt virtualization library.
%package -n mingw32-libvirt-static
Summary : %{summary}
Requires : mingw32-libvirt = %{version} -%{release}
%description -n mingw32-libvirt-static
MinGW Windows libvirt virtualization library, static version.
# Mingw64
%package -n mingw64-libvirt
Summary : %{summary}
%description -n mingw64-libvirt
MinGW Windows libvirt virtualization library.
%package -n mingw64-libvirt-static
Summary : %{summary}
Requires : mingw64-libvirt = %{version} -%{release}
%description -n mingw64-libvirt-static
MinGW Windows libvirt virtualization library, static version.
%{?mingw_debug_package}
%prep
%setup -q -n libvirt-%{version}
%build
2018-03-19 20:04:34 +03:00
%if ! %{supported_platform}
echo " T h i s R P M r e q u i r e s F e d o r a > = %{min_fedora} "
exit 1
%endif
2012-06-15 20:13:11 +04:00
%if ! %{with_phyp}
2013-01-10 00:50:03 +04:00
%define _without_phyp --without-phyp
2012-06-15 20:13:11 +04:00
%endif
%if ! %{with_esx}
2013-01-10 00:50:03 +04:00
%define _without_esx --without-esx
2012-06-15 20:13:11 +04:00
%endif
%if ! %{with_hyperv}
2013-01-10 00:50:03 +04:00
%define _without_hyperv --without-hyperv
2012-06-15 20:13:11 +04:00
%endif
%if ! %{with_xenapi}
2013-01-10 00:50:03 +04:00
%define _without_xenapi --without-xenapi
2012-06-15 20:13:11 +04:00
%endif
2015-06-10 10:50:00 +03:00
%if ! %{with_vz}
%define _without_vz --without-vz
2012-07-31 22:56:05 +04:00
%endif
2012-06-15 20:13:11 +04:00
%if 0%{?enable_autotools}
autoreconf -if
%endif
# XXX enable SASL in future
%mingw_configure \
--enable-static \
--without-xen \
--without-qemu \
--without-openvz \
--without-lxc \
--without-vbox \
%{?_without_xenapi} \
--without-sasl \
--without-polkit \
--without-libvirtd \
%{?_without_phyp} \
%{?_without_esx} \
%{?_without_hyperv} \
--without-vmware \
2012-07-31 22:56:05 +04:00
--without-parallels \
2012-06-15 20:13:11 +04:00
--without-netcf \
--without-audit \
build: add configure option to disable gnulib tests
The gnulib testsuite is relatively stable - the only times it is
likely to have a test change from pass to fail is on a gnulib
submodule update or a major system change (such as moving from
Fedora 18 to 19, or other large change to libc). While it is an
important test for end users on arbitrary machines (to make sure
that the portability glue works for their machine), it mostly
wastes time for development testing (as most developers aren't
making any of the major changes that would cause gnulib tests
to alter behavior). Thus, it pays to make the tests optional
at configure time, defaulting to off for development, on for
tarballs, with autobuilders requesting it to be on. It also
helps to allow a make-time override, via VIR_TEST_EXPENSIVE=[01]
(much the way automake sets up V=[01] for overriding the configure
time default of how verbose to be).
Automake has some pretty hard-coded magic with regards to the
TESTS variable; I had quite a job figuring out how to keep
'make distcheck' passing regardless of the configure option
setting in use, while still disabling the tests at runtime
when I did not configure them on and did not use the override
variable. Thankfully, we require GNU make, which lets me
hide some information from Automake's magic handling of TESTS.
* bootstrap.conf (bootstrap_epilogue): Munge gnulib test variable.
* configure.ac (--enable-expensive-tests): Add new enable switch.
(VIR_TEST_EXPENSIVE_DEFAULT, WITH_EXPENSIVE_TESTS): Set new
witnesses.
* gnulib/tests/Makefile.am (TESTS): Make tests conditional on
configure settings and the VIR_TEST_EXPENSIVE variable.
* tests/Makefile.am (TESTS_ENVIRONMENT): Expose VIR_TEST_EXPENSIVE
to all tests.
* autobuild.sh: Enable all tests during autobuilds.
* libvirt.spec.in (%configure): Likewise.
* mingw-libvirt.spec.in (%mingw_configure): Likewise.
* docs/hacking.html.in: Document the option.
* HACKING: Regenerate.
Signed-off-by: Eric Blake <eblake@redhat.com>
2013-07-31 17:18:58 +04:00
--without-dtrace \
--enable-expensive-tests
2012-06-15 20:13:11 +04:00
%mingw_make %{?_smp_mflags}
%install
%mingw_make_install " D E S T D I R = $RPM_BUILD_ROOT "
# Libtool files don't need to be bundled
find $RPM_BUILD_ROOT -name " * . l a " -delete
rm -rf $RPM_BUILD_ROOT %{mingw32_sysconfdir} /libvirt/nwfilter
rm -rf $RPM_BUILD_ROOT %{mingw64_sysconfdir} /libvirt/nwfilter
rm -rf $RPM_BUILD_ROOT %{mingw32_datadir} /doc/*
rm -rf $RPM_BUILD_ROOT %{mingw64_datadir} /doc/*
rm -rf $RPM_BUILD_ROOT %{mingw32_datadir} /gtk-doc/*
rm -rf $RPM_BUILD_ROOT %{mingw64_datadir} /gtk-doc/*
rm -rf $RPM_BUILD_ROOT %{mingw32_libexecdir} /libvirt_iohelper.exe
rm -rf $RPM_BUILD_ROOT %{mingw64_libexecdir} /libvirt_iohelper.exe
2013-01-05 03:36:57 +04:00
rm -rf $RPM_BUILD_ROOT %{mingw32_libexecdir} /libvirt-guests.sh
rm -rf $RPM_BUILD_ROOT %{mingw64_libexecdir} /libvirt-guests.sh
2012-06-15 20:13:11 +04:00
# Mingw32
%files -n mingw32-libvirt
%dir %{mingw32_sysconfdir} /libvirt/
%config (noreplace) %{mingw32_sysconfdir} /libvirt/libvirt.conf
2016-07-01 14:41:32 +03:00
%config (noreplace) %{mingw32_sysconfdir} /libvirt/libvirt-admin.conf
2012-06-15 20:13:11 +04:00
%{mingw32_bindir} /libvirt-0.dll
%{mingw32_bindir} /virsh.exe
2016-07-01 14:41:32 +03:00
%{mingw32_bindir} /virt-admin.exe
2012-06-15 20:13:11 +04:00
%{mingw32_bindir} /virt-xml-validate
%{mingw32_bindir} /virt-pki-validate
Introduce an LXC specific public API & library
This patch introduces support for LXC specific public APIs. In
common with what was done for QEMU, this creates a libvirt_lxc.so
library and libvirt/libvirt-lxc.h header file.
The actual APIs are
int virDomainLxcOpenNamespace(virDomainPtr domain,
int **fdlist,
unsigned int flags);
int virDomainLxcEnterNamespace(virDomainPtr domain,
unsigned int nfdlist,
int *fdlist,
unsigned int *noldfdlist,
int **oldfdlist,
unsigned int flags);
which provide a way to use the setns() system call to move the
calling process into the container's namespace. It is not
practical to write in a generically applicable manner. The
nearest that we could get to such an API would be an API which
allows to pass a command + argv to be executed inside a
container. Even if we had such a generic API, this LXC specific
API is still useful, because it allows the caller to maintain
the current process context, in particular any I/O streams they
have open.
NB the virDomainLxcEnterNamespace() API is special in that it
runs client side, so does not involve the internal driver API.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2012-12-21 17:15:19 +04:00
%{mingw32_bindir} /libvirt-lxc-0.dll
2012-06-15 20:13:11 +04:00
%{mingw32_bindir} /libvirt-qemu-0.dll
2016-07-01 14:41:32 +03:00
%{mingw32_bindir} /libvirt-admin-0.dll
2012-06-15 20:13:11 +04:00
%{mingw32_libdir} /libvirt.dll.a
%{mingw32_libdir} /pkgconfig/libvirt.pc
2014-06-20 20:47:15 +04:00
%{mingw32_libdir} /pkgconfig/libvirt-qemu.pc
%{mingw32_libdir} /pkgconfig/libvirt-lxc.pc
2016-07-01 14:41:32 +03:00
%{mingw32_libdir} /pkgconfig/libvirt-admin.pc
Introduce an LXC specific public API & library
This patch introduces support for LXC specific public APIs. In
common with what was done for QEMU, this creates a libvirt_lxc.so
library and libvirt/libvirt-lxc.h header file.
The actual APIs are
int virDomainLxcOpenNamespace(virDomainPtr domain,
int **fdlist,
unsigned int flags);
int virDomainLxcEnterNamespace(virDomainPtr domain,
unsigned int nfdlist,
int *fdlist,
unsigned int *noldfdlist,
int **oldfdlist,
unsigned int flags);
which provide a way to use the setns() system call to move the
calling process into the container's namespace. It is not
practical to write in a generically applicable manner. The
nearest that we could get to such an API would be an API which
allows to pass a command + argv to be executed inside a
container. Even if we had such a generic API, this LXC specific
API is still useful, because it allows the caller to maintain
the current process context, in particular any I/O streams they
have open.
NB the virDomainLxcEnterNamespace() API is special in that it
runs client side, so does not involve the internal driver API.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2012-12-21 17:15:19 +04:00
%{mingw32_libdir} /libvirt-lxc.dll.a
2012-06-15 20:13:11 +04:00
%{mingw32_libdir} /libvirt-qemu.dll.a
2016-07-01 14:41:32 +03:00
%{mingw32_libdir} /libvirt-admin.dll.a
2012-06-15 20:13:11 +04:00
%dir %{mingw32_datadir} /libvirt/
%dir %{mingw32_datadir} /libvirt/schemas/
%{mingw32_datadir} /libvirt/schemas/basictypes.rng
%{mingw32_datadir} /libvirt/schemas/capability.rng
2016-09-27 16:40:24 +03:00
%{mingw32_datadir} /libvirt/schemas/cputypes.rng
2012-06-15 20:13:11 +04:00
%{mingw32_datadir} /libvirt/schemas/domain.rng
2014-06-25 15:24:53 +04:00
%{mingw32_datadir} /libvirt/schemas/domaincaps.rng
2018-06-12 06:12:21 +03:00
%{mingw32_datadir} /libvirt/schemas/domaincheckpoint.rng
2012-06-15 20:13:11 +04:00
%{mingw32_datadir} /libvirt/schemas/domaincommon.rng
%{mingw32_datadir} /libvirt/schemas/domainsnapshot.rng
%{mingw32_datadir} /libvirt/schemas/interface.rng
%{mingw32_datadir} /libvirt/schemas/network.rng
%{mingw32_datadir} /libvirt/schemas/networkcommon.rng
2019-07-03 19:16:20 +03:00
%{mingw32_datadir} /libvirt/schemas/networkport.rng
2012-06-15 20:13:11 +04:00
%{mingw32_datadir} /libvirt/schemas/nodedev.rng
%{mingw32_datadir} /libvirt/schemas/nwfilter.rng
2018-07-03 18:32:08 +03:00
%{mingw32_datadir} /libvirt/schemas/nwfilter_params.rng
%{mingw32_datadir} /libvirt/schemas/nwfilterbinding.rng
2012-06-15 20:13:11 +04:00
%{mingw32_datadir} /libvirt/schemas/secret.rng
2014-04-12 05:33:45 +04:00
%{mingw32_datadir} /libvirt/schemas/storagecommon.rng
2012-06-15 20:13:11 +04:00
%{mingw32_datadir} /libvirt/schemas/storagepool.rng
2019-02-07 20:29:15 +03:00
%{mingw32_datadir} /libvirt/schemas/storagepoolcaps.rng
2012-06-15 20:13:11 +04:00
%{mingw32_datadir} /libvirt/schemas/storagevol.rng
%dir %{mingw32_datadir} /libvirt/api/
%{mingw32_datadir} /libvirt/api/libvirt-api.xml
Introduce an LXC specific public API & library
This patch introduces support for LXC specific public APIs. In
common with what was done for QEMU, this creates a libvirt_lxc.so
library and libvirt/libvirt-lxc.h header file.
The actual APIs are
int virDomainLxcOpenNamespace(virDomainPtr domain,
int **fdlist,
unsigned int flags);
int virDomainLxcEnterNamespace(virDomainPtr domain,
unsigned int nfdlist,
int *fdlist,
unsigned int *noldfdlist,
int **oldfdlist,
unsigned int flags);
which provide a way to use the setns() system call to move the
calling process into the container's namespace. It is not
practical to write in a generically applicable manner. The
nearest that we could get to such an API would be an API which
allows to pass a command + argv to be executed inside a
container. Even if we had such a generic API, this LXC specific
API is still useful, because it allows the caller to maintain
the current process context, in particular any I/O streams they
have open.
NB the virDomainLxcEnterNamespace() API is special in that it
runs client side, so does not involve the internal driver API.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2012-12-21 17:15:19 +04:00
%{mingw32_datadir} /libvirt/api/libvirt-lxc-api.xml
2012-06-15 20:13:11 +04:00
%{mingw32_datadir} /libvirt/api/libvirt-qemu-api.xml
2016-07-01 14:41:32 +03:00
%{mingw32_datadir} /libvirt/api/libvirt-admin-api.xml
2012-06-15 20:13:11 +04:00
2018-08-16 14:39:39 +03:00
%{mingw32_datadir} /libvirt/cpu_map/*.xml
2012-06-15 20:13:11 +04:00
2016-12-06 15:45:18 +03:00
%{mingw32_datadir} /libvirt/test-screenshot.png
2012-06-15 20:13:11 +04:00
%{mingw32_datadir} /locale/*/LC_MESSAGES/libvirt.mo
%dir %{mingw32_includedir} /libvirt
%{mingw32_includedir} /libvirt/libvirt.h
2016-07-01 14:41:32 +03:00
%{mingw32_includedir} /libvirt/libvirt-common.h
2014-10-23 14:28:16 +04:00
%{mingw32_includedir} /libvirt/libvirt-domain.h
backup: Introduce virDomainCheckpoint APIs
Introduce a bunch of new public APIs related to backup checkpoints.
Checkpoints are modeled heavily after virDomainSnapshotPtr (both
represent a point in time of the guest), although a snapshot exists
with the intent of rolling back to that state, while a checkpoint
exists to make it possible to create an incremental backup at a later
time. We may have a future hypervisor that can completely manage
checkpoints without libvirt metadata, but the first two planned
hypervisors (qemu and test) both always use libvirt for tracking
metadata relations between checkpoints, so for now, I've deferred
the counterpart of virDomainSnapshotHasMetadata for a separate
API addition at a later date if there is ever a need for it.
Note that until we allow snapshots and checkpoints to exist
simultaneously on the same domain (although the actual prevention of
this will be in a separate patch for the sake of an easier revert down
the road), that it is not possible to branch out to create more than
one checkpoint child to a given parent, although it may become
possible later when we revert to a snapshot that coincides with a
checkpoint. This also means that for now, the decision of which
checkpoint becomes the parent of a newly created one is the only
checkpoint with no child (so while there are APIs for dealing with a
current snapshot, we do not need those for checkpoints). We may end
up exposing a notion of a current checkpoint later, but it's easier to
add stuff when proven needed than to blindly support it now and wish
we hadn't exposed it.
The following map shows the API relations to snapshots, with new APIs
on the right:
Operate on a domain object to create/redefine a child:
virDomainSnapshotCreateXML virDomainCheckpointCreateXML
Operate on a child object for lifetime management:
virDomainSnapshotDelete virDomainCheckpointDelete
virDomainSnapshotFree virDomainCheckpointFree
virDomainSnapshotRef virDomainCheckpointRef
Operate on a child object to learn more about it:
virDomainSnapshotGetXMLDesc virDomainCheckpointGetXMLDesc
virDomainSnapshotGetConnect virDomainCheckpointGetConnect
virDomainSnapshotGetDomain virDomainCheckpointGetDomain
virDomainSnapshotGetName virDomainCheckpiontGetName
virDomainSnapshotGetParent virDomainCheckpiontGetParent
virDomainSnapshotHasMetadata (deferred for later)
virDomainSnapshotIsCurrent (no counterpart, see note above)
Operate on a domain object to list all children:
virDomainSnapshotNum (no counterparts, these are the old
virDomainSnapshotListNames racy interfaces)
virDomainSnapshotListAllSnapshots virDomainListAllCheckpoints
Operate on a child object to list descendents:
virDomainSnapshotNumChildren (no counterparts, these are the old
virDomainSnapshotListChildrenNames racy interfaces)
virDomainSnapshotListAllChildren virDomainCheckpointListAllChildren
Operate on a domain to locate a particular child:
virDomainSnapshotLookupByName virDomainCheckpointLookupByName
virDomainSnapshotCurrent (no counterpart, see note above)
virDomainHasCurrentSnapshot (no counterpart, old racy interface)
Operate on a snapshot to roll back to earlier state:
virDomainSnapshotRevert (no counterpart, instead checkpoints
are used in incremental backups via
XML to virDomainBackupBegin)
Signed-off-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2019-03-13 22:35:26 +03:00
%{mingw32_includedir} /libvirt/libvirt-domain-checkpoint.h
2014-10-23 14:28:16 +04:00
%{mingw32_includedir} /libvirt/libvirt-domain-snapshot.h
2014-10-23 14:28:16 +04:00
%{mingw32_includedir} /libvirt/libvirt-event.h
2014-10-23 14:28:16 +04:00
%{mingw32_includedir} /libvirt/libvirt-host.h
2014-10-23 14:28:16 +04:00
%{mingw32_includedir} /libvirt/libvirt-interface.h
2014-10-23 14:28:16 +04:00
%{mingw32_includedir} /libvirt/libvirt-network.h
2014-10-23 14:28:16 +04:00
%{mingw32_includedir} /libvirt/libvirt-nodedev.h
2014-10-23 14:28:16 +04:00
%{mingw32_includedir} /libvirt/libvirt-nwfilter.h
2014-10-23 14:28:16 +04:00
%{mingw32_includedir} /libvirt/libvirt-secret.h
2014-10-23 14:28:16 +04:00
%{mingw32_includedir} /libvirt/libvirt-storage.h
2014-10-23 14:28:16 +04:00
%{mingw32_includedir} /libvirt/libvirt-stream.h
2012-06-15 20:13:11 +04:00
%{mingw32_includedir} /libvirt/virterror.h
Introduce an LXC specific public API & library
This patch introduces support for LXC specific public APIs. In
common with what was done for QEMU, this creates a libvirt_lxc.so
library and libvirt/libvirt-lxc.h header file.
The actual APIs are
int virDomainLxcOpenNamespace(virDomainPtr domain,
int **fdlist,
unsigned int flags);
int virDomainLxcEnterNamespace(virDomainPtr domain,
unsigned int nfdlist,
int *fdlist,
unsigned int *noldfdlist,
int **oldfdlist,
unsigned int flags);
which provide a way to use the setns() system call to move the
calling process into the container's namespace. It is not
practical to write in a generically applicable manner. The
nearest that we could get to such an API would be an API which
allows to pass a command + argv to be executed inside a
container. Even if we had such a generic API, this LXC specific
API is still useful, because it allows the caller to maintain
the current process context, in particular any I/O streams they
have open.
NB the virDomainLxcEnterNamespace() API is special in that it
runs client side, so does not involve the internal driver API.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2012-12-21 17:15:19 +04:00
%{mingw32_includedir} /libvirt/libvirt-lxc.h
2012-06-15 20:13:11 +04:00
%{mingw32_includedir} /libvirt/libvirt-qemu.h
2016-07-01 14:41:32 +03:00
%{mingw32_includedir} /libvirt/libvirt-admin.h
2012-06-15 20:13:11 +04:00
%{mingw32_mandir} /man1/virsh.1*
2016-07-01 14:41:32 +03:00
%{mingw32_mandir} /man1/virt-admin.1*
2012-06-15 20:13:11 +04:00
%{mingw32_mandir} /man1/virt-xml-validate.1*
%{mingw32_mandir} /man1/virt-pki-validate.1*
2017-03-03 15:43:51 +03:00
%{mingw32_mandir} /man7/virkey*.7*
2012-06-15 20:13:11 +04:00
%files -n mingw32-libvirt-static
%{mingw32_libdir} /libvirt.a
Introduce an LXC specific public API & library
This patch introduces support for LXC specific public APIs. In
common with what was done for QEMU, this creates a libvirt_lxc.so
library and libvirt/libvirt-lxc.h header file.
The actual APIs are
int virDomainLxcOpenNamespace(virDomainPtr domain,
int **fdlist,
unsigned int flags);
int virDomainLxcEnterNamespace(virDomainPtr domain,
unsigned int nfdlist,
int *fdlist,
unsigned int *noldfdlist,
int **oldfdlist,
unsigned int flags);
which provide a way to use the setns() system call to move the
calling process into the container's namespace. It is not
practical to write in a generically applicable manner. The
nearest that we could get to such an API would be an API which
allows to pass a command + argv to be executed inside a
container. Even if we had such a generic API, this LXC specific
API is still useful, because it allows the caller to maintain
the current process context, in particular any I/O streams they
have open.
NB the virDomainLxcEnterNamespace() API is special in that it
runs client side, so does not involve the internal driver API.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2012-12-21 17:15:19 +04:00
%{mingw32_libdir} /libvirt-lxc.a
2012-06-15 20:13:11 +04:00
%{mingw32_libdir} /libvirt-qemu.a
2016-07-01 14:41:32 +03:00
%{mingw32_libdir} /libvirt-admin.a
2012-06-15 20:13:11 +04:00
# Mingw64
%files -n mingw64-libvirt
%dir %{mingw64_sysconfdir} /libvirt/
%config (noreplace) %{mingw64_sysconfdir} /libvirt/libvirt.conf
2016-07-01 14:41:32 +03:00
%config (noreplace) %{mingw64_sysconfdir} /libvirt/libvirt-admin.conf
2012-06-15 20:13:11 +04:00
%{mingw64_bindir} /libvirt-0.dll
%{mingw64_bindir} /virsh.exe
2016-07-01 14:41:32 +03:00
%{mingw64_bindir} /virt-admin.exe
2012-06-15 20:13:11 +04:00
%{mingw64_bindir} /virt-xml-validate
%{mingw64_bindir} /virt-pki-validate
Introduce an LXC specific public API & library
This patch introduces support for LXC specific public APIs. In
common with what was done for QEMU, this creates a libvirt_lxc.so
library and libvirt/libvirt-lxc.h header file.
The actual APIs are
int virDomainLxcOpenNamespace(virDomainPtr domain,
int **fdlist,
unsigned int flags);
int virDomainLxcEnterNamespace(virDomainPtr domain,
unsigned int nfdlist,
int *fdlist,
unsigned int *noldfdlist,
int **oldfdlist,
unsigned int flags);
which provide a way to use the setns() system call to move the
calling process into the container's namespace. It is not
practical to write in a generically applicable manner. The
nearest that we could get to such an API would be an API which
allows to pass a command + argv to be executed inside a
container. Even if we had such a generic API, this LXC specific
API is still useful, because it allows the caller to maintain
the current process context, in particular any I/O streams they
have open.
NB the virDomainLxcEnterNamespace() API is special in that it
runs client side, so does not involve the internal driver API.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2012-12-21 17:15:19 +04:00
%{mingw64_bindir} /libvirt-lxc-0.dll
2012-06-15 20:13:11 +04:00
%{mingw64_bindir} /libvirt-qemu-0.dll
2016-07-01 14:41:32 +03:00
%{mingw64_bindir} /libvirt-admin-0.dll
2012-06-15 20:13:11 +04:00
%{mingw64_libdir} /libvirt.dll.a
%{mingw64_libdir} /pkgconfig/libvirt.pc
2014-07-10 02:45:15 +04:00
%{mingw64_libdir} /pkgconfig/libvirt-qemu.pc
%{mingw64_libdir} /pkgconfig/libvirt-lxc.pc
2016-07-01 14:41:32 +03:00
%{mingw64_libdir} /pkgconfig/libvirt-admin.pc
Introduce an LXC specific public API & library
This patch introduces support for LXC specific public APIs. In
common with what was done for QEMU, this creates a libvirt_lxc.so
library and libvirt/libvirt-lxc.h header file.
The actual APIs are
int virDomainLxcOpenNamespace(virDomainPtr domain,
int **fdlist,
unsigned int flags);
int virDomainLxcEnterNamespace(virDomainPtr domain,
unsigned int nfdlist,
int *fdlist,
unsigned int *noldfdlist,
int **oldfdlist,
unsigned int flags);
which provide a way to use the setns() system call to move the
calling process into the container's namespace. It is not
practical to write in a generically applicable manner. The
nearest that we could get to such an API would be an API which
allows to pass a command + argv to be executed inside a
container. Even if we had such a generic API, this LXC specific
API is still useful, because it allows the caller to maintain
the current process context, in particular any I/O streams they
have open.
NB the virDomainLxcEnterNamespace() API is special in that it
runs client side, so does not involve the internal driver API.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2012-12-21 17:15:19 +04:00
%{mingw64_libdir} /libvirt-lxc.dll.a
2012-06-15 20:13:11 +04:00
%{mingw64_libdir} /libvirt-qemu.dll.a
2016-07-01 14:41:32 +03:00
%{mingw64_libdir} /libvirt-admin.dll.a
2012-06-15 20:13:11 +04:00
%dir %{mingw64_datadir} /libvirt/
%dir %{mingw64_datadir} /libvirt/schemas/
%{mingw64_datadir} /libvirt/schemas/basictypes.rng
%{mingw64_datadir} /libvirt/schemas/capability.rng
2016-09-27 15:45:40 +03:00
%{mingw64_datadir} /libvirt/schemas/cputypes.rng
2012-06-15 20:13:11 +04:00
%{mingw64_datadir} /libvirt/schemas/domain.rng
2014-06-25 15:24:53 +04:00
%{mingw64_datadir} /libvirt/schemas/domaincaps.rng
2018-06-12 06:12:21 +03:00
%{mingw64_datadir} /libvirt/schemas/domaincheckpoint.rng
2012-06-15 20:13:11 +04:00
%{mingw64_datadir} /libvirt/schemas/domaincommon.rng
%{mingw64_datadir} /libvirt/schemas/domainsnapshot.rng
%{mingw64_datadir} /libvirt/schemas/interface.rng
%{mingw64_datadir} /libvirt/schemas/network.rng
%{mingw64_datadir} /libvirt/schemas/networkcommon.rng
2019-07-03 19:16:20 +03:00
%{mingw64_datadir} /libvirt/schemas/networkport.rng
2012-06-15 20:13:11 +04:00
%{mingw64_datadir} /libvirt/schemas/nodedev.rng
%{mingw64_datadir} /libvirt/schemas/nwfilter.rng
2018-07-03 18:32:08 +03:00
%{mingw64_datadir} /libvirt/schemas/nwfilter_params.rng
%{mingw64_datadir} /libvirt/schemas/nwfilterbinding.rng
2012-06-15 20:13:11 +04:00
%{mingw64_datadir} /libvirt/schemas/secret.rng
2014-04-12 05:33:45 +04:00
%{mingw64_datadir} /libvirt/schemas/storagecommon.rng
2012-06-15 20:13:11 +04:00
%{mingw64_datadir} /libvirt/schemas/storagepool.rng
2019-02-07 20:29:15 +03:00
%{mingw64_datadir} /libvirt/schemas/storagepoolcaps.rng
2012-06-15 20:13:11 +04:00
%{mingw64_datadir} /libvirt/schemas/storagevol.rng
%dir %{mingw64_datadir} /libvirt/api/
%{mingw64_datadir} /libvirt/api/libvirt-api.xml
Introduce an LXC specific public API & library
This patch introduces support for LXC specific public APIs. In
common with what was done for QEMU, this creates a libvirt_lxc.so
library and libvirt/libvirt-lxc.h header file.
The actual APIs are
int virDomainLxcOpenNamespace(virDomainPtr domain,
int **fdlist,
unsigned int flags);
int virDomainLxcEnterNamespace(virDomainPtr domain,
unsigned int nfdlist,
int *fdlist,
unsigned int *noldfdlist,
int **oldfdlist,
unsigned int flags);
which provide a way to use the setns() system call to move the
calling process into the container's namespace. It is not
practical to write in a generically applicable manner. The
nearest that we could get to such an API would be an API which
allows to pass a command + argv to be executed inside a
container. Even if we had such a generic API, this LXC specific
API is still useful, because it allows the caller to maintain
the current process context, in particular any I/O streams they
have open.
NB the virDomainLxcEnterNamespace() API is special in that it
runs client side, so does not involve the internal driver API.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2012-12-21 17:15:19 +04:00
%{mingw64_datadir} /libvirt/api/libvirt-lxc-api.xml
2012-06-15 20:13:11 +04:00
%{mingw64_datadir} /libvirt/api/libvirt-qemu-api.xml
2016-07-01 14:41:32 +03:00
%{mingw64_datadir} /libvirt/api/libvirt-admin-api.xml
2012-06-15 20:13:11 +04:00
2018-08-16 14:39:39 +03:00
%{mingw64_datadir} /libvirt/cpu_map/*.xml
2012-06-15 20:13:11 +04:00
2016-12-06 15:45:18 +03:00
%{mingw64_datadir} /libvirt/test-screenshot.png
2012-06-15 20:13:11 +04:00
%{mingw64_datadir} /locale/*/LC_MESSAGES/libvirt.mo
%dir %{mingw64_includedir} /libvirt
%{mingw64_includedir} /libvirt/libvirt.h
2016-07-01 14:41:32 +03:00
%{mingw64_includedir} /libvirt/libvirt-common.h
2014-10-23 14:28:16 +04:00
%{mingw64_includedir} /libvirt/libvirt-domain.h
backup: Introduce virDomainCheckpoint APIs
Introduce a bunch of new public APIs related to backup checkpoints.
Checkpoints are modeled heavily after virDomainSnapshotPtr (both
represent a point in time of the guest), although a snapshot exists
with the intent of rolling back to that state, while a checkpoint
exists to make it possible to create an incremental backup at a later
time. We may have a future hypervisor that can completely manage
checkpoints without libvirt metadata, but the first two planned
hypervisors (qemu and test) both always use libvirt for tracking
metadata relations between checkpoints, so for now, I've deferred
the counterpart of virDomainSnapshotHasMetadata for a separate
API addition at a later date if there is ever a need for it.
Note that until we allow snapshots and checkpoints to exist
simultaneously on the same domain (although the actual prevention of
this will be in a separate patch for the sake of an easier revert down
the road), that it is not possible to branch out to create more than
one checkpoint child to a given parent, although it may become
possible later when we revert to a snapshot that coincides with a
checkpoint. This also means that for now, the decision of which
checkpoint becomes the parent of a newly created one is the only
checkpoint with no child (so while there are APIs for dealing with a
current snapshot, we do not need those for checkpoints). We may end
up exposing a notion of a current checkpoint later, but it's easier to
add stuff when proven needed than to blindly support it now and wish
we hadn't exposed it.
The following map shows the API relations to snapshots, with new APIs
on the right:
Operate on a domain object to create/redefine a child:
virDomainSnapshotCreateXML virDomainCheckpointCreateXML
Operate on a child object for lifetime management:
virDomainSnapshotDelete virDomainCheckpointDelete
virDomainSnapshotFree virDomainCheckpointFree
virDomainSnapshotRef virDomainCheckpointRef
Operate on a child object to learn more about it:
virDomainSnapshotGetXMLDesc virDomainCheckpointGetXMLDesc
virDomainSnapshotGetConnect virDomainCheckpointGetConnect
virDomainSnapshotGetDomain virDomainCheckpointGetDomain
virDomainSnapshotGetName virDomainCheckpiontGetName
virDomainSnapshotGetParent virDomainCheckpiontGetParent
virDomainSnapshotHasMetadata (deferred for later)
virDomainSnapshotIsCurrent (no counterpart, see note above)
Operate on a domain object to list all children:
virDomainSnapshotNum (no counterparts, these are the old
virDomainSnapshotListNames racy interfaces)
virDomainSnapshotListAllSnapshots virDomainListAllCheckpoints
Operate on a child object to list descendents:
virDomainSnapshotNumChildren (no counterparts, these are the old
virDomainSnapshotListChildrenNames racy interfaces)
virDomainSnapshotListAllChildren virDomainCheckpointListAllChildren
Operate on a domain to locate a particular child:
virDomainSnapshotLookupByName virDomainCheckpointLookupByName
virDomainSnapshotCurrent (no counterpart, see note above)
virDomainHasCurrentSnapshot (no counterpart, old racy interface)
Operate on a snapshot to roll back to earlier state:
virDomainSnapshotRevert (no counterpart, instead checkpoints
are used in incremental backups via
XML to virDomainBackupBegin)
Signed-off-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2019-03-13 22:35:26 +03:00
%{mingw64_includedir} /libvirt/libvirt-domain-checkpoint.h
2014-10-23 14:28:16 +04:00
%{mingw64_includedir} /libvirt/libvirt-domain-snapshot.h
2014-10-23 14:28:16 +04:00
%{mingw64_includedir} /libvirt/libvirt-event.h
2014-10-23 14:28:16 +04:00
%{mingw64_includedir} /libvirt/libvirt-host.h
2014-10-23 14:28:16 +04:00
%{mingw64_includedir} /libvirt/libvirt-interface.h
2014-10-23 14:28:16 +04:00
%{mingw64_includedir} /libvirt/libvirt-network.h
2014-10-23 14:28:16 +04:00
%{mingw64_includedir} /libvirt/libvirt-nodedev.h
2014-10-23 14:28:16 +04:00
%{mingw64_includedir} /libvirt/libvirt-nwfilter.h
2014-10-23 14:28:16 +04:00
%{mingw64_includedir} /libvirt/libvirt-secret.h
2014-10-23 14:28:16 +04:00
%{mingw64_includedir} /libvirt/libvirt-storage.h
2014-10-23 14:28:16 +04:00
%{mingw64_includedir} /libvirt/libvirt-stream.h
2012-06-15 20:13:11 +04:00
%{mingw64_includedir} /libvirt/virterror.h
Introduce an LXC specific public API & library
This patch introduces support for LXC specific public APIs. In
common with what was done for QEMU, this creates a libvirt_lxc.so
library and libvirt/libvirt-lxc.h header file.
The actual APIs are
int virDomainLxcOpenNamespace(virDomainPtr domain,
int **fdlist,
unsigned int flags);
int virDomainLxcEnterNamespace(virDomainPtr domain,
unsigned int nfdlist,
int *fdlist,
unsigned int *noldfdlist,
int **oldfdlist,
unsigned int flags);
which provide a way to use the setns() system call to move the
calling process into the container's namespace. It is not
practical to write in a generically applicable manner. The
nearest that we could get to such an API would be an API which
allows to pass a command + argv to be executed inside a
container. Even if we had such a generic API, this LXC specific
API is still useful, because it allows the caller to maintain
the current process context, in particular any I/O streams they
have open.
NB the virDomainLxcEnterNamespace() API is special in that it
runs client side, so does not involve the internal driver API.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2012-12-21 17:15:19 +04:00
%{mingw64_includedir} /libvirt/libvirt-lxc.h
2012-06-15 20:13:11 +04:00
%{mingw64_includedir} /libvirt/libvirt-qemu.h
2016-07-01 14:41:32 +03:00
%{mingw64_includedir} /libvirt/libvirt-admin.h
2012-06-15 20:13:11 +04:00
%{mingw64_mandir} /man1/virsh.1*
2016-07-01 14:41:32 +03:00
%{mingw64_mandir} /man1/virt-admin.1*
2012-06-15 20:13:11 +04:00
%{mingw64_mandir} /man1/virt-xml-validate.1*
%{mingw64_mandir} /man1/virt-pki-validate.1*
2017-03-03 15:43:51 +03:00
%{mingw64_mandir} /man7/virkey*.7*
2012-06-15 20:13:11 +04:00
%files -n mingw64-libvirt-static
%{mingw64_libdir} /libvirt.a
Introduce an LXC specific public API & library
This patch introduces support for LXC specific public APIs. In
common with what was done for QEMU, this creates a libvirt_lxc.so
library and libvirt/libvirt-lxc.h header file.
The actual APIs are
int virDomainLxcOpenNamespace(virDomainPtr domain,
int **fdlist,
unsigned int flags);
int virDomainLxcEnterNamespace(virDomainPtr domain,
unsigned int nfdlist,
int *fdlist,
unsigned int *noldfdlist,
int **oldfdlist,
unsigned int flags);
which provide a way to use the setns() system call to move the
calling process into the container's namespace. It is not
practical to write in a generically applicable manner. The
nearest that we could get to such an API would be an API which
allows to pass a command + argv to be executed inside a
container. Even if we had such a generic API, this LXC specific
API is still useful, because it allows the caller to maintain
the current process context, in particular any I/O streams they
have open.
NB the virDomainLxcEnterNamespace() API is special in that it
runs client side, so does not involve the internal driver API.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2012-12-21 17:15:19 +04:00
%{mingw64_libdir} /libvirt-lxc.a
2012-06-15 20:13:11 +04:00
%{mingw64_libdir} /libvirt-qemu.a
2016-07-01 14:41:32 +03:00
%{mingw64_libdir} /libvirt-admin.a
2012-06-15 20:13:11 +04:00
%changelog