kernel virtual machine

Setup:
Triple core Phenom II, 64-bit Ubuntu Karmic Koala, Ralink wireless NIC.

Repro:
1. Attempt to create a bridged connection using a wireless NIC.
2. Spend hours reading half-baked howtos and fail.
3. Throw in the towel and use VirtualBox where bridging "just works" after
you select it through a combo box.

Result:
Wireless bridging is darn near impossible with KVM (yet VirtualBox bridges
just fine on the same machine). Wired bridging requires manual (and hence
error prone) editing of configuration files. This is compounded by the fact
that if you screw up a network config on the remote host, you lose access
to it and have to go there (or use an expensive "enterprise" remote console
thingamabob) to correct your error.

Expected result:
From my (fairly limited) understanding, VirtualBox implements bridging to
in their code using a driver. KVM should consider doing the same thing.
Currently, bridging is a major pain in the ass, and NAT is useless for most
intents and purposes, since you can't connect to a NATted machine from the
outside.