It makes sense, assuming I'd be using the physical disk a lot. Thanks, I expected this would be the case. But if the file is constantly moving bits around on disk as I'm working, then I'd expect it would be practically impossible, or use a ridiculous amount of bandwidth.īitcasa says they've never done any official testing, but expects that it should work as long as my connection is good enough.Īny stories or theories on this? I'm planning on trying it with a small VM, but I don't want to accidentally waste a TB of bandwidth attempting a larger one if everyone has been unsuccessful at it. But at the same time, I don't know anything about the VDI file structure - if it stays relatively stable and doesn't change a whole lot while it's running, then Bitcasa should be smart enough to only transfer the changed pieces, rather than the entire file every time.

I'm thinking that it likely won't work well, because of all the bandwidth required to download and sync the VDI file. I'd like to try this so I can have lots of virtual machines without using local space, but I'm concerned about the performance of accessing a remote filesystem to read and write the VDI.

If not Bitcasa, then DropBox or SkyDrive or other similar services. Does anyone have any experience storing the VDI file on a cloud drive? Specifically, I'm looking into using Bitcasa infinite storage, which stores data on the cloud only, and maps the cloud drive so you can see it like a regular disk (there's local caching and cool stuff like that, but the file basically lives on the cloud).

Box vs dropbox vs bitcasa