Hello !
fth0 wrote:Ok, so it's a normal base VDI with standard settings.
Cool ! Fine ! Thanks !
fth0 wrote:Perhaps vboximg-mount --list --image=/30_MEG.vdi --verbose --wide can give us more information.
Caution with that
still alive bug/typo in manual (and the web...) :
wrong
Code: Select all
vboximg-mount --list --image=/30_MEG.vdi --verbose --wide
good
Code: Select all
vboximg-mount --list --image /30_MEG.vdi --verbose --wide
notice the wrong "
--image=", corrected with a space "
--image " !
Do they check their products, in regard of their manuals ?
Well, and so :
Code: Select all
vboximg-mount --list --image /30_MEG.vdi --verbose --wide
[empty line]
Attempting to lock medium chain from leaf image to base image
30_MEG.vdi ... Locking for read
[empty line]
Creating container for base image of format VDI
[empty line]
Opening medium chain
Open: /30_MEG.vdi
[empty line]
Virtual disk image:
[empty line]
Base: /30_MEG.vdi
UUID: 312021c6-0344-4e76-8c30-3249eeb7deb2
[empty line]
Partition Boot Start Sectors Size Offset Type
30_MEG.vdi(0) 17 61387 29.9M 8704 Linux native
[empty line]
fth0 wrote:When the file system has been mounted, what does a simple mount command show as the mount's properties?
Code: Select all
vboximg-mount -i /30_MEG.vdi --rw -o allow_root /x
mount
...
vboximg-mount on /x type fuse.vboximg-mount (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
fth0 wrote:I'm also no native English speaker, and I have to admit that my statement possibly wasn't correct English.
No no, it's all perfect.
fth0 wrote:If you like, you can write in your native language, and
Google Translate will try to help us.
Oh no, sometimes it's just incomprehensible,
I prefer continuing like that.
And, by the way, I'll be happy to read how Oracle's people work with vboximg-mount, regarding that problem...
Maybe the culprit is here, in the output of the your command :
Code: Select all
vboximg-mount --list --image /30_MEG.vdi --verbose --wide
Attempting to lock medium chain from leaf image to base image
30_MEG.vdi ... Locking for read
EDIT
Locking for read means
not allowing writes, right ? /EDIT
So that's why I mount my file with the "
--rw" flag, with no luck...
(sorry for the delay regarding my reply, I've checked "
Notify me when a reply is posted" and received nothing...)