Virtualbox ошибка 0x80070005 - Исправление ошибок и поиск оптимальных решений проблем

Reply with quote

E_ACCESSDENIED (0x80070005)

Greetings! Whenever I try to open Virtualbox on my non-admin account, I get this message:

Code: Select all Expand viewCollapse view: The object is not ready. Result Code: E_ACCESSDENIED (0x80070005) Component: VirtualBoxClientWrap Interface: IVirtualBoxClient {d2937a8e-cb8d-4382-90ba-b7da78a74573}

Any ideas how I can fix this?

Windows 10 Pro N 1803
Latest stable Virtualbox release, installed it literally 20 min ago

Attachments

: 2018-06-17_17-17-25.png (12.19 KiB) Viewed 32131 times

Batman8675: Posts: 1; Joined: 17. Jun 2018, 19:24

Reply with quote

Re: E_ACCESSDENIED (0x80070005)

by socratis » 18. Jun 2018, 19:42

Batman8675 wrote:Whenever I try to open Virtualbox on my non-admin account

Does this mean that if you open VirtualBox with an admin account, it works?

Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the «QUOTE» button, please use the «POST REPLY«, at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.

socratis: Site Moderator; Posts: 27689; Joined: 22. Oct 2010, 11:03; Location: Greece; Primary OS: Mac OS X other; VBox Version: PUEL; Guest OSses: Win(*>98), Linux*, OSX>10.5

Reply with quote

Re: E_ACCESSDENIED (0x80070005)

by mpack » 19. Jun 2018, 10:14

It looks like it has not been installed correctly, i.e. for the current user.

You need to use «Run as administrator» from your normal account to run the VirtualBox installer. This is very different from logging in using an «Admin» account and installing for that user account.

mpack: Site Moderator; Posts: 37957; Joined: 4. Sep 2008, 17:09; Primary OS: MS Windows 10; VBox Version: PUEL; Guest OSses: Mostly XP

Reply with quote

Re: E_ACCESSDENIED (0x80070005)

by Capricorn404 » 17. Jun 2019, 07:11

Hello!
I’ve got the same error mesage on my PCs under user unprivileged account. And I’ve found the reason of this error in incorrect permissions set for COM Object «VirtualBox Application». When I’ve set the default permissions for access and activation, error message has gone.
I think that the virtualbox windows setup application sets incorrect permissions for COM object. Please help me.
Thank you.

Capricorn404: Posts: 1; Joined: 17. Jun 2019, 05:33

Reply with quote

Re: E_ACCESSDENIED (0x80070005)

by mpack » 17. Jun 2019, 10:59

Capricorn404 wrote:I think that the virtualbox windows setup application sets incorrect permissions for COM object. Please help me.

(A) VirtualBox doesn’t have a setup application, the apparant application is just a wrapper for MSI, the standard built-in Windows app installer.
(B) Make sure you run the installer for the intended user account, not while logged in as the «Admin» user. With your normal user account, use «Run as administrator» to request temporary elevation of privileges.

mpack: Site Moderator; Posts: 37957; Joined: 4. Sep 2008, 17:09; Primary OS: MS Windows 10; VBox Version: PUEL; Guest OSses: Mostly XP

Reply with quote

Re: E_ACCESSDENIED (0x80070005)

by Foguete » 11. Apr 2020, 16:08

I know this is old, but I just ran into this, and it had nothing to do with admin/installation. Instead, in my case the problem was that for some reason I had a vbox process running in the background, and when I tried to launch/open vbox I got this same error. I setup my VMs to start up automatically (just a shortcut in my startup folder), so that’s probably why, but this was the first time it happened, and even though my VMs did start up automatically I shut them down, so I would’ve assumed there was no more vbox process running.

In any case, if anyone runs into this too, check your task manager, and manually kill any vbox process. Good luck.

Foguete: Posts: 1; Joined: 11. Apr 2020, 16:04

Reply with quote

Re: E_ACCESSDENIED (0x80070005)

by mpack » 11. Apr 2020, 19:38

It’s a good observation. Especially if someone is in the habit of auto-starting headless VMs and there being no sign that a VM is running — unless you check the tasklist. I guess the error could be more informative than «access denied» though!

mpack: Site Moderator; Posts: 37957; Joined: 4. Sep 2008, 17:09; Primary OS: MS Windows 10; VBox Version: PUEL; Guest OSses: Mostly XP

Reply with quote

Re: E_ACCESSDENIED (0x80070005)

by hemmingway » 13. Aug 2020, 14:10

I had the same problem.
The Virtual Box Manager could not write the *.vbox file.
The disk has no empty space. The *.vbox file size is zero and is corrupt.
Copying the *.vbox-prev file to *.vbox fixed this problem.

Greetings, Bernhard

hemmingway: Posts: 1; Joined: 13. Aug 2020, 14:00

Reply with quote

Re: E_ACCESSDENIED (0x80070005)

by mpack » 13. Aug 2020, 15:16

Unless you get «unable to create COM object» then it is not the same problem. Please create your own topic to discuss your problem.

mpack: Site Moderator; Posts: 37957; Joined: 4. Sep 2008, 17:09; Primary OS: MS Windows 10; VBox Version: PUEL; Guest OSses: Mostly XP

Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: No registered users and 31 guests

Источник

Hi,

hopefully this is the right category for this topic.

I had to replace one of my drives with a bigger one. I configured my Virtual Boxes and lots of FTP and SMB shares on this drive.
After migrating all files with

to the new HDD and adjusting the system shares afterwards, SMB and FTP are working fine.

Just the VirtualBox Plugin ran into an issue:

