Hello,
> These patches will be in the next bookworm point release, -
> unfortunately we missed the nearest one which is sheduled
> for Sep-06, - so the next only only. And we'll apply these
> 3 to the upstream 7.2.x stable branch as well.
Would it be possible to squeeze them in still? Since the
On 01.09.2025 16:47, Poldrack, Moritz wrote:
Thank you, we have applied the 3 patches and can confirm that it is working as
before again.
And thank you very much for your patience and your testing.
These patches will be in the next bookworm point release, -
unfortunately we missed the nearest
Thank you, we have applied the 3 patches and can confirm that it is working as
before again.
Excellent, thank you for the command line.
Please, can you try 3 more commits from staging-7.2 queue, on top
of the regular current debian 7.2 qemu release, starting with
https://gitlab.com/mjt0k/qemu/-/commits/b3ad24485306e19d0cd08d96211ef033464eb97a
--
653217a501 virtio-net: Add only one que
root@s249024:~# ps -fC qemu-system-x86_64
UID PIDPPID C STIME TTY TIME CMD
root 1816537 1 1 Aug28 ?00:16:45 /usr/bin/qemu-system-x86_64
-name guest=s251093,debug-threads=on -S -object
{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/
n.org
Cc: Blahut, Ash; Fuchs, Matthias
Subject: Re: Bug#1112044: Softlock from virt-net
Hi!
Can you provide qemu command line too, please?
Thanks,
/mjt
On 28.08.2025 18:00, Poldrack, Moritz wrote:
Certainly, the call is:
$ virsh migrate --change-protection --live $name --undefinesource --persistent --p2p
"qemu+ssh://$host/system --bandwidth $bandwidth
...
Can you provide qemu command line too, please?
Nah, not virsh command line but qemu c
Hi!
Can you provide qemu command line too, please?
Thanks,
/mjt
On 27.08.2025 09:52, Poldrack, Moritz wrote:
Excuse the confusion, ce1431615292dc735597db4062834bfb271381bc is the culprit.
This makes *much* more sense. Thank you very much for the work so far!
Let's ask the upstream..
Thanks,
/mjt
Excuse the confusion, ce1431615292dc735597db4062834bfb271381bc is the culprit.
The clipboard still contained the wrong hash.
On 25.08.2025 18:46, Moritz Poldrack wrote:
> We'll run the tests with the dropped changes during the day.
We could identify d34c201195ecea4fa5c3328a8f5507ca6d2c0a96 as the culprit.
On 25.08.2025 18:46, Moritz Poldrack wrote:
> Does it work when migrating between two deb12u14 (or deb12u15, since
> u14 and u15 is the same when qemu-system is concerned) ?
Migrating from and to u14 exhibits the same behaviour. We'll run the tests with
the dropped changes during the day.
On 25.08.2025 19:16, Michael Tokarev wrote:
..
virtio: Call set_features during reset
https://salsa.debian.org/qemu-team/qemu/-/commit/
ce1431615292dc735597db4062834bfb271381bc
virtio-net: Fix num_buffers for version 1
https://salsa.debian.org/qemu-team/qemu/-/commit/
cefd67f2543045cfebe51f9e
Control: found -1 1:7.2+dfsg-7+deb12u14
On 25.08.2025 18:46, Moritz Poldrack wrote:
Package: qemu-system-x86
Version: 1:7.2+dfsg-7+deb12u15
Source: qemu
This occurs during live-migrating a guest onto a host with u15, migrating it
back fixes the softlocks. A reset is required to fix it but is o
Package: qemu-system-x86
Version: 1:7.2+dfsg-7+deb12u15
Source: qemu
This occurs during live-migrating a guest onto a host with u15, migrating it
back fixes the softlocks. A reset is required to fix it but is only required
when the receiving host is on the latest version.
Last known good versio
15 matches
Mail list logo
