Several times :-)
I tried adding it into the global zone as well. Doing so manually worked
OK, but putting the config commands in /usbkey/config and either rebooting
or doing a ‘sysinfo -u’ didn’t.

I saw a comment somewhere to the effect that with a kvm zone, unless the
adapter was plumbed in the global zone, it would appear in the kvm zone. (I
can’t remember where I saw this). Given that I can’t get the adapter’s
presence to persist across a reboot, should I be looking at this first?

Unfortunately, there’s very little documentation on persisting adapter
information, beyond one example.

Gareth

On 29 May 2018 at 21:09:59, Mike Gerdts ([email protected]) wrote:

>
> Taking a closer look at the initial output you provided, I can see that
> the zone with the first NIC is 4bc5b510-2d5d-e47e-c3bc-d492dfeae320.  The
> "dladm show-vnic" output shows only one vnic in that zone.  That makes it
> completely unsurprising that you don't see the second vnic in the guest.
>
> Did you reboot the kvm instance after updating the configuration?
>
> Mike
> *smartos-discuss* | Archives
> <https://www.listbox.com/member/archive/184463/=now> | Modify
> <https://www.listbox.com/member/?> Your Subscription
> <http://www.listbox.com>
>



-------------------------------------------
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125
Powered by Listbox: http://www.listbox.com

Reply via email to