While booting in linux virtual machine (vmdk's) using vmplayer(without support files)

Error thrown,

etho : link is not ready fuse init (API version 7.13)
ADDRCONF(NETDEV_CHANGE) etho : link becomes ready



ALT+CRTL+DEL requried will reboot and working, but if delete supporting files which are created again the same error is coming.

When the boot process is finished, is the link (eth0) available/working?

I've seen these messages before and as long as the link becomes ready message is shown after the link is not ready message everything is fine (at least it was for me).

BTW: is this a typo: etho? That should be eth0 (a zero)

ALT+CRTL+DEL is solve the issue but if we delete the supporting files, issue will pop up again. 'eth0' only its error thrown by the machine.

Which "supporting files" are you talking about and why would you want to remove them?

Probably a language problem, but I don't know what you are trying to say.

Tell us more about the problem you are facing and be a bit more detailed when describing it.

linux.vmsd,linux.nvram, linux.vmxf, vmware.log are the supporting files got created while opening the linux.vmx in vmplayer. The vmdk's linux.vmdk and linux-test.vmdk are attached together.

eth0 : link is not ready fuse init (API version 7.13)
ADDRCONF(NETDEV_CHANGE) eth0 : link becomes ready

This error throughout while am playing the linux.vmx file attached with linux.vmdk and linux-test.vmdk. For my project I need to supply only linux.vmx, linux.vmdk and inux-test.vmdk, i.e., except the files which are created while playing it.

After reading your first post I thought this was network related, but this seems to be virtual machine (vmware) related. Sorry, but I can't help you with that (no real experience with vmware).

Maybe someone else will be able to help you with this issue.