3dsachin
Enthusiast
Enthusiast

Virtual Machine is showing as Invalid (vSphere 5.1)

Jump to solution

I understand that vSphere 5.1 is EOL and we are moving on to 6.7. However, I have a strange issue that one of our virtual machines is showing as "Invalid" with no descriptions. It seems like it is unable to read the vmx file at all. The server is up and running which is good. But, there are no controls available like; "Edit settings" etc.

I've tried VMware Knowledge Base  with no luck. All ESXi hosts have been rebooted. Although the VM is powered On, still it gives option to power on and fails if I try to do so.

Any suggestions please..

I am wondering if V2V will fix this without any impact.

PS: There are no backups for this VM.

0 Kudos
1 Solution

Accepted Solutions
3dsachin
Enthusiast
Enthusiast

Guys, I have an update. I dont understand the relation but after I rebooted both vCenter server and application server, the application server is showing fine in vCenter.

Thank you all for your inputs.

View solution in original post

0 Kudos
15 Replies
a_p_
Leadership
Leadership

As a first step, please post a complete list of files in the VM's folder. Make sure the listing contains file names, extensions, sizes, and time stamps.

Depending on whether the following files exist in the VM's folder, download *.vmx, *.vmsd *.log files, compress/zip them, and attach the .zip archive to a reply post.

André

0 Kudos
RickVerstegen
Expert
Expert

Looks like the ESXI host is unable to access the storage. Can you verify this?

This condition happens when the ESXi host cannot access the vmx file in the datastore, so it sort of forgets the configuration of the machine. The process which runs the virtual machine is still running on the host, so your VM does not crash.

Blog: https://rickverstegen84.wordpress.com/ Twitter: https://twitter.com/verstegenrick
0 Kudos
3dsachin
Enthusiast
Enthusiast

I can see and browse the datastore through the host where it is on now.

0 Kudos
3dsachin
Enthusiast
Enthusiast

Log File:

2018-09-24T06:57:57.848Z| vmx| I120: Log for VMware ESX pid=11124 version=5.1.0 build=build-3872664 option=Release

2018-09-24T06:57:57.848Z| vmx| I120: The process is 64-bit.

2018-09-24T06:57:57.848Z| vmx| I120: Host codepage=UTF-8 encoding=UTF-8

2018-09-24T06:57:57.848Z| vmx| I120: Host is VMkernel 5.1.0

2018-09-24T06:57:57.844Z| vmx| I120: VTHREAD initialize main thread 0 "vmx" pid 11124

2018-09-24T06:57:57.844Z| vmx| I120: Msg_SetLocaleEx: HostLocale=UTF-8 UserLocale=NULL

2018-09-24T06:57:57.845Z| vmx| I120: ConfigDB: Failed to load /usr/lib/vmware/config

2018-09-24T06:57:57.845Z| vmx| I120: ConfigDB: Failed to load ~/.vmware/config

2018-09-24T06:57:57.845Z| vmx| I120: OBJLIB-LIB : Objlib initialized.

2018-09-24T06:57:57.846Z| vmx| I120: PREF Optional preferences file not found at /usr/lib/vmware/config. Using default values.

2018-09-24T06:57:57.846Z| vmx| I120: PREF Optional preferences file not found at //.vmware/config. Using default values.

2018-09-24T06:57:57.846Z| vmx| I120: PREF Failed to load user preferences.

2018-09-24T06:57:57.848Z| vmx| I120: Hostname=PHOH1ESX01.minerals.local

2018-09-24T06:57:57.848Z| vmx| I120: IP=127.0.0.1 (lo0)

2018-09-24T06:57:57.848Z| vmx| I120: IP=10.0.33.25 (vmk0)

2018-09-24T06:57:57.848Z| vmx| I120: IP=10.80.61.36 (vmk1)

2018-09-24T06:57:57.848Z| vmx| I120: vmkernel build type: release

2018-09-24T06:57:57.848Z| vmx| I120: System uptime 338479961 us

2018-09-24T06:57:57.848Z| vmx| I120: Command line: "/bin/vmx" "-ssched.group=host/user/pool0" "-#" "product=4;name=VMware ESX;version=5.1.0;buildnumber=3872664;licensename=VMware ESX Server;licenseversion=5.0;" "-@" "duplex=3;msgs=ui" "/vmfs/volumes/51bfddd3-b47c738c-158b-0025b510015f/PHOAPP016/PHOAPP016.vmx"

2018-09-24T06:57:57.848Z| vmx| I120: Environment: "USER=root" "HOME=/" "SHELL=/bin/sh" "LANG=C"