VirtualBox error: rc=0x80070005 The object functionality is limited (0x80070005)
Fehler #0:
SoapFault exception: [SOAP-ENV:Client] VirtualBox error: rc=0x80070005 The object functionality is limited (0x80070005) in /usr/share/phpvirtualbox/lib/vboxServiceWrappers.php:2614
Stack trace:
#0 /usr/share/phpvirtualbox/lib/vboxServiceWrappers.php(2614): SoapClient->__soapCall('IMachine_getNam...', Array)
#1 /usr/share/phpvirtualbox/lib/vboxServiceWrappers.php(54): IMachine->getName()
#2 /usr/share/openmediavault/engined/rpc/virtualbox.inc(181): VBox_ManagedObject->__get('name')
#3 [internal function]: OMVRpcServiceVirtualBox->getMachines(Array, Array)
#4 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#5 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('getMachines', Array, Array)
#6 /usr/sbin/omv-engined(500): OMVRpc::exec('VirtualBox', 'getMachines', Array, Array, 1)
#7 {main}

Alles anzeigen

So, like I read in some other topics here, I uninstalled the plugin, removed the share, rebooted, reinstalled the plugin, recreated the share and copied the VBox data back.
Afterwards I adjusted the ACL for the files (because the error was still existent):

root@omv:/media/sonstiges/virtualbox# ls -la
insgesamt 2076
drwxrwsr-x+  3 vbox vboxusers    4096 Mär  1 10:06 .
drwxr-sr-x  17 root users        4096 Mär  1 10:04 ..
drwxrwsr-x+  4 vbox vboxusers    4096 Mär  1 10:06 MySQL
-rwxrwxr-x   1 vbox vboxusers    7791 Feb 18 22:02 mysql.vbox
-rwxrwxr-x   1 vbox vboxusers    7791 Feb 18 22:02 mysql.vbox-prev
-rwxrwxr-x   1 vbox vboxusers 2097152 Feb 18 22:02 mysql.vdi

But the error still keeps showing up. Also if I remove all VBox data so no VBox is existent.

Has anyone an idea about this?

Thanks in advance.

- #2
No idea on how to fix this error?
Offizieller Beitrag
- #3
The error you are getting is an access denied error. You shouldn’t have ACLs on the files. Run setfacl -b on all of the files and folders. The .vbox files should have 600 permissions and all folders should have 700 permissions. Everything should be owned by vbox:vboxusers.

Thanks for your answer, my listing above shows, that everything is owned by vbox:vboxusers and that the rights are 775 (I think), so it should work anyway?

After running your command nothing changed:

root@hpn:/media/sonstiges# setfacl -bR virtualbox
root@hpn:/media/sonstiges# ls -la virtualbox
insgesamt 2076
drwxrwsr-x  3 vbox vboxusers    4096 Mär  1 10:06 .
drwxr-sr-x 17 root users        4096 Mär  1 10:04 ..
drwxrwsr-x  4 vbox vboxusers    4096 Mär  1 10:06 MySQL
-rwxrwxr-x  1 vbox vboxusers    7791 Feb 18 22:02 mysql.vbox
-rwxrwxr-x  1 vbox vboxusers    7791 Feb 18 22:02 mysql.vbox-prev
-rwxrwxr-x  1 vbox vboxusers 2097152 Feb 18 22:02 mysql.vdi

Offizieller Beitrag
- #5
While 700 does not equal 775, I don’t think virtualbox cares if it is world-readable (some things do).

What is the output of: ps aux | grep virt
- #6
Sorry for my late response:
root@hpn:~# ps aux | grep virt root 5371 0.0 0.0 9904 892 pts/0 S+ 00:14 0:00 grep virt
But maybe I should mention, that I deactived the plugin atm.

Shall I change ACL to 700? I only kept the ones from cp -a and changed root with vbox, because the owner was changed from vbox:vboxusers to root:vboxuser during cp -a
Offizieller Beitrag
- #7
The output of ps doesn’t do any good if it isn’t running. I was wondering if one of the virtualbox services was running as the wrong user.

700 is a permission not and ACL.

I would purge the virtualbox package and plugin, delete the vbox user, and delete the virtualbox files in /etc/default/. Then I would reinstall the plugin and change the ownership of all of your VM files to the new vbox user that the plugin creates.
- #8
Ok after starting the service it shows:
root@hpn:/# ps aux | grep virt vbox 8646 0.0 0.0 104780 5688 ? S 00:32 0:00 /usr/lib/virtualbox/VBoxXPCOMIPCD vbox 8651 0.2 0.1 193956 8680 ? Sl 00:32 0:00 /usr/lib/virtualbox/VBoxSVC --auto-shutdown 999 8740 0.0 0.0 138568 4244 ? S 00:32 0:00 php-fpm: pool openmediavault-virtualbox 999 8741 0.0 0.0 138568 4244 ? S 00:32 0:00 php-fpm: pool openmediavault-virtualbox vbox 8809 0.2 0.0 210532 7004 ? Sl 00:32 0:00 /usr/lib/virtualbox/vboxwebsrv --background -H 127.0.0.1 root 8963 0.0 0.0 9904 896 pts/0 S+ 00:33 0:00 grep virt
now I’ll try the other things you wrote.
Offizieller Beitrag
- #9
I don’t see any difference between your ps output and mine. Hopefully, the other things work.
- #10
So I removed the plugin via WebGui (or was there anything else by «purge»?) and rebooted because the user was still in use (even if I deactivated the plugin before uninstalling it).
Then:
root@hpn:~# deluser --remove-home vbox Suche Dateien zum Sichern/Löschen ... »/var/lib/vbox« wurde nicht gesichert/gelöscht, da es mit ^/var/.* übereinstimmt. Entferne Benutzer »vbox« ... Warnung: Die Gruppe »vboxusers« hat keine Mitglieder mehr. Fertig.
And:
root@hpn:~# delgroup vboxusers Entferne Gruppe »vboxusers« ... Fertig.
Afterwards:
root@hpn:~# cd /etc/default root@hpn:/etc/default# dir | grep virt console-setup loadcpufreq openmediavault-virtualbox tftpd-hpa
And:
root@hpn:/etc/default# rm openmediavault-virtualbox
Then I reinstalled the plugin and cat /etc/passwd | cut -d: -f1 told me, that vbox was created again.

