vxprthu's Posts

This is a desktop pc, direct esxi install/run is not supported. You may try to add a compatible  PCI Network card, or try the community network driver. But i recommend to install a windows and use vmware workstation.

HI, There could be many reasons for your issue, but it looks driver issue. (if we assume that have network card in your machine) First, please check that your hardware is on the compatibility list (link was already shared before) Second, if the server is on the list, and you are aware of the hardware vendor, please download and use the vendor specific esxi installer image. It can be downloaded from VMware or the vendor site as well. Third, if the hardware is not supported, you may try the community nic driver from flings site. Otherwise, please share more details for better understanding you environment.

HI,   As far as i know, this is a workstation grade machine, therefore it has no IDRAC/IPMI feature installed. Even though you can run ESXi on, this hardware is not on the ESXI supported hw list. Probably you can use this machine as only compute resource without benefits of a dedicated server hardware. Not knowing the cpu and system temperature has no effect on the performance/life. You just need to be careful to the assigned resources to the vms and not overprovisioning (too much) If you decide to move to hosted virtualization (like WIN/LNX + VMware Workstation) then you can use third party monitoring tools like CoreTemp or others. I'm also using a Dell 7810 for homelab with WIn10+Workstation, and it works well. The vents speeds up when necessary.   Cheers,  

HI, You can add the dell driver repository to the upgrade manager as well: Then you can create baseline for the hardware drivers and update with the regular patches: Lifecycle Manager » Settings » Administration » Patch Setup » New https://vmwaredepot.dell.com/index.xml   Cheers

Hey, You can check the following log files on the esxi host to figure out what caused the reboot/psod: /var/log/vobd.log /var/run/log/hostd.log /var/log/vmksummary.log /var/run/log/shell.log  Also, if the host is rebooted after the psod just change back the  Misc.BlueScreenTimeout parameter's value to 0 in the host's advanced settings. In CLI you can check the vaule with the following command: esxcfg-advcfg -g /Misc/BlueScreenTimeout Regards,

HI, It is part of the booting process, not exactly the source of the issue. Could you please share the event log of the power on process, and in the meantime check other things, like available space on the datastore what has affect on booting the vm?   cheers,

Hey, Regarding the value of blue screen timeout: If the value is different than 0, then ESXi reboots automatically after the purple screen. I also recommend to check the /var/log/vobd.log file on the esxi host. This one is very easy to understand. If there is nothing in it you can check the followings as well. /var/run/log/hostd.log /var/log/vmksummary.log /var/run/log/shell.log   Cheers,

HI, The delay or timeout can be extended in the advanced system configuration options of the esxi hosts. Host » Configure » System » Advanced System Settings You should look for Misc.BlueScreenTimeout. It's value 0 by default which means no timeout. I think the maximum value is (or was) 65535 seconds which is around 18 hours. Cheers, 

HI, Even though he asked only for the folder, the files will not be renamed. Therefore he had to unregister the vm, rename the folder, rename all of the files, update vmx if necessary then re-register vm. To complete the process all of the steps must be performed, not just renaming a folder. I've tried to give a complete solution instead the one which looks faster but it may cause more complication. Or you think that renamed folder with old filenames is a good solution? However this is a known issue since ages, so this is something should be fixed by now... From another way, It also about skillset too, because you may know how to use cli and other tools, and you know what to do exactly but not everyone. (i'm not talking about myself). This is why this forum exists, to get help. Usually there are multiple answer for a question, and since you/me are not know the one who asked we have to try to follow the official way, and not cause more problems to the user.  As a final thought, I understand what are you saying and i agree. But try to see this from a different angle. If someone asking "How to rename a folder" are you sure he/she will be able to follow your process?   AJ.    

HI @continuum  Please don't forget that, you may have different skill set than the requestor has. Something could be easy for you while others are struggling with it. You can see an easy nfs mount is difficult, don't you think unregister/winscp/rename... tasks could be more difficult?  

Hi, Thanks for the images. Can you please be sure nfs v3 is enabled (we dont need nfs v4, so you can uncheck that) And can you please add IP/Netmask of your esxi host to the Allowed IP field instead of  a "*"   Thanks,