Howdy,
I just installed the crossbow snapshot from opensolaris.org, and bumped
into an issue when attempting to create a virtual nic:
$ dladm create-vnic -i 192.168.1.101 -d ni0 2
dladm: VNIC creation failed: No such file or directory (unknown
diagnostic)
When I truss the process, it looks like it''s failing when attempting to
open the vnic pseudo-device:
100878/1: open("/devices/pseudo/vnic at 0:ctl", O_RDWR)
Err#2
ENOENT
100878/1: fstat64(2, 0x08046C10) = 0
When I BFU''ed the crossbow image, I ran acr to resolve conflicts. Does
anyone happen to know why this device doesn''t exist after the bfu/acr?
Are
there specific files I need to edit to get things working?
Thanks,
- Ryan
--
UNIX Administrator
http://prefetch.net
On Sep 25, 2006, at 5:07 PM, Matty wrote:> > Howdy, > > I just installed the crossbow snapshot from opensolaris.org, and > bumped into an issue when attempting to create a virtual nic: > > $ dladm create-vnic -i 192.168.1.101 -d ni0 2 > dladm: VNIC creation failed: No such file or directory (unknown > diagnostic)Is the ni driver a GLDv3 driver? (if ''dladm show-link'' shows the ni0 link as being "legacy", it means it''s not yet GLDv3). Only GLDv3 devices can currently be used by Crossbow. This will change eventually with Nemo Unification.> When I truss the process, it looks like it''s failing when > attempting to open the vnic pseudo-device: > > 100878/1: open("/devices/pseudo/vnic at 0:ctl", O_RDWR) > Err#2 ENOENT > 100878/1: fstat64(2, 0x08046C10) = 0 > > When I BFU''ed the crossbow image, I ran acr to resolve conflicts. > Does anyone happen to know why this device doesn''t exist after the > bfu/acr? Are there specific files I need to edit to get things > working?That''s an unexpected failure. This should have worked, even with a non-GLDv3 driver. Is there an entry for the vnic driver in /etc/ name_to_major? Nicolas.
>> When I truss the process, it looks like it''s failing when attempting >> to open the vnic pseudo-device: >> >> 100878/1: open("/devices/pseudo/vnic at 0:ctl", O_RDWR) >> Err#2 ENOENT >> 100878/1: fstat64(2, 0x08046C10) = 0 >> >> When I BFU''ed the crossbow image, I ran acr to resolve conflicts. >> Does anyone happen to know why this device doesn''t exist after the >> bfu/acr? Are there specific files I need to edit to get things working? > > > That''s an unexpected failure. This should have worked, even with a > non-GLDv3 driver. Is there an entry for the vnic driver in /etc/ > name_to_major?look also for vnic colliding with another major (shouldn''t happen neither) Kais> > Nicolas. > >
On Mon, 25 Sep 2006, Nicolas Droux wrote:> On Sep 25, 2006, at 5:07 PM, Matty wrote: >> >> Howdy, >> >> I just installed the crossbow snapshot from opensolaris.org, and bumped >> into an issue when attempting to create a virtual nic: >> >> $ dladm create-vnic -i 192.168.1.101 -d ni0 2 >> dladm: VNIC creation failed: No such file or directory (unknown diagnostic) > > Is the ni driver a GLDv3 driver? (if ''dladm show-link'' shows the ni0 link as > being "legacy", it means it''s not yet GLDv3). Only GLDv3 devices can > currently be used by Crossbow. This will change eventually with Nemo > Unification.The adaptor is reported as a "legacy" device, so I reckon it''s not supported. I will switch adaptors and retry.>> When I truss the process, it looks like it''s failing when attempting to >> open the vnic pseudo-device: >> >> 100878/1: open("/devices/pseudo/vnic at 0:ctl", O_RDWR) Err#2 >> ENOENT >> 100878/1: fstat64(2, 0x08046C10) = 0 >> >> When I BFU''ed the crossbow image, I ran acr to resolve conflicts. Does >> anyone happen to know why this device doesn''t exist after the bfu/acr? Are >> there specific files I need to edit to get things working? > > That''s an unexpected failure. This should have worked, even with a non-GLDv3 > driver. Is there an entry for the vnic driver in /etc/name_to_major?I don''t see an entry for the vnic driver in /etc/name_to_major: # grep vnic /etc/name_to_major # Should the acr script add this? Any idea what entry needs to be added to get this to work? Thanks - Ryan -- UNIX Administrator http://prefetch.net
On Sep 25, 2006, at 7:38 PM, Matty wrote:> > On Mon, 25 Sep 2006, Nicolas Droux wrote: > >> On Sep 25, 2006, at 5:07 PM, Matty wrote: >>> Howdy, >>> I just installed the crossbow snapshot from opensolaris.org, and >>> bumped into an issue when attempting to create a virtual nic: >>> $ dladm create-vnic -i 192.168.1.101 -d ni0 2 >>> dladm: VNIC creation failed: No such file or directory (unknown >>> diagnostic) >> >> Is the ni driver a GLDv3 driver? (if ''dladm show-link'' shows the >> ni0 link as being "legacy", it means it''s not yet GLDv3). Only >> GLDv3 devices can currently be used by Crossbow. This will change >> eventually with Nemo Unification. > > The adaptor is reported as a "legacy" device, so I reckon it''s not > supported. I will switch adaptors and retry.The current pre-release works best with bge for which we''ve enabled hardware classification and multiple unicast MAC addresses, and a future version will provide better support for all other GLDv3 drivers (bge, e1000g, xge, nge, rge, ixgb).> >>> When I truss the process, it looks like it''s failing when >>> attempting to open the vnic pseudo-device: >>> 100878/1: open("/devices/pseudo/vnic at 0:ctl", O_RDWR) >>> Err#2 ENOENT >>> 100878/1: fstat64(2, 0x08046C10) = 0 >>> When I BFU''ed the crossbow image, I ran acr to resolve conflicts. >>> Does anyone happen to know why this device doesn''t exist after >>> the bfu/acr? Are there specific files I need to edit to get >>> things working? >> >> That''s an unexpected failure. This should have worked, even with a >> non-GLDv3 driver. Is there an entry for the vnic driver in /etc/ >> name_to_major? > > I don''t see an entry for the vnic driver in /etc/name_to_major: > > # grep vnic /etc/name_to_major > # > > Should the acr script add this? Any idea what entry needs to be > added to get this to work?It should have. The acr log would contain an entry like this: ... ZONE global on / PROCESSING etc/name_to_major with i.nametomajor added <drivername> to //etc/name_to_major ... What was the machine running before the bfu to Crossbow? You should be able to add the driver manually by running "add_drv vnic" as root. Thanks, Nicolas.