I think you would be fine using the SATA bus for just a RAID 1 of 2 SSD drives. That should give you plenty of throughput (6 Gb/s) for a small environment without having to worry about NVMe compa...
See more...
I think you would be fine using the SATA bus for just a RAID 1 of 2 SSD drives. That should give you plenty of throughput (6 Gb/s) for a small environment without having to worry about NVMe compatibility. Just my 2 cents.
Turns out this was the issue. Although I am fairly confident we had edited this file once already. VMware Knowledge Base After adding the line HOSTNAME=fqdn then restarting services I could log...
See more...
Turns out this was the issue. Although I am fairly confident we had edited this file once already. VMware Knowledge Base After adding the line HOSTNAME=fqdn then restarting services I could log in via https://fqdn:9443
I did just notice that when logged into the VCSA web console port 5480, the 'Network' tab lists the name of the device but not the FQDN. When I go to the 'Address' tab it will not allow me to edi...
See more...
I did just notice that when logged into the VCSA web console port 5480, the 'Network' tab lists the name of the device but not the FQDN. When I go to the 'Address' tab it will not allow me to edit the name to be the FQDN. I go to save it and it says it can't be saved
I just started getting this error when trying to connect to the web console of one of our vCenter VCSAs. It had worked fine previously. I am unaware of any configuration changes since the last ti...
See more...
I just started getting this error when trying to connect to the web console of one of our vCenter VCSAs. It had worked fine previously. I am unaware of any configuration changes since the last time this worked (within the past couple of weeks). I found this article VMware Knowledge Base and what I found unusual is that in regards to this "/etc/init.d/vmware-sso restart" I don't have the 'vmware-sso' file in the init.d directory. I have the other 2 files, and can restart like the article mentions (our vCenter isn't connected to AD). I've done the certificate regeneration already. I continue to get the same error. I've made sure the hostname is correct using the /opt/vmware/share/vami/vami_config_net command, and also when logged into port 5480 of the web console the hostname is correct. Any ideas?
But again, I'm just providing the platform. We don't provide support into their OS. I was just making the point that between our cloud and public cloud, a customer doesn't have to worry about wh...
See more...
But again, I'm just providing the platform. We don't provide support into their OS. I was just making the point that between our cloud and public cloud, a customer doesn't have to worry about who they are sharing their host with. I personally don't see how anyone sleeps at night when they're on a public cloud. As far as the risk, the exploits are able to see into the caches of the processors, so they can intercept all data being processed which includes intercepting passwords, etc. The exploits don't just see the data from their guest OS.
From everything I've read, what you just described is the main threat of these vulnerabilities. Customer A has a VM running on the same host as Customer B, and an exploit could intercept data at...
See more...
From everything I've read, what you just described is the main threat of these vulnerabilities. Customer A has a VM running on the same host as Customer B, and an exploit could intercept data at the processor level. I work on a private cloud, so our customers don't have to worry in this regard since they don't share their blades with anyone. If someone gets access to their guest VMs, they have bigger things to worry about than Meltdown and Spectre
The Zerto solution worked great. Our customer is back up and running. vCenter is showing that VMtools are out of date, so we're scheduling an outage to upgrade those. I didn't see your response b...
See more...
The Zerto solution worked great. Our customer is back up and running. vCenter is showing that VMtools are out of date, so we're scheduling an outage to upgrade those. I didn't see your response before we did the migration. We used our traditional naming convention, and there doesn't appear to be any issues. Backups are a pain to get going because of all the data needed for the initial seed.
Hello, We're moving a customer from their on-prem environment to our cloud platform. They are running ESX 5.5 Update 1 (1623387) and our environment is 5.5 Update 3a (3116895) We don't real...
See more...
Hello, We're moving a customer from their on-prem environment to our cloud platform. They are running ESX 5.5 Update 1 (1623387) and our environment is 5.5 Update 3a (3116895) We don't really want to put them on 5.5 Update 1 because there are many bug fixes in 5.5 Update 3a that are important to have. We're backing up the VMs using Asigra, then restoring to our environment and using Zerto to capture changes until the go-live. It's basically a 1-way DR failover to our infrastructure. We're just vetting out any problems putting the VMs onto our hosts with a different version of ESXi. Any htoughts are appreciated. Oh, and I believe we are also using a new install of vCenter on our side also.
The KB article indicates that the problem relates to quiescing the OS immediately after a restart or after boot. Is that what you all experience? I have several instances in my 'events' list for...
See more...
The KB article indicates that the problem relates to quiescing the OS immediately after a restart or after boot. Is that what you all experience? I have several instances in my 'events' list for a SQL guest where it will finally successfully create the snapshot after several failed attempts.
Yes, I would check disk management. If anyone else has access to the environment perhaps they went in and shrank the disk in Windows or something. Make sure there is no unallocated space showing.
How many spindles do you have and what brand/model of 7200 RPM drives are they? Onboard cache can make a slight difference as well as the model of drive. Not all 7200 RPM SATA drives are created...
See more...
How many spindles do you have and what brand/model of 7200 RPM drives are they? Onboard cache can make a slight difference as well as the model of drive. Not all 7200 RPM SATA drives are created equal.
When you think about it, it makes sense. In 5.5 you can only have FT enabled with 1 vcpu, so it does no good to have vcpu hotadd enabled. And apparently with vcpu hotadd enabled it does not use N...
See more...
When you think about it, it makes sense. In 5.5 you can only have FT enabled with 1 vcpu, so it does no good to have vcpu hotadd enabled. And apparently with vcpu hotadd enabled it does not use NUMA, but instead reverts back whatever came before NUMA. I can't remember what it's called.
I worked with a VCE tech today and he said "The hosts are experiencing heap exhaustion in relation to the vmkStateLogger (FT)." We also have vcpu hotadd turned on for the FT guests which is not a...
See more...
I worked with a VCE tech today and he said "The hosts are experiencing heap exhaustion in relation to the vmkStateLogger (FT)." We also have vcpu hotadd turned on for the FT guests which is not a supported configuration. He had a hard time digging up information himself, but the high VMWAIT times cannot be attributed to anything they would normally point to like storage i/o latency. Our first course of action he wants us to try is turning off 'vcpu hotadd' for the guests. This will require us getting a maintenance window from the customer, so I am not sure how soon this can be done.