And you are smart enough to fix it ;-) It is ugly to see it fly by.
On Thu, Dec 04, 2008 at 06:39:50AM -0600, [EMAIL PROTECTED] wrote: > Yes, the error is the 1st time said bridge is created. Call it a wart. ;-) > -- > Todd Fries .. [EMAIL PROTECTED] > > _____________________________________________ > | \ 1.636.410.0632 (voice) > | Free Daemon Consulting, LLC \ 1.405.227.9094 (voice) > | http://FreeDaemonConsulting.com \ 1.866.792.3418 (FAX) > | "..in support of free software solutions." \ 250797 (FWD) > | \ > \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ > > 37E7 D3EB 74D0 8D66 A68D B866 0326 204E 3F42 004A > http://todd.fries.net/pgp.txt > > Penned by Frank Bax on 20081203 22:31.57, we have: > > Hi Todd: > > > > You asked for feedback. Most of the time; qemu produces: > > > > {tun0 (bridge0 <-> em0)} > > > > But sometimes it produces: > > > > {tun0 (bridge0 <-> em0)brconfig: bridge0: No such process > > brconfig: bridge0: No such process > > } > > > > Network access still works, despite the error message. > > > > Frank > > > > > > On 2008-Nov-04, Todd T. Fries wrote: > >> Just out of curiosity, humor me, run qemu as root with the following added > >> options: > >> > >> -net nic,vlan=0 -net tap,vlan=0 > >> > >> I've observed that at some point user mode networking has started segv'ed > >> on > >> amd64 when running any qemu guest, and am sorry to report I have not yet > >> tracked down the source of the issue.. > >> > >> Please let me know if you have other experiences. > >> > >> Thanks,
