[cc'ing crossbow-discuss]
Gary Bainbridge wrote:
Am able to run VirtualBox inside a non-global zone on the same
network as the global zone using shared ip.
I want to use a vnic and assign the interface to a VM running BSD in
the non-global zone VirtualBox but need to use exclusive ip.
You can't mix shared and exlusive types in a zone. If I use a vnic
that is linked to the bge0 interface which is in the global zone on
192.168.1 network and assign the vnic to the global zone and setup
defaultrouter and netmasks files, the interface comes up but I can't
ping the router 192.168.1.1.
How can I get my VirtualBox graphical interface to display back to
the 192.168.1 network while at the same time assigning a vnic to a VM
which is a completely different network (10.)?
If your NIC is configured on a given subnet in the global zone, and you
can assign an address on the same subnet to your non-global zone, you
can create a VNIC on top of that NIC, assign the VNIC to the non-global
zone (with exclusive stack), and the zone will be able to talk to the
rest of the network as well as the global zone, for example for display.
The Crossbow virtual switching will know when packets need to be passed
between the two zones without leaving the machines, or whether the
packet needs to be sent on the wire.
If you cannot assign your zone an address on the same subnet, they you
could create a private virtual network with an etherstub, create two
VNICs on top of that etherstub, assign one VNIC to the non-global zone,
one to the global zone, and use the global zone to NAT or route between
the non-global zone and the rest of the network.
You can also create other combinations by assigning the non-global zone
multiple VNICs connected to different networks (e.g. "internal" vs
"external")
Nicolas.
--
Nicolas Droux - Solaris Kernel Networking - Sun Microsystems, Inc.
[email protected] - http://blogs.sun.com/droux
_______________________________________________
networking-discuss mailing list
[email protected]