So I used chown -R vbox:vboxusers /media/sonstiges/virtualbox and chmod -r 700 /media/sonstiges/virtualbox, configured and started the plugin, and received the same error again, when I change to “Virtual Machine” Tab.
Offizieller Beitrag
- #11
Uninstalling from the web interface does remove but doesn’t purge the plugin.

apt-get purge virtualbox phpvirtualbox openmediavault-virtualbox
apt-get autoremove

I would try it. If it doesn’t work, I would use this script to upgrade to virtualbox 5.0 (if you didn’t already).
- #12
With v5 the error is another one.
First I was not able to log in to WebGui any more (wrong user or password)
What I’ve done:
1) deactivate the plugin
2) run apt-get purge virtualbox phpvirtualbox openmediavault-virtualbox
3) apt-get autoremove
4) reboot
5) delete the user and group: deluser --remove-home vbox delgroup vboxusers
6) download and run the script for vbox 5 sh <path_to_script>/vb5_install.sh
7) reboot

During install I received the warning (for guest additions I think?)
WARNING: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (3.2.0-4-amd64) or it failed to load. Please recompile the kernel module and install it by sudo /sbin/vboxconfig You will not be able to start VMs until this problem is fixed.
After another reboot I was able to log in again.

Then I chown and chmoded the rights again to 700 for vbox:vboxusers but the error remains:
Could not connect to host (http://127.0.0.1:18083/) Fehler #64: exception 'Exception' with message 'Could not connect to host (http://127.0.0.1:18083/)' in /usr/share/phpvirtualbox/endpoints/lib/vboxconnector.php:220 Stack trace: #0 /usr/share/openmediavault/engined/rpc/virtualbox.inc(176): vboxconnector->connect() #1 [internal function]: OMVRpcServiceVirtualBox->getMachines(Array, Array) #2 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array) #3 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('getMachines', Array, Array) #4 /usr/sbin/omv-engined(500): OMVRpc::exec('VirtualBox', 'getMachines', Array, Array, 1) #5 {main}
Offizieller Beitrag
- #13
Did you recompile the vboxdrv? If the fix modules button is still in the virtualbox plugin, use it. Otherwise, try invoke-rc.d vboxdrv setup

Can’t connect is a different issue. Looks like your vboxwebsrv is not running because it can’t load the module.

Ok I tried the «fix module…» button but it failed:

Install build-essential.
Reading package lists...
Building dependency tree...
Reading state information...
build-essential is already the newest version.
build-essential set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Recompile VirtualBox module.
Stopping VirtualBox kernel modules ...done.
Recompiling VirtualBox kernel modules ...failed!
  (Look at /var/log/vbox-install.log to find out what went wrong)
Load VirtualBox module.
Starting VirtualBox kernel modules ...failed!
  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)
Restart vboxweb-service
Starting VirtualBox web service ...fail!

Alles anzeigen

So I assumed I needed backports kernel, installed it from OMV-Extras Plugin and rebooted to set it active.
Then tried «fix module..» again and it succeeded:

Install build-essential.
Reading package lists...
Building dependency tree...
Reading state information...
build-essential is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 12 not upgraded.
Recompile VirtualBox module.
Stopping VirtualBox kernel modules ...done.
Recompiling VirtualBox kernel modules ...done.
Starting VirtualBox kernel modules ...done.
Load VirtualBox module.
Starting VirtualBox kernel modules ...done.
Restart vboxweb-service
Starting VirtualBox web service ...done.

Alles anzeigen

Just to make sure I rebooted again.
And oh wonder the old error 0x80070005 is back

VirtualBox error: rc=0x80070005 The object functionality is limited (0x80070005)
Fehler #0:
SoapFault exception: [SOAP-ENV:Client] VirtualBox error: rc=0x80070005 The object functionality is limited (0x80070005) in /usr/share/phpvirtualbox/endpoints/lib/vboxServiceWrappers.php:2728
Stack trace:
#0 /usr/share/phpvirtualbox/endpoints/lib/vboxServiceWrappers.php(2728): SoapClient->__soapCall('IMachine_getNam...', Array)
#1 /usr/share/phpvirtualbox/endpoints/lib/vboxServiceWrappers.php(54): IMachine->getName()
#2 /usr/share/openmediavault/engined/rpc/virtualbox.inc(181): VBox_ManagedObject->__get('name')
#3 [internal function]: OMVRpcServiceVirtualBox->getMachines(Array, Array)
#4 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#5 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('getMachines', Array, Array)
#6 /usr/sbin/omv-engined(500): OMVRpc::exec('VirtualBox', 'getMachines', Array, Array, 1)
#7 {main}

Alles anzeigen

ps aux remains the same

root@hpn:~# ps aux | grep virt
999       3156  0.0  0.0 138576  6356 ?        S    09:19   0:00 php-fpm: pool openmediavault-virtualbox
999       3157  0.0  0.0 138576  6356 ?        S    09:19   0:00 php-fpm: pool openmediavault-virtualbox
vbox      3408  0.0  0.1 148064 15240 ?        Sl   09:19   0:00 /usr/lib/virtualbox/vboxwebsrv --background -H 127.0.0.1
vbox      3412  0.0  0.1 104832  9472 ?        S    09:19   0:00 /usr/lib/virtualbox/VBoxXPCOMIPCD
vbox      3420  0.0  0.1 199688 15296 ?        Sl   09:19   0:00 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
root      6707  0.0  0.0   9916  1860 pts/0    S+   09:24   0:00 grep virt

BTW: Am I going to have some issues/considerations upgrading OMV if I use another than the official kernel?

Offizieller Beitrag
- #15
You shouldn’t need the backports kernel but it does work for me. Did you look at /var/log/vbox-install.log?

Virtualbox has to compile its drivers for most kernels. So, it should work with other kernels but I haven’t tried.

I still have no idea why you are getting this error.
- #16
Ok, so sadly it seems that I have to reinstall omv or at least the vm (didn’t remember the test on that)
I had the same issues before with the MySql plugin, so I decided to run it inside a VM, but this now has problems, too. Wonder if I’ll get a stable environment someday :-).
Anyway thanks a lot for your help.
- #17
Hi ryecoaaron,

