Ticket #10813 (closed defect: invalid)
Incorrect file host system checks for host file system hosting "raw" vmdk files.
|Reported by:||tkutergin||Owned by:|
I am trying to setup VMs using "raw" access to host LVM volumes. To do that, raw VMDK files were created for each LVM volume which should be imported into VM. These files and VM configuration files are hosted on ext4 file system on Ubuntu 10.04 LTS. No real disk image is hosted on this file system. "Use host cache" is turned off in VirtualBox for SATA controller which has these "raw" VMDK files attached.
However, when starting VM, I had the same warning that Snapshots directory and vmdk files are located on ext4 file system and host cache is turned on. Is it correct ? There is no disk image on ext4. I am not sure about snapshot images but I do not plan to use them in this installation. Another question is whether "host cache" setting applies to raw disk access. (the whole intent to use "raw" I/O was to avoid double file system overhead and bypass host I/O cache).
To try to avoid "host cache" being turned on, I created small ext3 partition (in fact LVM volume) which was formatted as ext3 and mounted to host virtualbox data. ext4 warning disappeared, but there is new warning about VMDK logical size larger than media size. But again, VMDK is 'raw' and it will not grow on this partition. Is this because possible snapshots ?
What is proper approach of creating large virtual disks on LVM volumes without using large file system mounted on host if I do not need snapshot feature.