On 10/25/2024 9:55 AM, Peter Xu wrote:
On Thu, Oct 24, 2024 at 05:12:05PM -0400, Steven Sistare wrote:
On 10/10/2024 5:23 PM, Peter Xu wrote:
On Thu, Oct 10, 2024 at 04:06:13PM -0400, Steven Sistare wrote:
vhost requires us to stop the vm early:
qmp_migrate
stop vm
migration_ca
On Thu, Oct 24, 2024 at 05:12:05PM -0400, Steven Sistare wrote:
> On 10/10/2024 5:23 PM, Peter Xu wrote:
> > On Thu, Oct 10, 2024 at 04:06:13PM -0400, Steven Sistare wrote:
> > > vhost requires us to stop the vm early:
> > >qmp_migrate
> > > stop vm
> > > migration_call_notifiers MIG_
On 10/10/2024 5:23 PM, Peter Xu wrote:
On Thu, Oct 10, 2024 at 04:06:13PM -0400, Steven Sistare wrote:
vhost requires us to stop the vm early:
qmp_migrate
stop vm
migration_call_notifiers MIG_EVENT_PRECOPY_CPR_SETUP
vhost_cpr_notifier
vhost_reset_device - must be aft
On Thu, Oct 10, 2024 at 04:06:13PM -0400, Steven Sistare wrote:
> vhost requires us to stop the vm early:
> qmp_migrate
> stop vm
> migration_call_notifiers MIG_EVENT_PRECOPY_CPR_SETUP
> vhost_cpr_notifier
> vhost_reset_device - must be after stop vm
>
On 10/9/2024 4:36 PM, Peter Xu wrote:
On Wed, Oct 09, 2024 at 04:09:45PM -0400, Steven Sistare wrote:
On 10/9/2024 3:06 PM, Peter Xu wrote:
On Wed, Oct 09, 2024 at 02:43:44PM -0400, Steven Sistare wrote:
On 10/8/2024 3:48 PM, Peter Xu wrote:
On Tue, Oct 08, 2024 at 04:11:38PM -0300, Fabiano R
On 10/9/2024 6:08 PM, Fabiano Rosas wrote:
Peter Xu writes:
On Wed, Oct 09, 2024 at 04:18:31PM -0400, Steven Sistare wrote:
Yes, I am also brainstorming along these lines, looking for more gotcha's,
but its a big design change. I don't love it so far.
These issues all creep in because of tra
Peter Xu writes:
> On Wed, Oct 09, 2024 at 04:18:31PM -0400, Steven Sistare wrote:
>> Yes, I am also brainstorming along these lines, looking for more gotcha's,
>> but its a big design change. I don't love it so far.
>>
>> These issues all creep in because of transfer mode. Exec mode did not ha
On Wed, Oct 09, 2024 at 04:18:31PM -0400, Steven Sistare wrote:
> Yes, I am also brainstorming along these lines, looking for more gotcha's,
> but its a big design change. I don't love it so far.
>
> These issues all creep in because of transfer mode. Exec mode did not have
> this
> problem, as
On Wed, Oct 09, 2024 at 04:09:45PM -0400, Steven Sistare wrote:
> On 10/9/2024 3:06 PM, Peter Xu wrote:
> > On Wed, Oct 09, 2024 at 02:43:44PM -0400, Steven Sistare wrote:
> > > On 10/8/2024 3:48 PM, Peter Xu wrote:
> > > > On Tue, Oct 08, 2024 at 04:11:38PM -0300, Fabiano Rosas wrote:
> > > > > As
On 10/9/2024 3:59 PM, Peter Xu wrote:
On Wed, Oct 09, 2024 at 03:06:53PM -0400, Peter Xu wrote:
On Wed, Oct 09, 2024 at 02:43:44PM -0400, Steven Sistare wrote:
On 10/8/2024 3:48 PM, Peter Xu wrote:
On Tue, Oct 08, 2024 at 04:11:38PM -0300, Fabiano Rosas wrote:
As of half an hour ago =) We cou
On 10/9/2024 3:06 PM, Peter Xu wrote:
On Wed, Oct 09, 2024 at 02:43:44PM -0400, Steven Sistare wrote:
On 10/8/2024 3:48 PM, Peter Xu wrote:
On Tue, Oct 08, 2024 at 04:11:38PM -0300, Fabiano Rosas wrote:
As of half an hour ago =) We could put a feature branch up and work
together, if you have m
On Wed, Oct 09, 2024 at 03:06:53PM -0400, Peter Xu wrote:
> On Wed, Oct 09, 2024 at 02:43:44PM -0400, Steven Sistare wrote:
> > On 10/8/2024 3:48 PM, Peter Xu wrote:
> > > On Tue, Oct 08, 2024 at 04:11:38PM -0300, Fabiano Rosas wrote:
> > > > As of half an hour ago =) We could put a feature branch
On Wed, Oct 09, 2024 at 02:43:44PM -0400, Steven Sistare wrote:
> On 10/8/2024 3:48 PM, Peter Xu wrote:
> > On Tue, Oct 08, 2024 at 04:11:38PM -0300, Fabiano Rosas wrote:
> > > As of half an hour ago =) We could put a feature branch up and work
> > > together, if you have more concrete thoughts on
On 10/8/2024 3:48 PM, Peter Xu wrote:
On Tue, Oct 08, 2024 at 04:11:38PM -0300, Fabiano Rosas wrote:
As of half an hour ago =) We could put a feature branch up and work
together, if you have more concrete thoughts on how this would look like
let me know.
[I'll hijack this thread with one more
On Tue, Oct 08, 2024 at 04:11:38PM -0300, Fabiano Rosas wrote:
> As of half an hour ago =) We could put a feature branch up and work
> together, if you have more concrete thoughts on how this would look like
> let me know.
[I'll hijack this thread with one more email, as this is not cpr-relevant]
On Tue, Oct 08, 2024 at 03:12:32PM -0400, Steven Sistare wrote:
> > This is slightly tricky part and would be nice to be documented somewhere,
> > perhaps starting from in the commit message.
>
> I will extend the block comment in qmp_migrate:
>
> /*
> * For cpr-transfer, the target may
On 10/8/2024 3:11 PM, Fabiano Rosas wrote:
Peter Xu writes:
On Tue, Oct 08, 2024 at 03:28:30PM -0300, Fabiano Rosas wrote:
+/* Close cpr socket to tell source that we are listening */
+cpr_state_close();
Would it be possible to use some explicit reply message to mark this?
In theo
On 10/8/2024 2:47 PM, Peter Xu wrote:
On Tue, Oct 08, 2024 at 03:28:30PM -0300, Fabiano Rosas wrote:
+/* Close cpr socket to tell source that we are listening */
+cpr_state_close();
Would it be possible to use some explicit reply message to mark this?
In theory yes, but I fear that u
On 10/8/2024 11:45 AM, Peter Xu wrote:
On Mon, Oct 07, 2024 at 04:39:25PM -0400, Steven Sistare wrote:
On 10/7/2024 3:44 PM, Peter Xu wrote:
On Mon, Sep 30, 2024 at 12:40:44PM -0700, Steve Sistare wrote:
Add the cpr-transfer migration mode. Usage:
qemu-system-$arch -machine anon-alloc=mem
Peter Xu writes:
> On Tue, Oct 08, 2024 at 03:28:30PM -0300, Fabiano Rosas wrote:
>> >>> +/* Close cpr socket to tell source that we are listening */
>> >>> +cpr_state_close();
>> >>
>> >> Would it be possible to use some explicit reply message to mark this?
>> >
>> > In theory yes, bu
On Tue, Oct 08, 2024 at 03:28:30PM -0300, Fabiano Rosas wrote:
> >>> +/* Close cpr socket to tell source that we are listening */
> >>> +cpr_state_close();
> >>
> >> Would it be possible to use some explicit reply message to mark this?
> >
> > In theory yes, but I fear that using a retur
Steven Sistare writes:
> On 10/7/2024 3:44 PM, Peter Xu wrote:
>> On Mon, Sep 30, 2024 at 12:40:44PM -0700, Steve Sistare wrote:
>>> Add the cpr-transfer migration mode. Usage:
>>>qemu-system-$arch -machine anon-alloc=memfd ...
>>>
>>>start new QEMU with "-incoming -cpr-uri "
>>>
>>>
On Mon, Oct 07, 2024 at 04:39:25PM -0400, Steven Sistare wrote:
> On 10/7/2024 3:44 PM, Peter Xu wrote:
> > On Mon, Sep 30, 2024 at 12:40:44PM -0700, Steve Sistare wrote:
> > > Add the cpr-transfer migration mode. Usage:
> > >qemu-system-$arch -machine anon-alloc=memfd ...
> > >
> > >star
On 10/7/2024 3:44 PM, Peter Xu wrote:
On Mon, Sep 30, 2024 at 12:40:44PM -0700, Steve Sistare wrote:
Add the cpr-transfer migration mode. Usage:
qemu-system-$arch -machine anon-alloc=memfd ...
start new QEMU with "-incoming -cpr-uri "
Issue commands to old QEMU:
migrate_set_param
On Mon, Sep 30, 2024 at 12:40:44PM -0700, Steve Sistare wrote:
> Add the cpr-transfer migration mode. Usage:
> qemu-system-$arch -machine anon-alloc=memfd ...
>
> start new QEMU with "-incoming -cpr-uri "
>
> Issue commands to old QEMU:
> migrate_set_parameter mode cpr-transfer
> migr
Add the cpr-transfer migration mode. Usage:
qemu-system-$arch -machine anon-alloc=memfd ...
start new QEMU with "-incoming -cpr-uri "
Issue commands to old QEMU:
migrate_set_parameter mode cpr-transfer
migrate_set_parameter cpr-uri
migrate -d
The migrate command stops the VM, sav
26 matches
Mail list logo