just to complete this topic, I wanted to try it again with another new share and vm, so I uninstalled vbox again, switched back to the normal kernel and installed vbox 5 again as described above. All went well even the driver package.

But after restarting OMV and loading VirtualBox, it tells me «Some error has occured» and soon afterwards «0x80070005» is back. So I think I have to do a clean install of OMV. Maybe with the release of V3.

Regards.
Offizieller Beitrag
- #18
I would love for you to try a clean install (even on a different system or VM) to see if you can get it working with everything else eliminated.

Источник

Original issue reported on code.google.com by kvantar...@gmail.com on 26 Nov 2012 at 7:20

I hit this issue too, I had restarted the host after upgrading. I manually 
killed the vboxwebsrv process and started it again via the console - then it 
works. Not sure why, but my error output was the exact same as the one above.

Original comment by spm...@foxwd.com on 5 Dec 2012 at 4:39

As a follow up, not sure if this matters, but I seem to only hit this when the 
host comes up and the virtualbox directory is not present. I keep my virtualbox 
directory on a separate encrypted drive, which is manually mounted after boot - 
this never was a problem before, it used to just complain about the VM's being 
"inaccessible", then after clicking on each one they came up. Now I get this 
error, the only way to resolve it is to bounce the vboxweb-service.

Original comment by spm...@foxwd.com on 5 Dec 2012 at 4:46

I dont know if this helps but I looking at the vboxwebsrv log and got 
'E_ACCESSDENIED' error everytime I got this issue: The following is an extract 
of the log:

00:03:40.031675 SQW03    Processing connection from IP=127.0.0.1 socket=15 (1 
out of 6 threads idle)
00:03:40.257511 SQPmp    Request 100 on socket 16 queued for processing (1 
items on Q)
00:03:40.257568 SQW02    Processing connection from IP=127.0.0.1 socket=16 (4 
out of 6 threads idle)
00:03:40.259481 SQPmp    Request 101 on socket 10 queued for processing (1 
items on Q)
00:03:40.259522 SQW01    Processing connection from IP=127.0.0.1 socket=10 (3 
out of 6 threads idle)
00:03:40.300970 SQPmp    Request 102 on socket 11 queued for processing (1 
items on Q)
00:03:40.301029 SQW03    Processing connection from IP=127.0.0.1 socket=11 (4 
out of 6 threads idle)
00:03:40.305885 SQW03    API return code:            0x80070005 (E_ACCESSDENIED)
00:03:40.305915 SQW03    COM error info result code: 0x80070005
00:03:40.305924 SQW03    COM error info text:        The object functionality 
is limited
00:03:40.306749 SQPmp    Request 103 on socket 10 queued for processing (1 
items on Q)

Original comment by bigblack...@me.com on 13 Dec 2012 at 1:50

Same issue, if start it from console, it works fine. If by service, always get 
this error.

Original comment by gupeim...@gmail.com on 23 Dec 2012 at 2:06

Same problem here, on every system restart I have the same issue

Original comment by emi...@gmail.com on 9 Jan 2013 at 12:54

My system is: Linux acerX3900 3.2.0-35-generic

And vbox: 
vbox@acerX3900:~$ vboxmanage -v
4.2.6r82870

and phpvbox: 4.2

Original comment by emi...@gmail.com on 9 Jan 2013 at 12:58

Original comment by jvar...@alkaidconsulting.com on 5 Feb 2013 at 3:34

Original comment by amado...@gmail.com on 14 Feb 2013 at 6:31

Same issue on System A (32-bit), not on System B (64-bit).

System A: 
# VBoxManage --version
4.2.6r82870
# uname -a
Linux A 3.2.0-29-generic-pae #46-Ubuntu SMP Fri Jul 27 17:25:43 UTC 2012 i686 
i686 i386 GNU/Linux

System B
# VBoxManage --version
4.2.6r82870
# uname -a
Linux B 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 
x86_64 x86_64 GNU/Linux

Original comment by jer...@vikingco.com on 19 Feb 2013 at 7:46

I got the same issue with Virtualbox 4.2.6_OSE compiled from ports on FreeBSD 
9.1.

Running vboxwebsrv from terminal shows the same errors as described by message 
#3.

Original comment by Lars.Vel...@gmail.com on 22 Feb 2013 at 3:03

Same issue.

phpvirtualbox: 4.2-5

# vboxmanage -version
4.2.6r82870

# uname -a
Linux ************** 2.6.18-308.16.1.el5 #1 SMP Tue Oct 2 22:01:43 EDT 2012 
x86_64 x86_64 x86_64 GNU/Linux

# cat /etc/redhat-release 
CentOS release 5.8 (Final)

Original comment by m.t.t.k.1AE@gmail.com on 25 Feb 2013 at 8:23

Same issue.

# /usr/local/bin/VBoxManage --version
4.2.6_OSEr82870

# uname -a
FreeBSD *** 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec  4 09:23:10 UTC 
2012   GENERIC  amd64

Original comment by JohnnyGe...@gmail.com on 16 Mar 2013 at 2:29

same issue

# uname -a
Linux ++++ 3.5.0-26-generic #42-Ubuntu SMP Fri Mar 8 23:18:20 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux
# vboxmanage --version
4.2.10r84104



I have another box and this is working ok!  ==> 
# vboxmanage --version
4.2.10r84104
$ uname -a
Linux +++ 3.5.0-26-generic #42-Ubuntu SMP Fri Mar 8 23:18:20 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux

Original comment by emiliano...@gmail.com on 4 Apr 2013 at 1:53

Hello,

My configuration is:

 - CPU AMD Athlon(tm) II X2 250
 - Memory 8 Gb

 - Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-29-generic x86_64)
 - VirtualBox 4.2.10(84104)
 - phpvirtualbox 4.2.4


