search for: name_to_major

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:

...ys/strsubr.h update: usr/src/uts/common/sys/strsun.h update: usr/src/uts/common/sys/tihdr.h update: usr/src/uts/common/syscall/sendfile.c update: usr/src/uts/intel/Makefile.intel update: usr/src/uts/intel/ia32/ml/modstubs.s update: usr/src/uts/intel/os/minor_perm update: usr/src/uts/intel/os/name_to_major update: usr/src/uts/sparc/Makefile.sparc update: usr/src/uts/sparc/ml/modstubs.s update: usr/src/uts/sparc/os/minor_perm update: usr/src/uts/sparc/os/name_to_major

I have a number of systems running solaris10 and i see the package and binary for dtrace installed however whenever we try to run anything we get this error dtrace: failed to initialize dtrace: DTrace device not available on system the only system in which i dont have this error is the development server that has the full solaris 10 install while others are minimized, do i need additional

...bridge Files: create: usr/src/uts/sparc/pxb_bcm/Makefile update: usr/src/cmd/pcidr/etc/SUNW,EC_dr,ESC_dr_req,sysevent.conf update: usr/src/pkgdefs/SUNWckr/prototype_sparc update: usr/src/uts/sparc/Makefile.sparc.shared update: usr/src/uts/sparc/os/driver_aliases update: usr/src/uts/sparc/os/name_to_major update: usr/src/uts/sun4/io/px/pcie_pwr.h update: usr/src/uts/sun4/io/px/px_dma.c update: usr/src/uts/sun4/io/px/px_pci.c update: usr/src/uts/sun4/io/px/px_pci.h

> There are times when arg0 can be NULL [for the interrupt-start or > interrupt-complete probe] if there''s no associated device. > There''s already a bug open to address the error in the documentation. > 6284911 args to interrupt-start and interrupt-complete need more info Hmm, I noticed that, too. There''s currently a thread on yahoo''s solarisx86

...root -g sys kqemu.conf new owner is root kqemu.conf installed as /usr/kernel/drv/kqemu.conf rm -f /dev/kqemu add_drv kqemu devfsadm: driver failed to attach: kqemu Warning: Driver (kqemu) successfully added to system but failed to attach ( cd /dev ; /usr/sbin/mknod kqemu c `/usr/bin/grep kqemu /etc/name_to_major | /usr/bin/awk ''{print $2}''` 0 ) -bash-3.00# --- DMESG (same output on boot screen) --- Dec 6 17:21:44 mrhbit18 genunix: [ID 819705 kern.notice] /usr/kernel/drv/kqemu: undefined symbol Dec 6 17:21:44 mrhbit18 genunix: [ID 819705 kern.notice] /usr/kernel/drv/kqemu: undefined sy...

Hi All, I have bfu''ed to net-virt_xb-21_snv_81_021308. The dladm command on my machine does not have create-etherstub option. Please let me know what could be the issue. Thanks Khushal

Hello, on a v20z, we have as DOM 0 a Solaris XEN on snv44 64bits and we have as DOM U a Solaris XEN on snv44 64 bits. We then install a pseudo driver in the Solaris DOM 1 XEN snv44: installation is ok and driver works as expected. But on reboot of DOM 1, the driver is no more there (in modinfo, driver not found). Is there something special to do after a pseudo driver installation in a Solaris