Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Tue, 9 Aug 2016 19:46:21 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12852924.1438941441000.264775.1470771981206@Atlassian.JIRA>
In-Reply-To: <JIRA.12852924.1438941441000@Atlassian.JIRA>
References: <JIRA.12852924.1438941441000@Atlassian.JIRA> <JIRA.12852924.1438941441949@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-8715) Add support for
 qemu-guest-agent to libvirt provider
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 09 Aug 2016 19:46:23 -0000


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414117#comment-15414117 ] 

ASF GitHub Bot commented on CLOUDSTACK-8715:
--------------------------------------------

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?


> Add support for qemu-guest-agent to libvirt provider
> ----------------------------------------------------
>
>                 Key: CLOUDSTACK-8715
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8715
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: KVM
>            Reporter: Sten Spans
>            Assignee: Wido den Hollander
>              Labels: kvm, libvirt, qemu, systemvm
>             Fix For: Future
>
>
> The qemu guest agent is a newer part of qemu/kvm/libvirt which exposes quite a lot of useful functionality, which can only be provided by having an agent on the VM. This includes things like freezing/thawing filesystems (for backups), reading files on the guest, listing interfaces / ip addresses, etc.
> This feature has been requested by users, but is currently not implemented.
> http://users.cloudstack.apache.narkive.com/3TTmy3zj/enabling-qemu-guest-agent
> The first change needed is to add the following to the XML generated for KVM virtual machines,:
> <channel type='unix'>
>   <source mode='bind'/>
>   <target type='virtio' name='org.qemu.guest_agent.0'/>
> </channel>
> This provides the communication channel between libvirt and the agent on the host. All in all a pretty simple change to LibvirtComputingResource.java / LibvirtVMDef.java
> Secondly the qemu-guest-agent package needs to be added to the systemvm template.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)