Comment 19 for bug 520386

actually i am using a bridged network device for a virtual guest which serves as a gateway to a virtual network, allthough i run into the same problem as described above. my setup looks now as following:

kvm host
- eth0
- br0
- eth1
the br0 is bridged to eth1

kvm guest
- eth0 (br0 on kvm host)
- eth1 (virtual)

the guest runs as a gateway w/ nat so other virtual servers may be either accessed directly from the local network or from virtual servers. if anybody is interested in a detailed setup (the way i solved it actually) just drop me a mail

basically the trick was to setup the bridge on the host (either local or from remote console) and after a restart to change the client setup by adding a new netwok device to HostDevice eth1 (Bridge br0) and removing the old one. !!! this was done directly at an x session on the kvm-server - using the virt-machine-manager from my desktop connected to the server didnt show the eth1 device !!!

hope this helps anybody who runs into same issue

greets
Chronos