"vboxdrv" in security output?

[norbs]

Did change memory amount, not sure if that's what made this happen, got this email:

nas.local kernel log messages:
> real memory = 13958643712 (13312 MB)
> avail memory = 12365930496 (11793 MB)
> vboxdrv: fAsync=0 offMin=0x434 offMax=0x21e4

-- End of security output --

No changes, shows up during boot and in security email:

nas.local kernel log messages:
> vboxdrv: fAsync=0 offMin=0x321 offMax=0x5735

-- End of security output --

Been getting that in security emails?
I don't run any jails or use any plugins, any ideas? Safe to ignore?
Did NSA bug me? *adds another layer of tinfoil just in case*

 

[norbs]

Anyone? I've seen this a few times in other people's security outputs as well but no one questions that portion.

 

[Ericloewe]

You've been getting that message daily in the security report?

 

[norbs]

Yep for the past 3 days (but I have been rebooting my NAS at least once between those days).

Just checked my email and here is another:

nas.local kernel log messages:
> vboxdrv: fAsync=0 offMin=0x3c6 offMax=0x5d9a

-- End of security output --

Only thing I've changed was updating the firmware and driver from P16 to P20 but I can see the message on bootup with or without the card installed.

 

[Ericloewe]

@cyberjock - Any ideas? The values also seem to change every time.

 

[norbs]

[root@nas] ~# cat /var/log/dmesg.today | grep vboxdrv
vboxdrv: fAsync=0 offMin=0x3c6 offMax=0x5d9a
[root@nas] ~# cat /var/log/dmesg.yesterday | grep vboxdrv
vboxdrv: fAsync=0 offMin=0x321 offMax=0x5735
[root@nas] ~# cat /var/log/dmesg.today.save | grep vboxdrv
vboxdrv: fAsync=0 offMin=0x321 offMax=0x5735GEOM_ELI: Encryption: AES-XTS 256
vboxdrv: fAsync=0 offMin=0x321 offMax=0x5735
[root@nas] ~#

What does the vboxdrv actually provide? Is it specifically for jails or plugins?

 

[cyberjock]

No ideas, and since he's already admitted to playing with things we have said over and over again (and users have even told us that they did it despite us and later learned their lesson and admitted that they should have listened to us to begin with), I'm not to inclined to look into the problem (assuming its not self-inflicted to begin with).

 

[Ericloewe]

What does the vboxdrv actually provide? Is it specifically for jails or plugins?

Judging by the name, it provides interfaces through which virtualbox VMs can interact with the outside world.

 

[norbs]

I tried a new install (without my raid controller connected) and I see the same thing on boot-up.
If you search the forums for "vboxdrv" others have the same message on boot as well.
If it's not a big deal it's not a big deal, I was just curious because it's in my security output.

Anyways thanks for the help i guess... only reason I "played" with it was I didn't realize you guys only had the older driver until I got the warning. Plan on downgrading when I have time after I did some reading...