[pve-devel] [PATCH 3/3] add downtime && expected_downtime query-migrate info

[Stefan Priebe]

Strangely the status of the VM is always paused after migration.

Stefan
Am 27.12.2012 15:18, schrieb Stefan Priebe:
> Hi,
>
> have now done the same.
>
> With current git qemu migration is really fast using 1,6GB memory:
> Dec 27 15:17:45 starting migration of VM 105 to node 'cloud1-1202'
> (10.255.0.20)
> Dec 27 15:17:45 copying disk images
> Dec 27 15:17:45 starting VM 105 on remote node 'cloud1-1202'
> Dec 27 15:17:48 starting online/live migration on tcp:10.255.0.20:60000
> Dec 27 15:17:48 migrate_set_speed: 8589934592
> Dec 27 15:17:48 migrate_set_downtime: 0.05
> Dec 27 15:17:52 migration speed: 512.00 MB/s - downtime 174 ms
> Dec 27 15:17:52 migration status: completed
> Dec 27 15:17:53 migration finished successfuly (duration 00:00:09)
> TASK OK
>
> It's so fast that i can't check if i see that's while migrating.
>
> Greets,
> Stefan
>
> Am 27.12.2012 14:26, schrieb Alexandre DERUMIER:
>>>> The problem is the LATEST git qemu code they've changed a LOT of
>>>> include
>>>> file locations so nearly NO PVE patch applies...
>>
>> I'm currently building a pve-qemu-kvm on qemu 1.4, with basics patches
>>
>> fr-ca-keymap-corrections.diff
>> fairsched.diff
>> pve-auth.patch
>> vencrypt-auth-plain.patch
>> enable-kvm-by-default.patch
>>
>> should be enough to connect with vnc and test migration
>>
>> I'll keep in touch
>>
>>
>>
>> ----- Mail original -----
>>
>> De: "Stefan Priebe" <s.priebe at profihost.ag>
>> À: "Alexandre DERUMIER" <aderumier at odiso.com>
>> Cc: pve-devel at pve.proxmox.com, "Dietmar Maurer" <dietmar at proxmox.com>
>> Envoyé: Jeudi 27 Décembre 2012 13:40:24
>> Objet: Re: [pve-devel] [PATCH 3/3] add downtime && expected_downtime
>> query-migrate info
>>
>> Hi,
>> Am 27.12.2012 13:39, schrieb Alexandre DERUMIER:
>>>>> not right now - but i tested this yesterday and didn't saw a
>>>>> difference
>>>>> so i moved again to 3.6.11.
>>> It'll do test with a 3.6 kernel too, to see if I have a difference
>>
>> Thanks! Will retest with pve kernel too.
>>
>>> Do you have tried with last qemu 1.4 git ?
>>> Because I'm looking into the code, and the change in migration code
>>> is really huge.
>>> So we could known if it's a qemu migration code problem or not...
>>
>> The problem is the LATEST git qemu code they've changed a LOT of include
>> file locations so nearly NO PVE patch applies...
>>
>> Stefan
>>