Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
From: remibergsma <git@git.apache.org>
To: dev@cloudstack.apache.org
Reply-To: dev@cloudstack.apache.org
References: <git-pr-985-cloudstack@git.apache.org>
In-Reply-To: <git-pr-985-cloudstack@git.apache.org>
Subject: [GitHub] cloudstack pull request: CLOUDSTACK-8715: Add VirtIO channel
 to al...
Content-Type: text/plain
Message-Id: <20151028124333.E1E69DFE34@git1-us-west.apache.org>
Date: Wed, 28 Oct 2015 12:43:33 +0000 (UTC)

Github user remibergsma commented on the pull request:

    https://github.com/apache/cloudstack/pull/985#issuecomment-151832340
  
    @wido Thanks for working on this, awesome!
    
    I was testing this PR and found that the SSVM and CPVM systemvms do not start properly. This is the error:
    
    ```
    2015-10-28 12:36:30,145 WARN  [resource.wrapper.LibvirtStartCommandWrapper] (agentRequest-Handler-4:null) Li
    bvirtException 
    org.libvirt.LibvirtException: internal error: process exited while connecting to monitor: 2015-10-28T12:36:2
    9.904910Z qemu-kvm: -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/v-273-VM.org.qemu.guest_agent.0,server,nowait: Failed to bind socket: Permission denied
    2015-10-28T12:36:29.904949Z qemu-kvm: -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/v-273-VM.org.qemu.guest_agent.0,server,nowait: chardev: opening backend "socket" failed
    
            at org.libvirt.ErrorHandler.processError(Unknown Source)
            at org.libvirt.Connect.processError(Unknown Source)
            at org.libvirt.Connect.processError(Unknown Source)
            at org.libvirt.Connect.domainCreateXML(Unknown Source)
            at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.startVM(LibvirtComputingResource.java:1292)
            at com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStartCommandWrapper.execute(LibvirtStartCommandWrapper.java:82)
            at com.cloud.hypervisor.kvm.resource.wrapper.LibvirtStartCommandWrapper.execute(LibvirtStartCommandWrapper.java:46)
            at com.cloud.hypervisor.kvm.resource.wrapper.LibvirtRequestWrapper.execute(LibvirtRequestWrapper.java:75)
            at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.executeRequest(LibvirtComputingResource.java:1316)
            at com.cloud.agent.Agent.processRequest(Agent.java:518)
            at com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:823)
            at com.cloud.utils.nio.Task.call(Task.java:83)
            at com.cloud.utils.nio.Task.call(Task.java:29)
            at java.util.concurrent.FutureTask.run(FutureTask.java:266)
            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
            at java.lang.Thread.run(Thread.java:745)
    ```
    
    Here is the channel dir:
    
    ```
    [root@kvm1 channel]# ls -al /var/lib/libvirt/qemu/channel/
    total 12
    drwxr-x---. 3 qemu qemu 4096 Oct 28 09:55 .
    drwxr-x---. 7 root root 4096 Oct 28 12:39 ..
    drwxr-x---. 2 qemu qemu 4096 Sep 15 14:03 target
    ```
    
    The `target` folder was empty.
    
    I've installed the rpm package that I've built from this branch. The agent seems to run as root:
    
    ```
    root      9815  0.4  3.1 4815960 255916 ?      Sl   10:17   0:41 /usr/lib/jvm/jre/bin/java -Xms256m -Xmx2048 <cut>
    ```
    
    It was tested on a KVM hypervisor on CentOS 7. Ping me if you need more details.


---
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.
---