On Mon, Apr 15, 2019 at 01:01:13PM +0300, Liran Alon wrote:
>
>
> > On 15 Apr 2019, at 12:37, Stefan Hajnoczi wrote:
> >
> > On Thu, Apr 11, 2019 at 01:45:06AM +0300, Liran Alon wrote:
> >>
> >>
> >>> On 9 Apr 2019, at 17:29, Stefan Hajnoczi wrote:
> >>>
> >>> On Thu, Mar 21, 2019 at
> On 15 Apr 2019, at 12:37, Stefan Hajnoczi wrote:
>
> On Thu, Apr 11, 2019 at 01:45:06AM +0300, Liran Alon wrote:
>>
>>
>>> On 9 Apr 2019, at 17:29, Stefan Hajnoczi wrote:
>>>
>>> On Thu, Mar 21, 2019 at 09:55:42AM +0200, Nir Weiner wrote:
Originally migration was not possible with
On Thu, Apr 11, 2019 at 01:45:06AM +0300, Liran Alon wrote:
>
>
> > On 9 Apr 2019, at 17:29, Stefan Hajnoczi wrote:
> >
> > On Thu, Mar 21, 2019 at 09:55:42AM +0200, Nir Weiner wrote:
> >> Originally migration was not possible with vhost-scsi because
> >> as part of migration, the source host
> On 9 Apr 2019, at 17:29, Stefan Hajnoczi wrote:
>
> On Thu, Mar 21, 2019 at 09:55:42AM +0200, Nir Weiner wrote:
>> Originally migration was not possible with vhost-scsi because
>> as part of migration, the source host target SCSI device state
>> needs to be saved and loaded into the
On Thu, Mar 21, 2019 at 09:55:42AM +0200, Nir Weiner wrote:
> Originally migration was not possible with vhost-scsi because
> as part of migration, the source host target SCSI device state
> needs to be saved and loaded into the destination host target SCSI
> device. This cannot be done by QEMU.
>
Second ping.
This series has been sent almost 2 weeks ago. We would appreciate some
feedback/review.
Thanks,
-Liran
> On 27 Mar 2019, at 12:40, Nir Weiner wrote:
>
> On 3/21/19 9:55 AM, Nir Weiner wrote:
>
>> Originally migration was not possible with vhost-scsi because
>> as part of
On 3/21/19 9:55 AM, Nir Weiner wrote:
Originally migration was not possible with vhost-scsi because
as part of migration, the source host target SCSI device state
needs to be saved and loaded into the destination host target SCSI
device. This cannot be done by QEMU.
As this can be handled
Originally migration was not possible with vhost-scsi because
as part of migration, the source host target SCSI device state
needs to be saved and loaded into the destination host target SCSI
device. This cannot be done by QEMU.
As this can be handled either by external orchestrator or by having
