Error VERR_SUPDRV_COMPONENT_NOT_FOUND

Discussions related to using VirtualBox on Solaris hosts.

Re: Error VERR_SUPDRV_COMPONENT_NOT_FOUND

Postby Ramshankar » 11. Jan 2012, 17:03

At first boot everything is fine, and at 3rd boot you say a couple of the drivers don't work, but what happened during those 2 boots? Did the system power cycle? Did you restore an old boot-archive?

If the boot-archive is consistent and has vbox drivers in it, it should come up the same way everytime. If it doesn't come up, attach /var/adm/messages file here and I'll see if there's anything there that indicates why it doesn't.

Also, if you install VirtualBox using 3rd party services etc., that does other things it's difficult for us to offer any sort of support.
Oracle Corp.
Ramshankar
Oracle Corporation
 
Posts: 780
Joined: 7. Jan 2008, 16:17

Re: Error VERR_SUPDRV_COMPONENT_NOT_FOUND

Postby pabloc » 11. Jan 2012, 20:38

Hi Ramshankar,

vboxflt kernel module doesn´t load. My tests were the following:

1) first boot (checked if vbox modules were loaded properly, by running:

#modinfo |grep -i vbox

After that, reboot the OS with:

#shutdown -y -g0 -i6 (maybe power off with -i5, then power on)

2) second boot: did the same as first step

3) After third boot:

#modinfo |grep -i vbox

