Krysan, Susan
2007-Aug-31 17:04 UTC
RE: [Xen-devel] [PATCH 0/3] continuable destroy domain: MakeXEN_DOMCTL_destroydomain hypercall continuable
Thank you very much for the patch. I will test it next week on our large x86_64 box with large vms. Thanks, Sue Krysan Linux Systems Group Unisys Corporation -----Original Message----- From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Isaku Yamahata Sent: Friday, August 31, 2007 10:06 AM To: xen-devel@lists.xensource.com Cc: Isaku Yamahata; Krysan, Susan; xen-ia64-devel@lists.xensource.com Subject: [Xen-devel] [PATCH 0/3] continuable destroy domain: MakeXEN_DOMCTL_destroydomain hypercall continuable Make XEN_DOMCTL_destroydomain hypercall continuable. XEN_DOMCTL_destroydomain hypercall frees domain resources, especially it frees all pages of the domain. When domain memory is very large, it takes too long resulting in soft lockup warning message or something worse. See http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1037 To fix those issues, make the hypercall continuable and repeat the hypercall until the domain is destroyed. NOTE: - the patch 1 is same as before. - I tested this patch by creating/detroying domain. However my environment doesn''t have enough memory to reproduce the issues reported as bugzilla, so I couldn''t test if this patch set eliminates the issue. [PATCH 1/3] continuable destroy domain: common part [PATCH 2/3] continuable destroy domain: x86 part [PATCH 3/3] continuable destroy domain: ia64 part thanks, _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Krysan, Susan
2007-Sep-11 21:57 UTC
RE: [Xen-devel] [PATCH 0/3] continuable destroy domain: MakeXEN_DOMCTL_destroydomain hypercall continuable
I tested the patches on Unisys ES7000 x86_64 host using 64-bit SLES10 paravirtualized domains. I compared unstable c/s 15730 and 15826 and unfortunately, the amount of time the host is unresponsive when shutting down large vms has not changed. For example, on a 32x 128gb host, the shutdown of a 62gb vm causes 1 minute and 40 seconds of host unresponsiveness both before and after the patches are applied. Also, I noticed that not only does the amount of unresponsive host time increase when the memory size of the domains increase, but it also increases when the size of the host memory increases. Here are my test results: Amt of time host unresponsive Host size Shutdown 32x 25gb vm Shutdown 32x 62gb vm 16x 64gb 30 sec 1 min 5 sec 32x 128gb 40 sec 1 min 40 sec Thanks, Sue Krysan Linux Systems Group Unisys Corporation -----Original Message----- From: Krysan, Susan Sent: Friday, August 31, 2007 1:04 PM To: ''yamahata@valinux.co.jp''; ''xen-devel@lists.xensource.com'' Cc: Subrahmanian, Raj; Carb, Brian A; Szymanski, Lukasz K; Puthiyaparambil, Aravindh; Vessey, Bruce A; Ware, Donald K; Baker, Robert S Subject: RE: [Xen-devel] [PATCH 0/3] continuable destroy domain: MakeXEN_DOMCTL_destroydomain hypercall continuable Thank you very much for the patch. I will test it next week on our large x86_64 box with large vms. Thanks, Sue Krysan Linux Systems Group Unisys Corporation -----Original Message----- From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Isaku Yamahata Sent: Friday, August 31, 2007 10:06 AM To: xen-devel@lists.xensource.com Cc: Isaku Yamahata; Krysan, Susan; xen-ia64-devel@lists.xensource.com Subject: [Xen-devel] [PATCH 0/3] continuable destroy domain: MakeXEN_DOMCTL_destroydomain hypercall continuable Make XEN_DOMCTL_destroydomain hypercall continuable. XEN_DOMCTL_destroydomain hypercall frees domain resources, especially it frees all pages of the domain. When domain memory is very large, it takes too long resulting in soft lockup warning message or something worse. See http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1037 To fix those issues, make the hypercall continuable and repeat the hypercall until the domain is destroyed. NOTE: - the patch 1 is same as before. - I tested this patch by creating/detroying domain. However my environment doesn''t have enough memory to reproduce the issues reported as bugzilla, so I couldn''t test if this patch set eliminates the issue. [PATCH 1/3] continuable destroy domain: common part [PATCH 2/3] continuable destroy domain: x86 part [PATCH 3/3] continuable destroy domain: ia64 part thanks, _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2007-Sep-12 07:34 UTC
Re: [Xen-devel] [PATCH 0/3] continuable destroy domain: MakeXEN_DOMCTL_destroydomain hypercall continuable
That¹s quite surprising. You should add tracing to domain_kill() and find out how many times it gets preempted, how long it runs for between preemptions, etc. and hence find out whether the preemption logic is working at all for you. -- Keir On 11/9/07 22:57, "Krysan, Susan" <KRYSANS@unisys.com> wrote:> I tested the patches on Unisys ES7000 x86_64 host using 64-bit SLES10 > paravirtualized domains. I compared unstable c/s 15730 and 15826 and > unfortunately, the amount of time the host is unresponsive when shutting down > large vms has not changed. For example, on a 32x 128gb host, the shutdown of > a 62gb vm causes 1 minute and 40 seconds of host unresponsiveness both before > and after the patches are applied. Also, I noticed that not only does the > amount of unresponsive host time increase when the memory size of the domains > increase, but it also increases when the size of the host memory increases. > Here are my test results:_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel