QEMU is a generic and open source machine emulator and virtualizer.
QEMU can be used in several different ways. The most common is for System Emulation, where it provides a virtual model of an entire machine (CPU, memory and emulated devices) to run a guest OS. In this mode the CPU may be fully emulated, or it may work with a hypervisor such as KVM or Xen to allow the guest to run directly on the host CPU.
Note that this package is produced using a Git based workflow. Please refer to README.PACKAGING before making modifications.
Embed a build result badge whereever you need it. Select from
the options below and copy the result over to your README or on
your website, and enjoy it refresh automatically whenever the
build result changes.
- Include upstream patches designated as stable material and
reviewed for applicability to include here. NOTE that the
PIIX4 patch has migration implications: the change will also be
applied to the SLE-15-SP2 qemu, and a live migration from that
version to this SLE-15-SP3 qemu would require this patch to be
applied for a successful migration if PIIX4 southbridge is used
in the machine emulation (x86 i440fx)
block-rbd-fix-memory-leak-in-qemu_rbd_co.patch
block-rbd-Fix-memory-leak-in-qemu_rbd_co.patch
cpu-core-Fix-help-of-CPU-core-device-typ.patch
hw-arm-virt-acpi-build-Fix-GSIV-values-o.patch
hw-block-fdc-Fix-fallback-property-on-sy.patch
hw-isa-Kconfig-Add-missing-dependency-VI.patch
hw-isa-piix4-Migrate-Reset-Control-Regis.patch
hw-virtio-pci-Added-AER-capability.patch
hw-virtio-pci-Added-counter-for-pcie-cap.patch
s390x-css-report-errors-from-ccw_dstream.patch
target-xtensa-fix-meson.build-rule-for-x.patch
util-fix-use-after-free-in-module_load_o.patch
virtio-pci-compat-page-aligned-ATS.patch
I'm sorry, maybe I still missing something about Obsoletes & Friends enough... Can you help me understand why qemu-kvm would be missing for all arches? In fact, I'm not only Obsoleting it, I'm also Providing it, isn't that fine?
FWIW, I've done a few tests with this repository enabled, and it seemed to work:
$ zypper lr
Repository priorities in effect: > (See 'zypper lr -P' for details)
90 (raised priority) : 1 repository
99 (default priority) : 4 repositories
$ zypper in --from 1 qemu-kvm
Loading repository data...
Reading installed packages...
'qemu-kvm' not found in package names. Trying capabilities.
Resolving package dependencies...
The following 37 NEW packages are going to be installed:
acl canokey-qemu kernel-devel kernel-macros libaio1 libcapstone4 libefa1 libfdt1 libibverbs libibverbs1 libjpeg8 liblzo2-2 libmana1 libmlx4-1 libmlx5-1 libndctl6 libnuma1 libpixman-1-0 libpmem1 libpng16-16 librdmacm1 libslirp0 libsnappy1 liburing2 libvdeplug3 libxdp1
libyajl2 qemu qemu-accel-tcg-x86 qemu-ipxe qemu-ovmf-x86_64 qemu-seabios qemu-vgabios qemu-x86 rdma-core system-user-qemu xen-libs
I.e., as you can see, no qemu-kvm package is being installed:
$ rpm -qa|grep qemu-kvm
$
And:
$ zypper in --from 1 qemu-kvm
Loading repository data...
Reading installed packages...
'qemu-kvm' not found in package names. Trying capabilities.
'qemu' providing 'qemu-kvm' is already installed.
Resolving package dependencies...
Nothing to do.
$ zypper se --provides qemu-kvm
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+----------------------+----------------------------------------------------+-----------
| os-autoinst-qemu-kvm | Convenience package providing os-autoinst+qemu-kvm | package
| qemu | Machine emulator and virtualizer | srcpackage
i+ | qemu | Machine emulator and virtualizer | package
Furthermore, if I have the actual qemu-kvm package installed, with <= it is automatically removed, which is what I want... So things look good to me. What am I missing?
Mmm... I guess I can try with "Obsoletes: qemu-kvm < %{version}-%{release}
But, yes, the actual qemu-kvm package must be removed, because now the qemu pacakge Obsoletes it, by providing everything that it was providing before (i.e., one symlink).
I don't understand what you mean with "Doesn't the package require other packages to build or install?"
Ok, I've now tested Obsoletes: qemu-kvm < %{version}-%{release}, and no, it does not do what I want and need, while Obsoletes: qemu-kvm = %{version} does. And the SR has been accepted already, so I'm sticking to that
Bruce Rogers (bfrogers)
accepted
request 885459
from
Comments 5
qemu-kvm ist missing now for all arch!
And this wrong:
Pacakges we OBSOLETE (and CONFLICT)
Obsoletes: kvm <= %{version} Obsoletes: qemu-kvm <= %{version} Obsoletes: qemu-sgabios <= 8
Should be <, not <=
I'm sorry, maybe I still missing something about Obsoletes & Friends enough... Can you help me understand why qemu-kvm would be missing for all arches? In fact, I'm not only Obsoleting it, I'm also Providing it, isn't that fine?
FWIW, I've done a few tests with this repository enabled, and it seemed to work:
I.e., as you can see, no
qemu-kvmpackage is being installed:$ rpm -qa|grep qemu-kvm $
And:
Furthermore, if I have the actual
qemu-kvmpackage installed, with<=it is automatically removed, which is what I want... So things look good to me. What am I missing?First a short answer. An offered version (=) cannot be obsolete (<=) at the same time.
And why should qemu-kvm be removed? Doesn't the package require other packages to build or install?
Mmm... I guess I can try with "Obsoletes: qemu-kvm < %{version}-%{release}
But, yes, the actual qemu-kvm package must be removed, because now the qemu pacakge Obsoletes it, by providing everything that it was providing before (i.e., one symlink).
I don't understand what you mean with "Doesn't the package require other packages to build or install?"
Ok, I've now tested
Obsoletes: qemu-kvm < %{version}-%{release}, and no, it does not do what I want and need, whileObsoletes: qemu-kvm = %{version}does. And the SR has been accepted already, so I'm sticking to that