[OmniOS-discuss] KVM within a child zone
Natxo Asenjo
natxo.asenjo at gmail.com
Tue Dec 23 09:56:30 UTC 2014
On Tue, Dec 23, 2014 at 10:44 AM, Lauri Tirkkonen <lotheac at iki.fi> wrote:
> On Tue, Dec 23 2014 19:28:47 +1000, Michael Mounteney wrote:
> > That gets it a bit closer but I still need the real interface (e1000g1)
> > for vnc and sshing in etc. and I can't give that to the zone
> > exclusively.
>
> You can create a vnic over your physical interface (with dladm(1M)) and
> then give that to the zone.
>
my thoghts exactly. This is what I do in such cases:
First let's see the real network hardware:
# dladm show-phys
LINK MEDIA STATE SPEED DUPLEX DEVICE
bge0 Ethernet up 1000 full bge0
then create a vnic on top of that
# dladm create-vnic -l bge0 vnic1
check it's there:
# dladm show-vnic
LINK OVER SPEED MACADDRESS MACADDRTYPE VID
vnic1 bge0 1000 2:8:20:ae:f6:c0 random 0
create a zone and assign it the new vnic:
global # zonecfg -z sapacc
sapacc: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:sapacc> create
zonecfg:sapacc> set zonepath=/export/zones/sapacc
zonecfg:sapacc> set autoboot=false
zonecfg:sapacc> set ip-type=exclusive
zonecfg:sapacc> add net
zonecfg:sapacc:net> set physical=vnic1
zonecfg:sapacc:net> end
zonecfg:sapacc> verify
zonecfg:sapacc> commit
zonecfg:sapacc> exit
And then configure the vnic inside the zone like you would normally
--
Groeten,
natxo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://omniosce.org/ml-archive/attachments/20141223/355ebfd1/attachment.html>
More information about the OmniOS-discuss
mailing list