Filed as : https://issues.apache.org/jira/browse/CLOUDSTACK-4990
On 10/29/2013, 1:45 PM, Kelven Yang wrote:
It looks like a LXC resource agent bug. LXC resource agent needs to
respond VNC command correctly in order to get console work on LXC.
Could you file a bug against LXC resource agent comp
It looks like a LXC resource agent bug. LXC resource agent needs to
respond VNC command correctly in order to get console work on LXC.
Could you file a bug against LXC resource agent component?
Kelven
On 10/29/13, 7:13 AM, "Francois Gaudreault"
wrote:
>Kelven,
>
>This is what I get in the LXC
Kelven,
This is what I get in the LXC host agent log when I try to check the
console from CS:
2013-10-29 10:07:42,079 WARN [cloud.agent.Agent]
(agentRequest-Handler-4:null) Caught:
java.lang.NullPointerException
at
com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.execute(Libv
As long as the container VNC console is reachable from console proxy
agent, I don't see a technical issue here. Need some log details to
understand the situation. For example, what information does LXC
hypervisor resource agent returns on GetVncPort command?
Kelven
On 10/28/13 10:59 AM, "Franco
Thanks! Is the console proxy issue will be fixed at some point in the
future or this won't be possible?
Francois
On 10/28/2013, 1:57 PM, Phong Nguyen wrote:
Yes, the console proxy VM is unable to connect to the LXC console. Use
virsh to connect from the host.
virsh -c lxc:/// console i-2-20-
Yes, the console proxy VM is unable to connect to the LXC console. Use
virsh to connect from the host.
virsh -c lxc:/// console i-2-20-VM
-Phong
On Mon, Oct 28, 2013 at 1:22 PM, Francois Gaudreault <
fgaudrea...@cloudops.com> wrote:
> Ok, I followed Chiradeep's comment here, and it now works f
Ok, I followed Chiradeep's comment here, and it now works fine. I have
CentOS 6 containers running.
My only other questions would be:
- Is it normal that the console proxy VM cannot proxy the container's
console?
- How can I access the container console from the host? (I am on CentOS)
I can ss
So here's what should work
Create zone
Add a KVM cluster -> add a KVM host -> wait for systemvms to start
Add a LXC cluster -> add a LXC host
On 10/24/13 9:55 AM, "Francois Gaudreault"
wrote:
>If it's designed to do that, then something is wrong with how CS deals
>with it.
>
>When I was trying t
> So we need a KVM cluster to run the VMs? (Added the author of the feature)
As it was originally discussed and implemented, the decision was to use KVM
as the system VM for LXC clusters instead of creating an LXC system VM. A
zone with only LXC clusters will deploy a KVM system VM on a host runni
If it's designed to do that, then something is wrong with how CS deals
with it.
When I was trying to get the KVM images to work, they were starting,
getting IPs, but then something was killing the VM. I though for
sometime that libvirt was the issue, so I tried Ubuntu 13.10, 12.04 and
CentOS
If this is the case, then you should remove the ability to create LXC
zones or clarify the documentation about that.
According to the wiki page:
Each of the different hypervisors currently have their own System VMs.
These system VM images are used to run a console proxy, secondary
storage, an
According to the feature page on the wiki, the KVM images are supposed
to be used... or maybe I understood it wrong.
Francois
On 10/22/2013, 1:24 AM, Chiradeep Vittal wrote:
As far as I understand, in an LXC scenario, the system vms are expected to
run on real hypervisors.
You can always use t
As far as I understand, in an LXC scenario, the system vms are expected to
run on real hypervisors.
You can always use the QuickCloud way to not use system vms at all.
On 10/21/13 1:45 PM, "Francois Gaudreault"
wrote:
>Ok I think we have to look at this further. I'll stop hijacking other
>thread
13 matches
Mail list logo
