VMware bug? Can anyone replicate?

Discussion in 'Mac Apps and Mac App Store' started by Nermal, Jun 4, 2008.

  1. Nermal Moderator

    Nermal

    Staff Member

    Joined:
    Dec 7, 2002
    Location:
    New Zealand
    #1
    Hi everyone :)

    I'm running VMware 1.1.2 on 10.5.3. I have a VM running XP x64, and have set up Shared Folders. I've shared my FireWire hard drive and have mapped it to Z: in the VM.

    If I open up Z: and look at its properties, the Total Size, Used Space and Free Space reported are actually the stats for my internal hard drive, not the FireWire one! I'm trying to copy a 30 GB file to the FireWire drive (790 GB free) but it fails with an "insufficient space" error (my internal drive only has 21 GB free).

    Does anyone else have the same issue?

    Edit: It seems to be a bit more complex than that. I also had a Y: drive mapped, shared from my internal drive. The moment I unmapped Y:, Z: sprung up to 790 GB free. I need to do a little more investigating!
     
  2. Nermal thread starter Moderator

    Nermal

    Staff Member

    Joined:
    Dec 7, 2002
    Location:
    New Zealand
    #2
    OK, testing scenario:

    1. Set up a VM, I don't know whether XP x64 is required or not, but it's what I use.
    2. Set up two shared folders, from separate drives.
    3. Map Z: to one folder.
    4. Map Y: to the other folder.
    5. See whether the free space count for either mapped drive is wrong.

    Can someone please try this? :)
     
  3. Nuc macrumors 6502a

    Nuc

    Joined:
    Jan 20, 2003
    Location:
    TN
    #3
    I would try it but don't have 1.1.2 or XP 64. I have the VMWare 2.0b1 the latest beta. Why not update to it and see if this fixes your issues. Also 1.1.3 is available if you don't want to install beta software...

    Nuc
     
  4. Nermal thread starter Moderator

    Nermal

    Staff Member

    Joined:
    Dec 7, 2002
    Location:
    New Zealand
    #4
    Good grief, I only installed 1.1.2 a couple of weeks ago! :eek:

    Edit: But I don't see this issue in either the 1.1.3 or 2 release notes.
     

Share This Page