Oracle Vm Virtualbox Extension Pack 39; Is Installed (verr_not_found)

0 views

Skip to first unread message

Message has been deleted

Carey Jangam

unread,

Jul 17, 2024, 9:51:06 PM7/17/24

to diabavemi

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

oracle vm virtualbox extension pack 39; is installed (verr_not_found)

Descargar https://tlniurl.com/2yP5jO

I even remove myself from vboxusers and add it back again, and after that reboot my system. still doesn't work.
as it works with root privilege, I assume it's a permission issue. I can't find out where though.

PS: I actually don't know the exact difference between virtualbox and virtualbox-bin. both packages seem the same to me except some UI differences. I guess maybe virtualbox-bin has been merged to virtualbox?

some more information:
permission of /dev/vboxusb and all it's sub directories has been correctly set to root:vboxusers. does it mean udev has been working as expected?
however as I mentioned in the first post, if I run it with root permission everything works alright. I assume it's still a permission issue.
here's the log from virtualbox:

The problem was that my user wasn't fully part of the vboxusers group. There was an entry in /etc/group, but not in the shadow files. After adding the user using system-config-user the USB devices appeared and the error message dissapeared.

Maybe you should check your /etc/*shadow* files. So, as far as I remember, system-config-users is some kind of GUI interface for user management. Maybe you can find out how to get your username into the shadow files?

yes, I saw that thread, too. the problem is I don't know how to modify this file
what I'm thinking is, if it's just a permission problem of /dev/vboxusb, I can simply resolve it by manually changing the owner and owner group to my current user/group. so I tried but it doesn't work. I think there must be something else that requires permission, too. I don't know what though.

flockyrocky, I have faced with the same problem today and finally at least USB 1.0 is working (have no extention pack for USB 2.0 support).
First - I had some problem with my user assignment to 'vboxusers' group. All seemed to be ok, but I can't make "cd /dev/vboxusb" (permission denied). Don't found true reason, but after reboot all is ok.
Second - I got this error after "export VBOX_USB=usbfs". Without this statement all is working fine for me.

well to the first question I can explain. according to the wiki, after adding yourself to vboxusers group, you should logout or reboot before it works.
and for the 2nd issue, I think I always have this setting from the beginning. if it's the reason, virtualbox must have changed something recently. I'll try it, thanks for your help.

No. I had installed VirtualBox a couple of weeks ago. But there was no need for USB support for me at that time. Yesterday I decided to connect USB device to VirtualBox and read wiki about it. I have added my user to vboxusers group, then assigned VBOX_USB variable. Then I got an error described at start of this topic. I have tried to change rights on /dev/vboxusb from 750 to 770 without success. Then I have rebooted and successfully started VirtualBox without VBOX_USB with USB. Not sure that /dev/vboxusb right have matter, because I assume these files are created automatically by udev and no I see there again 750 on folders and 660 on files.

Basically I have spent the last 3 or 4 hours (maybe more) trying to figure this out on my own - I thought it would be a good idea to report this here as this thread is similar (to say the least) to my case and then keep searching for a solution to this annoyance.

Reboot the host if you have upgraded the linux package (the Linux kernel) earlier today. Always do that. Then USB devices will start working again. Because I bet they don't work on the host either, let alone VirtualBox... So reboot the host and try again.

After physically plugging in the USB device you need to also "plug in" the device in VirtualBox (from Devices), or create a USB filter that "plugs it in" automatically. Make sure that the USB support checkbox from the VM's settings is checked.

I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).

This is odd... Which OS are you running as guest? Because you may need to install the Guest Additions (on the guest OS, obviously, it's why they're called guest additions). And, umm, "Test"? Test as in what? If it's a Windows guest then you probably shouldn't select "Other" as type.

Anyway. USB devices should at least show up in the list ( ). You're saying that they show up on the host, but VirtualBox doesn't see them. Ok... I would probably remove VirtualBox entirely, reboot, reinstall VirtualBox and the extension pack following the wiki, and reboot again - speaking of which, please don't use anything else but 'makepkg -s' to compile the extension pack. If you're going to use the AUR, use it properly. You can install VirtualBox itself from the official repositories (using just pacman). The AUR version ("virtualbox-bin") is compiled by Oracle, kept mainly for comparison against the one in the official repositories.

VirtualBox is a hypervisor used to run operating systems in a special environment, called a virtual machine, on top of the existing operating system. VirtualBox is in constant development and new features are implemented continuously. It comes with a Qt GUI interface, as well as headless and SDL command-line tools for managing and running virtual machines.

In order to integrate functions of the host system to the guests, including shared folders and clipboard, video acceleration and a seamless window integration mode, guest additions are provided for some guest operating systems.

To compile the VirtualBox modules provided by virtualbox-host-dkms, it will also be necessary to install the appropriate headers package(s) for your installed kernel(s) (e.g. linux-lts-headers for linux-lts). [1] When either VirtualBox or the kernel is updated, the kernel modules will be automatically recompiled thanks to the DKMS pacman hook.

virtualbox-host-modules-arch and virtualbox-host-dkms use systemd-modules-load.service to load VirtualBox modules automatically at boot time. For the modules to be loaded after installation, either reboot or load the modules once manually; the list of modules can be found in /usr/lib/modules-load.d/virtualbox-host-modules-arch.conf or /usr/lib/modules-load.d/virtualbox-host-dkms.conf.

It is also recommended to install the virtualbox-guest-iso package on the host running VirtualBox. This package will act as a disc image that can be used to install the guest additions onto guest systems other than Arch Linux. The .iso file will be located at /usr/lib/virtualbox/additions/VBoxGuestAdditions.iso, and may have to be mounted manually inside the virtual machine. Once mounted, you can run the guest additions installer inside the guest. For Arch Linux guest also see VirtualBox/Install Arch Linux as a guest#Install the Guest Additions.

In order to avoid having to install the guest system manually, some operating systems support unattended installation. This allows the user to configure the system to be installed in VirtualBox's interface prior to starting the machine. At the end of the setup process, the operating system is installed without requiring any further user interaction. This feature requires the virtualbox-unattended-templatesAUR package.

The Oracle VM VirtualBox Extension Pack provides additional features and is released under a non-free license only available for personal use. To install it, the virtualbox-ext-oracleAUR package is available, and a prebuilt version can be found in the seblu repository.

If you prefer to use the traditional and manual way: download the extension pack manually and install it via the GUI (File > Tools > Extension Pack Manager) or via VBoxManage extpack install , make sure you have a toolkit like Polkit to grant privileged access to VirtualBox. The installation of extension pack requires root access.

One of the non-free extension pack features is support for the Remote Desktop Protocol (RDP). This part of functionality can also be obtained with the open source VNC Extension Pack, by installing the virtualbox-ext-vnc package.

A security feature in Wayland (i.e. when using GDM) disallows VirtualBox to grab all keyboard input. This is annoying when you want to pass window manager shortcuts to your guest operating system. It can be bypassed by whitelisting VirtualBox:

VirtualBox does not support QEMU's QCOW2 disk image format. To use a QCOW2 disk image with VirtualBox you therefore need to convert it, which you can do with qemu-img. qemu-img can convert QCOW to / from VDI, VMDK, VHDX, RAW and various other formats (which you can see by running qemu-img --help).