From: Honghui Zhang <zhanghonghui-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Regarding LXC and Libvirt integration state.
Date: Tue, 5 Feb 2013 17:34:13 +0800 [thread overview]
Message-ID: <5110D215.9090101@huawei.com> (raw)
In-Reply-To: <CAF0SE4czOKVjB-0D461jZr1DoGyjbcCDCeNswqem6k0t9hkinA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 2013/2/5 17:21, Kunal Kushwaha wrote:
> Hi Daniel,
>
> I am trying to create LXC containers on Centos 6.3. My libvirt version is
> libvirt-0.9.10-21.el6_3.8.x86_64.
>
> I used your mail from
> http://lists.linux-foundation.org/pipermail/containers/2008-September/013237.html
> for creating LXC container.
>
> I am facing following issues.
>
> 1. If I use bridge network, from inside container, I am not able to access
> host network. Not even able to ping the br0 of host machine.
Do you have add the route in the container and configure you br0 ip addr in
the host?
> 2. Cannot ping the container from host machine.
Well, you could not get the reply from container unless you have add the route
in the container.
>
> Also, It would be great help, if you can give some light on, how much
> libvirt supports LXC.
> - I tried to add network , Storage using virsh command, but it is not
> working.
>
> If these are not supported, what is roadmap for these features?
>
> Sorry for sounding demanding, but just want to understand the libvirt and
> LXC integration state.
>
prev parent reply other threads:[~2013-02-05 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 9:21 Regarding LXC and Libvirt integration state Kunal Kushwaha
[not found] ` <CAF0SE4czOKVjB-0D461jZr1DoGyjbcCDCeNswqem6k0t9hkinA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-05 9:34 ` Honghui Zhang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5110D215.9090101@huawei.com \
--to=zhanghonghui-hv44wf8li93qt0dzr+alfa@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox