I updated the first post with more screenshots.
Re: Unable power on VM - ESXi 5.5.0
Re: Unable power on VM - ESXi 5.5.0
Yeah there's nothing wrong there. If your VM was working fine one minute and then you performed a yum update and now it won't boot, it's a problem with packages/kernel that got upgraded, not the VM's configuration that changed.
Re: Esxi 6.5 Active Directory Integration
So what group are you using as admins then?
get-vm with multiple -ne
I got multiple vms I want to ignore when selecting get-vm
vm1
vm2
vm3
vm4
get-vm | ? {$_.name -ne (get-vm vm1,vm2, vm3,vm4)}
of do I need to do it this wway?
get-vm | ? {($_.name -ne vm1) -and ($_.name -ne vm2 ......}
Re: Unable power on VM - ESXi 5.5.0
Have you made any change on vm configuration as i can see in vmware log . did you remove the disk and re add ?
see time as per vmware log
2018-01-26T11:32:48.959Z| vmx| I120: DICT | scsi0:0.fileName = VM-Linux-yspp0097-LDAP.vmdk |
2018-01-26T11:32:48.960Z| vmx| I120: DICT | scsi1:0.fileName = /vmfs/volumes/52673d7e-c347a1c2-1b79-2c59e53cc874/VM-Linux-yspp0097-LDAP-PROD/VM-Linux-yspp0097-LDAP-PROD.vmdk |
changes made here
2018-01-26T11:42:40.491Z| vmx| I120: DICT | scsi0:0.fileName = VM-Linux-yspp0097-LDAP-PROD_2.vmdk |
2018-01-26T11:42:40.491Z| vmx| I120: DICT | scsi1:0.fileName = VM-Linux-yspp0097-LDAP-PROD_1.vmdk |
current VMX file
scsi1:0.fileName = VM-Linux-yspp0097-LDAP-PROD_1.vmdk
scsi0:0.fileName = "VM-Linux-yspp0097-LDAP-PROD_2.vmdk
VM-Linux-yspp0097-LDAP.vmdk is missing here .
Re: Unable power on VM - ESXi 5.5.0
ranchuab It does not do in the VM before the update "yum". After a system update as a machine was no longer rebooting, I did the vMotion for another datastore and host.
daphnissov It is not an operating system problem, I have already opened a support ticket on RedHat in which I have been confirmed that the VM does not load the disk, so I can not enter Rescue mode to try something.
Re: download vcenter problem
If you experience issues when downloading, follow these troubleshooting steps:
The You either are not entitled or do not have permissions to download this product. Check with your My VMware Super User, Procurement Contact or Administrator. If you recently purchased this product through VMware Store or through a third-party, try downloading late
error can occur if you try to download a Datacenter Product and you are not associated with the same account as the product license. To resolve this issue, ensure you are added to the account. For more information, see How to invite new users to an account in My VMware (2070555) and How to remove a user in My VMware (2070557).
follow up below link
Re: AutoCad laggy on high end infrastructure and Nvidia GRID M60
I've honestly never changed that setting. As far as I can tell from the manual it may only apply to desktops with the PCOIP host card in them which is different than the APEX ... someone correct me if I'm wrong.
Install bootloader on SDCARD drive(/sdf) and start ESXi from /sde (HPE Microserver Gen8 specific issue)
Dear VMware gurus,
I have a HPE microserver Gen8 Xeon1220Lv2.
/sda 4tb data drive
/sdb 4tb data drive
/sdc 4tb data drive
/sdd 4tb data drive
/sde SSD drive (64gb)
/sdf SDCARD drive (2gb)
Due to the HPE's B120i SATA controller hardware limitation, if I select /sda-/sdd as a data drive, /sde SSD drive cannot be a boot drive.
To set /sda as a boot drive, I have to use B120i hardware RAID1 or RAID0.
In order to avoid from this hardware limitation, Microserver Gen8 users are often set /sdf SDCARD drive as a boot loader */boot* partition, and install root "/" partition on /sde SSD drive to install Linux.
Then, my question is how to install boot loader on /sdf and root partition on /sde for ESXi installation.
Best regards,
hidesan
Re: Activate for VMware vCenter Server Appliance 6.5
Re: Activate for VMware vCenter Server Appliance 6.5
Re: Unable power on VM - ESXi 5.5.0
There is nothing with the virtual BIOS settings for the disk. The VM settings are using SCSI disks and SCSI disks are not visible in Primary/Slave disks options in BIOS (even in physical PC/servers).
From the looks of the log, it looks like the VM is powering up and somehow the guest OS is hung.
If the yum update included patches for Spectre/Meltdown, try changing the VM hardware compatibility from 8 to 10. Version 10 is the maximum that ESXi 5.5 can support.
https://kb.vmware.com/s/article/2007240
More specifically, if the yum update include a Meltdown patch, it might be looking for the PCID feature which is not exposed to the VM in version 8 compatibility. The CPU that you have is Sandy Bridge has the PCID feature but does not have the INVPCID instruction. There is nothing we can do about that if the Meltdown patch requires the INVPCID instruction unless you have a server with Haswell CPU without EVC masking.
Re: Activate for VMware vCenter Server Appliance 6.5
change MRU to round robin
Re: download vcenter problem
in both links says :
- Hover over Accounts and select Users and Permissions.
but in my account there is no Users and Permissions
and i can't click on Accounts
Re: Activate for VMware vCenter Server Appliance 6.5
You're using the HTML5 client which doesn't have license capabilities in this release. Use the Flex client at https://<FQDN>/vsphere-client/ instead.
Re: Install bootloader on SDCARD drive(/sdf) and start ESXi from /sde (HPE Microserver Gen8 specific issue)
I don't think it's possible for you to declare where the bootloader resides versus where the other partitions ESXi creates reside. Why not just install ESXi directly on the SD card? By the way, you need a larger card than 2 GB. I'd recommend 8 GB in size. Once installed on the SD card, you can use the local SSD for whatever you want.
How to manage vms which are not a part of ha cluster
Hello all,
how to restart vm when esxi host fails which was not in a ha cluster..please anyone help me on this
Thanks & Regards
Re: Problem mounting Fusion-IO after reboot
What is the card's model, firmware version, and what driver and driver version are you using inside ESXi?
Re: How to manage vms which are not a part of ha cluster
You can either turn on autostart or login to the ESXi host manually and power on VMs.