Results 1 to 5 of 5

Thread: Virtualbox no longer running since NVidia-Update

  1. #1

    Default Virtualbox no longer running since NVidia-Update

    trying to start a running installation of virtualbox I get

    VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: libnvidia-tls.so.270.41.06: cannot open shared object file: No such file or directory

    and it seems that it doesn't work with the new 275 build I got pushed when updating. Updating virtualbox didn't help. Besides uninstalling the 275 version of nvidia and installing the 270, any other way to fix this?

    Peter

  2. #2
    Join Date
    Mar 2010
    Location
    Austin - Texas
    Posts
    10,140
    Blog Entries
    48

    Smile Re: Virtualbox no longer running since NVidia-Update

    peterlipp
    trying to start a running installation of virtualbox I get

    VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: libnvidia-tls.so.270.41.06: cannot open shared object file: No such file or directory

    and it seems that it doesn't work with the new 275 build I got pushed when updating. Updating virtualbox didn't help. Besides uninstalling the 275 version of nvidia and installing the 270, any other way to fix this?

    Peter
    Peter have you tried to reinstall the vbox kernel drivers? If not, open up a terminal session and run the following command:

    Code:
    sudo /etc/init.d/vboxdrv setup
    I started a thread which includes some good info on VirtualBox you can find here:

    What VM do you recommend for openSUSE?

    Thank You,
    My Blog: https://forums.opensuse.org/blogs/jdmcdaniel3/

    Software efficiency halves every 18 months, thus compensating for Moore's Law

    Its James again from Austin, Texas

  3. #3

    Default Re: Virtualbox no longer running since NVidia-Update

    Peter have you tried to reinstall the vbox kernel drivers?
    They have been rebuilt and all, certainly not the issue.
    Thanks

    Peter

  4. #4

    Default Re: Virtualbox no longer running since NVidia-Update

    So,

    Since I needed the beast running I went back to the 270 version and this is working again. Would still love to find out how to fix it the other way round if possible....

    Peter

  5. #5

    Default Re: Virtualbox no longer running since NVidia-Update

    Quote Originally Posted by peterlipp View Post
    So,

    Since I needed the beast running I went back to the 270 version and this is working again. Would still love to find out how to fix it the other way round if possible....

    Peter
    It looks like you should rebuild vboxdrv *after* updating nvidia. I didn't know that either but looking at VirtualBox.so, here's what I get on a nvidia system:

    Code:
    # ldd /usr/lib/virtualbox/VirtualBox.so  | grep nvidia
    libnvidia-tls.so.275.21 => /usr/lib64/tls/libnvidia-tls.so.275.21 (0x00007fd8b2dce000)
    libnvidia-glcore.so.275.21 => /usr/lib64/libnvidia-glcore.so.275.21 (0x00007fd8b0fa6000
    and this library is in package x11-video-nvidiaG02-275.21-7.1.x86_64:

    Code:
    # rpm -qf /usr/lib64/tls/libnvidia-tls.so.275.21
    x11-video-nvidiaG02-275.21-7.1.x86_64
    So if you update the nvidia driver without rebuilding vboxdrv, VirtualBox.so will still look for a library which has been replaced since you updated x11-video-nvidiaG02.

    Btw, I looked at VirtualBox.so with ldd on an ATI based system: it didn't seem to require any ATI specific library. Interesting enough! ...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •