Ping
14.05.2019, 12:36, "Yury Kotov" :
> Ping
>
> 18.04.2019, 20:46, "Yury Kotov" :
>> 18.04.2019, 20:01, "Dr. David Alan Gilbert" :
>>> * Yury Kotov (yury-ko...@yandex-team.ru) wrote:
18.04.2019, 19:03, "Dr. David Alan Gilbert" :
> * Yury Kotov (yury-ko...@yandex-team.ru) wrote
Ping
18.04.2019, 20:46, "Yury Kotov" :
> 18.04.2019, 20:01, "Dr. David Alan Gilbert" :
>> * Yury Kotov (yury-ko...@yandex-team.ru) wrote:
>>> 18.04.2019, 19:03, "Dr. David Alan Gilbert" :
>>> > * Yury Kotov (yury-ko...@yandex-team.ru) wrote:
>>> >> 18.04.2019, 17:20, "Dr. David Alan Gilber
18.04.2019, 20:01, "Dr. David Alan Gilbert" :
> * Yury Kotov (yury-ko...@yandex-team.ru) wrote:
>> 18.04.2019, 19:03, "Dr. David Alan Gilbert" :
>> > * Yury Kotov (yury-ko...@yandex-team.ru) wrote:
>> >> 18.04.2019, 17:20, "Dr. David Alan Gilbert" :
>> >> > * Yury Kotov (yury-ko...@yandex-tea
* Yury Kotov (yury-ko...@yandex-team.ru) wrote:
> 18.04.2019, 19:03, "Dr. David Alan Gilbert" :
> > * Yury Kotov (yury-ko...@yandex-team.ru) wrote:
> >> 18.04.2019, 17:20, "Dr. David Alan Gilbert" :
> >> > * Yury Kotov (yury-ko...@yandex-team.ru) wrote:
> >> >> 15.04.2019, 14:30, "Dr. David Ala
18.04.2019, 19:03, "Dr. David Alan Gilbert" :
> * Yury Kotov (yury-ko...@yandex-team.ru) wrote:
>> 18.04.2019, 17:20, "Dr. David Alan Gilbert" :
>> > * Yury Kotov (yury-ko...@yandex-team.ru) wrote:
>> >> 15.04.2019, 14:30, "Dr. David Alan Gilbert" :
>> >> > * Daniel P. Berrangé (berra...@redh
* Yury Kotov (yury-ko...@yandex-team.ru) wrote:
> 18.04.2019, 17:20, "Dr. David Alan Gilbert" :
> > * Yury Kotov (yury-ko...@yandex-team.ru) wrote:
> >> 15.04.2019, 14:30, "Dr. David Alan Gilbert" :
> >> > * Daniel P. Berrangé (berra...@redhat.com) wrote:
> >> >> On Mon, Apr 15, 2019 at 12:15:1
18.04.2019, 17:20, "Dr. David Alan Gilbert" :
> * Yury Kotov (yury-ko...@yandex-team.ru) wrote:
>> 15.04.2019, 14:30, "Dr. David Alan Gilbert" :
>> > * Daniel P. Berrangé (berra...@redhat.com) wrote:
>> >> On Mon, Apr 15, 2019 at 12:15:12PM +0100, Dr. David Alan Gilbert wrote:
>> >> > * Danie
* Yury Kotov (yury-ko...@yandex-team.ru) wrote:
> 15.04.2019, 14:30, "Dr. David Alan Gilbert" :
> > * Daniel P. Berrangé (berra...@redhat.com) wrote:
> >> On Mon, Apr 15, 2019 at 12:15:12PM +0100, Dr. David Alan Gilbert wrote:
> >> > * Daniel P. Berrangé (berra...@redhat.com) wrote:
> >> > > On
15.04.2019, 14:30, "Dr. David Alan Gilbert" :
> * Daniel P. Berrangé (berra...@redhat.com) wrote:
>> On Mon, Apr 15, 2019 at 12:15:12PM +0100, Dr. David Alan Gilbert wrote:
>> > * Daniel P. Berrangé (berra...@redhat.com) wrote:
>> > > On Mon, Apr 15, 2019 at 01:33:21PM +0300, Yury Kotov wrote:
>
15.04.2019, 15:21, "Yury Kotov" :
> 15.04.2019, 14:30, "Dr. David Alan Gilbert" :
>> * Daniel P. Berrangé (berra...@redhat.com) wrote:
>>> On Mon, Apr 15, 2019 at 12:15:12PM +0100, Dr. David Alan Gilbert wrote:
>>> > * Daniel P. Berrangé (berra...@redhat.com) wrote:
>>> > > On Mon, Apr 15, 2
15.04.2019, 14:30, "Dr. David Alan Gilbert" :
> * Daniel P. Berrangé (berra...@redhat.com) wrote:
>> On Mon, Apr 15, 2019 at 12:15:12PM +0100, Dr. David Alan Gilbert wrote:
>> > * Daniel P. Berrangé (berra...@redhat.com) wrote:
>> > > On Mon, Apr 15, 2019 at 01:33:21PM +0300, Yury Kotov wrote:
>
* Daniel P. Berrangé (berra...@redhat.com) wrote:
> On Mon, Apr 15, 2019 at 12:15:12PM +0100, Dr. David Alan Gilbert wrote:
> > * Daniel P. Berrangé (berra...@redhat.com) wrote:
> > > On Mon, Apr 15, 2019 at 01:33:21PM +0300, Yury Kotov wrote:
> > > > 15.04.2019, 13:25, "Daniel P. Berrangé" :
> > >
On Mon, Apr 15, 2019 at 12:15:12PM +0100, Dr. David Alan Gilbert wrote:
> * Daniel P. Berrangé (berra...@redhat.com) wrote:
> > On Mon, Apr 15, 2019 at 01:33:21PM +0300, Yury Kotov wrote:
> > > 15.04.2019, 13:25, "Daniel P. Berrangé" :
> > > > On Mon, Apr 15, 2019 at 01:17:06PM +0300, Yury Kotov wr
* Daniel P. Berrangé (berra...@redhat.com) wrote:
> On Mon, Apr 15, 2019 at 01:33:21PM +0300, Yury Kotov wrote:
> > 15.04.2019, 13:25, "Daniel P. Berrangé" :
> > > On Mon, Apr 15, 2019 at 01:17:06PM +0300, Yury Kotov wrote:
> > >> 15.04.2019, 13:11, "Daniel P. Berrangé" :
> > >> > On Mon, Apr 15,
On Mon, Apr 15, 2019 at 01:33:21PM +0300, Yury Kotov wrote:
> 15.04.2019, 13:25, "Daniel P. Berrangé" :
> > On Mon, Apr 15, 2019 at 01:17:06PM +0300, Yury Kotov wrote:
> >> 15.04.2019, 13:11, "Daniel P. Berrangé" :
> >> > On Mon, Apr 15, 2019 at 12:50:08PM +0300, Yury Kotov wrote:
> >> >> Hi,
>
15.04.2019, 13:25, "Daniel P. Berrangé" :
> On Mon, Apr 15, 2019 at 01:17:06PM +0300, Yury Kotov wrote:
>> 15.04.2019, 13:11, "Daniel P. Berrangé" :
>> > On Mon, Apr 15, 2019 at 12:50:08PM +0300, Yury Kotov wrote:
>> >> Hi,
>> >>
>> >> Just to clarify. I see two possible solutions:
>> >>
>>
On Mon, Apr 15, 2019 at 01:17:06PM +0300, Yury Kotov wrote:
> 15.04.2019, 13:11, "Daniel P. Berrangé" :
> > On Mon, Apr 15, 2019 at 12:50:08PM +0300, Yury Kotov wrote:
> >> Hi,
> >>
> >> Just to clarify. I see two possible solutions:
> >>
> >> 1) Since the migration code doesn't receive fd, it i
15.04.2019, 13:17, "Yury Kotov" :
> 15.04.2019, 13:11, "Daniel P. Berrangé" :
>> On Mon, Apr 15, 2019 at 12:50:08PM +0300, Yury Kotov wrote:
>>> Hi,
>>>
>>> Just to clarify. I see two possible solutions:
>>>
>>> 1) Since the migration code doesn't receive fd, it isn't responsible for
>>> c
15.04.2019, 13:11, "Daniel P. Berrangé" :
> On Mon, Apr 15, 2019 at 12:50:08PM +0300, Yury Kotov wrote:
>> Hi,
>>
>> Just to clarify. I see two possible solutions:
>>
>> 1) Since the migration code doesn't receive fd, it isn't responsible for
>> closing it. So, it may be better to use migrate_f
On Mon, Apr 15, 2019 at 12:50:08PM +0300, Yury Kotov wrote:
> Hi,
>
> Just to clarify. I see two possible solutions:
>
> 1) Since the migration code doesn't receive fd, it isn't responsible for
> closing it. So, it may be better to use migrate_fd_param for both
> incoming/outgoing and add dupping
Hi,
Just to clarify. I see two possible solutions:
1) Since the migration code doesn't receive fd, it isn't responsible for
closing it. So, it may be better to use migrate_fd_param for both
incoming/outgoing and add dupping for migrate_fd_param. Thus, clients must
close the fd themselves. But exi
11.04.2019, 15:39, "Daniel P. Berrangé" :
> On Thu, Apr 11, 2019 at 03:31:43PM +0300, Yury Kotov wrote:
>> 11.04.2019, 15:04, "Daniel P. Berrangé" :
>> > On Wed, Apr 10, 2019 at 12:26:52PM +0300, Yury Kotov wrote:
>> >> Currently such case is possible for incoming:
>> >> QMP: add-fd (fdset =
On Thu, Apr 11, 2019 at 03:31:43PM +0300, Yury Kotov wrote:
> 11.04.2019, 15:04, "Daniel P. Berrangé" :
> > On Wed, Apr 10, 2019 at 12:26:52PM +0300, Yury Kotov wrote:
> >> Currently such case is possible for incoming:
> >> QMP: add-fd (fdset = 0, fd of some file):
> >> adds fd to fdset 0 an
11.04.2019, 15:04, "Daniel P. Berrangé" :
> On Wed, Apr 10, 2019 at 12:26:52PM +0300, Yury Kotov wrote:
>> Currently such case is possible for incoming:
>> QMP: add-fd (fdset = 0, fd of some file):
>> adds fd to fdset 0 and returns QEMU's fd (e.g. 33)
>> QMP: migrate-incoming (uri = "fd:33"
On Wed, Apr 10, 2019 at 12:26:52PM +0300, Yury Kotov wrote:
> Currently such case is possible for incoming:
> QMP: add-fd (fdset = 0, fd of some file):
> adds fd to fdset 0 and returns QEMU's fd (e.g. 33)
> QMP: migrate-incoming (uri = "fd:33"): fd is stored in QIOChannel *ioc
> ...
> Incoming
Hi,
10.04.2019, 16:58, "Dr. David Alan Gilbert" :
> * Yury Kotov (yury-ko...@yandex-team.ru) wrote:
>> Currently such case is possible for incoming:
>> QMP: add-fd (fdset = 0, fd of some file):
>> adds fd to fdset 0 and returns QEMU's fd (e.g. 33)
>> QMP: migrate-incoming (uri = "fd:33"):
* Yury Kotov (yury-ko...@yandex-team.ru) wrote:
> Currently such case is possible for incoming:
> QMP: add-fd (fdset = 0, fd of some file):
> adds fd to fdset 0 and returns QEMU's fd (e.g. 33)
> QMP: migrate-incoming (uri = "fd:33"): fd is stored in QIOChannel *ioc
> ...
> Incoming migration co
Patchew URL:
https://patchew.org/QEMU/20190410092652.22616-1-yury-ko...@yandex-team.ru/
Hi,
This series failed the docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEG
Currently such case is possible for incoming:
QMP: add-fd (fdset = 0, fd of some file):
adds fd to fdset 0 and returns QEMU's fd (e.g. 33)
QMP: migrate-incoming (uri = "fd:33"): fd is stored in QIOChannel *ioc
...
Incoming migration completes and unrefs ioc -> close(33)
QMP: remove-fd (fdset =
29 matches
Mail list logo