02.07.2020 14:44, Vladimir Sementsov-Ogievskiy wrote:
02.07.2020 10:23, Max Reitz wrote:
On 01.07.20 18:16, Vladimir Sementsov-Ogievskiy wrote:
29.06.2020 18:00, Max Reitz wrote:
On 29.06.20 16:18, Vladimir Sementsov-Ogievskiy wrote:
29.06.2020 16:48, Max Reitz wrote:
Hi,
In an iotest, I’m
02.07.2020 10:23, Max Reitz wrote:
On 01.07.20 18:16, Vladimir Sementsov-Ogievskiy wrote:
29.06.2020 18:00, Max Reitz wrote:
On 29.06.20 16:18, Vladimir Sementsov-Ogievskiy wrote:
29.06.2020 16:48, Max Reitz wrote:
Hi,
In an iotest, I’m trying to quit qemu immediately after a migration has
f
On 01.07.20 18:16, Vladimir Sementsov-Ogievskiy wrote:
> 29.06.2020 18:00, Max Reitz wrote:
>> On 29.06.20 16:18, Vladimir Sementsov-Ogievskiy wrote:
>>> 29.06.2020 16:48, Max Reitz wrote:
Hi,
In an iotest, I’m trying to quit qemu immediately after a migration has
failed. Unfor
29.06.2020 18:00, Max Reitz wrote:
On 29.06.20 16:18, Vladimir Sementsov-Ogievskiy wrote:
29.06.2020 16:48, Max Reitz wrote:
Hi,
In an iotest, I’m trying to quit qemu immediately after a migration has
failed. Unfortunately, that doesn’t seem to be possible in a clean way:
migrate_fd_cleanup()
* Max Reitz (mre...@redhat.com) wrote:
> On 29.06.20 17:41, Dr. David Alan Gilbert wrote:
> > * Max Reitz (mre...@redhat.com) wrote:
> >> Hi,
> >>
> >> In an iotest, I’m trying to quit qemu immediately after a migration has
> >> failed. Unfortunately, that doesn’t seem to be possible in a clean wa
On 29.06.20 17:41, Dr. David Alan Gilbert wrote:
> * Max Reitz (mre...@redhat.com) wrote:
>> Hi,
>>
>> In an iotest, I’m trying to quit qemu immediately after a migration has
>> failed. Unfortunately, that doesn’t seem to be possible in a clean way:
>> migrate_fd_cleanup() runs only at some point
On 29.06.20 17:45, Daniel P. Berrangé wrote:
> On Mon, Jun 29, 2020 at 03:48:35PM +0200, Max Reitz wrote:
>> In practice this particular issue might not be that big of a problem,
>> because it just means qemu aborts when the user intended to let it quit
>> anyway. But on one hand I could imagine t
On Mon, Jun 29, 2020 at 03:48:35PM +0200, Max Reitz wrote:
> In practice this particular issue might not be that big of a problem,
> because it just means qemu aborts when the user intended to let it quit
> anyway. But on one hand I could imagine that there are other clean-up
> paths that should d
* Max Reitz (mre...@redhat.com) wrote:
> Hi,
>
> In an iotest, I’m trying to quit qemu immediately after a migration has
> failed. Unfortunately, that doesn’t seem to be possible in a clean way:
> migrate_fd_cleanup() runs only at some point after the migration state
> is already “failed”, so if
On 29.06.20 16:18, Vladimir Sementsov-Ogievskiy wrote:
> 29.06.2020 16:48, Max Reitz wrote:
>> Hi,
>>
>> In an iotest, I’m trying to quit qemu immediately after a migration has
>> failed. Unfortunately, that doesn’t seem to be possible in a clean way:
>> migrate_fd_cleanup() runs only at some poin
29.06.2020 16:48, Max Reitz wrote:
Hi,
In an iotest, I’m trying to quit qemu immediately after a migration has
failed. Unfortunately, that doesn’t seem to be possible in a clean way:
migrate_fd_cleanup() runs only at some point after the migration state
is already “failed”, so if I just wait fo
11 matches
Mail list logo