Date: Sat, 12 Feb 2011 09:00:41 +0000 (UTC) From: Janne Snabb <snabb@epipe.com> To: "Justin T. Gibbs" <gibbs@FreeBSD.org> Cc: freebsd-xen@FreeBSD.org Subject: Re: xn0: Error 2 parsing device/vif/0/mac [PATCH] Message-ID: <alpine.BSF.2.00.1102120852130.20212@tiktik.epipe.com> In-Reply-To: <4D47514C.7090706@FreeBSD.org> References: <alpine.BSF.2.00.1101150731240.20212@tiktik.epipe.com> <alpine.BSF.2.00.1101151002450.20212@tiktik.epipe.com> <4D47514C.7090706@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 31 Jan 2011, Justin T. Gibbs wrote: [..] > but Xend populates the MAC node in the frontend's tree > unless the "ioemu" tag is in the VIF configuration line for that interface. > Why this is the case, I have no idea - again the behavior is not documented. You are indeed correct. When I change: vif = [ 'type=ioemu, bridge=br0' ] ...to: vif = [ 'bridge=br0' ] ...in the configuration file for my FreeBSD XENHVM domU, the mac node magically appears on the front-end side: # xenstore-read device/vif/0/mac 00:16:3e:69:3e:99 ...and thus my patch becomes irrelevant. This is confusing. Especially because all the example configurations shipped with Xen have 'type=ioemu' in their vif definitions. I'll update the PR to include this workaround. -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1102120852130.20212>