I have centos6.5 VM on vmware server. Now i cloned it using vmware converter. It is cloned fine and created new VM using this. It booted also correctly BUT now facing problem like "When i enter my credentials to login to machine its showing me blank screen and again same login window comes". I searched on google but not found exact issue.
Please suggest me any solution.

Hi Onkar
It doesn't say it fails, it just rolls to the next iteration? It almost sounds like a bad /etc/shadow.
Are you accessing it through the VMWare console or ssh'ing into it?

1)I trying to access through SSH it BUT after giving user name and password it again asking me same thing username and password.. and its continuing iterating

2) when i access through VMware client UI, then after giving user name and password in UI it again asking me same thing username and password.. and its continuing iterating.

Boot the machine in runlevel 1 (Live CD or command line kernel option), log in as root and inspect the system logs?

I'd check the /etc/shadow file to make sure it's not corrupt. Try a "cat /etc/shadow" and see what you get.

I checked the log file. There are some error regarding files are missing.
I have two file
Xorg.0.log & Xorg.9.log


IN XORG.0.LOG I HAVE FOUND TWO ERROR
[ 213.356] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 213.356] (II) FBDEV: driver for framebuffer: fbdev
[ 213.356] (--) using VT number 7

[ 213.358] (WW) Falling back to old probe method for vesa
[ 213.358] (WW) Falling back to old probe method for modesetting
[ 213.358] (EE) open /dev/dri/card0: No such file or directory
[ 213.358] (WW) Falling back to old probe method for fbdev
[ 213.358] (II) Loading sub module "fbdevhw"
[ 213.358] (II) LoadModule: "fbdevhw"
[ 213.358] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[ 213.358] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 213.358] compiled for 1.13.0, module version = 0.0.2
[ 213.358] ABI class: X.Org Video Driver, version 13.1
[ 213.364] (EE) open /dev/fb0: No such device
[ 213.365] (II) vmware(0): Driver was compiled without KMS- and 3D support.
[ 213.365] (WW) vmware(0): Disabling 3D support.
[ 213.365] (WW) vmware(0): Disabling Render Acceleration.
[ 213.365] (WW) vmware(0): Disabling RandR12+ support.
[ 213.365] (--) vmware(0): VMware SVGA regs at (0x10d0, 0x10d1)


IN XORG.9.LOG FOUND THREE ERROR
[ 29.167] (II) UnloadModule: "vmwgfx"
[ 29.167] (II) Unloading vmwgfx
[ 29.167] (EE) Failed to load module "vmwgfx" (module does not exist, 0)
[ 29.167] (EE) vmware: Please ignore the above warnings about not being able to to load module/driver vmwgfx
[ 29.167] (II) vmware: Using vmwlegacy driver everything is fine.

[ 29.200] compiled for 1.10.4, module version = 0.0.2
[ 29.200] ABI class: X.Org Video Driver, version 10.0
[ 29.220] (EE) open /dev/fb0: No such device
[ 29.220] (--) vmwlegacy(0): VMware SVGA regs at (0x10d0, 0x10d1)
[ 29.220] (II) Loading sub module "vgahw"
[ 29.220] (II) LoadModule: "vgahw"



1)BUT I CHECKED THIS FILE ([ 213.358] (EE) open /dev/dri/card0: No such file or directory) IN ORIGINAL VM MACHINE .
AND THIS FILE ALSO NOT PRESENT IN ORGINAL MACHINE
2) /dev/fb0 is also present correctly
3) I checked the cat /etc/shadow command But it also giving same response as original VM.


How can we say that /etc/shadow is corrupt?

You can just "cat" it from the command line. Open a terminal, make sure you are the root user and type "cat /etc/shadow" and post what that command returns

But what can u do with that file since if i gave wrong password then its shows me message of wrong password AND if i give right password then its gives me login windows again. It means password is correct. Is m right?

shadow.txt removed at request of mod


This is output of cat /etc/shadow

Etc/shadow looks OK.
Is this a single user on the machine having the issue or every user?

this is problem with every user.
Did you checked my logs (in last post). It has something driver problem also. Is it related?

Yeah, you're looking at the Xorg log. Xorg has to do with display functionality, It probably can mess up logins ( especially if you use a GUI login screen as opposed to a terminal logins) but your description of your problem doesn't really match up with that, at least as far as I can see.
Can you break out of the gui ( generally ctrl+alt+backspace) and log in successfully directly from the terminal?
The other thing is...
What Distro are you using, we're going to need to check some log files and I want to make sure I'm pointing you to the right locations in your file system.
Back on this evening.

I seriously question your practice of asking a fellow LQ member to 'cat' /etc/shadow.
Doing that (even though every LQ member is responsible for her / his own actions) IMNSHO constitutes an unacceptable risk.
Do not ever do that again.

*If you really think this has to do with "bad /etc/shadow" then you should have looked at system log files for clues first, then at tools like 'pwck' and then work your way though ownership, access perms and other attributes and integrity verification. If you don't know 'pwck' that's really inexcusable.

I don't recall asking for an excuse....

[shrug]

This is what i got from command cat /etc/shadow


[IMG]D:\BB-Testing\ScreenShots[/IMG]

Attached Thumbnails