Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8F845200B61 for ; Tue, 9 Aug 2016 21:46:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8E18F160AA5; Tue, 9 Aug 2016 19:46:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CD98D160A6B for ; Tue, 9 Aug 2016 21:46:09 +0200 (CEST) Received: (qmail 54405 invoked by uid 500); 9 Aug 2016 19:46:08 -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 54394 invoked by uid 99); 9 Aug 2016 19:46:08 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Aug 2016 19:46:08 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 8A58ADFCC0; Tue, 9 Aug 2016 19:46:08 +0000 (UTC) From: rhtyd To: dev@cloudstack.apache.org Reply-To: dev@cloudstack.apache.org References: In-Reply-To: Subject: [GitHub] cloudstack issue #1545: CLOUDSTACK-8715: Add channel to Instances for Qemu G... Content-Type: text/plain Message-Id: <20160809194608.8A58ADFCC0@git1-us-west.apache.org> Date: Tue, 9 Aug 2016 19:46:08 +0000 (UTC) archived-at: Tue, 09 Aug 2016 19:46:10 -0000 Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1545 @wido thanks @jburwell With 4.9/lts we've reproduced many issues around patchviasocket timing out. If this is a better and more robust approach, should we have this fix in 4.9/lts as well? This may require a new systemvmtemplate though. Given our 4.6 based systemvm template is quite old (at least 8-9 months) and there have been security/openssl related updates, does it make sense to generate/publish a new systemvmtemplte for 4.9.1/lts? @wido is there a way we can avoid installation/generation of a new systemvm template package? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---