After booting the host system you will be able to set up bridged networking over VNICs (crossbow vnics, as documented). For a short limited time you will be able to reach all configured addresses from host to guests and vice versa, as well as from guest to guest. Starting a round robin ping to all configured addresses however, after a certain time you will experience some of the configured NICs are not answering anymore. If the guest(s) are rebooted, no connection will be possible anymore, which means that Vbox does not reinitialise it's host driver(s) correctly, even if all guests were stopped and restartet. Rebooting the host will of course temporarily solve the problem. rem_drv and add_drv for vboxflt does NOT help.
To test this behaviour I have 4 vnics created for each of 2 guests and 4 vnics for the host.
and I put all vnics into the same network 10.0.0.0 (255.0.0.0).
All vnics must be plumbed in the host first and configured with IPs different from the guests.
I tested this behaviour positively with Linux and Solaris guests (both 32 and 64 bit), but as it's behaving like a host driver problem, this should hold true for all possible guests.
