-
Notifications
You must be signed in to change notification settings - Fork 241
Virtualbox 6: vboxdrv has been renamed to vboxsup #86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for the explanation, I just had the same error. I stumbled upon vkalenic's fork and compiled it. VirtualBox now works again. You can find it here: |
Any idea if this fix allows version 7 to run? |
I'm using this fork which works fine with VirtualBox 7: https://github.com/zongou/portable-vbox But it would be nice if someone could merge the improvements from all the forks. |
none of these forks are able to let you use the bridged network..only nat...so they are not really full working...since 2015 with the came of windows 10 runar buvik abandoned the project... :( |
Not worried about network, just the latest version of virtualbox 7
…-------- Original message --------
From: p060477 ***@***.***>
Date: 10/19/22 4:10 PM (GMT-05:00)
To: vboxme/Portable-VirtualBox ***@***.***>
Cc: pendragonmikel ***@***.***>, Comment ***@***.***>
Subject: Re: [vboxme/Portable-VirtualBox] Virtualbox 6: vboxdrv has been renamed to vboxsup (Issue #86)
none of these forks are able to let you use the bridged network..only nat...so they are not really full working...since 2015 with the came of windows 10 runar buvik abandoned the project... :(
—
Reply to this email directly, view it on GitHub<#86 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AYMXH5RIEMY4NBUS32R6QNLWEBISJANCNFSM5NNCP66Q>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Awesome! Thanks for the response
…-------- Original message --------
From: d4k0 ***@***.***>
Date: 10/19/22 3:58 PM (GMT-05:00)
To: vboxme/Portable-VirtualBox ***@***.***>
Cc: pendragonmikel ***@***.***>, Comment ***@***.***>
Subject: Re: [vboxme/Portable-VirtualBox] Virtualbox 6: vboxdrv has been renamed to vboxsup (Issue #86)
I'm using this fork which works fine with VirtualBox 7:
https://github.com/zongou/portable-vbox
But it would be nice if someone could merge the improvements from all the forks.
—
Reply to this email directly, view it on GitHub<#86 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AYMXH5VN477E2XOJEO4IYRLWEBHGHANCNFSM5NNCP66Q>.
You are receiving this because you commented.Message ID: ***@***.***>
|
@p060477 https://zotovp.wordpress.com/2017/04/02/portable-virtualbox-network-support-windows-10/ |
thxs so much...no in my case do not work..anyway thxs so much indeed |
virtualbox already have an option to make it semi-portable: the manual says:
so setting that variable solve the problem of portabilizing the machines, now i can format my pc , then put that variable and everything will work as before. a simple command will portabilize virtualbox: say for example that you want to always save your machines to E:\VBOX, then open a command line window (cmd) and run this: if you want virtualbox to be fully portable (in the sense of removing all files and registry entries...etc ), then a simple script to install virtualbox and uninstall it will solve it. now we can install the latest virtualbox and have it working without errors. if you think that those forks work fine with virtualbox v7 then you are wrong they did simple changes and left a lot of things that should be done, for example the drivers and services are not fully cleaned, use for example https://github.com/zongou/portable-vbox fork , compile it, install it, run virtualbox and stop it, see services , you will find a service of virtualbox there (VBoxSDS)... and other errors will happen too of services and drivers not starting..etc. so use the official installer it will work better |
@badrelmers |
This page does not exist anymore... does anyone have a fork of it? |
Unfortunately the Virtualbox-Support gets worse again. Not only has the automatic unpacking stopped working (see existing issues). With release 6.1.32 the virtualbox driver has been renamed from vboxdrv to vboxsup. This results in a "NtCreateFile(\Device\VBoxDrvStub)" error.
The text was updated successfully, but these errors were encountered: