virtualbox.org

I am using an iMac with El Capatan version 10.10, I think. And I have the latest version of Vitrtualbox installed. Now everytime I start it up, the bluetooth on my mouse and keyboard disconnect all the time. Now it shouldn't be doing this. Is virtualbox buggy or something? Like I have a bluetooth keyboard and mouse, and the second I start up Virtulbox, my bluetooth disconnects me, and my mouse stops working, and my keyboards disconnects. And I can't click anywhere on my screen or type. And I have to power off my computer all of the time with power button. So what is going on here? Is virtualbox buggy or something? I am running the latest version which is 5.2.10or something like that. So please let me know on how to fix this issue that I am having. And this has never happened to me before when I have been using Virtualbox. Now all of a sudden this is happening. So please let me know on how to fix this issue that I am having. Because I would like to start using this without any issues or problems. And also let me know on how to make sure that my bluetooth doesn't disconnect my computer either. So just let me know on how to fix this. So thank you very much!

jordanlg30 wrote:I am using an iMac with El Capatan version 10.10, I think. And I have the latest version of Vitrtualbox installed.

So, you question is probably Mac OS Host related not Mac OS X Guest, but still...

I have an iMac with High Sierra 10.13.4 also with the latest version of VirtualBox installed.

jordanlg30 wrote:Now everytime I start it up, the bluetooth on my mouse and keyboard disconnect all the time.

Mine doesn't do that and neither does that of the many other iMac users with bluetooth mice and keyboards otherwise they would all be jumping up and down and complaining and as far as I recall your is the first report of this.

jordanlg30 wrote:So please let me know on how to fix this issue that I am having

We are going to need more information from you. Does this happen when you start the VirtualBox application? One particular guest? All guests? If it is one particular guest with the problem we will need to see the VBox.log file from it (zipped of course). Is there a crash log in your host OS? Posting the output from kextstat might also help.

-Andy.

Go in the VM Settings » Ports » USB » USB Device Filters. In there 99% you have a "blank filter", usually named 'New Filter 1' or similar, which if you check its properties, all of the fields are empty. Delete that USB filter.

And Andy is right, this is a "Mac OSX Hosts" issue, not a "Mac OSX Guests" issue. Moving accordingly.


PS. Next time (or any time) that you report an issue, please be accurate:

jordanlg30 wrote:with El Capatan version 10.10, I think ... which is 5.2.10 or something like that

We can't figure out what's going on if you're not as accurate as possible. Don't "think", don't "or something". Make absolutely sure, you're the only one that can be sure, since you are sitting in front of your computer, not us. I don't want to start guessing...

I have a PS Vita game console. And I connect the usb cable to Virtualbox, and it doesn't detect that it is connected. It says failed to connect on the screen. And I also deleted the Usb filter. So virtualbox is not disconnecting my bluetooth. But now my Playstation vita cable won't detect Virtualbox. It said failed to connect to windows 7. So why is this not working for? I also already installed the extension pack for my Virtualbox, but it doesn't seem to do anything for it. Because the usb cable won't connect to the virtualbox. So what is going on here? Can you help me out? Because I need this to connect to my Virtualbox. And I need to fix this problem that I am having. So thank you very much.

If as Socratis surmised, you had a blank USB device filter that would pass all of the USB devices connected to the host onto the guest. Having deleted that, no USB devices are being passed to the guest. You need to make a device filter that is specific to the PS Vita game console so it, and only it, gets passed to the guest.

-Andy.

I already have a new filter added, and it says new filter 1. But this doesn't seem to work for me. I hear the connecting sound and then it disconnects, and it just doesn't work. So please what I am doing wrong? Is Virtualbox buggy or something? I have the Ps Vita listed in the usb devices and also the new filter 1 there. But still no success for me. I also tried different usb ports on my computer, but nothing seems to work for me. So do you have any suggestions to give me? Should I try to get another version of Virtualbox? Or is there a special version that I need to download to make this work? Please help me out here. Because I would really like to get this working. So thank you very much.

jordanlg30 wrote:Is Virtualbox buggy or something?

I think I know what's buggy, and it's not VirtualBox. Please stop calling VirtualBox buggy, unless you have solid evidence. And at the moment you don't have solid evidence. You don't even have a basic understanding on how VirtualBox works. So, do me a favor, don't start throwing characterization around, all right? You're borderline on the "troll" group...

