On Thu, Jul 18, 2013 at 09:43:54PM +0200, Marius Tomaschewski wrote:
Am 18.07.2013 17:02, schrieb Richard Weinberger:
Am 18.07.2013 16:50, schrieb Jim Fehlig:
Richard,
I think you should have cc'd the bug assignee when discussing this issue
upstream. Adding him now...
Oh, sorry
Am 19.07.2013 10:36, schrieb Daniel P. Berrange:
On Thu, Jul 18, 2013 at 09:43:54PM +0200, Marius Tomaschewski wrote:
Am 18.07.2013 17:02, schrieb Richard Weinberger:
Am 18.07.2013 16:50, schrieb Jim Fehlig:
Richard,
I think you should have cc'd the bug assignee when discussing this issue
On Wed, Jul 17, 2013 at 11:33:22PM +0200, Richard Weinberger wrote:
Am 12.07.2013 03:36, schrieb Gao feng:
On 07/11/2013 07:58 PM, Richard Weinberger wrote:
Am 11.07.2013 11:49, schrieb Daniel P. Berrange:
On Thu, Jul 11, 2013 at 11:44:48AM +0200, Richard Weinberger wrote:
Am 11.07.2013
Richard,
I think you should have cc'd the bug assignee when discussing this issue
upstream. Adding him now...
Regards,
Jim
Daniel P. Berrange wrote:
On Wed, Jul 17, 2013 at 11:33:22PM +0200, Richard Weinberger wrote:
Am 12.07.2013 03:36, schrieb Gao feng:
On 07/11/2013 07:58 PM,
Am 18.07.2013 16:50, schrieb Jim Fehlig:
Richard,
I think you should have cc'd the bug assignee when discussing this issue
upstream. Adding him now...
Oh, sorry for that!
I thought I did so after pointing Marius to the thread in the mailing list
archive,
but obviously I forgot.
Thanks,
Am 18.07.2013 17:02, schrieb Richard Weinberger:
Am 18.07.2013 16:50, schrieb Jim Fehlig:
Richard,
I think you should have cc'd the bug assignee when discussing this issue
upstream. Adding him now...
Oh, sorry for that!
I thought I did so after pointing Marius to the thread in the
Am 12.07.2013 03:36, schrieb Gao feng:
On 07/11/2013 07:58 PM, Richard Weinberger wrote:
Am 11.07.2013 11:49, schrieb Daniel P. Berrange:
On Thu, Jul 11, 2013 at 11:44:48AM +0200, Richard Weinberger wrote:
Am 11.07.2013 11:42, schrieb Gao feng:
On 07/11/2013 03:18 PM, Richard Weinberger
Am 10.07.2013 11:42, schrieb Gao feng:
On 07/10/2013 03:23 PM, Richard Weinberger wrote:
Am 10.07.2013 09:03, schrieb Gao feng:
On 07/10/2013 02:00 PM, Richard Weinberger wrote:
Yes,actually libvirt did up the veth devices, that's why only veth2
veth5 are down.
Where does libvirt up the
On 07/11/2013 03:18 PM, Richard Weinberger wrote:
Am 10.07.2013 11:42, schrieb Gao feng:
On 07/10/2013 03:23 PM, Richard Weinberger wrote:
Am 10.07.2013 09:03, schrieb Gao feng:
On 07/10/2013 02:00 PM, Richard Weinberger wrote:
Yes,actually libvirt did up the veth devices, that's why only
On Thu, Jul 11, 2013 at 09:18:24AM +0200, Richard Weinberger wrote:
This morning I've installed a wrapper around ip to show me the process tree
upon ip link ... down is used.
The log showed this:
769 ?Ss 0:00 /usr/lib/systemd/systemd-udevd
17759 ?S 0:00 \_
Am 11.07.2013 11:42, schrieb Gao feng:
On 07/11/2013 03:18 PM, Richard Weinberger wrote:
Am 10.07.2013 11:42, schrieb Gao feng:
On 07/10/2013 03:23 PM, Richard Weinberger wrote:
Am 10.07.2013 09:03, schrieb Gao feng:
On 07/10/2013 02:00 PM, Richard Weinberger wrote:
Yes,actually libvirt
On Thu, Jul 11, 2013 at 11:44:48AM +0200, Richard Weinberger wrote:
Am 11.07.2013 11:42, schrieb Gao feng:
On 07/11/2013 03:18 PM, Richard Weinberger wrote:
This morning I've installed a wrapper around ip to show me the process
tree upon ip link ... down is used.
The log showed this:
Am 11.07.2013 11:49, schrieb Daniel P. Berrange:
On Thu, Jul 11, 2013 at 11:44:48AM +0200, Richard Weinberger wrote:
Am 11.07.2013 11:42, schrieb Gao feng:
On 07/11/2013 03:18 PM, Richard Weinberger wrote:
This morning I've installed a wrapper around ip to show me the process
tree upon ip
On 07/11/2013 07:58 PM, Richard Weinberger wrote:
Am 11.07.2013 11:49, schrieb Daniel P. Berrange:
On Thu, Jul 11, 2013 at 11:44:48AM +0200, Richard Weinberger wrote:
Am 11.07.2013 11:42, schrieb Gao feng:
On 07/11/2013 03:18 PM, Richard Weinberger wrote:
This morning I've installed a wrapper
Am 10.07.2013 03:20, schrieb Gao feng:
On 07/09/2013 09:11 PM, Richard Weinberger wrote:
Am 08.07.2013 05:54, schrieb Gao feng:
On 07/05/2013 06:22 PM, Richard Weinberger wrote:
Am 05.07.2013 03:36, schrieb Gao feng:
On 07/05/2013 04:45 AM, Richard Weinberger wrote:
Hi,
Am 03.07.2013
On 07/10/2013 02:00 PM, Richard Weinberger wrote:
Yes,actually libvirt did up the veth devices, that's why only veth2 veth5
are down.
Where does libvirt up the devices? The debug log does not contain any ip
link set dev XXX up commands.
Also in src/util/virnetdevveth.c I'm unable to
Am 10.07.2013 09:03, schrieb Gao feng:
On 07/10/2013 02:00 PM, Richard Weinberger wrote:
Yes,actually libvirt did up the veth devices, that's why only veth2 veth5
are down.
Where does libvirt up the devices? The debug log does not contain any ip
link set dev XXX up commands.
Also in
On 07/10/2013 03:23 PM, Richard Weinberger wrote:
Am 10.07.2013 09:03, schrieb Gao feng:
On 07/10/2013 02:00 PM, Richard Weinberger wrote:
Yes,actually libvirt did up the veth devices, that's why only veth2 veth5
are down.
Where does libvirt up the devices? The debug log does not contain
Am 10.07.2013 11:42, schrieb Gao feng:
On 07/10/2013 03:23 PM, Richard Weinberger wrote:
Am 10.07.2013 09:03, schrieb Gao feng:
On 07/10/2013 02:00 PM, Richard Weinberger wrote:
Yes,actually libvirt did up the veth devices, that's why only veth2
veth5 are down.
Where does libvirt up the
Am 08.07.2013 05:54, schrieb Gao feng:
On 07/05/2013 06:22 PM, Richard Weinberger wrote:
Am 05.07.2013 03:36, schrieb Gao feng:
On 07/05/2013 04:45 AM, Richard Weinberger wrote:
Hi,
Am 03.07.2013 12:04, schrieb Gao feng:
Hi,
On 07/01/2013 03:45 PM, Richard Weinberger wrote:
Hi!
If you
On 07/09/2013 09:11 PM, Richard Weinberger wrote:
Am 08.07.2013 05:54, schrieb Gao feng:
On 07/05/2013 06:22 PM, Richard Weinberger wrote:
Am 05.07.2013 03:36, schrieb Gao feng:
On 07/05/2013 04:45 AM, Richard Weinberger wrote:
Hi,
Am 03.07.2013 12:04, schrieb Gao feng:
Hi,
On 07/01/2013
On 07/05/2013 06:22 PM, Richard Weinberger wrote:
Am 05.07.2013 03:36, schrieb Gao feng:
On 07/05/2013 04:45 AM, Richard Weinberger wrote:
Hi,
Am 03.07.2013 12:04, schrieb Gao feng:
Hi,
On 07/01/2013 03:45 PM, Richard Weinberger wrote:
Hi!
If you have multiple LXC containers with
Am 05.07.2013 03:36, schrieb Gao feng:
On 07/05/2013 04:45 AM, Richard Weinberger wrote:
Hi,
Am 03.07.2013 12:04, schrieb Gao feng:
Hi,
On 07/01/2013 03:45 PM, Richard Weinberger wrote:
Hi!
If you have multiple LXC containers with networking and the autostart
feature enabled libvirtd
Hi,
Am 03.07.2013 12:04, schrieb Gao feng:
Hi,
On 07/01/2013 03:45 PM, Richard Weinberger wrote:
Hi!
If you have multiple LXC containers with networking and the autostart
feature enabled libvirtd fails to
up some veth interfaces on the host side.
Most of the time only the first veth
On 07/05/2013 04:45 AM, Richard Weinberger wrote:
Hi,
Am 03.07.2013 12:04, schrieb Gao feng:
Hi,
On 07/01/2013 03:45 PM, Richard Weinberger wrote:
Hi!
If you have multiple LXC containers with networking and the autostart
feature enabled libvirtd fails to
up some veth interfaces on the
Hi,
On 07/01/2013 03:45 PM, Richard Weinberger wrote:
Hi!
If you have multiple LXC containers with networking and the autostart feature
enabled libvirtd fails to
up some veth interfaces on the host side.
Most of the time only the first veth device is in state up, all others are
down.
Hi!
If you have multiple LXC containers with networking and the autostart feature
enabled libvirtd fails to
up some veth interfaces on the host side.
Most of the time only the first veth device is in state up, all others are down.
Reproducing is easy.
1. Define a few containers (5 in my case)
27 matches
Mail list logo