-
qemu-kvm-2.12.0-97.module+el8.2.0+5545+14c6799fa4f4eeb0 · ·
Update to qemu-kvm-2.12.0-97.module+el8.2.0+5545+14c6799f
-
-
qemu-kvm-4.2.0-7.module+el8.2.0+5520+4e5817f35cbd791b · ·
Update to qemu-kvm-4.2.0-7.module+el8.2.0+5520+4e5817f3
-
qemu-kvm-4.1.0-23.module+el8.1.1+5467+ba2d821bf1384346 · ·
Update to qemu-kvm-4.1.0-23.module+el8.1.1+5467+ba2d821b
-
qemu-kvm-4.2.0-6.module+el8.2.0+5451+991cea0d66edf3fb · ·
Update to qemu-kvm-4.2.0-6.module+el8.2.0+5451+991cea0d
-
qemu-kvm-4.1.0-22.module+el8.1.1+5444+e567605f0fbcc043 · ·
Update to qemu-kvm-4.1.0-22.module+el8.1.1+5444+e567605f
-
qemu-kvm-4.2.0-5.module+el8.2.0+5389+367d9739076382fe · ·
Update to qemu-kvm-4.2.0-5.module+el8.2.0+5389+367d9739
-
qemu-kvm-2.12.0-96.module+el8.2.0+5387+0c6765ef08c8ee21 · ·
Update to qemu-kvm-2.12.0-96.module+el8.2.0+5387+0c6765ef
-
qemu-kvm-4.1.0-21.module+el8.1.1+5388+fd51bfbc7800eb5a · ·
Update to qemu-kvm-4.1.0-21.module+el8.1.1+5388+fd51bfbc
-
prop-ptr-pull-requestf0d753b1 · ·
Clean-ups: qom-ify serial and remove QDEV_PROP_PTR Hi, QDEV_PROP_PTR is marked in multiple places as "FIXME/TODO/remove me". In most cases, it can be easily replaced with QDEV_PROP_LINK when the pointer points to an Object. There are a few places where such substitution isn't possible. For those places, it seems reasonable to use a specific setter method instead, and keep the user_creatable = false. In other places, proper usage of qdev or other facilies is the solution. The serial code wasn't converted to qdev, which makes it a bit more archaic to deal with. Let's convert it first, so we can more easily embed it from other devices, and re-export some properties and drop QDEV_PROP_PTR usage.
-
dbus-vmstate7-pull-request586ca6ba · ·
Add dbus-vmstate Hi, With external processes or helpers participating to the VM support, it becomes necessary to handle their migration. Various options exist to transfer their state: 1) as the VM memory, RAM or devices (we could say that's how vhost-user devices can be handled today, they are expected to restore from ring state) 2) other "vmstate" (as with TPM emulator state blobs) 3) left to be handled by management layer 1) is not practical, since an external processes may legitimatelly need arbitrary state date to back a device or a service, or may not even have an associated device. 2) needs ad-hoc code for each helper, but is simple and working 3) is complicated for management layer, QEMU has the migration timing The proposed "dbus-vmstate" object will connect to a given D-Bus address, and save/load from org.qemu.VMState1 owners on migration. Thus helpers can easily have their state migrated with QEMU, without implementing ad-hoc support (such as done for TPM emulation) D-Bus is ubiquitous on Linux (it is systemd IPC), and can be made to work on various other OSes. There are several implementations and good bindings for various languages. (the tests/dbus-vmstate-test.c is a good example of how simple the implementation of services can be, even in C) dbus-vmstate is put into use by the libvirt series "[PATCH 00/23] Use a slirp helper process". v2: - fix build with broken mingw-glib
-
-
screendump-pull-request53a61ecb · ·
console: screendump improvements Hi, The following patches have been extracted from the "[PATCH v6 00/25] monitor: add asynchronous command type", as they are reviewable/mergeable independantly. They introduce some internal API changes, and fix qemu_open()/qemu_close()/unlink() misusages which should be quite harmless.
-
qemu-kvm-2.12.0-95.module+el8.2.0+5354+b7ebf7be5616e4dd · ·
Update to qemu-kvm-2.12.0-95.module+el8.2.0+5354+b7ebf7be
-
qemu-kvm-4.1.0-14.module+el8.1.0+5345+1e7a7e596f8a44a3 · ·
Update to qemu-kvm-4.1.0-14.module+el8.1.0+5345+1e7a7e59
-
qemu-kvm-4.1.0-20.module+el8.1.1+5309+6d656f05c94699bf · ·
Update to qemu-kvm-4.1.0-20.module+el8.1.1+5309+6d656f05
-
qemu-kvm-2.12.0-94.module+el8.2.0+5297+222a20afc9090b2b · ·
Update to qemu-kvm-2.12.0-94.module+el8.2.0+5297+222a20af
-