Vbox unable to create new disk images on NTFS volume

[imrazor]

I just wanted to make sure that this was a known bug/feature, and not some peculiarity of my setup. I have a dual boot laptop, with a Debian SSD, Win10 Pro SSD, and a spinning NTFS drive called Data. When I try to create a .vdi file on the NTFS volume from Linux, Virtualbox tells me to go jump off a cliff. From Virtualbox in Windows, I have no issues.

Is this expected behavior? It's not the end of the world, because I can just reboot into Windows, create the VM, then add it in Linux, but it is annoying.

[socratis]

When I try to create a .vdi file on the NTFS volume from Linux

I'm having a hard time seeing that VirtualBox would really care if the partition is NTFS, HFS+, ext#, btrfs, FAT of anything else for that matter. Is VirtualBox the only application you're having this problem with? I'm going to try it out and update with the results.

[socratis]

Just as I suspected, I can confirm that VirtualBox has no problem to create a VDI (actually the whole VM) in an NTFS partition. Permissions issues? Mounting flags?

[imrazor]

I wouldn't think it's permissions. I can easily create and delete files and folders on the drive. It's auto mounted in fstab thusly:

Code: Select all

/dev/sda1	/media/Data	ntfs	auto,uid=1000,gid=1000	0 0

Does Virtualbox use a different UID or GID? I assumed it operated under my credentials.

[imrazor]

Never mind, the problem was a bad path in Virtualbox's preferences. Not sure how that could've happened, since you have to select a valid path in the first place. Anyway, seems to be working properly now.