In the beginning everything worked out fine but then something went wrong

    Same issue -> The object functionality is limited (0x80070005)


Then with the command -> vboxmanage list systemproperties 

    in the list, the row -> Default machine folder:

        i found the value -> /root/VirtualBox VMs


WHY??? The installer user is "myuser" so i changed the value with the command

    VBoxManage setproperty machinefolder /home/myuser


and after reboot there is no error message :-)


Now, after seven days, it is still working!

Bye

Original comment by armandov...@gmail.com on 4 Apr 2013 at 4:20

Thanks. Your suggestion helps vor me!

Original comment by bernhard...@gmail.com on 7 Apr 2013 at 11:54

I still have this issue on one of my machines after an upgrade. I can create 
new machines, stop and start machines etc... but cannot view the host machine 
details.

I will try wiping all configurations and starting over but am very confused. I 
did not have this problem upgrading the other server so am wondering whether 
there may be another cause.

Original comment by scmurc...@gmail.com on 7 Apr 2013 at 7:31

Hello,

I also got exactly this error.
It was also wrong setting of  Default machine folder:
VBoxManage list systemproperties
Then I fixed it with:
VBoxManage setproperty machinefolder /home/VM

And it did not fixed the problem.
Then after some more investigation I found in log file:
08:20:00.593286 nspr-4   ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) 
aIID={22781af3-1c96-4126-9edf-67a020e0e858} aComponent={SessionMachine} 
aText={No storage device attached to device slot 0 on port 15 of controller 
'SCSI Controller'}, preserve=false

So decided to investigate VBox side, and after frying to get info about IID:
 VBoxManage showvminfo {0e6a45b7-da15-4b82-a9b5-76327576672d}
Name:            <inaccessible!>
UUID:            0e6a45b7-da15-4b82-a9b5-76327576672d
Config file:     /home/VM/test5k/test5k.vbox
Access error details:
VBoxManage: error: Runtime error opening '/home/VM/test5k/test5k.vbox' for 
reading: -102 (File not found.).
VBoxManage: error: 
/home/vbox/vbox-4.2.12/src/VBox/Main/src-server/MachineImpl.cpp[725] (nsresult 
Machine::registeredInit())
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component 
Machine, interface IMachine

This showed up, that I have some problem in configuration with olde deleted VM:
 VBoxManage list vms
"<inaccessible>" {0e6a45b7-da15-4b82-a9b5-76327576672d}
.....

Thats it!

just run 
 VBoxManage unregistervm {0e6a45b7-da15-4b82-a9b5-76327576672d}
and problem was fixed!


Happy using!

Original comment by aru...@spmetas.lt on 13 Apr 2013 at 3:33

I had the exact same problem. Deleting old VMs was the solution for me as well. 
Thank you so much!

Original comment by audun.bj...@gmail.com on 13 Apr 2013 at 7:13

This issue occured after killing vbox processes which caused one of the .vbox 
config files to be empty. Simply copying the vbox-prev to to .vbox fixed the 
issue.

Original comment by bendi...@gmail.com on 13 May 2013 at 12:47

Unfortunately, after .vbox restoration, pb still the same...

Original comment by form....@gmail.com on 21 Jun 2013 at 12:33

Please open a new issue if any of you are still having this problem

Original comment by imooreya...@gmail.com on 12 Jul 2013 at 4:51

Changed state: WontFix

Original comment by broadsco...@gmail.com on 24 Sep 2013 at 10:06

OK i've resolved with this method:

1) Stop all Vbox service 

sudo /etc/init.d/vboxweb-service stop
sudo /etc/init.d/vboxdrv stop
sudo /etc/init.d/vboxdrv vboxballoonctrl-service stop
sudo /etc/init.d/vboxdrv vboxautostart-service stop

2) Go to /home/virtbox/.VirtualBox#+
Then backup your Virtualbox.xml with the command 
cp Virtualbox.xml VirtualBox.xml.bk
Then
nano Virtualbox.xml

So, in my case i've found 2 "Wrong/Fake/Not Exist" VMS and i've found a lot of 
wrong paths. 
I've deleted all of that erros then i restart the services (first the sudo 
/etc/init.d/vboxdrv stop)

Now all work fine :)

Give me a Feedback or confirmation!

Original comment by i...@bdevil.it on 23 Dec 2013 at 5:02

It works ...

1) Stop all Vbox services
sudo /etc/init.d/vboxweb-service stop
sudo /etc/init.d/vboxdrv stop

2) Check the configuration stored in VirtualBox.xml and repair

3) Start all Vbox services
sudo /etc/init.d/vboxdrv start
sudo /etc/init.d/vboxweb-service start

Original comment by quadrat....@gmail.com on 7 Aug 2014 at 5:00

Источник

Original issue reported on code.google.com by kvantar...@gmail.com on 26 Nov 2012 at 7:20

I hit this issue too, I had restarted the host after upgrading. I manually 
killed the vboxwebsrv process and started it again via the console - then it 
works. Not sure why, but my error output was the exact same as the one above.

Original comment by spm...@foxwd.com on 5 Dec 2012 at 4:39

As a follow up, not sure if this matters, but I seem to only hit this when the 
host comes up and the virtualbox directory is not present. I keep my virtualbox 
directory on a separate encrypted drive, which is manually mounted after boot - 
this never was a problem before, it used to just complain about the VM's being 
"inaccessible", then after clicking on each one they came up. Now I get this 
error, the only way to resolve it is to bounce the vboxweb-service.

Original comment by spm...@foxwd.com on 5 Dec 2012 at 4:46

I dont know if this helps but I looking at the vboxwebsrv log and got 
'E_ACCESSDENIED' error everytime I got this issue: The following is an extract 
of the log:

