disk read error when reading vmware's vmdi

[gour]

Hi!

Attempt to read vmware-5.5.x's vmdi disk with virtualbox-1.4 fails with: "A disk read error occured Press Ctrl+Alt+Del to restart". which occurs shortly after display pf InnoTek logo.

The error occurs both with binary & OSE editions.

My system:

gaura-nitai ~ # uname -a Linux gaura-nitai 2.6.19-gentoo-r4 #11 Mon May 21 21:17:54 CEST 2007 x86_64 AMD Athlon(tm) 64 Processor 3000+ AuthenticAMD GNU/Linux

gaura-nitai ~ # gcc -v Using built-in specs. Target: x86_64-pc-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-4.1.2/workgcc-4.1.2/configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.1.2 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.2 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.2/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.2/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/include/g++-v4 --host=x86_64-pc-linux-gnu --disable-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --enable-secureplt --disable-libunwind-exceptions --enable-multilib --disable-libmudflap --disable-libssp --disable-libgcj --enable-languages=c,c++,fortran --enable-shared --enable-threads=posix --enable-cxa_atexit --enable-clocale=gnu Thread model: posix

The attached log file is when running OSE version.

Sincerely, Gour

[gour]

log file showing the error

[cromo]

I have a similar problem, although the message says "NTLDR is missing, Press Ctrl-Alt-Del to restart". the vmdk file has been created with vmware server 1.0. I am using binary version of Virtualbox under linux.

Attached the log file.

[cromo]

Log file.

[stonecrest]

I am seeing this issue as well ("A disk read error occured").

Also, I can't seem to restart the VM via host-del like the documentation suggests for sending a ctrl-alt-del. The host key works fine, but host-del doesn't cause a restart. I'm using the vboxsdl program if that matters.

[cromo]

I can confirm that host-del doesn't work, just like pretty much any other host+key combination, after that error shows.

[Klaus Espenlaub]

Is any of the images which trigger this bug by any chance a fixed image or an image split into several chunks? I'm asking because those have a separate text-mode description file, as this is essentially all I'm interested in for now (and not because I suspect a bug in other formats). No need for big image uploads so far.

VirtualBox 1.4.0 follows vey closely the VMDK format specifications, but it could very well be that there are some minor things not mentioned in the spec.

[gour]

Mine is fixed image of 4GB in size. Here is ls output:

gour@gaura-nitai ~/vmware/Win2k $ ls -al
total 6945096
drwxr-xr-x 2 gour users        424 2007-06-11 13:43 .
drwxr-xr-x 3 gour users         72 2007-06-07 09:47 ..
-rw-r--r-- 1 gour users      40763 2007-06-08 18:46 vmware-0.log
-rw-r--r-- 1 gour users      32447 2007-06-08 14:34 vmware-1.log
-rw-r--r-- 1 gour users      42486 2007-06-07 20:05 vmware-2.log
-rw-r--r-- 1 gour users      31440 2007-06-11 13:43 vmware.log
-rw------- 1 gour users 2629828608 2007-06-11 13:43 Win2k-000001.vmdk
-rw------- 1 gour users       8664 2007-06-11 13:43 Win2k.nvram
-rw------- 1 gour users  268435456 2005-07-12 11:32 Win2k-Snapshot1.vmem
-rw------- 1 gour users   17830798 2005-07-12 11:32 Win2k-Snapshot1.vmsn
-rw------- 1 gour users 4188667904 2007-06-09 10:26 Win2k.vmdk
-rw------- 1 gour users        450 2005-07-12 11:31 Win2k.vmsd
-rw------- 1 gour users       1618 2007-06-11 13:39 Win2k.vmx 

Sincerely,
Gour

[Klaus Espenlaub]

Replying to gour:

Mine is fixed image of 4GB in size. Here is ls output:

-rw------- 1 gour users 4188667904 2007-06-09 10:26 Win2k.vmdk

that's impossible (unless the VMDK format specs is really very inaccurate). Fixed images always consist of two files, one small text file image.vmdk and the actual data in image-flat.vmdk.

Can you check whether VMware have renamed files a bit and put the text file describing the image now in Win2k.vmsd? If that's a text file please attach it to this ticket. The VMware installation I have access to also has such files, but they are always 0 bytes in size.

[gour]

Replying to klaus:

that's impossible (unless the VMDK format specs is really very inaccurate). Fixed images always consist of two files, one small text file image.vmdk and the actual data in image-flat.vmdk.

Maybe I should add that I've one snapshot taken.

Can you check whether VMware have renamed files a bit and put the text file describing the image now in Win2k.vmsd? If that's a text file please attach it to this ticket. The VMware installation I have access to also has such files, but they are always 0 bytes in size.

I'm including it...

Sincerely,
Gour

[gour]

vmsd file

[Klaus Espenlaub]

OK, seems like they are doing strange things when snapshots are present. Using VMDK images with snapshots is not possible for now, and looking at the mess they make, probably never will.

[Klaus Espenlaub]

The geometry issues should be fixed in current OSE svn version and in the next release (1.4.2).