I am using Fusion 3.0.2 on MacBookPro.
I have a few external hard drives, and ALL of them work nicely
in my WindowsXP vm when I connect.
I have "ONE" different one... a Western Digital 1TB "WD Elements",
a 1TB formatted as NTFS (same as others I have). This one, when
I plug it in, gets attached to the OSX host. Then when I click the icon
for it in my vm, and click Connect... OSX then pops up and says
"The host is currently using the device "Western Digital External HDD".
When I press OK, it then pops up again, and won't let go. Then I force
it by unplugging it, and select my XP vm, and attach it again, and this
time it usually will mount into my vm, but certainly not always.
Then after about 2 minutes, it will wake up in the vm, and start
scanning it, where I can then select to open it, etc.
At this point it works ok.
What is causing the OSX side from trying to grab it and hang on so
hard to it?
Did you install the western digital software on the Mac? It grabs the disks and won't let go. There's also a hidden partition that get's mounted on the disk every time you plug it in (which you can't delete since it's in the enclosure firmware) - very very annoying.
If the virtual machine has focus, and is set to auto-connect USB devices, you can plug it in and windows will directly mount it first.
I have a number of USB Drives that I really do not want to mount automatically under OS X however I want the USB Drives to be available to the Virtual Machines and I use entries in the
fstabfile to keep these drives from mounting automatically under OS X.
fstabfile typically does not exist so to create it bring up a
Terminaland type the following command:
sudo nano /etc/fstab
Next add an appropriate entry on a single line and then save the file and exit
fstabfile I have the following entry.
LABEL=WINONLY none msdos rw,noauto 0 0
If yours is formatted
ntfsalong with the
LABELto what you have named the drive.
On a similar note I have FireWire Drives that I only want available at certain times to OS X and these are not used with Virtual Machines and in this case I use the UUID of the FireWire Drive as in the example below I have an old small drive I boot the Mac with to test certain things I don't want messing up my primary boot volume so booting the Mac with this is helpful. The first line below is just a comment so I know which drive that UUID belongs to without having to look it back up in Disk Utility.
# Leopard_FW2 - 27.5 GB Testing Volume - Leopard_FW2 Volume UUID=2A52C767-AE89-357C-85E7-64A6B68B5434 none hfs rw,noauto
So if you do not want a drive automatically mounting under OS X when you plug it in then this is a way of keeping it from being mounted automatically.
Also, when I try to nicely dismount it in OSX, i get a message "The disk "Elements" is in
use and could not be ejected. Try quitting applications and try again. (ok). So the I have
to physically unplug it, and try again.
That sounds interesting... I'll have to try that. So from the above error I get when
I try to eject it "The disk "Elements" is in use and could not be ejected"... is
"Elements" the name I should use??
Also just so you know if you need to mount it under OS X once you've added it to the fstab file then you can go into Disk Utility and select it and click the Mount button once you've disconnected it from the Virtual Machine.
No you should not have to reboot, I never do and it works for me as I edit the fstab on the fly from time to time.
The LABEL needs to be spelled the same way it is shown under Disk Utility under Info > Name:
Hint: You also can add multiple lines with different case spellings like one line each with one for proper case, upper case and lower case so this because a catch all for that Name.
BTW I'm headed out for next 6 hours so I will not be able to respond to further replies until I get back.
Still doing it even with the line in... is there a way to put a wildcard, so
I can say "don't mount ANYTHING" for the time i'm doing this one, to
test if it might be some other name? From what I can see it is called
"Elements", and WHEN it FINALLY mounts in my XP vm (it can
take 10-15 minutes (and things are SLOW during that period) before
it opens the "scan" and I can say "Open in folder". After that, the
drive works JUST FINE, and my speed resumes to normal.
This is a WEIRD drive! (i have others that are no problem...)