Now... I told you to delete the blank filter, no? Did you? No you didn't, you came back and confirmed it. So, unless you start following instructions, you're not going to go very far, in general.

Read the following thread: USB basics and troubleshooting, all of the posts, three times.

If you still have a problem after reading through the whole thing, please follow the advice of the last post, #8: Asking for help and post the information requested.

Please stick to the advice given, otherwise that advice will stop being given.

I'm sorry to tell you this, but it is still not working. I have tried everything. I added a new usb filter, and nothing works, whatsoever. And I am not trolling, this does NOT work. All of the other virtual machines work connect to the ps vita, and virtualbox does not work at all. Please, I need to know why it is not working for. And you should know more about this than I do. Adding a new usb filter just disconnects my bluetooth from my computer. So forget that part. I have also read the usb basics and troubleshooting, but that doesn't seem to help me out either. So can you please let me know on what is going on here. Because Virtualbox shouldn't be doing this to me. And all of the other virtual machine programs work flawlessly without a problem. So something happens to be wrong with Virtualbox. And it is not my computer doing this to me. So I need to know on how to fix this problem. And I am not going to give up on this, until I get the correct answer from. That's all I have to say. So thanks a lot.

jordanlg30 wrote:hat's all I have to say.

Really? Seriously? How about the information that I asked?

You didn't read the USB basics. Not all of them. Because at number 8, "Asking for help", there are SPECIFIC information requested. VERY SPECIFIC information. How much did you provide?

• ABSOLUTELY NOT A SINGLE ONE.

This is going to be my last post if you don't cooperate and follow the instructions, and the only thing you keep on repeating (like a chicken running around with it's head chopped) is "how to fix", "how to fix", "how to fix", "how to fix", "how to fix", "how to fix", "how to fix", "how to fix", "how to fix", "how to fix", "how to fix"...

Well, the instructions are given. Re-read the whole series of articles. Twice. Follow them. Provide what I asked for. Otherwise this is the end of my contribution, and if you keep on repeating the same tune, the locking of the thread.

I need you to answer me on why this is happening. I added Windows 10 to my virtualbox, and it still doesn't detect my ps vita. Now what is going on here? You need to answer me on this. And stop telling me how to fix over again. That is just rude. Okay? I just don't understand on how to make the vita recognize the virtualbox. I defiantly think that Virtualbox is buggy. This needs to be fixed in the next update or something. When I add a new filter again, the windows 10 machine disconnects and so does the bluetooth. I need to know on why this doesn't work. And I have read all of the usb guides, and nothing works whatsoever. So this is not a good situation. And please don't lock my thread either, because that is disrespectful. And that is not right to do. I just need you to guide me on how to make my Ps vita connect to my virtualbox correctly, so that it connects fine through the usb cable. All righty then. So that is that. So thank you very much.

• You were asked multiple times to provide specific information. You disrespected us and ignored the advice multiple times.
• You were warned to not repeat the same thing over and over again. You disrespected us and ignored the advice multiple times.
• You were told to not call something a bug without evidence. You disrespected us and ignored the advice multiple times.

If your next post does not include the diagnostic information requested multiple times, this thread will be deleted, and you'll get a formal warning. We have been disrespected enough! That's going to be the end of the conversation!

@jordanlg30
Your duplicate post has been deleted. According to the forum rules, duplicate posts are not allowed.

I would stay here, you already have a dedicated post. You just need to read it...

I assume that you have a USB-Bluetooth controller in the host PC. When a VM grabs ownership of that USB device the host must obviously lose control of all Bluetooth devices. It doesn't matter if you use a blank filter or a specific one: either way the VM ends up owning the Bluetooth modem which means it owns all of bluetooth.

To stop it happening the simplest solution is to disable USB2 and USB3 support in the VM settings. If the VM needs access then redirect a virtual serial port, or get it a separate USB bluetooth modem.

And no, it is not a bug in VirtualBox. USB devices are not designed to be shared between two masters.

@jordanlg30
I have deleted yet another duplicate message from you, this time on "OSX Guests". This is the second one, after you have been already warned. There is no excuse.

If you repeat it, I'm going to have to ban you. We cannot be dealing with users that do not want to listen! I hope this message is clear.