00:03:40.031675 SQW03    Processing connection from IP=127.0.0.1 socket=15 (1 
out of 6 threads idle)
00:03:40.257511 SQPmp    Request 100 on socket 16 queued for processing (1 
items on Q)
00:03:40.257568 SQW02    Processing connection from IP=127.0.0.1 socket=16 (4 
out of 6 threads idle)
00:03:40.259481 SQPmp    Request 101 on socket 10 queued for processing (1 
items on Q)
00:03:40.259522 SQW01    Processing connection from IP=127.0.0.1 socket=10 (3 
out of 6 threads idle)
00:03:40.300970 SQPmp    Request 102 on socket 11 queued for processing (1 
items on Q)
00:03:40.301029 SQW03    Processing connection from IP=127.0.0.1 socket=11 (4 
out of 6 threads idle)
00:03:40.305885 SQW03    API return code:            0x80070005 (E_ACCESSDENIED)
00:03:40.305915 SQW03    COM error info result code: 0x80070005
00:03:40.305924 SQW03    COM error info text:        The object functionality 
is limited
00:03:40.306749 SQPmp    Request 103 on socket 10 queued for processing (1 
items on Q)

Original comment by bigblack...@me.com on 13 Dec 2012 at 1:50

Same issue, if start it from console, it works fine. If by service, always get 
this error.

Original comment by gupeim...@gmail.com on 23 Dec 2012 at 2:06

Same problem here, on every system restart I have the same issue

Original comment by emi...@gmail.com on 9 Jan 2013 at 12:54

My system is: Linux acerX3900 3.2.0-35-generic

And vbox: 
vbox@acerX3900:~$ vboxmanage -v
4.2.6r82870

and phpvbox: 4.2

Original comment by emi...@gmail.com on 9 Jan 2013 at 12:58

Original comment by jvar...@alkaidconsulting.com on 5 Feb 2013 at 3:34

Original comment by amado...@gmail.com on 14 Feb 2013 at 6:31

Same issue on System A (32-bit), not on System B (64-bit).

System A: 
# VBoxManage --version
4.2.6r82870
# uname -a
Linux A 3.2.0-29-generic-pae #46-Ubuntu SMP Fri Jul 27 17:25:43 UTC 2012 i686 
i686 i386 GNU/Linux

System B
# VBoxManage --version
4.2.6r82870
# uname -a
Linux B 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 
x86_64 x86_64 GNU/Linux

Original comment by jer...@vikingco.com on 19 Feb 2013 at 7:46

I got the same issue with Virtualbox 4.2.6_OSE compiled from ports on FreeBSD 
9.1.

Running vboxwebsrv from terminal shows the same errors as described by message 
#3.

Original comment by Lars.Vel...@gmail.com on 22 Feb 2013 at 3:03

Same issue.

phpvirtualbox: 4.2-5

# vboxmanage -version
4.2.6r82870

# uname -a
Linux ************** 2.6.18-308.16.1.el5 #1 SMP Tue Oct 2 22:01:43 EDT 2012 
x86_64 x86_64 x86_64 GNU/Linux

# cat /etc/redhat-release 
CentOS release 5.8 (Final)

Original comment by m.t.t.k.1AE@gmail.com on 25 Feb 2013 at 8:23

Same issue.

# /usr/local/bin/VBoxManage --version
4.2.6_OSEr82870

# uname -a
FreeBSD *** 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec  4 09:23:10 UTC 
2012   GENERIC  amd64

Original comment by JohnnyGe...@gmail.com on 16 Mar 2013 at 2:29

same issue

# uname -a
Linux ++++ 3.5.0-26-generic #42-Ubuntu SMP Fri Mar 8 23:18:20 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux
# vboxmanage --version
4.2.10r84104



I have another box and this is working ok!  ==> 
# vboxmanage --version
4.2.10r84104
$ uname -a
Linux +++ 3.5.0-26-generic #42-Ubuntu SMP Fri Mar 8 23:18:20 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux

Original comment by emiliano...@gmail.com on 4 Apr 2013 at 1:53

Hello,

My configuration is:

 - CPU AMD Athlon(tm) II X2 250
 - Memory 8 Gb

 - Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-29-generic x86_64)
 - VirtualBox 4.2.10(84104)
 - phpvirtualbox 4.2.4


In the beginning everything worked out fine but then something went wrong

    Same issue -> The object functionality is limited (0x80070005)


Then with the command -> vboxmanage list systemproperties 

    in the list, the row -> Default machine folder:

        i found the value -> /root/VirtualBox VMs


WHY??? The installer user is "myuser" so i changed the value with the command

    VBoxManage setproperty machinefolder /home/myuser


and after reboot there is no error message :-)


Now, after seven days, it is still working!

Bye

Original comment by armandov...@gmail.com on 4 Apr 2013 at 4:20

Thanks. Your suggestion helps vor me!

Original comment by bernhard...@gmail.com on 7 Apr 2013 at 11:54

I still have this issue on one of my machines after an upgrade. I can create 
new machines, stop and start machines etc... but cannot view the host machine 
details.

I will try wiping all configurations and starting over but am very confused. I 
did not have this problem upgrading the other server so am wondering whether 
there may be another cause.

Original comment by scmurc...@gmail.com on 7 Apr 2013 at 7:31

Hello,

I also got exactly this error.
It was also wrong setting of  Default machine folder:
VBoxManage list systemproperties
Then I fixed it with:
VBoxManage setproperty machinefolder /home/VM

And it did not fixed the problem.
Then after some more investigation I found in log file:
08:20:00.593286 nspr-4   ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) 
aIID={22781af3-1c96-4126-9edf-67a020e0e858} aComponent={SessionMachine} 
aText={No storage device attached to device slot 0 on port 15 of controller 
'SCSI Controller'}, preserve=false

So decided to investigate VBox side, and after frying to get info about IID:
 VBoxManage showvminfo {0e6a45b7-da15-4b82-a9b5-76327576672d}
Name:            <inaccessible!>
UUID:            0e6a45b7-da15-4b82-a9b5-76327576672d
Config file:     /home/VM/test5k/test5k.vbox
Access error details:
VBoxManage: error: Runtime error opening '/home/VM/test5k/test5k.vbox' for 
reading: -102 (File not found.).
VBoxManage: error: 
/home/vbox/vbox-4.2.12/src/VBox/Main/src-server/MachineImpl.cpp[725] (nsresult 
Machine::registeredInit())
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component 
Machine, interface IMachine

