From commits-return-94927-archive-asf-public=cust-asf.ponee.io@cloudstack.apache.org Tue Nov 26 23:24:14 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 6E87218065D for ; Wed, 27 Nov 2019 00:24:14 +0100 (CET) Received: (qmail 28402 invoked by uid 500); 26 Nov 2019 23:24:13 -0000 Mailing-List: contact commits-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list commits@cloudstack.apache.org Received: (qmail 28393 invoked by uid 99); 26 Nov 2019 23:24:13 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Nov 2019 23:24:13 +0000 From: GitBox To: commits@cloudstack.apache.org Subject: [GitHub] [cloudstack] andrijapanicsb commented on issue #3720: VM stopped/crashing while Migration with Maintenance Mode (KVM) Message-ID: <157481065363.11318.5623551025547354225.gitbox@gitbox.apache.org> Date: Tue, 26 Nov 2019 23:24:13 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit andrijapanicsb commented on issue #3720: VM stopped/crashing while Migration with Maintenance Mode (KVM) URL: https://github.com/apache/cloudstack/issues/3720#issuecomment-558860214 I believe the biggest problem I saw was VM crashing due to qemu bugs/issue (i.e. recently saw this one “qemu-kvm general protection error in libtcmalloc.so.4.4.5”) – can’t speak for other issues, since I don’t recall having them with ACS 4.5/4.8 with Ubuntu 14.04 (qemu 2.0 initially, later upgraded to 2.5) If not mistaken, there is indeed a behavior that if there is no enough capacities in the cluster (test with a single KVM host in the cluster), the VMs will be stopped – and that is a thing to change in my opinion. Maintenance should fail and host should be in ErrorInMaintenance mode. If you want to do maintenance of that host, put the storage into the maintenance mode and you are good to go. Even better, make an additional parameter like “forceMaintenance” which will indeed stop VMs in order to reach Maintenance mode. Othewise will simply be in ErrorInMaintenance. I really don’ recall having issues with 5 VMs/agent threads – and I’ve been doing a lot of maintenance with couple of hunders of VMs 2-3 years ago (ACS 4.8). This one should be reproduced first. Regards, Andrija Panic Andrija Panic Cloud Architect s: +44 20 3603 0540 | m: +381 69 272 3690 e: andrija.panic@shapeblue.com  |  w: www.shapeblue.com  |  t:  @shapeblue a: Amadeus House, Floral Street, London WC2E 9DPUK Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark.This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Find out more about ShapeBlue and our range of CloudStack related services: IaaS Cloud Design & Build | CSForge - rapid IaaS deployment framework CloudStack Consulting | CloudStack Software Engineering CloudStack Infrastructure Support | CloudStack Bootcamp Training Courses ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: users@infra.apache.org With regards, Apache Git Services