Compare commits
2 Commits
v8.1.5-4+v
...
v8.0.2-3+v
Author | SHA1 | Date | |
---|---|---|---|
a417b83c07 | |||
40f9a6f1c2 |
2
Makefile
2
Makefile
@@ -55,7 +55,7 @@ $(BUILDDIR): keycodemapdb | submodule
|
||||
deb kvm: $(DEBS)
|
||||
$(DEB_DBG): $(DEB)
|
||||
$(DEB): $(BUILDDIR)
|
||||
cd $(BUILDDIR); dpkg-buildpackage -b -us -uc -j
|
||||
cd $(BUILDDIR); dpkg-buildpackage -b -us -uc -j32
|
||||
lintian $(DEBS)
|
||||
|
||||
sbuild: $(DSC)
|
||||
|
13
debian/changelog
vendored
13
debian/changelog
vendored
@@ -1,3 +1,16 @@
|
||||
pve-qemu-kvm (8.0.2-3+vitastor2) bookworm; urgency=medium
|
||||
|
||||
* Improve performance by adding io_uring support
|
||||
* Fix qemu-img deadlocks after iothread fixes
|
||||
|
||||
-- Vitaliy Filippov <vitalif@yourcmc.ru> Tue, 19 Jul 2023 02:07:02 +0300
|
||||
|
||||
pve-qemu-kvm (8.0.2-3+vitastor1) bookworm; urgency=medium
|
||||
|
||||
* Add Vitastor support
|
||||
|
||||
-- Vitaliy Filippov <vitalif@yourcmc.ru> Sat, 24 Jun 2023 00:50:32 +0300
|
||||
|
||||
pve-qemu-kvm (8.0.2-3) bookworm; urgency=medium
|
||||
|
||||
* fix regression in QEMU 8.0 for drive mirror with bitmap
|
||||
|
1
debian/control
vendored
1
debian/control
vendored
@@ -58,6 +58,7 @@ Depends: ceph-common (>= 0.48),
|
||||
libspice-server1 (>= 0.14.0~),
|
||||
libusb-1.0-0 (>= 1.0.17-1),
|
||||
libusbredirparser1 (>= 0.6-2),
|
||||
vitastor-client (>= 0.9.4),
|
||||
libuuid1,
|
||||
${misc:Depends},
|
||||
${shlibs:Depends},
|
||||
|
1212
debian/patches/pve-qemu-8.0-vitastor.patch
vendored
Normal file
1212
debian/patches/pve-qemu-8.0-vitastor.patch
vendored
Normal file
File diff suppressed because it is too large
Load Diff
1
debian/patches/series
vendored
1
debian/patches/series
vendored
@@ -58,3 +58,4 @@ pve/0042-Revert-block-rbd-implement-bdrv_co_block_status.patch
|
||||
pve/0043-alloc-track-fix-deadlock-during-drop.patch
|
||||
pve/0044-migration-for-snapshots-hold-the-BQL-during-setup-ca.patch
|
||||
pve/0045-savevm-async-don-t-hold-BQL-during-setup.patch
|
||||
pve-qemu-8.0-vitastor.patch
|
||||
|
Reference in New Issue
Block a user