From issues-return-73762-apmail-cloudstack-issues-archive=cloudstack.apache.org@cloudstack.apache.org Wed Sep 28 01:01:20 2016 Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C70D419FF6 for ; Wed, 28 Sep 2016 01:01:20 +0000 (UTC) Received: (qmail 63085 invoked by uid 500); 28 Sep 2016 01:01:20 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 63051 invoked by uid 500); 28 Sep 2016 01:01:20 -0000 Mailing-List: contact issues-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 issues@cloudstack.apache.org Received: (qmail 63015 invoked by uid 500); 28 Sep 2016 01:01:20 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 63009 invoked by uid 99); 28 Sep 2016 01:01:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Sep 2016 01:01:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 7F39A2C0B05 for ; Wed, 28 Sep 2016 01:01:20 +0000 (UTC) Date: Wed, 28 Sep 2016 01:01:20 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-9379) Support nested virtualization at VM level on VMware Hypervisor MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-9379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527965#comment-15527965 ] ASF GitHub Bot commented on CLOUDSTACK-9379: -------------------------------------------- Github user jburwell commented on the issue: https://github.com/apache/cloudstack/pull/1542 @serg38 the goal is not only verify that functionality works now, but in the future to protect against regressions. My thinking is that we could deploy a CentOS VM, install KVM, and verify that we can create an ephemeral VM within it. A specially packaged template could have the KVM packages pre-installed and a small Debian or Alpine template on-board. The test would pass when it is able to SSH into the nested VM over the link-local interface. Such a test would be self-contained and not require any particular storage or network settings. Does such a test seem reasonable and valuable? > Support nested virtualization at VM level on VMware Hypervisor > -------------------------------------------------------------- > > Key: CLOUDSTACK-9379 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9379 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the default.) > Components: VMware > Affects Versions: 4.9.0 > Reporter: Nicolas Vazquez > Assignee: Nicolas Vazquez > Fix For: 4.10.0.0 > > > h2. Introduction > It is desired to support nested virtualization at VM level for VMware hypervisor. Current behaviour supports enabling/desabling global nested virtualization by modifying global config {{'vmware.nested.virtualization'}}. It is wished to improve this feature, having control at VM level instead of a global control only. > h2. Proposal > A new global configuration is added, to enable/disable VM nested virtualization control: {{'vmware.nested.virtualization.perVM'}}. Default value=false > h2. Behaviour > After a vm deployment or start command, vm params include {{nestedVirtualizationFlag}} key and its value is: > * true -> nested virtualization enabled > * false -> nested virtualization disabled > We will determinate nested virtualization enabled/disabled by examining: > * (1) global configuration {{'vmware.nested.virtualization'}} value > * (2) global configuration {{'vmware.nested.virtualization.perVM'}} value > * (3) {{'nestedVirtualizationFlag'}} value in {{user_vm_details}} if present, null if not. > Using this 3 values, there are different use cases: > # (1) = TRUE, (2) = TRUE, (3) is null -> ENABLED > # (1) = TRUE, (2) = TRUE, (3) = TRUE -> ENABLED > # (1) = TRUE, (2) = TRUE, (3) = FALSE -> DISABLED > # (1) = TRUE, (2) = FALSE -> ENABLED > # (1) = FALSE, (2) = TRUE, (3) is null -> DISABLED > # (1) = FALSE, (2) = TRUE, (3) = TRUE -> ENABLED > # (1) = FALSE, (2) = TRUE, (3) = FALSE -> DISABLED > # (1) = FALSE, (2) = FALSE -> DISABLED -- This message was sent by Atlassian JIRA (v6.3.4#6332)