VMware Cloud Community
cptkirkh
Contributor
Contributor

issue on vmguest not starting

So i have test lab that has ESXI 6.5 installed and a couple of VMs.  I have a Windows 10 guest that was running and i wanted to test a power outage.  When the Windows 10 guest went to start back up after the power was turn on i only get the path to the vmx file fpr the virtual name.  I tried to unregister and register the vm back but it does the same thing.   any ideas on how to get this back up and running?  Thanks.

unnamed.png

0 Kudos
9 Replies
vijayrana968
Virtuoso
Virtuoso

ESXI has lost connectivity to datastore. Please verify datastore status and health. Rescan ESXi storage adapter for devices and VMFS volumes.

0 Kudos
cptkirkh
Contributor
Contributor

t looks like the datastore is fine.  Or it seems that way to me.  The other VMs look fine.

vms.png

Datastore..

datastores.png

0 Kudos
EricChigoz
Enthusiast
Enthusiast

Hello Cpt..

Good day.

Please remove the VM from inventory,  browse to the folder on the datastore and add *.vmx file to the inventory again.

Thank you.

Find this helpful? Please award points. Thank you !
0 Kudos
cptkirkh
Contributor
Contributor

already tried that.  One thing i noticed is when you browse the datastore the icon for the vmx file in the folder for the vm that has the issue looks like a text file but if you go to another folder in a vm that works it looks like a normal vmx file.  See photo below

problem VM

image (2).png

good vm

image (1).png

0 Kudos
a_p_
Leadership
Leadership

Just a quick guess.

Compare the permissions from the command line (running ls -lisa) with other .vmx files.

What may also be an option is to unregister the VM, download the .vmx file from the datastore (and make sure it looks ok), delete the file from the datastore, and then upload the .vmx file again.


André

0 Kudos
cptkirkh
Contributor
Contributor

I check the permissions and still nothing.  I also downloaded the file and there are no issues.  I deleted it and uploaded again and checked the permissions and it still didn't work right.

0 Kudos
a_p_
Leadership
Leadership

Can you please attach the .vmx file to a reply post?


André

0 Kudos
cptkirkh
Contributor
Contributor

.encoding = "UTF-8"

config.version = "8"

virtualHW.version = "11"

vmci0.present = "TRUE"

numvcpus = "2"

memSize = "4008"

scsi0.virtualDev = "lsisas1068"

scsi0.present = "TRUE"

ide1:0.deviceType = "atapi-cdrom"

ide1:0.fileName = "/vmfs/devices/cdrom/mpx.vmhba33:C0:T0:L0"

ide1:0.present = "TRUE"

floppy0.startConnected = "FALSE"

floppy0.clientDevice = "TRUE"

floppy0.fileName = "vmware-null-remote-floppy"

ethernet0.virtualDev = "e1000e"

ethernet0.networkName = "VM Network"

ethernet0.addressType = "generated"

ethernet0.present = "TRUE"

scsi0:0.deviceType = "scsi-hardDisk"

scsi0:0.fileName = "Windows10.vmdk"

scsi0:0.present = "TRUE"

displayName = "Windows10"

guestOS = "windows9-64"

toolScripts.afterPowerOn = "TRUE"

toolScripts.afterResume = "TRUE"

toolScripts.beforeSuspend = "TRUE"

toolScripts.beforePowerOff = "TRUE"

uuid.bios = "56 4d f4 11 e7 e7 36 14-89 a5 49 69 9c ed b1 09"

uuid.location = "56 4d f4 11 e7 e7 36 14-89 a5 49 69 9c ed b1 09"

vc.uuid = "52 90 44 c9 c1 12 d9 50-67 55 c0 f9 f6 3d 65 c8"

ethernet0.generatedAddress = "00:0c:29:ed:b1:09"

vmci0.id = "-1662144247"

cleanShutdown = "FALSE"

ide1:0.allowGuestConnectionControl = "TRUE"

tools.syncTime = "FALSE"

extendedConfigFile = "Windows10.vmxf"

sched.cpu.units = "mhz"

sched.cpu.affinity = "all"

sched.cpu.latencySensitivity = "normal"

tools.upgrade.policy = "manual"

ide1:0.startConnected = "TRUE"

nvram = "Windows10.nvram"

pciBridge0.present = "TRUE"

svga.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"

hpet0.present = "TRUE"

virtualHW.productCompatibility = "hosted"

sched.swap.derivedName = "/vmfs/volumes/5721dc97-f5dd1728-a35a-00221934797e/Windows10/Windows10-8fc9b2e1.vswp"

replay.supported = "FALSE"

pciBridge0.pciSlotNumber = "17"

pciBridge4.pciSlotNumber = "21"

pciBridge5.pciSlotNumber = "22"

pciBridge6.pciSlotNumber = "23"

pciBridge7.pciSlotNumber = "24"

scsi0.pciSlotNumber = "160"

ethernet0.pciSlotNumber = "192"

vmci0.pciSlotNumber = "32"

scsi0.sasWWID = "50 05 05 61 e7 e7 36 10"

ethernet0.generatedAddressOffset = "0"

vm.genid = "-8986844904631733493"

vm.genidX = "4065389974555988378"

monitor.phys_bits_used = "42"

vmotion.checkpointFBSize = "4194304"

vmotion.checkpointSVGAPrimarySize = "4194304"

softPowerOff = "FALSE"

toolsInstallManager.lastInstallError = "0"

svga.guestBackedPrimaryAware = "TRUE"

tools.remindInstall = "FALSE"

toolsInstallManager.updateCounter = "4"

numa.autosize.vcpu.maxPerVirt

0 Kudos
a_p_
Leadership
Leadership

Either you didn't paste the complete contents, or the file has been truncated!? At least the last line in your reply is not a value pair.

What you could try is to delete the last line, which should render the .vmx file valid. However, I'd rather recommend to check what's missing by comparing the configuration (.vmx) file with the relevant entries in the .log files, and appending the missing parts to the configuration file.

If you want, compress/zip the .vmx file along with the VM's vmware*.log files, and attach (you'll find an Attach link in the lower right corner of the reply box) the .zip archive to a reply post.


André

0 Kudos