Return-Path: X-Original-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 76728C5CF for ; Tue, 26 Jun 2012 03:57:00 +0000 (UTC) Received: (qmail 16172 invoked by uid 500); 26 Jun 2012 03:57:00 -0000 Delivered-To: apmail-incubator-cloudstack-users-archive@incubator.apache.org Received: (qmail 15980 invoked by uid 500); 26 Jun 2012 03:56:59 -0000 Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-users@incubator.apache.org Delivered-To: mailing list cloudstack-users@incubator.apache.org Received: (qmail 15938 invoked by uid 99); 26 Jun 2012 03:56:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jun 2012 03:56:58 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.220.175] (HELO mail-vc0-f175.google.com) (209.85.220.175) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jun 2012 03:56:50 +0000 Received: by vcbfl15 with SMTP id fl15so2605050vcb.6 for ; Mon, 25 Jun 2012 20:56:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:content-type:x-gm-message-state; bh=NbavZowBVj1tj2TyWvLoY9Ko2nRQUqyNSVWnvr7Vjrg=; b=GZGhhGcd/3uTxVxL2YaoTYM7hVEqyxkas6H2RmOo2ScgU+Idwc5OqbHeW7YEQDVTWz Nh1aAI8so3CCxh1Re0xpq+pxlIbjuQhPBgUdt5yDv3l2qWeQW8DlmUHX5qUI5D4cPc2V tOs7y4jk+Q6qsaxe8eWEIw6//xpmCsZCLyTNBcrHJD8iYIvtcRYblcLl5bIEwN2MkDPr 5E/NNiwr2SLcw9XK6SyKuXYRlkTVZ/hncdWlTGaVqpN8I/ujzp5RzCDEGW4FENl4Rc8i SCtaE4brXhU0EWFPVbL7ifvQX4Cj9aaVAacSnHWSNfa41pYY1O4B0K/FpBkhciYDyKbs Bmug== Received: by 10.220.221.7 with SMTP id ia7mr9825496vcb.31.1340682989381; Mon, 25 Jun 2012 20:56:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.111.198 with HTTP; Mon, 25 Jun 2012 20:56:09 -0700 (PDT) X-Originating-IP: [115.113.153.226] In-Reply-To: References: From: mayur dhande Date: Tue, 26 Jun 2012 09:26:09 +0530 Message-ID: Subject: Re: How to test the high availability feature of VMs running on kvm hosts in cloudstack To: cloudstack-users@incubator.apache.org Content-Type: multipart/alternative; boundary=14dae9cfc7e656a86f04c3581538 X-Gm-Message-State: ALoCoQkXhKoiwEVe03PJINSqBjTs0dQGbYGsEkM78/21jokPNEMA+NLNrDmxQQUXIFFZVMOltYg+ --14dae9cfc7e656a86f04c3581538 Content-Type: text/plain; charset=ISO-8859-1 Enable maintenance mode on that host through CloudStack UI. (Infrastructure -> Zone -> Host -> Enable maintenance mode). This will cause migration of all system VMs, DomR and HA enabled user instances to other available host. Regards, Mayur On Tue, Jun 26, 2012 at 7:33 AM, jekie wrote: > Hi all: > I created a new computing service with high availability enabled in > cloudstack UI console successfully.With that computing service,i added a > new kvm virtual machine on which windows server 2003 sp2 x64 operation > system is running.My Problem is how to test auto-failover of high > availability feature of the virtual machine? Pulling out Network cable of > KVM host will cause the entire cloud fail. --14dae9cfc7e656a86f04c3581538--