'vboxflt' module wasn't loaded. (I will attach messages log file in the next message....I will be at home in a few hours). The boot-archive wasn't updated (except when I executed rem_drv/add_drv/update_drv.

The virtualbox Solaris package was installed as a basic installation. (without any 3rd party stuff)

I'm thinking about the following (if it helps):

My Solaris box was installed via PXE (custom jumpstart) - I have only a CD R/W drive in this machine.

- The compressed fs (miniroot) for doing the installation, was modified slightly, by adding to /etc/driver_aliases the right PCI data for my NIC (intel), because it was not recognized properly. Then everything was working fine until now (except vboxflt).

Hope it can give us a little help?

Thanks.

Best Regards,
Pablo.

P.S.: I'll attach later the messages logfile when booting the OS.
pabloc
 
Posts: 3
Joined: 7. Jan 2012, 23:34
Primary OS: Solaris
VBox Version: OSE other
Guest OSses: FreeBSD

Re: Error VERR_SUPDRV_COMPONENT_NOT_FOUND

Postby Alduin » 9. Feb 2012, 10:19

I can confirm that I also have this problem on an OpenIndiana 151a host using VirtualBox 3.2.14. It occurs after every 5-7 power cycles (using init 5).

I'm wondering if this may be connected to the e1000g driver/datalink. In the past when I used the RealTek RTL8111DL as a network I didn't have these problems. But then I switched to an Intel EXPI9400PT/EXPI9402PT (same on both NIC cards) and these problems became frequent.
Alduin
 
Posts: 8
Joined: 9. Feb 2012, 10:13

Re: Error VERR_SUPDRV_COMPONENT_NOT_FOUND

Postby Ramshankar » 9. Feb 2012, 16:29

pabloc wrote:'vboxflt' module wasn't loaded. (I will attach messages log file in the next message....I will be at home in a few hours). The boot-archive wasn't updated (except when I executed rem_drv/add_drv/update_drv.
The virtualbox Solaris package was installed as a basic installation. (without any 3rd party stuff)

The VirtualBox installer explicitly updates the boot-archive after installing it's drivers. Yes attach the messages file perhaps it fails to load due to some error but it seems unlikely as it loads fine on install and 2 boots later suddenly stops loading. There is no hardware device specific code in the filter driver but Solaris might be doing something funny if the hardware changes.
Oracle Corp.
Ramshankar
Oracle Corporation
 
Posts: 780
Joined: 7. Jan 2008, 16:17

Re: Error VERR_SUPDRV_COMPONENT_NOT_FOUND

Postby Alduin » 15. Feb 2012, 11:28

I have added log files with this post: WHAT A F*ING HURDLE IT WAS!!!

I had this error today (2012-02-15). The last boot before that was yesterday, that is 2012-02-14 and the virtual machine had no problems with the e1000g controller back then. The virtual machine has run fine at least during the last 5 boots before that (I believe), there are in the /var/adm/messages log as well.
Attachments
VBox.log
Today's log with the error occurred.
(38.04 KiB) Downloaded 37 times
messages.vboxflt.zip
All /var/adm/messages in a zip file
(60.86 KiB) Downloaded 27 times
Alduin
 
Posts: 8
Joined: 9. Feb 2012, 10:13

Re: Error VERR_SUPDRV_COMPONENT_NOT_FOUND

Postby Alduin » 15. Feb 2012, 12:36

I have found that a series of nwam messages that were logged in the /var/adm/messages appear to be a precursor to this:

-------------------
Feb 14 06:13:59 OpenIndana mac: [ID 435574 kern.info] NOTICE: e1000g1 link up, 1000 Mbps, full duplex
Feb 14 06:14:03 OpenIndana nwamd[95]: [ID 621993 daemon.error] 8: start_dhcp: ipadm_create_addr on e1000g1 returned: Could not communicate with dhcpagent, retrying in 10 sec
Feb 14 06:14:03 OpenIndana mac: [ID 486395 kern.info] NOTICE: e1000g1 link down
Feb 14 06:14:03 OpenIndana nwamd[95]: [ID 247971 daemon.error] 1: nwamd_down_interface: ipadm_delete_addr failed on e1000g1: Could not communicate with dhcpagent
Feb 14 06:14:03 OpenIndana nwamd[95]: [ID 750975 daemon.error] 9: start_dhcp: ipadm_create_addr on e1000g1 returned: Could not communicate with dhcpagent, retrying in 10 sec
-------------------
they occurred repeatedly during startup but everything worked fine after boot was finished.


Here are some log entries that were generated in the /var/adm/messages which I did rem_drv vboxflt / add_drv vboxflt:
-------------------
Feb 15 11:26:13 OpenIndana vboxdrv: [ID 200995 kern.notice] vboxflt:file_t::f_vnode at 16
Feb 15 11:26:13 OpenIndana rootnex: [ID 349649 kern.info] fcoe0 at root
Feb 15 11:26:13 OpenIndana genunix: [ID 936769 kern.info] fcoe0 is /fcoe
Feb 15 11:26:13 OpenIndana acpinex: [ID 328922 kern.info] acpinex: sb@0, acpinex1
Feb 15 11:26:13 OpenIndana genunix: [ID 936769 kern.info] acpinex1 is /fw/sb@0
Feb 15 11:26:13 OpenIndana unix: [ID 954099 kern.info] NOTICE: IRQ18 is being shared by drivers with different interrupt levels.
Feb 15 11:26:13 OpenIndana This may result in reduced system performance.
Feb 15 11:26:13 OpenIndana pcplusmp: [ID 805372 kern.info] pcplusmp: ide (ata) instance 2 irq 0xe vector 0x44 ioapic 0x8 intin 0xe is bound to cpu 3
Feb 15 11:26:13 OpenIndana unix: [ID 954099 kern.info] NOTICE: IRQ18 is being shared by drivers with different interrupt levels.
Feb 15 11:26:13 OpenIndana This may result in reduced system performance.
Feb 15 11:26:13 OpenIndana pcplusmp: [ID 805372 kern.info] pcplusmp: ide (ata) instance 3 irq 0xf vector 0x44 ioapic 0x8 intin 0xf is bound to cpu 0
Feb 15 11:26:13 OpenIndana unix: [ID 954099 kern.info] NOTICE: IRQ17 is being shared by drivers with different interrupt levels.
Feb 15 11:26:13 OpenIndana This may result in reduced system performance.
Feb 15 11:26:13 OpenIndana unix: [ID 954099 kern.info] NOTICE: IRQ17 is being shared by drivers with different interrupt levels.
Feb 15 11:26:13 OpenIndana This may result in reduced system performance.
Feb 15 11:26:13 OpenIndana isa: [ID 202937 kern.info] ISA-device: pit_beep0
Feb 15 11:26:13 OpenIndana genunix: [ID 936769 kern.info] pit_beep0 is /pci@0,0/isa@14,3/pit_beep
Feb 15 11:26:13 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: pseudo1
Feb 15 11:26:13 OpenIndana genunix: [ID 936769 kern.info] pseudo1 is /pseudo/zconsnex@1
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: nvidia255
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] nvidia255 is /pseudo/nvidia@255
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: fcp0
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp@0
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: dcpc0
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] dcpc0 is /pseudo/dcpc@0
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: fasttrap0
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] fasttrap0 is /pseudo/fasttrap@0
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: fbt0
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] fbt0 is /pseudo/fbt@0
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: lockstat0
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat@0
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: profile0
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] profile0 is /pseudo/profile@0
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: sdt0
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] sdt0 is /pseudo/sdt@0
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: systrace0
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] systrace0 is /pseudo/systrace@0
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: fcsm0
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm@0
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: llc10
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1@0
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: lofi0
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi@0
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: ramdisk1024
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] ramdisk1024 is /pseudo/ramdisk@1024
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: ucode0
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] ucode0 is /pseudo/ucode@0
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: winlock0
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] winlock0 is /pseudo/winlock@0
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: nsmb0
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] nsmb0 is /pseudo/nsmb@0
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: ncall0
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] ncall0 is /pseudo/ncall@0
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: fssnap0
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap@0
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: bpf0
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] bpf0 is /pseudo/bpf@0
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: nsctl0
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] nsctl0 is /pseudo/nsctl@0
Feb 15 11:26:14 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: nsctl0
Feb 15 11:26:14 OpenIndana genunix: [ID 936769 kern.info] nsctl0 is /pseudo/nsctl@0
Feb 15 11:26:15 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: sdbc0
Feb 15 11:26:15 OpenIndana genunix: [ID 936769 kern.info] sdbc0 is /pseudo/sdbc@0
Feb 15 11:26:15 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: rdc0
Feb 15 11:26:15 OpenIndana genunix: [ID 936769 kern.info] rdc0 is /pseudo/rdc@0
Feb 15 11:26:15 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: ii0
Feb 15 11:26:15 OpenIndana genunix: [ID 936769 kern.info] ii0 is /pseudo/ii@0
Feb 15 11:26:15 OpenIndana sv: [ID 369078 kern.info] sv (revision 11.11, SunOS 5.11, None)
Feb 15 11:26:15 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: sv0
Feb 15 11:26:15 OpenIndana genunix: [ID 936769 kern.info] sv0 is /pseudo/sv@0
Feb 15 11:26:15 OpenIndana pseudo: [ID 129642 kern.info] pseudo-device: vboxflt0
Feb 15 11:26:15 OpenIndana genunix: [ID 936769 kern.info] vboxflt0 is /pseudo/vboxflt@0
-------------------
Alduin
 
Posts: 8
Joined: 9. Feb 2012, 10:13

Previous

Return to VirtualBox on Solaris Hosts

Who is online

Users browsing this forum: No registered users and 1 guest