This showed up, that I have some problem in configuration with olde deleted VM:
 VBoxManage list vms
"<inaccessible>" {0e6a45b7-da15-4b82-a9b5-76327576672d}
.....

Thats it!

just run 
 VBoxManage unregistervm {0e6a45b7-da15-4b82-a9b5-76327576672d}
and problem was fixed!


Happy using!

Original comment by aru...@spmetas.lt on 13 Apr 2013 at 3:33

I had the exact same problem. Deleting old VMs was the solution for me as well. 
Thank you so much!

Original comment by audun.bj...@gmail.com on 13 Apr 2013 at 7:13

This issue occured after killing vbox processes which caused one of the .vbox 
config files to be empty. Simply copying the vbox-prev to to .vbox fixed the 
issue.

Original comment by bendi...@gmail.com on 13 May 2013 at 12:47

Unfortunately, after .vbox restoration, pb still the same...

Original comment by form....@gmail.com on 21 Jun 2013 at 12:33

Please open a new issue if any of you are still having this problem

Original comment by imooreya...@gmail.com on 12 Jul 2013 at 4:51

Changed state: WontFix

Original comment by broadsco...@gmail.com on 24 Sep 2013 at 10:06

OK i've resolved with this method:

1) Stop all Vbox service 

sudo /etc/init.d/vboxweb-service stop
sudo /etc/init.d/vboxdrv stop
sudo /etc/init.d/vboxdrv vboxballoonctrl-service stop
sudo /etc/init.d/vboxdrv vboxautostart-service stop

2) Go to /home/virtbox/.VirtualBox#+
Then backup your Virtualbox.xml with the command 
cp Virtualbox.xml VirtualBox.xml.bk
Then
nano Virtualbox.xml

So, in my case i've found 2 "Wrong/Fake/Not Exist" VMS and i've found a lot of 
wrong paths. 
I've deleted all of that erros then i restart the services (first the sudo 
/etc/init.d/vboxdrv stop)

Now all work fine :)

Give me a Feedback or confirmation!

Original comment by i...@bdevil.it on 23 Dec 2013 at 5:02

It works ...

1) Stop all Vbox services
sudo /etc/init.d/vboxweb-service stop
sudo /etc/init.d/vboxdrv stop

2) Check the configuration stored in VirtualBox.xml and repair

3) Start all Vbox services
sudo /etc/init.d/vboxdrv start
sudo /etc/init.d/vboxweb-service start

Original comment by quadrat....@gmail.com on 7 Aug 2014 at 5:00

Источник

Comments

spowelljr

changed the title
minikube start command failing — VirtualBox

VBoxManage: error: Code E_ACCESSDENIED (0x80070005) — Access denied

Oct 26, 2021

nbusseneau

added a commit
to nbusseneau/minikube
that referenced
this issue

Oct 28, 2021

We change the default `--host-only-cidr` to `192.168.59.1/24` in order
to be compatible with the new default host-only networking restrictions
implemented in VirtualBox 6.1.28.

This fixes acces denied errors on `minikube start` when using VirtualBox
>= 6.1.28:

```
VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)
VBoxManage: error: Context: "EnableStaticIPConfig(Bstr(pszIp).raw(), Bstr(pszNetmask).raw())" at line 242 of file VBoxManageHostonly.cpp
```

More details:

VirtualBox 6.1.28 introduced new restrictions on host-only networking:
https://www.virtualbox.org/wiki/Changelog-6.1#v28

Manual: https://www.virtualbox.org/manual/ch06.html#network_hostonly

> On Linux, Mac OS X and Solaris Oracle VM VirtualBox will only allow IP
> addresses in 192.68.56.0/21 range to be assigned to host-only
> adapters. For IPv6 only link-local addresses are allowed. If other
> ranges are desired, they can be enabled by creating
> /etc/vbox/networks.conf and specifying allowed ranges there. For
> example, to allow 10.0.0.0/8 and 192.168.0.0/16 IPv4 ranges as well as
> 2001::/64 range put the following lines into /etc/vbox/networks.conf:
>
>      * 10.0.0.0/8 192.168.0.0/16
>      * 2001::/64
>
> Lines starting with the hash # are ignored. Next example allows any
> addresses, effectively disabling range control:
>
>      * 0.0.0.0/0 ::/0

These new restrictions manifest in the form of the following issue on
`minikube start` due to the default `--host-only-cidr` used by the
VirtualBox driver being `192.168.99.1/24`:

```console
~ minikube start --driver=virtualbox
😄  minikube v1.23.2 on Ubuntu 18.04
✨  Using the virtualbox driver based on user configuration
👍  Starting control plane node minikube in cluster minikube
🔥  Creating virtualbox VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
🔥  Deleting "minikube" in virtualbox ...
🤦  StartHost failed, but will try again: creating host: create: creating: Error setting up host only network on machine start: /usr/bin/VBoxManage hostonlyif ipconfig vboxnet0 --ip 192.168.99.1 --netmask 255.255.255.0 failed:
VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)
VBoxManage: error: Context: "EnableStaticIPConfig(Bstr(pszIp).raw(), Bstr(pszNetmask).raw())" at line 242 of file VBoxManageHostonly.cpp

🔥  Creating virtualbox VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
😿  Failed to start virtualbox VM. Running "minikube delete" may fix it: creating host: create: creating: Error setting up host only network on machine start: /usr/bin/VBoxManage hostonlyif ipconfig vboxnet1 --ip 192.168.99.1 --netmask 255.255.255.0 failed:
VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)
VBoxManage: error: Context: "EnableStaticIPConfig(Bstr(pszIp).raw(), Bstr(pszNetmask).raw())" at line 242 of file VBoxManageHostonly.cpp

❌  Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: creating: Error setting up host only network on machine start: /usr/bin/VBoxManage hostonlyif ipconfig vboxnet1 --ip 192.168.99.1 --netmask 255.255.255.0 failed:
VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)
VBoxManage: error: Context: "EnableStaticIPConfig(Bstr(pszIp).raw(), Bstr(pszNetmask).raw())" at line 242 of file VBoxManageHostonly.cpp

╭───────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                           │
│    😿  If the above advice does not help, please let us know:                             │
│    👉  https://github.com/kubernetes/minikube/issues/new/choose                           │
│                                                                                           │
│    Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.    │
│                                                                                           │
╰───────────────────────────────────────────────────────────────────────────────────────────╯
```

