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 A2FD9D26B for ; Tue, 10 Jul 2012 09:27:30 +0000 (UTC) Received: (qmail 24284 invoked by uid 500); 10 Jul 2012 09:27:30 -0000 Delivered-To: apmail-incubator-cloudstack-users-archive@incubator.apache.org Received: (qmail 24100 invoked by uid 500); 10 Jul 2012 09:27:30 -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 24069 invoked by uid 99); 10 Jul 2012 09:27:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jul 2012 09:27:28 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [213.199.154.141] (HELO db3outboundpool.messaging.microsoft.com) (213.199.154.141) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jul 2012 09:27:20 +0000 Received: from mail106-db3-R.bigfish.com (10.3.81.250) by DB3EHSOBE003.bigfish.com (10.3.84.23) with Microsoft SMTP Server id 14.1.225.23; Tue, 10 Jul 2012 09:24:40 +0000 Received: from mail106-db3 (localhost [127.0.0.1]) by mail106-db3-R.bigfish.com (Postfix) with ESMTP id D144F140446 for ; Tue, 10 Jul 2012 09:24:40 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.248.213;KIP:(null);UIP:(null);IPV:NLI;H:AMXPRD0610HT003.eurprd06.prod.outlook.com;RD:none;EFVD:NLI X-SpamScore: -6 X-BigFish: VPS-6(zz542M4015Izz1202hzz8275bh8275dhz2dh2a8h668h839h944hd25hf0ah107ah) Received: from mail106-db3 (localhost.localdomain [127.0.0.1]) by mail106-db3 (MessageSwitch) id 134191227833629_17406; Tue, 10 Jul 2012 09:24:38 +0000 (UTC) Received: from DB3EHSMHS013.bigfish.com (unknown [10.3.81.237]) by mail106-db3.bigfish.com (Postfix) with ESMTP id 0390B2A00E7 for ; Tue, 10 Jul 2012 09:24:38 +0000 (UTC) Received: from AMXPRD0610HT003.eurprd06.prod.outlook.com (157.56.248.213) by DB3EHSMHS013.bigfish.com (10.3.87.113) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 10 Jul 2012 09:24:37 +0000 Received: from AMXPRD0610MB388.eurprd06.prod.outlook.com ([169.254.3.14]) by AMXPRD0610HT003.eurprd06.prod.outlook.com ([10.255.58.38]) with mapi id 14.16.0175.005; Tue, 10 Jul 2012 09:26:50 +0000 From: Tamas Monos To: "cloudstack-users@incubator.apache.org" Subject: RE: Forcing System VMs to respawn Thread-Topic: Forcing System VMs to respawn Thread-Index: AQHNXgwtX+EWeyqsJkmcLKrvSfHisJciP2fA Date: Tue, 10 Jul 2012 09:26:50 +0000 Message-ID: References: <544B2AEE-C86E-4328-8C35-71D08DF668A7@me.com> In-Reply-To: <544B2AEE-C86E-4328-8C35-71D08DF668A7@me.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [217.168.19.152] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: veber.co.uk Hi, You can destroy your system VM (SSVM,CPVM) the same way you destroy a user = VM instance. The system will automatically create a new one when the previous one was de= stroyed, with a new IP (I believe). Regards Tamas Monos DDI +44(0= )2034687012 Chief Technical Office +44(0= )2034687000 Veber: The Hosting Specialists Fax +44(0)871 522 7057 http://www.veber.co.uk Follow us on Twitter: www.twitter.com/veberhost Follow us on Facebook: www.facebook.com/veberhost -----Original Message----- From: Caleb Call [mailto:calebcall@me.com]=20 Sent: 09 July 2012 20:50 To: cloudstack-users@incubator.apache.org Subject: Forcing System VMs to respawn Is there a way to get the system VMs to respawn. From what I understand, t= hey are supposed to respawn when they are needed. Even after stopping them= , they weren't releasing the Public IPs so I had to kill them off (had to r= econfigure the networks). So now that I've gone through and fixed my netwo= rks and re-enabled everything (Zone, pod, cluster, hosts, etc) I was expect= ing them to start back up with no luck. Anyway to force this to happen? Thanks, Caleb