this is just a heads up about:
6738714 guest domains should be able to use multiple unicast addresses
this bug prevents zones from using vnics when inside of domUs. (it's an
old bug but it just came to my attention, so i figured it might be news
to others as well.)
----- Forwarded message from David Edmondson <d...@sun.com> -----
Date: Mon, 15 Jun 2009 16:21:20 +0100
From: David Edmondson <d...@sun.com>
To: Edward Pilatowicz <edward.pilatow...@sun.com>
Cc: "Fajar A. Nugraha" <fa...@fajar.net>, xen-disc...@opensolaris.org
Subject: Re: snv domU + zones ?
* edward.pilatow...@sun.com [2009-06-11 19:22:18]
> On Thu, Jun 11, 2009 at 03:35:52PM +0100, David Edmondson wrote:
>> * fa...@fajar.net [2009-06-11 15:10:34]
>> > On Thu, Jun 11, 2009 at 2:58 PM, David Edmondson<d...@sun.com> wrote:
>> >> VNICs inside a domU don't work very well (in fact, they work fine, they
>> >> just don't get to see any traffic from outside the domU)
>> > Why is that?
>> > I had thought it would be somewhat similar to tun/tap + bridge in
>> > Linux, where you can have tun/tap interfaces and bridges in dom0,
>> > domU, or both, and they'd function correctly as expected.
>> It's not similar to Linux in this respect. The VNIC implementation would
>> be better described as a non-learning switch (e.g. you assign ports to
>> VMs and each port has an assigned MAC address).
>> There's an RFE to fix this (allow the guest to add more unicast MAC
>> addresses), but it's not yet completed.
> what's the CR number for this RFE?
David Edmondson, Sun Microsystems, http://dme.org
----- End forwarded message -----
zones-discuss mailing list