Changes to vdi image using vboximg-mount are not persistent

[jpt]

Hi,

File /new_vdi.vdi created by the VBox Machines' Management Tool, attached to a machine running Linux Debian Bullseye 64bits and partitionned/formated with gparted. That partition is then mounted and copying data (file "from_vm.txt") to it works fine, so power off machine and detach file from machine.

Then, using a terminal from the host, where /x and /y are two mountpoints for test :

1st run, writing file "from_host.txt" to vdi image :

vboximg-mount --rw -i /new_vdi.vdi -o allow_root /x/
mount /x/vol0 /y/
touch /y/from_host.txt
echo "try from host" > /y/from_host.txt 
sync
ls /y/ # --> from_host.txt  from_vm.txt  lost+found
cat /y/from_host.txt # --> "try from host"
umount /y/
umount /x/

Everything is fine.

2nd run, reading from vdi image :

vboximg-mount --rw -i /new_vdi.vdi -o allow_root /x/
mount /x/vol0 /y/
ls /y/ # --> from_vm.txt  lost+found
umount /y/
umount /x/

Written file "from_host.txt" lost !

Same problem here ​https://www.reddit.com/r/virtualbox/comments/mogadt/vboximgmount_readwrite_persistence/ or there : ​https://forums.virtualbox.org/viewtopic.php?f=7&t=96967&p=515917, and no one provides a good working command line.

Thanks a lot in advance.

[jpt]

Problem still alive with 6.1.34...

Regards, -- jpt

[Klaus Espenlaub]

Yes, known issue. Fixed after 6.1.34. We're working on getting test builds out which is a bit more tedious than usual (blasted code signing...).

[fth0]

I've successfully verified the bugfix with the VirtualBox test build 6.1.35r151427.

[galitsyn]

Thank you for reporting the issue. It should be fixed in VirtualBox 6.1.36. Please refer to https://www.alldomusa.eu.org/wiki/Downloads page.