2018-09-24T06:57:57.848Z| vmx| I120: Msg_SetLocaleEx: HostLocale=UTF-8 UserLocale=NULL

2018-09-24T06:57:57.848Z| vmx| I120: Duplex socket: 3

2018-09-24T06:57:57.870Z| vmx| I120: Connecting 'ui' to fd '3' with user '(null)'

2018-09-24T06:57:57.870Z| vmx| I120: VmdbAddConnection: cnxPath=/db/connection/#1/, cnxIx=1

2018-09-24T06:57:57.870Z| vmx| I120: /vmfs/volumes/51bfddd3-b47c738c-158b-0025b510015f/PHOAPP016/PHOAPP016.vmx: Setup symlink /var/run/vmware/982625c796939ab40147541b797eff67 -> /var/run/vmware/root_0/1537772277849066_11124

2018-09-24T06:57:57.870Z| vmx| I120: Vix: [11124 mainDispatch.c:475]: VMAutomation: Initializing VMAutomation.

2018-09-24T06:57:57.871Z| vmx| I120: Vix: [11124 mainDispatch.c:772]: VMAutomationOpenListenerSocket() listening

2018-09-24T06:57:57.878Z| vmx| I120: Vix: [11124 mainDispatch.c:3870]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0

2018-09-24T06:57:57.878Z| vmx| I120: Transitioned vmx/execState/val to poweredOff

2018-09-24T06:57:57.878Z| vmx| I120: Vix: [11124 mainDispatch.c:3870]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0

2018-09-24T06:57:57.878Z| vmx| I120: Vix: [11124 mainDispatch.c:3870]: VMAutomation_ReportPowerOpFinished: statevar=2, newAppState=1877, success=1 additionalError=0

2018-09-24T06:57:57.878Z| vmx| I120: Vix: [11124 mainDispatch.c:3870]: VMAutomation_ReportPowerOpFinished: statevar=3, newAppState=1881, success=1 additionalError=0

2018-09-24T06:57:57.878Z| vmx| I120: UTIL: Change file descriptor limit from soft 2848,hard 2848 to soft 4096,hard 4096.

2018-09-24T06:57:57.878Z| vmx| I120: PTSC: using TSC + offset (-11580441110270536)

2018-09-24T06:57:57.878Z| vmx| I120: PTSC: hardware TSCs are synchronized.

2018-09-24T06:57:57.878Z| vmx| I120: PTSC: current PTSC=677004346412

2018-09-24T06:57:57.878Z| vmx| I120: FeatureCompat: No EVC masks.

2018-09-24T06:57:57.881Z| vmx| I120: hostCPUID vendor: GenuineIntel

2018-09-24T06:57:57.881Z| vmx| I120: hostCPUID family: 0x6 model: 0x2d stepping: 0x7

2018-09-24T06:57:57.881Z| vmx| I120: hostCPUID codename: Sandy Bridge EP

2018-09-24T06:57:57.881Z| vmx| I120: hostCPUID name: Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 00000000, 0: 0x0000000d 0x756e6547 0x6c65746e 0x49656e69

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 00000001, 0: 0x000206d7 0x00200800 0x17bee3ff 0xbfebfbff

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 00000002, 0: 0x76035a01 0x00f0b2ff 0x00000000 0x00ca0000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 00000003, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 00000004, 0: 0x3c004121 0x01c0003f 0x0000003f 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 00000004, 1: 0x3c004122 0x01c0003f 0x0000003f 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 00000004, 2: 0x3c004143 0x01c0003f 0x000001ff 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 00000004, 3: 0x3c07c163 0x04c0003f 0x00003fff 0x00000006

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 00000004, 4: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 00000005, 0: 0x00000040 0x00000040 0x00000003 0x00021120

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 00000006, 0: 0x00000077 0x00000002 0x00000009 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 00000007, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 00000008, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 00000009, 0: 0x00000001 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000a, 0: 0x07300403 0x00000000 0x00000000 0x00000603

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000b, 0: 0x00000001 0x00000002 0x00000100 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000b, 1: 0x00000005 0x00000010 0x00000201 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000b, 2: 0x00000000 0x00000000 0x00000002 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000c, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 0: 0x00000007 0x00000240 0x00000340 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 1: 0x00000001 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 2: 0x00000100 0x00000240 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 3: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 4: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 5: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 6: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 7: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 8: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 9: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, a: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, b: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, c: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, d: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, e: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, f: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 10: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 11: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 12: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 13: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 14: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 15: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 16: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 17: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 18: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 19: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 1a: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 1b: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 1c: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 1d: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 1e: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 1f: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 20: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 21: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 22: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 23: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 24: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 25: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 26: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 27: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 28: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 29: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 2a: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 2b: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 2c: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 2d: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 2e: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 2f: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 30: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 31: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 32: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 33: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 34: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 35: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 36: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 37: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 38: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 39: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 3a: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 3b: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 3c: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 3d: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 3e: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 0000000d, 3f: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 80000000, 0: 0x80000008 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 80000001, 0: 0x00000000 0x00000000 0x00000001 0x2c100800

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 80000002, 0: 0x20202020 0x49202020 0x6c65746e 0x20295228

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 80000003, 0: 0x6e6f6558 0x20295228 0x20555043 0x322d3545

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 80000004, 0: 0x20303536 0x20402030 0x30302e32 0x007a4847

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 80000005, 0: 0x00000000 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 80000006, 0: 0x00000000 0x00000000 0x01006040 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 80000007, 0: 0x00000000 0x00000000 0x00000000 0x00000100