When switching to a valid CIDR, `minikube start` works as usual:

```console
~ minikube start --driver=virtualbox --host-only-cidr "192.168.59.1/24"
😄  minikube v1.23.2 on Ubuntu 18.04
✨  Using the virtualbox driver based on user configuration
👍  Starting control plane node minikube in cluster minikube
🔥  Creating virtualbox VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
🐳  Preparing Kubernetes v1.22.2 on Docker 20.10.8 ...
...
```

Related issue: kubernetes#12765

Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>

nbusseneau

added a commit
to nbusseneau/minikube
that referenced
this issue

Oct 28, 2021

We change the default `--host-only-cidr` to `192.168.59.1/24` in order
to be compatible with the new default host-only networking restrictions
implemented in VirtualBox 6.1.28.

This fixes acces denied errors on `minikube start` when using VirtualBox
>= 6.1.28:

```
VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)
VBoxManage: error: Context: "EnableStaticIPConfig(Bstr(pszIp).raw(), Bstr(pszNetmask).raw())" at line 242 of file VBoxManageHostonly.cpp
```

More details:

VirtualBox 6.1.28 introduced new restrictions on host-only networking:
https://www.virtualbox.org/wiki/Changelog-6.1#v28

Manual: https://www.virtualbox.org/manual/ch06.html#network_hostonly

> On Linux, Mac OS X and Solaris Oracle VM VirtualBox will only allow IP
> addresses in 192.68.56.0/21 range to be assigned to host-only
> adapters. For IPv6 only link-local addresses are allowed. If other
> ranges are desired, they can be enabled by creating
> /etc/vbox/networks.conf and specifying allowed ranges there. For
> example, to allow 10.0.0.0/8 and 192.168.0.0/16 IPv4 ranges as well as
> 2001::/64 range put the following lines into /etc/vbox/networks.conf:
>
>      * 10.0.0.0/8 192.168.0.0/16
>      * 2001::/64
>
> Lines starting with the hash # are ignored. Next example allows any
> addresses, effectively disabling range control:
>
>      * 0.0.0.0/0 ::/0

These new restrictions manifest in the form of the following issue on
`minikube start` due to the default `--host-only-cidr` used by the
VirtualBox driver being `192.168.99.1/24`:

```console
~ minikube start --driver=virtualbox
😄  minikube v1.23.2 on Ubuntu 18.04
✨  Using the virtualbox driver based on user configuration
👍  Starting control plane node minikube in cluster minikube
🔥  Creating virtualbox VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
🔥  Deleting "minikube" in virtualbox ...
🤦  StartHost failed, but will try again: creating host: create: creating: Error setting up host only network on machine start: /usr/bin/VBoxManage hostonlyif ipconfig vboxnet0 --ip 192.168.99.1 --netmask 255.255.255.0 failed:
VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)
VBoxManage: error: Context: "EnableStaticIPConfig(Bstr(pszIp).raw(), Bstr(pszNetmask).raw())" at line 242 of file VBoxManageHostonly.cpp

🔥  Creating virtualbox VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
😿  Failed to start virtualbox VM. Running "minikube delete" may fix it: creating host: create: creating: Error setting up host only network on machine start: /usr/bin/VBoxManage hostonlyif ipconfig vboxnet1 --ip 192.168.99.1 --netmask 255.255.255.0 failed:
VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)
VBoxManage: error: Context: "EnableStaticIPConfig(Bstr(pszIp).raw(), Bstr(pszNetmask).raw())" at line 242 of file VBoxManageHostonly.cpp

❌  Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: creating: Error setting up host only network on machine start: /usr/bin/VBoxManage hostonlyif ipconfig vboxnet1 --ip 192.168.99.1 --netmask 255.255.255.0 failed:
VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)
VBoxManage: error: Context: "EnableStaticIPConfig(Bstr(pszIp).raw(), Bstr(pszNetmask).raw())" at line 242 of file VBoxManageHostonly.cpp

╭───────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                           │
│    😿  If the above advice does not help, please let us know:                             │
│    👉  https://github.com/kubernetes/minikube/issues/new/choose                           │
│                                                                                           │
│    Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.    │
│                                                                                           │
╰───────────────────────────────────────────────────────────────────────────────────────────╯
```

When switching to a valid CIDR, `minikube start` works as usual:

```console
~ minikube start --driver=virtualbox --host-only-cidr "192.168.59.1/24"
😄  minikube v1.23.2 on Ubuntu 18.04
✨  Using the virtualbox driver based on user configuration
👍  Starting control plane node minikube in cluster minikube
🔥  Creating virtualbox VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
🐳  Preparing Kubernetes v1.22.2 on Docker 20.10.8 ...
    ▪ Generating certificates and keys ...
    ▪ Booting up control plane ...
    ▪ Configuring RBAC rules ...
    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🔎  Verifying Kubernetes components...
🌟  Enabled addons: storage-provisioner, default-storageclass
🏄  Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
```

fixes kubernetes#12765

Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>

This was referenced

Nov 1, 2021

joaopapereira

added a commit
to carvel-dev/kbld
that referenced
this issue

Nov 2, 2021

joaopapereira

added a commit
to carvel-dev/kbld
that referenced
this issue

Nov 2, 2021

cppforlife

pushed a commit
to carvel-dev/kbld
that referenced
this issue

Nov 2, 2021

Источник