Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Those processes look like they're more for volume management than VMs. Before you started playing with the portable VirtualBox, did you do any experiments with other hypervisors? Maybe one that's built into Windows? You could also try downloading and installing the "normal" VirtualBox to see if it gives the same error, it might be a bug in the portable version.
Those processes look like they're more for volume management than VMs. Before you started playing with the portable VirtualBox, did you do any experiments with other hypervisors? Maybe one that's built into Windows? You could also try downloading and installing the "normal" VirtualBox to see if it gives the same error, it might be a bug in the portable version.
Thank you. I have not tried any other hypervisors (whatever it means . Do you mean inside VirtualBOx settings?
I will give a try with full, non-portable version then. Though I have to admit I am very sceptical about it.
VirtualBox is a hypervisor. Other hypervisors would be VMWare, Xen, KVM, Hyper-V, etc. The error is saying you have another hypervisor already running. Maybe another virtualbox installation, or vmware, or hyper-v...something else is already using the hardware virtualization provided by your processor.
VirtualBox is a hypervisor. Other hypervisors would be VMWare, Xen, KVM, Hyper-V, etc. The error is saying you have another hypervisor already running. Maybe another virtualbox installation, or vmware, or hyper-v...something else is already using the hardware virtualization provided by your processor.
Thank you. You are right. I have installed the non-portable version and it worked. Then I uninstalled it an the portable version (same that caused problem/error) of VirtualBoc has became operational.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
. Do you mean inside VirtualBOx settings?