2018-09-24T06:57:57.882Z| vmx| I120: hostCPUID level 80000008, 0: 0x0000302e 0x00000000 0x00000000 0x00000000

2018-09-24T06:57:57.882Z| vmx| I120: CPUID differences from hostCPUID.

2018-09-24T06:57:57.882Z| vmx| I120: CPUID[1] level 00000001, 0: 0x000206d7 0x01200800 0x17bee3ff 0xbfebfbff

2018-09-24T06:57:57.882Z| vmx| I120: CPUID[1] level 0000000b, 0: 0x00000001 0x00000002 0x00000100 0x00000001

2018-09-24T06:57:57.882Z| vmx| I120: CPUID[1] level 0000000b, 1: 0x00000005 0x00000010 0x00000201 0x00000001

2018-09-24T06:57:57.882Z| vmx| I120: CPUID[1] level 0000000b, 2: 0x00000000 0x00000000 0x00000002 0x00000001

2018-09-24T06:57:57.882Z| vmx| I120: CPUID[2] level 00000001, 0: 0x000206d7 0x02200800 0x17bee3ff 0xbfebfbff

2018-09-24T06:57:57.882Z| vmx| I120: CPUID[2] level 0000000b, 0: 0x00000001 0x00000002 0x00000100 0x00000002

2018-09-24T06:57:57.882Z| vmx| I120: CPUID[2] level 0000000b, 1: 0x00000005 0x00000010 0x00000201 0x00000002

2018-09-24T06:57:57.882Z| vmx| I120: CPUID[2] level 0000000b, 2: 0x00000000 0x00000000 0x00000002 0x00000002

2018-09-24T06:57:57.882Z| vmx| I120: CPUID[3] level 00000001, 0: 0x000206d7 0x03200800 0x17bee3ff 0xbfebfbff

2018-09-24T06:57:57.882Z| vmx| I120: CPUID[3] level 0000000b, 0: 0x00000001 0x00000002 0x00000100 0x00000003

2018-09-24T06:57:57.882Z| vmx| I120: CPUID[3] level 0000000b, 1: 0x00000005 0x00000010 0x00000201 0x00000003

2018-09-24T06:57:57.882Z| vmx| I120: CPUID[3] level 0000000b, 2: 0x00000000 0x00000000 0x00000002 0x00000003

2018-09-24T06:57:57.882Z| vmx| I120: CPUID[4] level 00000001, 0: 0x000206d7 0x04200800 0x17bee3ff 0xbfebfbff

2018-09-24T06:57:57.882Z| vmx| I120: CPUID[4] level 0000000b, 0: 0x00000001 0x00000002 0x00000100 0x00000004

2018-09-24T06:57:57.882Z| vmx| I120: CPUID[4] level 0000000b, 1: 0x00000005 0x00000010 0x00000201 0x00000004

2018-09-24T06:57:57.882Z| vmx| I120: CPUID[4] level 0000000b, 2: 0x00000000 0x00000000 0x00000002 0x00000004

2018-09-24T06:57:57.882Z| vmx| I120: CPUID[5] level 00000001, 0: 0x000206d7 0x05200800 0x17bee3ff 0xbfebfbff

2018-09-24T06:57:57.882Z| vmx| I120: CPUID[5] level 0000000b, 0: 0x00000001 0x0000

0 Kudos
3dsachin
Enthusiast
Enthusiast

VMX File

.encoding = "UTF-8"

config.version = "8"

virtualHW.version = "8"

pciBridge0.present = "true"

pciBridge4.present = "true"

pciBridge4.virtualDev = "pcieRootPort"

pciBridge4.functions = "8"

