Main system grabs thumbdrive before Virtualbox can recognize it

[Scorpa54]

I have Virtualbox files from my previous OS, 18.04, that are set up to recognize certain thumbdrives. Now that I have updated Virtualbox doesn't even get a hint that something has been plugged in.
I have stopped the automount feature in Jammy to no avail. I have tried to grab the device in Virtualbox settings but as the main system has already recognized it Virtualbox claims no devices attached. Expletive deleted.

MSI X299 Tomahawk
Intel i7-7800X 6 core
Asus Nvidia GeForce GTX1060 6GB

[Snowhog]

Which Virtualbox? What is available through the repositories, or Oracle Virtualbox?

[claydoh]

You want to check your removable device settings, and try and 'forget' all relevant devices, if not all of them, not just disable it at the top level.



The only other way the system would mount the thumb drive on its own (that I can think of) is if you have told it to, via your /etc/fstab, or some other desktop environment's automounting system, something like that.

[Scorpa54]

Which Virtualbox? What is available through the repositories, or Oracle Virtualbox?

Oracle 6.1.38

[Scorpa54]

You want to check your removable device settings, and try and 'forget' all relevant devices, if not all of them, not just disable it at the top level.



The only other way the system would mount the thumb drive on its own (that I can think of) is if you have told it to, via your /etc/fstab, or some other desktop environment's automounting system, something like that.

That is where I disabled all automount. I haven't told the system anything, I'm just finding these things as I try to do things I have down before the upgrade. I will fully admit I don't have the skill for the deeper nuances of the OS.

[claydoh]

Ok, so what exactly do you mean by the "main system has already recognized it"?
Maybe I was reading to much into it, and thinking that it is being auto-mounted. Which it it would not be doing, if you have removed any devices from that section, and haven't added anything to your /etc/fstab file.
Yes, yous OS will definitely recognize the hardware, but otherwise , without images or other data, to go on, the thumb drives won't get mounted unless you are mounting them yourself.

My guess is that you are going to have to reconfigure the thumbdrives in virtualbox, which has probably just lost track of which drive is which ID or something like that.
I will wager VB has seem more updates and changes than *buntu has since 2016
I am mildly surprised that the virtual machines even try to run, but it has always been pretty good at longer term file format support.

[Snowhog]

Have you installed the VBoxGuestAdditions_6.1.38.iso yet? Do you know how?

[Scorpa54]

Ok, so what exactly do you mean by the "main system has already recognized it"?
Maybe I was reading to much into it, and thinking that it is being auto-mounted. Which it it would not be doing, if you have removed any devices from that section, and haven't added anything to your /etc/fstab file.
Yes, yous OS will definitely recognize the hardware, but otherwise , without images or other data, to go on, the thumb drives won't get mounted unless you are mounting them yourself.

My guess is that you are going to have to reconfigure the thumbdrives in virtualbox, which has probably just lost track of which drive is which ID or something like that.
I will wager VB has seem more updates and changes than *buntu has since 2016
I am mildly surprised that the virtual machines even try to run, but it has always been pretty good at longer term file format support.

It's not mounted but it is visible on the Dolphin sidebar and this is while I have virtualbox running. Virtualbox would recognize it right away with my previous OS..

I tried to reconfigure the drives in virtualbox, even tried a new drive but it claims there are no devices attached.

[Scorpa54]

Have you installed the VBoxGuestAdditions_6.1.38.iso yet? Do you know how?

Never heard of it and can't say that I do but I'll look into it. Thank you kindly.

[Scorpa54]

Not entirely sure what I did but I think it was doing a startup after adding my name to the vboxusers group and now it works