Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
Hi Alexandre, attached you'll find a patchset with 10 more patches which make migration even more faster. They're stable for me too. Greets, Stefan Am 29.12.2012 15:54, schrieb Stefan Priebe - Profihost AG: Great! To me even xzbrle works fine now. Am 29.12.2012 um 15:47 schrieb Alexandre DERUMIER aderum...@odiso.com: I have just done some little tests with qemu 1.3 + migration patches set, now it's working fine, no more crash ! (playing video hd). setting migrate_set_downtime to 1sec, give me: for no memory activity : 36ms downtime for high memory activity : 650ms downtime I'll do more extensive tests monday. Thanks for the patches ! - Mail original - De: Stefan Priebe s.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@proxmox.com Envoyé: Samedi 29 Décembre 2012 15:07:30 Objet: Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info Hi, Am 29.12.2012 15:02, schrieb Alexandre DERUMIER: oh, ok. I'll tests the patchs mondays. Thanks! Does migration works fine for you with them ? Yes - it works fine / perfectly. But i've no VM with a desktop to play HD videos ;-) Stefan - Mail original - De: Stefan Priebe s.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@proxmox.com Envoyé: Samedi 29 Décembre 2012 14:55:33 Objet: Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info Hi Alexandre, Am 29.12.2012 14:51, schrieb Alexandre DERUMIER: Great to known that you finally found it !. Not found ;-) just know that the rework of the migration code fixes it. May be it might be a deadlock - they've changed the locking and threading handling. (Do you have respond to Paolo Bonzini, because the last response I see was that it was not working). No - i just tried to apply parts of the patchset on qemu 1.3 instead of using whole 1.4 git trunk. Alexandre might you try my rebased patches on top of pve-qemu 1.3? So, Do you want to apply the first patch only (to fix you bug), or apply the whole patches set ? (equal to current git code ?). All patches i had attached ;-) Not sure that Dietmar want to apply the big patches set ;) sure but just wanted to know if they're stable for you too. So if they're i will care about them in my own branch. So I've at least a working migration. I'll retest the whole patches set, because I was having migration problem (vm paused with error) with last qemu git. That's why i've ported not all patches and on top of qemu 1.3 instead of qemu 1.4. Stefan ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel qemu-migration-full.tar.gz Description: application/gzip ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
Hi, Am 30.12.2012 16:29, schrieb Alexandre DERUMIER: Seem stable here too, thanks ! great! Willd definitely keep them in my branch. Migration is now as fast and as stable i originally expected from kvm. Dietmar are you interested too / have you thought about implement them into pve-qemu-kvm? Greets Stefan ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
Hi,
i could fix my problem by applying the first 22 migration patches of
this bunch:
http://www.mail-archive.com/qemu-commits@nongnu.org/msg02028.html
Alexandre might you try my rebased patches on top of pve-qemu 1.3?
Attaches is a bunch of patches to apply on top of the qemu-kvm-src from
PVE. Please also patch the internal async patch see separate patch.
At last you need to remove the always-update-expected-downtime.patch
patch from the debian series file.
Thanks!
Stefan
Am 28.12.2012 09:19, schrieb Alexandre DERUMIER:
I'm looking into qemu src code,
in arch_init.c - ram_save_iterate()
it should return false, to retry transfert iteration of remaining memory ,
until the last step:ram_save_complete()
Seem that for Stefan, it's return 0 directly with migrate_set_downtime = 1.
I think interesting part is here:
Maybe can we add somes logs ? (BTW, is it possible to logs qemu STDOUT
somewhere in a file ?)
bwidth = qemu_get_clock_ns(rt_clock) - bwidth;
bwidth = (bytes_transferred - bytes_transferred_last) / bwidth;
/* if we haven't transferred anything this round, force
* expected_downtime to a very high value, but without
* crashing */
if (bwidth == 0) {
bwidth = 0.01;
}
qemu_put_be64(f, RAM_SAVE_FLAG_EOS);
expected_downtime = ram_save_remaining() * TARGET_PAGE_SIZE / bwidth;
DPRINTF(ram_save_live: expected(% PRIu64 ) = max( PRIu64 )?\n,
expected_downtime, migrate_max_downtime());
if (expected_downtime = migrate_max_downtime()) {
migration_bitmap_sync();
expected_downtime = ram_save_remaining() * TARGET_PAGE_SIZE / bwidth;
s-expected_downtime = expected_downtime / 100; /* ns - ms */
return expected_downtime = migrate_max_downtime();
}
return 0;
- Mail original -
De: Dietmar Maurer diet...@proxmox.com
À: Stefan Priebe - Profihost AG s.pri...@profihost.ag
Cc: Alexandre DERUMIER aderum...@odiso.com, pve-devel@pve.proxmox.com
Envoyé: Vendredi 28 Décembre 2012 07:39:50
Objet: RE: [pve-devel] [PATCH 3/3] add downtime expected_downtime
query-migrate info
Am 27.12.2012 16:21, schrieb Alexandre DERUMIER:
But if it's work fine for you with 1s migrate_downtime, we need to
find where the problem is in the current qemu 1.3 code ... (maybe
qemu mailing can help)
To my last mails nobody answered...
What information do you miss (what last mails?)?
Last mails to qemu mailing list. It was regarding my migration problems.
Ah, yes. I will do further tests today to reproduce the bug here.
qemu-migration.tar.gz
Description: application/gzip
commit 446219a884f32853ad178e7f53fba6f07f2dafa8
Author: Stefan Priebe s.pri...@profihost.ag
Date: Sat Dec 29 14:21:45 2012 +0100
internal-snapshot-async.patch: fix buffer-file.h to qemu-file.h
diff --git a/debian/patches/internal-snapshot-async.patch
b/debian/patches/internal-snapshot-async.patch
index 6c86de3..3847409 100644
--- a/debian/patches/internal-snapshot-async.patch
+++ b/debian/patches/internal-snapshot-async.patch
@@ -245,7 +245,7 @@ Index: new/savevm-async.c
+#include qmp-commands.h
+#include blockdev.h
+#include qemu/qom-qobject.h
-+#include buffered_file.h
++#include qemu-file.h
+#include migration.h
+
+/* #define DEBUG_SAVEVM_STATE */___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
Hi Alexandre, Am 29.12.2012 14:51, schrieb Alexandre DERUMIER: Great to known that you finally found it !. Not found ;-) just know that the rework of the migration code fixes it. May be it might be a deadlock - they've changed the locking and threading handling. (Do you have respond to Paolo Bonzini, because the last response I see was that it was not working). No - i just tried to apply parts of the patchset on qemu 1.3 instead of using whole 1.4 git trunk. Alexandre might you try my rebased patches on top of pve-qemu 1.3? So, Do you want to apply the first patch only (to fix you bug), or apply the whole patches set ? (equal to current git code ?). All patches i had attached ;-) Not sure that Dietmar want to apply the big patches set ;) sure but just wanted to know if they're stable for you too. So if they're i will care about them in my own branch. So I've at least a working migration. I'll retest the whole patches set, because I was having migration problem (vm paused with error) with last qemu git. That's why i've ported not all patches and on top of qemu 1.3 instead of qemu 1.4. Stefan ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
oh, ok. I'll tests the patchs mondays. Does migration works fine for you with them ? - Mail original - De: Stefan Priebe s.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@proxmox.com Envoyé: Samedi 29 Décembre 2012 14:55:33 Objet: Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info Hi Alexandre, Am 29.12.2012 14:51, schrieb Alexandre DERUMIER: Great to known that you finally found it !. Not found ;-) just know that the rework of the migration code fixes it. May be it might be a deadlock - they've changed the locking and threading handling. (Do you have respond to Paolo Bonzini, because the last response I see was that it was not working). No - i just tried to apply parts of the patchset on qemu 1.3 instead of using whole 1.4 git trunk. Alexandre might you try my rebased patches on top of pve-qemu 1.3? So, Do you want to apply the first patch only (to fix you bug), or apply the whole patches set ? (equal to current git code ?). All patches i had attached ;-) Not sure that Dietmar want to apply the big patches set ;) sure but just wanted to know if they're stable for you too. So if they're i will care about them in my own branch. So I've at least a working migration. I'll retest the whole patches set, because I was having migration problem (vm paused with error) with last qemu git. That's why i've ported not all patches and on top of qemu 1.3 instead of qemu 1.4. Stefan ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
Hi, Am 29.12.2012 15:02, schrieb Alexandre DERUMIER: oh, ok. I'll tests the patchs mondays. Thanks! Does migration works fine for you with them ? Yes - it works fine / perfectly. But i've no VM with a desktop to play HD videos ;-) Stefan - Mail original - De: Stefan Priebe s.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@proxmox.com Envoyé: Samedi 29 Décembre 2012 14:55:33 Objet: Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info Hi Alexandre, Am 29.12.2012 14:51, schrieb Alexandre DERUMIER: Great to known that you finally found it !. Not found ;-) just know that the rework of the migration code fixes it. May be it might be a deadlock - they've changed the locking and threading handling. (Do you have respond to Paolo Bonzini, because the last response I see was that it was not working). No - i just tried to apply parts of the patchset on qemu 1.3 instead of using whole 1.4 git trunk. Alexandre might you try my rebased patches on top of pve-qemu 1.3? So, Do you want to apply the first patch only (to fix you bug), or apply the whole patches set ? (equal to current git code ?). All patches i had attached ;-) Not sure that Dietmar want to apply the big patches set ;) sure but just wanted to know if they're stable for you too. So if they're i will care about them in my own branch. So I've at least a working migration. I'll retest the whole patches set, because I was having migration problem (vm paused with error) with last qemu git. That's why i've ported not all patches and on top of qemu 1.3 instead of qemu 1.4. Stefan ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
Hi, this is what it looks like with patched qemu and my direct tcp migration patch while having a memory stress tester runing over 3GB MEM. Whole migration done in 19s!! The downtime is just so high as we allow 1s by default. Dec 29 15:17:19 starting migration of VM 101 to node 'cloud1-1203' (10.255.0.22) Dec 29 15:17:19 copying disk images Dec 29 15:17:19 starting VM 101 on remote node 'cloud1-1203' Dec 29 15:17:23 starting online/live migration on 10.255.0.22:6 Dec 29 15:17:23 migrate_set_speed: 8589934592 Dec 29 15:17:23 migrate_set_downtime: 1 Dec 29 15:17:27 migration status: active (transferred 2128861698, remaining 2152247296), total 4303814656) , expected downtime 0 Dec 29 15:17:27 migration xbzrle cachesize: 4294967296 transferred 0 pages 0 cachemiss 518714 overflow 0 Dec 29 15:17:31 migration status: active (transferred 4130570874, remaining 1161080832), total 4303814656) , expected downtime 0 Dec 29 15:17:31 migration xbzrle cachesize: 4294967296 transferred 41562 pages 88 cachemiss 979148 overflow 27159 Dec 29 15:17:35 migration speed: 341.33 MB/s - downtime 1223 ms Dec 29 15:17:35 migration status: completed Dec 29 15:17:38 migration finished successfuly (duration 00:00:19) TASK OK Greets, Stefan Am 29.12.2012 15:07, schrieb Stefan Priebe: Hi, Am 29.12.2012 15:02, schrieb Alexandre DERUMIER: oh, ok. I'll tests the patchs mondays. Thanks! Does migration works fine for you with them ? Yes - it works fine / perfectly. But i've no VM with a desktop to play HD videos ;-) Stefan - Mail original - De: Stefan Priebe s.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@proxmox.com Envoyé: Samedi 29 Décembre 2012 14:55:33 Objet: Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info Hi Alexandre, Am 29.12.2012 14:51, schrieb Alexandre DERUMIER: Great to known that you finally found it !. Not found ;-) just know that the rework of the migration code fixes it. May be it might be a deadlock - they've changed the locking and threading handling. (Do you have respond to Paolo Bonzini, because the last response I see was that it was not working). No - i just tried to apply parts of the patchset on qemu 1.3 instead of using whole 1.4 git trunk. Alexandre might you try my rebased patches on top of pve-qemu 1.3? So, Do you want to apply the first patch only (to fix you bug), or apply the whole patches set ? (equal to current git code ?). All patches i had attached ;-) Not sure that Dietmar want to apply the big patches set ;) sure but just wanted to know if they're stable for you too. So if they're i will care about them in my own branch. So I've at least a working migration. I'll retest the whole patches set, because I was having migration problem (vm paused with error) with last qemu git. That's why i've ported not all patches and on top of qemu 1.3 instead of qemu 1.4. Stefan ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
I have just done some little tests with qemu 1.3 + migration patches set, now it's working fine, no more crash ! (playing video hd). setting migrate_set_downtime to 1sec, give me: for no memory activity : 36ms downtime for high memory activity : 650ms downtime I'll do more extensive tests monday. Thanks for the patches ! - Mail original - De: Stefan Priebe s.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@proxmox.com Envoyé: Samedi 29 Décembre 2012 15:07:30 Objet: Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info Hi, Am 29.12.2012 15:02, schrieb Alexandre DERUMIER: oh, ok. I'll tests the patchs mondays. Thanks! Does migration works fine for you with them ? Yes - it works fine / perfectly. But i've no VM with a desktop to play HD videos ;-) Stefan - Mail original - De: Stefan Priebe s.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@proxmox.com Envoyé: Samedi 29 Décembre 2012 14:55:33 Objet: Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info Hi Alexandre, Am 29.12.2012 14:51, schrieb Alexandre DERUMIER: Great to known that you finally found it !. Not found ;-) just know that the rework of the migration code fixes it. May be it might be a deadlock - they've changed the locking and threading handling. (Do you have respond to Paolo Bonzini, because the last response I see was that it was not working). No - i just tried to apply parts of the patchset on qemu 1.3 instead of using whole 1.4 git trunk. Alexandre might you try my rebased patches on top of pve-qemu 1.3? So, Do you want to apply the first patch only (to fix you bug), or apply the whole patches set ? (equal to current git code ?). All patches i had attached ;-) Not sure that Dietmar want to apply the big patches set ;) sure but just wanted to know if they're stable for you too. So if they're i will care about them in my own branch. So I've at least a working migration. I'll retest the whole patches set, because I was having migration problem (vm paused with error) with last qemu git. That's why i've ported not all patches and on top of qemu 1.3 instead of qemu 1.4. Stefan ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
Great! To me even xzbrle works fine now. Am 29.12.2012 um 15:47 schrieb Alexandre DERUMIER aderum...@odiso.com: I have just done some little tests with qemu 1.3 + migration patches set, now it's working fine, no more crash ! (playing video hd). setting migrate_set_downtime to 1sec, give me: for no memory activity : 36ms downtime for high memory activity : 650ms downtime I'll do more extensive tests monday. Thanks for the patches ! - Mail original - De: Stefan Priebe s.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@proxmox.com Envoyé: Samedi 29 Décembre 2012 15:07:30 Objet: Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info Hi, Am 29.12.2012 15:02, schrieb Alexandre DERUMIER: oh, ok. I'll tests the patchs mondays. Thanks! Does migration works fine for you with them ? Yes - it works fine / perfectly. But i've no VM with a desktop to play HD videos ;-) Stefan - Mail original - De: Stefan Priebe s.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@proxmox.com Envoyé: Samedi 29 Décembre 2012 14:55:33 Objet: Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info Hi Alexandre, Am 29.12.2012 14:51, schrieb Alexandre DERUMIER: Great to known that you finally found it !. Not found ;-) just know that the rework of the migration code fixes it. May be it might be a deadlock - they've changed the locking and threading handling. (Do you have respond to Paolo Bonzini, because the last response I see was that it was not working). No - i just tried to apply parts of the patchset on qemu 1.3 instead of using whole 1.4 git trunk. Alexandre might you try my rebased patches on top of pve-qemu 1.3? So, Do you want to apply the first patch only (to fix you bug), or apply the whole patches set ? (equal to current git code ?). All patches i had attached ;-) Not sure that Dietmar want to apply the big patches set ;) sure but just wanted to know if they're stable for you too. So if they're i will care about them in my own branch. So I've at least a working migration. I'll retest the whole patches set, because I was having migration problem (vm paused with error) with last qemu git. That's why i've ported not all patches and on top of qemu 1.3 instead of qemu 1.4. Stefan ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
I'm looking into qemu src code,
in arch_init.c - ram_save_iterate()
it should return false, to retry transfert iteration of remaining memory ,
until the last step:ram_save_complete()
Seem that for Stefan, it's return 0 directly with migrate_set_downtime = 1.
I think interesting part is here:
Maybe can we add somes logs ? (BTW, is it possible to logs qemu STDOUT
somewhere in a file ?)
bwidth = qemu_get_clock_ns(rt_clock) - bwidth;
bwidth = (bytes_transferred - bytes_transferred_last) / bwidth;
/* if we haven't transferred anything this round, force
* expected_downtime to a very high value, but without
* crashing */
if (bwidth == 0) {
bwidth = 0.01;
}
qemu_put_be64(f, RAM_SAVE_FLAG_EOS);
expected_downtime = ram_save_remaining() * TARGET_PAGE_SIZE / bwidth;
DPRINTF(ram_save_live: expected(% PRIu64 ) = max( PRIu64 )?\n,
expected_downtime, migrate_max_downtime());
if (expected_downtime = migrate_max_downtime()) {
migration_bitmap_sync();
expected_downtime = ram_save_remaining() * TARGET_PAGE_SIZE / bwidth;
s-expected_downtime = expected_downtime / 100; /* ns - ms */
return expected_downtime = migrate_max_downtime();
}
return 0;
- Mail original -
De: Dietmar Maurer diet...@proxmox.com
À: Stefan Priebe - Profihost AG s.pri...@profihost.ag
Cc: Alexandre DERUMIER aderum...@odiso.com, pve-devel@pve.proxmox.com
Envoyé: Vendredi 28 Décembre 2012 07:39:50
Objet: RE: [pve-devel] [PATCH 3/3] add downtime expected_downtime
query-migrate info
Am 27.12.2012 16:21, schrieb Alexandre DERUMIER:
But if it's work fine for you with 1s migrate_downtime, we need to
find where the problem is in the current qemu 1.3 code ... (maybe
qemu mailing can help)
To my last mails nobody answered...
What information do you miss (what last mails?)?
Last mails to qemu mailing list. It was regarding my migration problems.
Ah, yes. I will do further tests today to reproduce the bug here.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
I think interesting part is here: Maybe can we add somes logs ? (BTW, is it possible to logs qemu STDOUT somewhere in a file ?) simply start qemu without -daemonize, and add #define DEBUG_ARCH_INIT 1 in arch_init.c (to enable DPRINTF()) ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
I'll try and have a look. Hopefully it shows any usable stuff. Am 28.12.2012 um 09:29 schrieb Dietmar Maurer diet...@proxmox.com: I think interesting part is here: Maybe can we add somes logs ? (BTW, is it possible to logs qemu STDOUT somewhere in a file ?) simply start qemu without -daemonize, and add #define DEBUG_ARCH_INIT 1 in arch_init.c (to enable DPRINTF()) ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
Sure you mean just the output in the web GUI?
yes
- Mail original -
De: Stefan Priebe - Profihost AG s.pri...@profihost.ag
À: Alexandre DERUMIER aderum...@odiso.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Jeudi 27 Décembre 2012 11:11:56
Objet: Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime
query-migrate info
Sure you mean just the output in the web GUI?
Stefan
Am 27.12.2012 um 10:29 schrieb Alexandre DERUMIER aderum...@odiso.com:
Can you send a migration log ?
- Mail original -
De: Stefan Priebe - Profihost AG s.pri...@profihost.ag
À: Alexandre DERUMIER aderum...@odiso.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Jeudi 27 Décembre 2012 10:26:45
Objet: Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime
query-migrate info
Ok was just an idea. To me also 0.3 does not work but 0.03 works ;-( also
limit bandwidth to 500mb does not help.
Stefan
Am 27.12.2012 um 10:09 schrieb Alexandre DERUMIER aderum...@odiso.com:
for me expected downtime is 0 until the end of the migration.
here a sample log, using default 30ms downtime.
Dec 27 07:24:06 starting migration of VM 9 to node 'kvmtest2'
(10.3.94.47)
Dec 27 07:24:06 copying disk images
Dec 27 07:24:06 starting VM 9 on remote node 'kvmtest2'
Dec 27 07:24:08 starting migration tunnel
Dec 27 07:24:09 starting online/live migration on port 6
Dec 27 07:24:09 migrate_set_speed: 8589934592
Dec 27 07:24:11 migration status: active (transferred 66518837, remaining
8314994688), total 8397455360, expected downtime 0)
Dec 27 07:24:13 migration status: active (transferred 121753397, remaining
8259760128), total 8397455360, expected downtime 0)
Dec 27 07:24:15 migration status: active (transferred 171867087, remaining
7475191808), total 8397455360, expected downtime 0)
Dec 27 07:24:17 migration status: active (transferred 178976948, remaining
4921823232), total 8397455360, expected downtime 0)
Dec 27 07:24:19 migration status: active (transferred 227210472, remaining
4726611968), total 8397455360, expected downtime 0)
Dec 27 07:24:21 migration status: active (transferred 282889143, remaining
4361879552), total 8397455360, expected downtime 0)
Dec 27 07:24:23 migration status: active (transferred 345327372, remaining
4270788608), total 8397455360, expected downtime 0)
Dec 27 07:24:25 migration status: active (transferred 407383430, remaining
4185169920), total 8397455360, expected downtime 0)
Dec 27 07:24:27 migration status: active (transferred 469084514, remaining
3742027776), total 8397455360, expected downtime 0)
Dec 27 07:24:29 migration status: active (transferred 469687094, remaining
1273860096), total 8397455360, expected downtime 0)
Dec 27 07:24:31 migration status: active (transferred 501247097, remaining
79024128), total 8397455360, expected downtime 3893)
Dec 27 07:24:33 migration status: active (transferred 532052759, remaining
103800832), total 8397455360, expected downtime 139)
Dec 27 07:24:35 migration status: active (transferred 593541297, remaining
34357248), total 8397455360, expected downtime 85)
Dec 27 07:24:35 migration status: active (transferred 603842750, remaining
37982208), total 8397455360, expected downtime 44)
Dec 27 07:24:36 migration status: active (transferred 612899069, remaining
28667904), total 8397455360, expected downtime 44)
Dec 27 07:24:36 migration status: active (transferred 623036734, remaining
30404608), total 8397455360, expected downtime 43)
Dec 27 07:24:36 migration status: active (transferred 632519102, remaining
28622848), total 8397455360, expected downtime 38)
Dec 27 07:24:36 migration status: active (transferred 638048739, remaining
26222592), total 8397455360, expected downtime 33)
Dec 27 07:24:37 migration speed: 285.71 MB/s - downtime 648 ms
Dec 27 07:24:37 migration status: completed
Dec 27 07:24:42 migration finished successfuly (duration 00:00:36)
TASK OK
- Mail original -
De: Stefan Priebe s.pri...@profihost.ag
À: Alexandre Derumier aderum...@odiso.com
Cc: pve-devel@pve.proxmox.com
Envoyé: Jeudi 27 Décembre 2012 10:03:39
Objet: Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime
query-migrate info
Hi,
to me the whole VM stalls when the new expected downtime is 0. (64bit VM
4GB Mem 1GB in use VM totally IDLE).
That's why a low migration_downtime value help for me as qemu does no
longer believe that the expected downtime is 0.
Greets,
Stefan
Am 27.12.2012 09:18, schrieb Alexandre Derumier:
Signed-off-by: Alexandre Derumier aderum...@odiso.com
---
PVE/QemuMigrate.pm | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/PVE/QemuMigrate.pm b/PVE/QemuMigrate.pm
index 282cbc5..38f1d05 100644
--- a/PVE/QemuMigrate.pm
+++ b/PVE/QemuMigrate.pm
@@ -402,7 +402,8 @@ sub phase2 {
my $delay = time() - $start;
if ($delay 0) {
my $mbps
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
Hi, Am 27.12.2012 11:21, schrieb Alexandre DERUMIER: Sure you mean just the output in the web GUI? yes Output with latest qemu-server and latest pve-qemu-kvm. VM with 4GB Mem and 100MB used (totally IDLE): Dec 27 12:55:46 starting migration of VM 105 to node 'cloud1-1203' (10.255.0.22) Dec 27 12:55:46 copying disk images Dec 27 12:55:46 starting VM 105 on remote node 'cloud1-1203' Dec 27 12:55:48 starting migration tunnel Dec 27 12:55:49 starting online/live migration on port 6 Dec 27 12:55:49 migrate_set_speed: 8589934592 Dec 27 12:55:49 migrate_set_downtime: 1 Dec 27 12:55:51 migration speed: 1024.00 MB/s - downtime 1534 ms Dec 27 12:55:51 migration status: completed Dec 27 12:55:54 migration finished successfuly (duration 00:00:09) TASK OK The same again with 1GB Memory used (cached mem): Dec 27 12:57:11 starting migration of VM 105 to node 'cloud1-1202' (10.255.0.20) Dec 27 12:57:11 copying disk images Dec 27 12:57:11 starting VM 105 on remote node 'cloud1-1202' Dec 27 12:57:15 starting migration tunnel Dec 27 12:57:15 starting online/live migration on port 6 Dec 27 12:57:15 migrate_set_speed: 8589934592 Dec 27 12:57:15 migrate_set_downtime: 1 Dec 27 12:58:45 migration speed: 22.76 MB/s - downtime 90004 ms Dec 27 12:58:45 migration status: completed Dec 27 12:58:49 migration finished successfuly (duration 00:01:38) TASK OK VM was halted between and no output of stats where done as the monitor was blocked. The same again with 1GB Memory and migrate_downtime set to 0.03 (cached mem): Dec 27 13:00:19 starting migration of VM 105 to node 'cloud1-1203' (10.255.0.22) Dec 27 13:00:19 copying disk images Dec 27 13:00:19 starting VM 105 on remote node 'cloud1-1203' Dec 27 13:00:22 starting migration tunnel Dec 27 13:00:23 starting online/live migration on port 6 Dec 27 13:00:23 migrate_set_speed: 8589934592 Dec 27 13:00:23 migrate_set_downtime: 0.03 Dec 27 13:00:25 migration status: active (transferred 404647386, remaining 680390656), total 2156265472) , expected downtime 190 Dec 27 13:00:27 migration status: active (transferred 880582320, remaining 203579392), total 2156265472) , expected downtime 53 Dec 27 13:00:29 migration speed: 341.33 MB/s - downtime 490 ms Dec 27 13:00:29 migration status: completed Dec 27 13:00:32 migration finished successfuly (duration 00:00:13) TASK OK Stefan ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
Hi, Am 27.12.2012 12:36, schrieb Dietmar Maurer: for me expected downtime is 0 until the end of the migration. Just uploaded a fix for that - please can you test: https://git.proxmox.com/?p=pve-qemu-kvm.git;a=commit;h=ca5316794924e7af304c5af762d68e0f0e5cdc5d Thanks sadly it doesn't fix the problem. I send you some outputs in the answer of alexandres question a minute ago. Greets, Stefan ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
The same again with 1GB Memory used (cached mem): Dec 27 12:57:11 starting migration of VM 105 to node 'cloud1-1202' (10.255.0.20) Dec 27 12:57:11 copying disk images Dec 27 12:57:11 starting VM 105 on remote node 'cloud1-1202' Dec 27 12:57:15 starting migration tunnel Dec 27 12:57:15 starting online/live migration on port 6 Dec 27 12:57:15 migrate_set_speed: 8589934592 Dec 27 12:57:15 migrate_set_downtime: 1 Dec 27 12:58:45 migration speed: 22.76 MB/s - downtime 90004 ms Dec 27 12:58:45 migration status: completed Dec 27 12:58:49 migration finished successfuly (duration 00:01:38) TASK OK damn, 9ms of downtime, that's crazy. It's like it's trying to finish the migration direcly, sending the whole 1GB memory in 1 pass. I think the monitor is blocked because it's blocked also for me at the end of the migration (but some ms, not 9ms) Sound like a bug somewhere is qemu - Mail original - De: Stefan Priebe s.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@proxmox.com Envoyé: Jeudi 27 Décembre 2012 13:00:47 Objet: Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info Hi, Am 27.12.2012 11:21, schrieb Alexandre DERUMIER: Sure you mean just the output in the web GUI? yes Output with latest qemu-server and latest pve-qemu-kvm. VM with 4GB Mem and 100MB used (totally IDLE): Dec 27 12:55:46 starting migration of VM 105 to node 'cloud1-1203' (10.255.0.22) Dec 27 12:55:46 copying disk images Dec 27 12:55:46 starting VM 105 on remote node 'cloud1-1203' Dec 27 12:55:48 starting migration tunnel Dec 27 12:55:49 starting online/live migration on port 6 Dec 27 12:55:49 migrate_set_speed: 8589934592 Dec 27 12:55:49 migrate_set_downtime: 1 Dec 27 12:55:51 migration speed: 1024.00 MB/s - downtime 1534 ms Dec 27 12:55:51 migration status: completed Dec 27 12:55:54 migration finished successfuly (duration 00:00:09) TASK OK The same again with 1GB Memory used (cached mem): Dec 27 12:57:11 starting migration of VM 105 to node 'cloud1-1202' (10.255.0.20) Dec 27 12:57:11 copying disk images Dec 27 12:57:11 starting VM 105 on remote node 'cloud1-1202' Dec 27 12:57:15 starting migration tunnel Dec 27 12:57:15 starting online/live migration on port 6 Dec 27 12:57:15 migrate_set_speed: 8589934592 Dec 27 12:57:15 migrate_set_downtime: 1 Dec 27 12:58:45 migration speed: 22.76 MB/s - downtime 90004 ms Dec 27 12:58:45 migration status: completed Dec 27 12:58:49 migration finished successfuly (duration 00:01:38) TASK OK VM was halted between and no output of stats where done as the monitor was blocked. The same again with 1GB Memory and migrate_downtime set to 0.03 (cached mem): Dec 27 13:00:19 starting migration of VM 105 to node 'cloud1-1203' (10.255.0.22) Dec 27 13:00:19 copying disk images Dec 27 13:00:19 starting VM 105 on remote node 'cloud1-1203' Dec 27 13:00:22 starting migration tunnel Dec 27 13:00:23 starting online/live migration on port 6 Dec 27 13:00:23 migrate_set_speed: 8589934592 Dec 27 13:00:23 migrate_set_downtime: 0.03 Dec 27 13:00:25 migration status: active (transferred 404647386, remaining 680390656), total 2156265472) , expected downtime 190 Dec 27 13:00:27 migration status: active (transferred 880582320, remaining 203579392), total 2156265472) , expected downtime 53 Dec 27 13:00:29 migration speed: 341.33 MB/s - downtime 490 ms Dec 27 13:00:29 migration status: completed Dec 27 13:00:32 migration finished successfuly (duration 00:00:13) TASK OK Stefan ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
Hi, Am 27.12.2012 13:19, schrieb Dietmar Maurer: The same again with 1GB Memory used (cached mem): Does the cache contains duplicated pages? Or pages filled with zeroes? Should'nt be zeros. If there are duplicated pages i've no idea. I've done the following: - boot VM (mem usage is 100MB) - started find /usr -type f -print0 | xargs cat /dev/null - memory usage is 860MB cached and 100MB usage Greets, Stefan ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
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 ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
not right now - but i tested this yesterday and didn't saw a difference so i moved again to 3.6.11. But i can retest? Yes, please re-test. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
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.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@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 ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
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:6 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.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@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 ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
downtime 0) Dec 27 15:35:02 migration status: active (transferred 581027192, remaining 125509632), total 8397586432, expected downtime 0) Dec 27 15:35:03 migration status: active (transferred 603663775, remaining 40046592), total 8397586432, expected downtime 0) Dec 27 15:35:03 migration status: active (transferred 618874620, remaining 0), total 8397586432, expected downtime 0) Dec 27 15:35:04 migration status: active (transferred 660269388, remaining 0), total 8397586432, expected downtime 0) Dec 27 15:35:05 migration status: active (transferred 691792794, remaining 0), total 8397586432, expected downtime 0) Dec 27 15:35:06 migration status: active (transferred 724227279, remaining 0), total 8397586432, expected downtime 0) Dec 27 15:35:07 migration status: active (transferred 756320817, remaining 0), total 8397586432, expected downtime 0) Dec 27 15:35:08 migration status: active (transferred 788061555, remaining 0), total 8397586432, expected downtime 0) Dec 27 15:35:09 migration status: active (transferred 817596465, remaining 42708992), total 8397586432, expected downtime 0) Dec 27 15:35:10 migration status: active (transferred 827831246, remaining 14131200), total 8397586432, expected downtime 0) Dec 27 15:35:10 migration status: active (transferred 836576473, remaining 0), total 8397586432, expected downtime 0) Dec 27 15:35:10 migration status: active (transferred 868789540, remaining 32485376), total 8397586432, expected downtime 0) Dec 27 15:36:10 migration status: active (transferred 2892113024, remaining 50008064), total 8397586432, expected downtime 0) Dec 27 15:36:10 migration status: active (transferred 2899587577, remaining 32702464), total 8397586432, expected downtime 0) Dec 27 15:36:11 migration status: active (transferred 2928403594, remaining 13905920), total 8397586432, expected downtime 0) Dec 27 15:36:12 migration speed: 86.96 MB/s - downtime 603 ms Dec 27 15:36:12 migration status: completed Dec 27 15:36:16 migration finished successfuly (duration 00:01:39) TASK OK - Mail original - De: Stefan Priebe s.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@proxmox.com Envoyé: Jeudi 27 Décembre 2012 15:22:45 Objet: Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info Sorry my fault ;-) Stefan Am 27.12.2012 15:19, schrieb 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:6 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.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@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 ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
Hi, Am 27.12.2012 16:21, schrieb Alexandre DERUMIER: But if it's work fine for you with 1s migrate_downtime, we need to find where the problem is in the current qemu 1.3 code ... (maybe qemu mailing can help) To my last mails nobody answered... Stefan - Mail original - De: Stefan Priebe s.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@proxmox.com Envoyé: Jeudi 27 Décembre 2012 15:19:41 Objet: Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info 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:6 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.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@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 ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
Am 27.12.2012 16:21, schrieb Alexandre DERUMIER: But if it's work fine for you with 1s migrate_downtime, we need to find where the problem is in the current qemu 1.3 code ... (maybe qemu mailing can help) To my last mails nobody answered... What information do you miss (what last mails?)? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
Am 28.12.2012 um 07:15 schrieb Dietmar Maurer diet...@proxmox.com: Am 27.12.2012 16:21, schrieb Alexandre DERUMIER: But if it's work fine for you with 1s migrate_downtime, we need to find where the problem is in the current qemu 1.3 code ... (maybe qemu mailing can help) To my last mails nobody answered... What information do you miss (what last mails?)? Last mails to qemu mailing list. It was regarding my migration problems. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
Am 27.12.2012 16:21, schrieb Alexandre DERUMIER: But if it's work fine for you with 1s migrate_downtime, we need to find where the problem is in the current qemu 1.3 code ... (maybe qemu mailing can help) To my last mails nobody answered... What information do you miss (what last mails?)? Last mails to qemu mailing list. It was regarding my migration problems. Ah, yes. I will do further tests today to reproduce the bug here. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info
To my last mails nobody answered... I have reply to the mail, adding more infos, because I think it was not enough detailled. I also put paolo bonzini and juan quintala (the migration code author) in copy. - Mail original - De: Stefan Priebe s.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@proxmox.com Envoyé: Jeudi 27 Décembre 2012 19:38:49 Objet: Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info Hi, Am 27.12.2012 16:21, schrieb Alexandre DERUMIER: But if it's work fine for you with 1s migrate_downtime, we need to find where the problem is in the current qemu 1.3 code ... (maybe qemu mailing can help) To my last mails nobody answered... Stefan - Mail original - De: Stefan Priebe s.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@proxmox.com Envoyé: Jeudi 27 Décembre 2012 15:19:41 Objet: Re: [pve-devel] [PATCH 3/3] add downtime expected_downtime query-migrate info 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:6 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.pri...@profihost.ag À: Alexandre DERUMIER aderum...@odiso.com Cc: pve-devel@pve.proxmox.com, Dietmar Maurer diet...@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 ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
