(My answer is basic and likely incomplete, others may have better details, but since nobody has answered yet...)
If I understand your question correctly, you're asking if you configure the networking bandwidth during zone creation with vmadm? I can 99.8% say that no, you cannot. VMadm creates/modifies only minimal networking in zones, additional configuration/provisioning is either manually or via the config management of your choice. You can assign max bandwidth with dladm, from the Global Zone. There is also flowadm that looks like it's layered on top (allowing more granular control), but I haven't touched it yet. ~$ iperf -c somezone ------------------------------------------------------------ Client connecting to nodemin, TCP port 5001 TCP window size: 512 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.126 port 34476 connected with 192.168.1.238 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 1.07 GBytes 921 Mbits/sec [root@gz /]# dladm set-linkprop -z da4a549d-5426-edec-fe79-c95a4043e715 -p maxbw=10 net0 ~$ iperf -c somezone ------------------------------------------------------------ Client connecting to nodemin, TCP port 5001 TCP window size: 512 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.1.126 port 36018 connected with 192.168.1.238 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-18.9 sec 256 KBytes 111 Kbits/sec On Mon, Aug 28, 2017 at 8:45 AM, Tiraen <[email protected]> wrote: > Good afternoon, the question of such a plan. I correctly understood, > judging by the man pages > and what gives > dladm show-linkprop > > At the moment, bandwidth of the channel is not yet realized when creating > a virtual machine? > > Is there any more or less sane way for this? > > > > > > net0 promisc-filtered rw off on off,on > LINK PROPERTY PERM VALUE DEFAULT POSSIBLE > net0 allowed-ips rw -- -- -- > net0 allowed-dhcp-cids rw -- -- -- > net0 rxrings rw -- -- -- > net0 rxrings-effective r- -- -- -- > net0 txrings rw -- -- -- > net0 txrings-effective r- -- -- -- > net0 txrings-available r- 0 -- -- > net0 rxrings-available r- 0 -- -- > net0 rxhwclnt-available r- 0 -- -- > net0 txhwclnt-available r- 0 -- -- > net0 autopush rw -- -- -- > net0 zone rw d8117d3c-0aee-6644-abfc-9629a3bf576b -- > -- > net0 state r- up up up,down > net0 mtu rw 1500 1500 1500 > net0 secondary-macs rw -- -- -- > net0 maxbw rw -- -- -- > net0 cpus rw -- -- -- > net0 cpus-effective r- 0,7 -- -- > net0 pool rw -- -- -- > net0 pool-effective r- -- -- -- > net0 priority rw high high > low,medium,high > net0 tagmode rw vlanonly vlanonly > normal,vlanonly > net0 protection rw restricted, -- > mac-nospoof, > dhcp-nospoof restricted, > ip-nospoof, > > dhcp-nospoof > net0 promisc-filtered rw off on off,on > net0 allowed-ips rw -- -- -- > net0 allowed-dhcp-cids rw -- -- -- > net0 rxrings rw -- -- -- > net0 rxrings-effective r- -- -- -- > net0 txrings rw -- -- -- > net0 txrings-effective r- -- -- -- > net0 txrings-available r- 0 -- -- > net0 rxrings-available r- 0 -- -- > net0 rxhwclnt-available r- 0 -- -- > net0 txhwclnt-available r- 0 -- -- > > -- > With best regards, > > Vyacheslav Yakushev, > > Unix system administrator > > https://t.me/kelewind > *smartos-discuss* | Archives > <https://www.listbox.com/member/archive/184463/=now> > <https://www.listbox.com/member/archive/rss/184463/29048856-acd40977> | > Modify > <https://www.listbox.com/member/?&;> > Your Subscription <http://www.listbox.com> > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
