Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A5A021732A for ; Fri, 24 Apr 2015 12:29:26 +0000 (UTC) Received: (qmail 87891 invoked by uid 500); 24 Apr 2015 12:29:26 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 87838 invoked by uid 500); 24 Apr 2015 12:29:26 -0000 Mailing-List: contact dev-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 dev@cloudstack.apache.org Received: (qmail 87822 invoked by uid 99); 24 Apr 2015 12:29:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Apr 2015 12:29:25 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: message received from 54.164.171.186 which is an MX secondary for dev@cloudstack.apache.org) Received: from [54.164.171.186] (HELO mx1-us-east.apache.org) (54.164.171.186) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Apr 2015 12:29:19 +0000 Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id A4FF443E41 for ; Fri, 24 Apr 2015 12:28:58 +0000 (UTC) Received: by pacyx8 with SMTP id yx8so47391393pac.1 for ; Fri, 24 Apr 2015 05:28:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=3SWKwXGKEXb4BzAn7IltxoLeVL/6iEDBXB5dUBJM5iQ=; b=r5JKjlXZ4CDKdJln6QLk9HK1hLnuGWitIewuKuEZqaqzhozGVyhkV3xpS+bompB6U7 ToDm4bkNxEmz483mHC/UzyT5zKlJhMt6hO6kAtnscHeRlDS3Us+PFgTml2nvSmNiAp19 dA2qGEfALwyhKoGmcQa3/oTmRLC0KCNISIOSh97DwBWOKAtj5N82+VtkPLo7fuUW0fb2 pr8M54jZCP4vvaWKUh/lSgqc92Fr3mDQ1z48q/LrzSFaLZLeVSJnCsrbac/vD91dbITl 6i01fvdYgOd52+tp2BN2qQM+fvwE5snawXUkceWHzefcTpmPeUstVg1NKwznrDDIzrgf RJiw== X-Received: by 10.68.204.36 with SMTP id kv4mr14315960pbc.37.1429878537988; Fri, 24 Apr 2015 05:28:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.70.86.100 with HTTP; Fri, 24 Apr 2015 05:28:37 -0700 (PDT) From: =?UTF-8?Q?Jan=2DArve_Nyg=C3=A5rd?= Date: Fri, 24 Apr 2015 14:28:37 +0200 Message-ID: Subject: Question regarding VM snapshot restrictions To: "dev@cloudstack.apache.org" Content-Type: multipart/alternative; boundary=047d7b11178154332c0514778a3a X-Virus-Checked: Checked by ClamAV on apache.org --047d7b11178154332c0514778a3a Content-Type: text/plain; charset=UTF-8 Hi, With 4.5 there are some restrictions applied to VMs that have VM snapshots. According to CLOUDSTACK-7688 VM snapshot stops working when the following operations are performed on VM with VM snapshots: 1. Volumes of VM are migrated to other storage 2. Add and remove NIC to/from VM 3. Attach and Detach volume to VM 4. Scale up/down of VM(change service offering) 5. Volume snapshot which is not major use case in this scenario 6. Resize volume 7. Live migration of VM which involves storage migration Does anyone have more technical details about why this is restricted? I tried some quick tests with XenServer 6.5 and CS 4.5.1 and I was able to both revert and take VM snapshots in CloudStack while adding vCPU and NICs on the hypervisor. Thanks, -thinktwo --047d7b11178154332c0514778a3a--