On Nov 28, 2007, at 5:38 AM, K wrote:

>
> 1/ Anchor vNic, the equivalent of linux dummy interfaces, we need more
> flexibility in the way we setup xen networking. What is sad is that
> the code is already available in the unreleased crossbow bits... but
> it won't appear in nevada until Q1 2008 :(

Indeed ... a frustration for many, including myself, who need specific
pieces of functionality from larger projects that have larger schedules.

We've been using a "dummy" NIC driver for the development of the Virtual
Router project which should be coming online soon.  I'm in the  
process of
getting a legal approval for making the driver available sooner ...  
It's based
on afe, which is already in the OpenSolaris repository, so I don't  
see any
problems with making it available, but I need to check first.

The intent of the driver, of course, is to bridge the gap until  
Crossbow Anchor
VNICs appear in Nevada, so any long term dependency on the driver  
should be
discouraged, but having to allocate hardware NICs for virtual  
interfaces in the
mean time is certainly a more substantial discouragement.

Kev

> This is a real blocker for me as my ISP just started implementing port
> security and locks my connection everytime it sees a foreign mac
> address using one of the IP addresses that were originally assigned to
> my dom0. On linux, I can setup a dummy interface and create a bridge
> with it for a domU but on Solaris I need a physical NIC per bridge ! 
> $!!
> @#$!
>
> For this particular feature, I am ready to give a few hundred dollars
> as booty if anyone has a workaround.
>
> 2/ Pci passthru, this is really useful so you can let a domU access a
> PCI card. It comes really handy if you want to virtualize a PBX that
> is using cheap zaptel FXO cards. Again on linux, xen pci passthru has
> been available for a while. Last time I mention this on the xen
> solaris discussion, I received a very dry reply.
>
> 3/ Problem with DMA under Xen ... e.g. my areca raid cards works
> perfect on a 8GB box without xen but because of the way xen allocates
> memory... I am forced to allocate only 1 or 2 gig for the dom0 or the
> areca drivers will fail miserably trying to do DMA above the first 4G
> address space. This very same problem affected xen under linux over a
> year ago and seems to have been addressed. Several  persons on the ZFS
> discuss list who complain about poor ZFS IO performance are affected
> by this issue.
>
> 4/ Poor exploit mitigation under Solaris. In comparaison, OpenBSD,
> grsec linux and Windows => XP SP2 have really good exploit
> mitigation.... It is a shame because solaris offered a non-exec stack
> before nearly everyone else... but it stopped there... no heap
> protection, etc...
>
> The only thing that is preventing me from switching back to linux (no
> zfs), freebsd (no xen) or openbsd (no xen and no zfs), right now is
> ZFS and it is the same reason I switched to Solaris in the first  
> place.
>
>
>
> _______________________________________________
> xen-discuss mailing list
> [EMAIL PROTECTED]

_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to