(Please try to keep the context, you trimmed out the stuff my questions
referred to)
On 6/17/2013 1:56 PM, Wolfgang Hennerbichler wrote:
On 06/11/2013 03:00 PM, Jakob Bohm wrote:
On 6/11/2013 11:44 AM, Wolfgang Hennerbichler wrote:
> > I've updated from qemu 1.0 to qemu 1.4. One of my VM's used to bridge
> > traffic (within the VM) between two interfaces. This stopped working in
> > the new Qemu-Version. It seems as if qemu is blocking traffic as soon as
> > it sees mac adresses floating on interfaces it wouldn't expect.
Did you by any chance upgrade the host computers kernel too?
Would this be relevant for this issue? The host computer is running a
stock ubuntu LTS kernel (3.2.0-37)
Since the bridging is done by the kernel, a kernel upgrade is
as good a suspect as the a qemu upgrade, that is all.
Are there any bridge or other packet related messages in the Host and Guest
syslogs?
sorry, didn't find any related messages.
Are you allowing libvirt to mess up the network configuration on your host
computer?
I just allow libvirt to add devices to my network bridge. libvirt didn't
configure those bridges, though. And there's no difference to the
previous configuration, except for the fact that it stopped working with
the qemu 1.4.2.
Good
One of those could also be related to the problem.
so you're saying I didn't run into a "feature" but a problem on my hosts?
This is really an issue for me...
No, I was just saying that because the bridging code
is split between qemu and the host kernel, when a bridge
stops working, either of the two might be involved.
Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. http://www.wisemo.com
Transformervej 29, 2730 Herlev, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
