virtualbox.org

hack3rcon wrote:If I could find the solution then why I should ask here?

If you can't find the solution yourself, then you should ask. That's what the forum is for.

You should also read, comprehend, and act on the answers you receive, with detailed-enough reports if something is still wrong. My comment was posted to encourage this:

scottgus1 wrote:consider what changes you need to make in your willingness to read what others have posted as response to your questions and comprehension of what they have posted.

Read what was posted between your post here: viewtopic.php?f=7&t=95379&start=15#p463500 and here: viewtopic.php?f=7&t=95379&start=15#p464571

There were 5 posts by 4 people between, with information on what you might have done wrong in troubleshooting your host PC. You blew all that information off and pressed on to a new question. Do you see Socratis' apparent frustration here: viewtopic.php?f=7&t=95379&start=15#p463292 and here: viewtopic.php?f=7&t=95379&start=15#p463295?

This is classic 'help vampire' behavior. You can change.

socratis on [color=#FF0000][u]2019-10-30[/u][/color] wrote:can you try with the latest test builds?

May I add that this has been dragging on for over than a month now...

By the time we're done, VirtualBox 7.1.14 will be available. I think I'm going to leave this one alone and bow out, until the situation changes drastically. Heck, I need to read 50 posts just to refresh my memory...

Is the information that I provided enough?

hack3rcon wrote:Is the information that I provided enough?

I just went back through the thread. The information that you provided was enough for the Linux gurus to tell you what you needed to do. You didn't respond to most of it. In fact, your last post, quoting my entire previous post, completely ignores what I posted about how you can improve in responding to those trying to help you.

socratis wrote:I think I'm going to leave this one alone and bow out

Right behind you!

Problem exist.
I don't know why nobody can tell me how can I sign the modules?

Code: Select all

$ sudo /sbin/vboxconfig
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: modprobe vboxdrv failed. Please use 'dmesg' to find out why.

There were problems setting up VirtualBox.  To re-start the set-up process, run
  /sbin/vboxconfig
as root.  If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.

$ sudo dmesg -k -l err,warn,notice,debug
[12305.873644] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 0000000062ecd0d9, val ffffffffc1c9c40f

$ sudo modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Exec format error

No idea?
Why not tested a product before release!!!

hack3rcon wrote:Why not tested a product before release!!!

The product is being tested right now. You are the tester. What else did you think you were?

You can see all of the information that I posted. They are not enough?

Enough for what? If I had a comment to make on your problems then I would already have posted them. I don't use Linux hosts, am not really interested in Linux, so I'm not qualified to comment. The only reason I'm here is to moderate.

Others far more qualified than I have already commented in this thread.

The information was not enough?

This topic is getting nowhere. Locking it.

virtualbox.org

VirtualBox can't run after update.

Re: VirtualBox can't run after update.

Re: VirtualBox can't run after update.

Re: VirtualBox can't run after update.

Re: VirtualBox can't run after update.

Re: VirtualBox can't run after update.

Re: VirtualBox can't run after update.

Re: VirtualBox can't run after update.

Re: VirtualBox can't run after update.

Re: VirtualBox can't run after update.

Re: VirtualBox can't run after update.

Re: VirtualBox can't run after update.