virtualbox.org

hi all...There have been lots of discussions about VB on macs, but there are still major issues, but i cant find anywhere that these have been fixed.

We are running VB 4.2.4 r81684
Macbook Pro Retina, 10.8.2, 2.5GHz intel i5

A fresh install of this latest version of VB, and the creation of a fresh W7 guest, with guest add-ons installed, and the latest VB extensions pack version that matches the version of VB we are running. We have done everything 'by the book'

These problems also are exactly the same on 3 previous versions.

The first issue is that external USB drives simply refuse to be picked up by VM windows 7 guests. When you plug in the USB device, (we have tried several types, with different versions of formatting), the device, even though the filter is added in the USB devices, will not appear in the VB guest. If you eject the device form the mac, and try to connect from the toolbar on the bottom of the VB window, you get the error, on the top of the guest window.

Failed to attach the USB device Unknown device to the virtual machine .

Callee RC: NS_ERROR_CALL_FAILED (0x800706BE)

Then the VB control is lost, you see the good old 'inaccessible' black screen in the preview, and the VM will not shut down, or at least the only way to regain control is to quit the VB application and start again. The VM comes up in the inventory as 'aborted'

As i understand this, ive read that a mac os update recently has caused this issue, which is damn annoying, but when will there be a fix from VB???
Or a workaround? The release of the mac update was before the latest version of VB we are running, so why would the fix not be in the latest version we are running??? Can ANYONE help? Thanks in advance.

amazing...a fundamental issue that no-one can fix....

These kinds of problems that are reproducible should be reported to bugtracker. If you have not signed on to Bugtracker before you will need to select a new Nickname to be able to report issues.
It would also help if you can post the ticket number here so other can see the progress, add information, or see the final results.

Perryg wrote:These kinds of problems that are reproducible should be reported to bugtracker. If you have not signed on to Bugtracker before you will need to select a new Nickname to be able to report issues.
It would also help if you can post the ticket number here so other can see the progress, add information, or see the final results.

That was a poor reply, here we are over a year later with the same issue but no bug raised, although I can see others have the issue.

I will try and fill in a bug report

Ah, I can see the issue here. A new ID is needed to log in and start a bug track. Which is why people don't bother .....

YTC1 wrote:

Perryg wrote:These kinds of problems that are reproducible should be reported to bugtracker. If you have not signed on to Bugtracker before you will need to select a new Nickname to be able to report issues.
It would also help if you can post the ticket number here so other can see the progress, add information, or see the final results.

That was a poor reply, here we are over a year later with the same issue but no bug raised, although I can see others have the issue.

I will try and fill in a bug report

Before you criticise you might want to provide code or some other helpful input to fix the issue. It is open source and the DEVs only have so much time to provide a free product to you and others.

You will notice I have started a bug.

I was initially surprised that there was not one listed, especially as the issue has been around for a long time. I have only just switched to using a Mac as it is a more reliable and supported platform than the laptop I have been running Solaris 11 on for the last 4 years, on which VB works excellently.

I do appreciate that the devs give a lot of their time free, I was merely irritated by your short sharp post to the OP that looks to have scared him off.

What else would you have me say. I can not fix the issue and the only ones that can are the DEVs, thus the reply to bugtracker. I guess I could have said sucks to be you but that would have been derogatory and would not solve the issue.

Perryg wrote:What else would you have me say. I can not fix the issue and the only ones that can are the DEVs, thus the reply to bugtracker. I guess I could have said sucks to be you but that would have been derogatory and would not solve the issue.

Helped him/guided him to opening a bug report ?

My angst is that it has been around for a while, there has to be a reason that no one has opened a bug report.
It could be that initially a bug report appears to be a PITA to open. (When in fact it is pretty simple).

All speculation. As you said it was easy and pointed out in the reply "If you have not signed on to Bugtracker before you will need to select a new Nickname to be able to report issues" . All anyone can do is suggest the proper direction, then its up to the person with issue to follow through. My take is you were frustrated and wanted to vent. I can even relate to that but you have to vent in the proper way/place. No one here can help with this issue.

check out topic V4.2.x information inaccessible
in particular post at 14. Dec 2012, 12:43