pciBridge5.present = "true"

pciBridge5.virtualDev = "pcieRootPort"

pciBridge5.functions = "8"

pciBridge6.present = "true"

pciBridge6.virtualDev = "pcieRootPort"

pciBridge6.functions = "8"

pciBridge7.present = "true"

pciBridge7.virtualDev = "pcieRootPort"

pciBridge7.functions = "8"

vmci0.present = "true"

hpet0.present = "true"

nvram = "APP016.nvram"

virtualHW.productCompatibility = "hosted"

powerType.powerOff = "soft"

powerType.powerOn = "hard"

powerType.suspend = "hard"

powerType.reset = "soft"

displayName = "APP016"

extendedConfigFile = "APP016.vmxf"

floppy0.present = "true"

numvcpus = "4"

scsi0.present = "true"

scsi0.sharedBus = "none"

scsi0.virtualDev = "lsisas1068"

scsi0.pciSlotNumber = "160"

memsize = "8192"

scsi0:0.present = "true"

scsi0:0.fileName = "APP016.vmdk"

scsi0:0.deviceType = "scsi-hardDisk"

sched.scsi0:0.shares = "normal"

sched.scsi0:0.throughputCap = "off"

scsi0:1.present = "true"

scsi0:1.fileName = "APP016_1.vmdk"

scsi0:1.deviceType = "scsi-hardDisk"

sched.scsi0:1.shares = "normal"

sched.scsi0:1.throughputCap = "off"

ide1:0.present = "true"

ide1:0.clientDevice = "true"

ide1:0.deviceType = "atapi-cdrom"

ide1:0.startConnected = "false"

floppy0.startConnected = "false"

floppy0.fileName = ""

floppy0.clientDevice = "true"

ethernet0.present = "true"

ethernet0.pciSlotNumber = "192"

ethernet0.virtualDev = "vmxnet3"

ethernet0.dvs.switchId = "ba f9 0a 50 85 12 a5 2b-6d ce c4 9c ae 58 45 30"

ethernet0.dvs.portId = "108"

ethernet0.dvs.portgroupId = "dvportgroup-30"

ethernet0.dvs.connectionId = "437447355"

ethernet0.addressType = "vpx"

ethernet0.generatedAddress = "00:50:56:8a:52:fd"

svga.vramSize = "8388608"

vmci0.pciSlotNumber = "32"

disk.EnableUUID = "true"

guestOS = "windows7srv-64"

annotation = "Autoserver v1.0.32|0AEMC Avamar for windows|0AGraphics Conversion Library|0ALeica GeoMOS Monitor 6.0|0ALeica Geosystems CLM Administrator Server 1.2|0ALeica Geosystems CLM Remote Daemon Server 1.2|0ALeica Geosystems CLM Server Package 1.2|0AMicrosoft SQL server 2008R2 (64-bit)|0ANPort Administration Suite V1.19|0AQuikslope 6|0ASoftrock Autosync 6|0ASoftrock licensing"

uuid.bios = "42 0a 1a 61 46 15 5e 34-a1 86 42 9e 31 be dc 88"

vc.uuid = "50 0a b8 da b6 c4 3a ab-68 4c e4 13 4e c5 73 e3"

virtualHW.scheduledUpgrade.state = "none"

virtualHW.scheduledUpgrade.when = "never"

snapshot.action = "keep"

sched.cpu.min = "0"

sched.cpu.units = "mhz"

sched.cpu.shares = "normal"

sched.cpu.latencySensitivity = "normal"

sched.mem.min = "0"

sched.mem.shares = "normal"

tools.upgrade.policy = "manual"

replay.supported = "FALSE"

unity.wasCapable = "false"

replay.filename = ""

scsi0:0.redo = ""

pciBridge0.pciSlotNumber = "17"

pciBridge4.pciSlotNumber = "21"

pciBridge5.pciSlotNumber = "22"

pciBridge6.pciSlotNumber = "23"

pciBridge7.pciSlotNumber = "24"

scsi0.sasWWID = "50 05 05 61 46 15 5e 30"

ethernet0.generatedAddressOffset = "0"

tools.remindInstall = "false"

hostCPUID.0 = "0000000d756e65476c65746e49656e69"

hostCPUID.1 = "000206d70020080017bee3ffbfebfbff"

hostCPUID.80000001 = "0000000000000000000000012c100800"

guestCPUID.0 = "0000000d756e65476c65746e49656e69"

guestCPUID.1 = "000206d700010800969822030fabfbff"

guestCPUID.80000001 = "00000000000000000000000128100800"

userCPUID.0 = "0000000d756e65476c65746e49656e69"

