I mean how to restart those vms on another host
↧
Re: How to manage vms which are not a part of ha cluster
↧
Re: How to manage vms which are not a part of ha cluster
If it's not in an HA cluster, essentially you don't (automatically). If the VMs reside on storage which is shared with at least one other ESXi host, you can manually unregister them from the source host, register them on the destination, and power them up on the destination.
↧
↧
Re: Unable power on VM - ESXi 5.5.0
daphnissov I made the change, but it did not work.
Any more tips before telling the company that I lost a machine from the production environment?
↧
Re: Unable power on VM - ESXi 5.5.0
Can you show the VMX file at this point? Or just take a screenshot under edit settings with the hard drives expanded.
↧
Re: How to manage vms which are not a part of ha cluster
Thanks alot on this ..
↧
↧
Re: How to manage vms which are not a part of ha cluster
Does this answer your question?
↧
Re: Does Fusion 6 works with MacOS 10.12.6?
Thank you both for your answers.
On my MacOS 10.12.6 Fusion 6 does start and seems to work until the point when I try to start existing or install new virtual machine.
I guess I'm out of luck. Fusion 6 is not eligible for upgrade to version 10. And I cannot even try Fusion 10 evaluation. After installing it the window shows 0 days left for evaluation.
J.
↧
Re: Unable power on VM - ESXi 5.5.0
daphnissov Is that what you wanted to see?
↧
Re: Unable power on VM - ESXi 5.5.0
Yes, ok. Just to reduce complexity here, remove the the ISO from your CD-ROM's configuration. It's a VMware tools ISO that's still mounted and shouldn't be.
I want to understand the course of events here. Exactly what steps were taken between when this VM was booting and when it wasn't? Was it only a yum update and nothing more? You didn't reconfigure the VM? You did nothing else? Please be as specific as you can while I look through your log files.
↧
↧
Passing username password to Operations Manager Console Login
Hi,
I want to pass username and password to the Operations Manager Console to do an automatic login? I haven't found any documentation or information to do that. Maybe someone has done something similar and could give me a hint?
Thanks,
Michael
↧
Re: Unable power on VM - ESXi 5.5.0
daphnissov The CD-ROM is not mounted or connected.
I just did the OS update procedure by running the yum update command and nothing more, after this procedure that the mentioned fault occurred.
As the machine was slow to start, I entered her console and it was all black.
↧
Re: Unable power on VM - ESXi 5.5.0
What's confusing here is that you seem to only have one VMDK in your VM's configuration, then you power it down and have 2 VMDKs and neither of which, according to the file name, corresponds to the first. So on what date and time did the VM first stop booting correctly?
As late as this time stamp (found in vmware-55.log), you only appear to have one VMDK.
2018-01-26T11:32:48.959Z| vmx| I120: DICT scsi0:0.fileName = VM-Linux-yspp0097-LDAP.vmdk
But thereafter, you now have two (vmware-56.log and vmware.log)
2018-01-26T11:42:40.491Z| vmx| I120: DICT scsi0:0.deviceType = scsi-hardDisk
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 sched.scsi0:0.shares = normal
2018-01-26T11:42:40.491Z| vmx| I120: DICT sched.scsi0:0.throughputCap = off
2018-01-26T11:42:40.491Z| vmx| I120: DICT scsi0:0.present = TRUE
2018-01-26T11:42:40.491Z| vmx| I120: DICT ethernet0.virtualDev = e1000
2018-01-26T11:42:40.491Z| vmx| I120: DICT ethernet0.networkName = LAN
2018-01-26T11:42:40.491Z| vmx| I120: DICT ethernet0.addressType = generated
2018-01-26T11:42:40.491Z| vmx| I120: DICT ethernet0.generatedAddress = 00:0c:29:2e:94:b5
2018-01-26T11:42:40.491Z| vmx| I120: DICT ethernet0.present = TRUE
2018-01-26T11:42:40.491Z| vmx| I120: DICT scsi1:0.deviceType = scsi-hardDisk
2018-01-26T11:42:40.491Z| vmx| I120: DICT scsi1:0.fileName = VM-Linux-yspp0097-LDAP-PROD_1.vmdk
2018-01-26T11:42:40.491Z| vmx| I120: DICT sched.scsi1:0.shares = normal
2018-01-26T11:42:40.491Z| vmx| I120: DICT scsi1:0.present = TRUE
So if this VM worked fine up until it was booted at 1/26 11:42, then someone changed the VM's configuration. I want to understand the chain of events leading up to this, because a yum update inside the guest OS has no power to make such a configuration change.
↧
Re: Unable power on VM - ESXi 5.5.0
It is a bit strange to see CPUID masks in the vmx configuration file (especially those with .amd).
hostCPUID.0 = "0000000d756e65476c65746e49656e69"
hostCPUID.1 = "000206d70020080017bee3ffbfebfbff"
hostCPUID.80000001 = "0000000000000000000000012c100800"
guestCPUID.0 = "0000000d756e65476c65746e49656e69"
guestCPUID.1 = "000206d200020800969822031fabfbff"
guestCPUID.80000001 = "00000000000000000000000128100800"
userCPUID.0 = "0000000d756e65476c65746e49656e69"
userCPUID.1 = "000206d700200800169822031fabfbff"
userCPUID.80000001 = "00000000000000000000000128100800"
cpuid.80000001.eax.amd = "--------------------------------"
cpuid.80000001.ebx.amd = "--------------------------------"
cpuid.80000001.ecx.amd = "--------------------------------"
cpuid.80000001.edx.amd = "-----------H--------------------"
cpuid.80000001.eax = "--------------------------------"
cpuid.80000001.ebx = "--------------------------------"
cpuid.80000001.ecx = "--------------------------------"
cpuid.80000001.edx = "-----------H--------------------"
The guestCPUID.1 and userCPUID.1 looks like are masking out some capabilities from the guest OS including PCID.
The easiest would be to just put a # in front of guestCPUID.1 and userCPUID.1 and try to power up. Sorry I don't have the time and patience to examine bit-by-bit to detail the differences in CPU features but looks like PCID capability is masked out.
hostCPUID.1. ecx = 17bee3ff
vs
guestCPUID.1 ecx = 96982203 = 1001:0110:1001:1000:0010:0010:0000:0011
The hex 8 above is bits 19 - 16: = 1000
Bit 17 ecx = 0 means PCID is masked out
↧
↧
Re: Unable power on VM - ESXi 5.5.0
daphnissov as far as I was with a RedHat engineer remotely, he asked me to change the SCSI control type from "LSI Logic Parallel" to "Vmware Paravirtual."
I do not know if this could have caused the name change of VMDK. But even changing the controller type continued with the same problem.
↧
Re: Clean up "Other" objects?
Hello Mario,
+----------------------------------------------------------------------------------------------------------+---------+---------------------------+
| Unassociated objects | | |
| d6107259-8e9b-9dc1-9e10-246e963c74a8 < valid vSAN StatsDB | | 3/3 |
| aa1a7259-b4f2-55c6-ecf2-246e963c74a8 < namespace AKA vsan-loadtest-debug-8a949a26-5e95-4ce1-b358-92ae23b138a7-dh-vhost00***** | 3/3 |
| ad1a7259-6765-a6e1-f342-246e963c74a8 < vmdk AKA vmdk '8a949a26-5e95-4ce1-b358-92ae23b138a7-dh-vhost00*****-0.vmdk' | 11/11 |
| ad1a7259-1a3d-c1f9-2cbf-246e963e72f0 < vmdk AKA 8a949a26-5e95-4ce1-b358-92ae23b138a7-dh-vhost01*****-0.vmdk | 11/11 |
| 2c1f6a5a-6799-bcfb-19d4-246e963c74a8 < valid VM - .vswp file | | 3/3 |
+----------------------------------------------------------------------------------------------------------+---------+---------------------------+
As I was saying - you can likely fully remove 'ad1a7259-6765-a6e1-f342-246e963c74a8' AKA '8a949a26-5e95-4ce1-b358-92ae23b138a7-dh-vhost00*****-0.vmdk' by using delete in the datastore browser and the namespace Object (aa1a7259-b4f2-55c6-ecf2-246e963c74a) also, do this after removing the vmdk Object.
It is possible to delete any using Objects using Objtool delete, including 'vdisk' Objects that exist on vsandatastore but are not (currently) associated with a .vmdk descriptor nor namespace (perhaps this was removed before the vdisk was fully removed) - this is of course permanent and irreversible so make sure you are using the correct Object UUIDs (ad1a7259-1a3d-c1f9-2cbf-246e963e72f0 here).
Bob
↧
Re: Unable power on VM - ESXi 5.5.0
bluefirestorm thanks your time and patience, in which file should I change these parameters?
↧
Re: Unable power on VM - ESXi 5.5.0
I asked when this VM first stopped booting correctly. Do you have that information?
Also, get to an SSH session and cd to the directory with your VM's files. Show output of ls -lh.
↧
↧
Re: Unable power on VM - ESXi 5.5.0
Also, I was mistaken here. You appear to have two VMDKs from the outset. The first is named VM-Linux-yspp0097-LDAP.vmdk and the second is VM-Linux-yspp0097-LDAP-PROD.vmdk. Note the addition of "PROD" on the end. It appears that the first file may have been renamed to _2 and the second file named to _1. Please show output in the VM's home directory of all files.
↧
Re: Passing username password to Operations Manager Console Login
You'll need to use the vIDM appliance which allows for SSO and credentials pass-through.
↧
Re: Newly deployed PSC appliance setup is stuck at 40%
I found my issue. The new hosts that were built with 6.5 U1e did not have NTP running. This caused the config setup to stop at 60% (session timed out). Doh! This was even after I used static NTP during the config process of the PSC.
Lesson learned make sure your hosts have NTP configured and running before trying to build your vsphere environment.
↧