userCPUID.1 = "000206d700200800169822030fabfbff"

userCPUID.80000001 = "00000000000000000000000128100800"

evcCompatibilityMode = "FALSE"

vmotion.checkpointFBSize = "8388608"

softPowerOff = "FALSE"

vmotion.checkpointSVGASize = "11534336"

scsi0:1.ctkEnabled = "false"

scsi0:1.redo = ""

vmci0.id = "834591880"

tools.syncTime = "FALSE"

uuid.location = "56 4d c9 20 2a 93 2e d8-18 b5 3d fe 59 2a 4f 8f"

cleanShutdown = "FALSE"

migrate.hostlog = "./APP016-aaf6870b.hlog"

sched.swap.derivedName = "/vmfs/volumes/51bfddd3-b47c738c-158b-0025b510015f/APP016/APP016-aaf6870b.vswp"

config.readOnly = "FALSE"

0 Kudos
3dsachin
Enthusiast
Enthusiast

vmsd file is 0KB

0 Kudos
Devi94
Hot Shot
Hot Shot

If you have all files present in datastore, can you take downtime of 30 mins to re-register VM?

0 Kudos
3dsachin
Enthusiast
Enthusiast

Yes. What action plan are you suggesting?

thanks

0 Kudos
RickVerstegen
Expert
Expert

One way to re-register the VM would be to shut down the virtual machine, remove it from inventory, browse the datastore, then re-add it to inventory and power on the virtual machine.

Blog: https://rickverstegen84.wordpress.com/ Twitter: https://twitter.com/verstegenrick
0 Kudos
3dsachin
Enthusiast
Enthusiast

Thanks Rick. I’ve tried this already and it did not work. I am thinking if V2v would work, but not sure of the repercussion.

0 Kudos
3dsachin
Enthusiast
Enthusiast

Guys, I have an update. I dont understand the relation but after I rebooted both vCenter server and application server, the application server is showing fine in vCenter.

Thank you all for your inputs.

View solution in original post

0 Kudos
markzz
Enthusiast
Enthusiast

We are migrating from 5.5 to 6.5 (why 6.5 there's a reason)

Back to the point at hand.

In particular Windows 2008, Windows 2008r2 servers and Windows 7 VDI's have this issue.

They appear to power off and are marked as ServersName(invalid) as tools are upgraded. This doesn't occur 100% of the time but it does occur about 50%.

When this occurs you really have to right click the guest which is now called ServersName(invalid) and remove from inventory.

Brows the storage, find the servers ServersName.vmx file and register the guest again..

OH and do this via the HTML5 interface.. (Not the horrid flash based WEB Interface as you can not remove from inventory, you must use the less horrid HTML5 interface)

So there's some info on the current behavior of a typical Win7, 2008 machine...

After reading a few discussions on this I was thinking is this something to do with the fact that esxi 6.5 appears to not be able to access the guests config until it's powered off etc..

I also noticed the issue only occured with VM's that didn't discover new hardware once in 6.5..

So to test this I've stopped upgrading the tools..

My routine is ugly but it does appear to prevent this issue of the guests becoming invalid..

I'm hot migrating, once the guest is running on an ESXi 6.5 host, I perform the below routine.

1. Power the guest off.

2. power the guest on.

3. wait until the guest is at the login screen, give it about 60 seconds with it's self (at the login screen)..

4. reboot the guest

5. wait again until the guest is at the login screen give it again about 60 seconds.

6. Upgrade the VMTools unassisted.. The guest upgrades the VMtools, Reboots and is all good..

I'm aware this is not pretty but it works persistently and appears to prevent the ServersName(invalid) issue occuring..

For god sake VMWare what are you doing..

We get this horrible management environment and a bag of critical issues to manage.

Maybe I have it wrong. I thought VMWare were now owned by Dell.. It must be Microsoft who have purchased them, it's obvious by the misguided technical direction and flaky products..

0 Kudos
3dsachin
Enthusiast
Enthusiast

Thanks for sharing your experience. It's sounds crazy and could be nerve racking when critical servers are involved. However, we have now migrated from vSphere 5.1 to vSphere 6.7. It's not user friendly as you tend to refresh too often to see the changes.

jefferson342
Contributor
Contributor

it is the condition when the ESXi host cannot access the vmx file, please post a complete list of files in the VM's folder, check the listings contain file names, extensions, sizes, and time stamps.

0 Kudos
3dsachin
Enthusiast
Enthusiast

Hi Jeff. Thanks for your response. This would probably have been the case then and the problem was resolved by rebooting the virtual machine.

0 Kudos