On my Windows 10 Home I am getting an error message saying "This virtual machine requires AVX2 but AVX is not present. This virtual machine cannot be powered on."
VMWare Workstation 12.5.5
Lenovo ideapad 310
AMD A12 - 9700P RADEON R7
10 COMPUTE CORES 4C+6G
Sorry, I've been unable to stick with this ticket as more pressing matters came up.
Total speculation so far, but my gut reaction is this is probably a certificate issue. I have no evidence to support this theory, but with VMware, it's usually a good place to start.
I looked at it a little bit more today and delved a little deeper into the API. I used a Chrome extension called Postman to test the API.
For those new to this, I'll try and provide enough detail so you can reproduce:
Establish Session:
POST: https://vc/rest/com/vmware/cis/session
Authorization: Basic Auth
Username: administrator@vsphere.local
Password: <your password>
Check "Save helper data to request" (not sure if this is necessary)
Click Send
This will generate a SAML token and spit it back in a cookie -- it's not obvious in Postman, but the cookie is "vmware-api-session-id" and you can see the value in a json the POST returns.
Once you establish this authentication you can use the API documented here:
Online Documentation - vSphere Automation SDK for REST 6.5 - VMware {code}
When I use the "vcenter" or "cis" API it works fine. When I try anything under the "appliance" API it fails:
So these work:
GET: https://vc/rest/vcenter/vm
GET: https://vc/rest/vcenter/vm/vm-100
POST: https://vc/rest/com/vmware/cis/session?~action=get
These do not, and get that vapi.security.authorization.invalid error:
POST: https://vc/rest/appliance/recovery/backup/job
HEADER: Content-Type: application/json
HEADER: Accept: application/json
BODY: raw: JSON (application/json):
{ "piece":
{
"location_type":"FTP",
"comment":"Automatic backup",
"parts":["seat"],
"location":"ftp://backup/vcsa-test",
"location_user":"backup",
"location_password":"yourpassword"
}
}
GET: https://vc/rest/appliance/monitoring
The full error response in JSON is:
{
"type": "com.vmware.vapi.std.errors.unauthorized",
"value": {
"messages": [
{
"args": [],
"default_message": "Unable to authorize user",
"id": "vapi.security.authorization.invalid"
}
]
}
}
I did not see anything in the vpxd logs. When monitoring them, they didn't even appear to have a response to my attempts.
I did however stumble across this in the /var/log/vmware/applmgmt/vapi.log and vami.log. The list is the attempted GET for monitoring, and the create is the attempted POST for the backup:
2017-04-04T16:08:11.094 [3000]INFO:vmware.appliance.vapi.auth:Authorization request for service_id: com.vmware.appliance.monitoring, operation_id: list
2017-04-04T16:08:11.094 [3000]ERROR:vmware.appliance.extensions.authorization.authorization_sso:FindAllParentGroups Failed {[Errno 2] No such file or directory}
2017-04-04T16:08:11.094 [3000]ERROR:vmware.appliance.extensions.authorization.authorization_sso:FindAllParentGroups Failed {[Errno 2] No such file or directory}
2017-04-04T16:08:11.094 [3000]INFO:twisted:"127.0.0.1" - - [04/Apr/2017:16:08:10 +0000] "POST /api HTTP/1.1" 200 332 "-" "vAPI http client"
2017-04-04T16:10:50.094 [3000]INFO:vmware.appliance.vapi.auth:Authorization request for service_id: com.vmware.appliance.recovery.backup.job, operation_id: create
2017-04-04T16:10:50.094 [3000]ERROR:vmware.appliance.extensions.authorization.authorization_sso:FindAllParentGroups Failed {[Errno 2] No such file or directory}
2017-04-04T16:10:50.094 [3000]ERROR:vmware.appliance.extensions.authorization.authorization_sso:FindAllParentGroups Failed {[Errno 2] No such file or directory}
2017-04-04T16:10:50.094 [3000]INFO:twisted:"127.0.0.1" - - [04/Apr/2017:16:10:49 +0000] "POST /api HTTP/1.1" 200 332 "-" "vAPI http client
No idea if this is related, as the timing didn't seem to work out. But I did find these entries in /var/log/vmware/vapi/endpoint interesting:
2017-04-04T15:32:00.500Z | INFO | state-manager1 | DefaultStateManager | Invoking rebuild cis-api-connections-builder
2017-04-04T15:32:00.633Z | INFO | state-manager1 | ApiConnectionsCisUtil | Unsupported source (metadata) type in metadata source entry cis.common.ep.localurl : http://localhost:16666/cls/
2017-04-04T15:32:00.633Z | WARN | state-manager1 | ApiConnectionsCisUtil | Cannot find metadata source definitions in VAPI endpoint Service Endpoint of type com.vmware.cis.data.provider with protocol vapi.json.http at http://localhost:16666/cls/
2017-04-04T15:32:00.633Z | WARN | state-manager1 | ApiConnectionsCisUtil | Unable to find metadata endpoint in service Service with localization key cis.content-library.ServiceDescription and id 5e812b2e-01b8-49c7-9184-9e9782d8e86e.
2017-04-04T15:32:00.633Z | INFO | state-manager1 | ApiConnectionsCisUtil | Unsupported source (metadata) type in metadata source entry cis.common.ep.localurl : http://localhost:16666/cls/
2017-04-04T15:32:00.633Z | INFO | state-manager1 | ApiConnectionsStateBuilder | Cannot resolve protocol priorities between the following services. Will use the first one.
First: 5e812b2e-01b8-49c7-9184-9e9782d8e86e\com.vmware.cis.cls.vapi at http://vc:80/cls/
Second: 5e812b2e-01b8-49c7-9184-9e9782d8e86e\com.vmware.cis.cls.vapi at http://localhost:16666/cls/
2017-04-04T15:32:00.633Z | INFO | state-manager1 | ApiConnectionsCisUtil | Unsupported source (metadata) type in metadata source entry cis.common.ep.localurl : http://localhost:16666/cls/
2017-04-04T15:32:00.633Z | WARN | state-manager1 | ApiConnectionsCisUtil | Cannot find metadata source definitions in VAPI endpoint Service Endpoint of type com.vmware.cdc.provider with protocol vapi.json.http at http://localhost:16666/cls/
2017-04-04T15:32:00.633Z | WARN | state-manager1 | ApiConnectionsCisUtil | Unable to find metadata endpoint in service Service with localization key cis.content-library.ServiceDescription and id 5e812b2e-01b8-49c7-9184-9e9782d8e86e.
2017-04-04T15:32:00.633Z | INFO | state-manager1 | ApiConnectionsCisUtil | Unsupported source (metadata) type in metadata source entry cis.common.ep.localurl : http://localhost:10080/invsvc/vapi
2017-04-04T15:32:00.633Z | INFO | state-manager1 | ApiConnectionsCisUtil | Unsupported source (metadata) type in metadata source entry cis.common.ep.localurl : http://localhost:8900/vmonapi
2017-04-04T15:32:00.633Z | INFO | state-manager1 | ApiConnectionsCisUtil | Unsupported source (metadata) type in metadata source entry cis.common.ep.localurl : http://localhost:9090/ds/vapi
2017-04-04T15:32:00.634Z | WARN | state-manager1 | ApiConnectionsCisUtil | Cannot find metadata source files/URLs in VAPI endpoint Service Endpoint of type com.vmware.vapi.endpoint with protocol vapi.json.http at http://vc:80/site/api
2017-04-04T15:32:00.634Z | WARN | state-manager1 | ApiConnectionsCisUtil | Unable to find metadata endpoint in service Service with localization key cis.vapi.endpoint.serviceDescriptionResourceKey and id e0cc58e8-7ce4-48f9-9426-61648da55b2d.
2017-04-04T15:32:00.634Z | INFO | state-manager1 | ApiConnectionsCisUtil | Unsupported source (metadata) type in metadata source entry cis.common.ep.localurl : http://localhost:12346/site/api
2017-04-04T15:32:00.634Z | WARN | state-manager1 | ApiConnectionsCisUtil | Cannot find metadata source definitions in VAPI endpoint Service Endpoint of type com.vmware.vapi.endpoint with protocol vapi.json.http at http://localhost:12346/site/api
2017-04-04T15:32:00.634Z | WARN | state-manager1 | ApiConnectionsCisUtil | Unable to find metadata endpoint in service Service with localization key cis.vapi.endpoint.serviceDescriptionResourceKey and id e0cc58e8-7ce4-48f9-9426-61648da55b2d.
2017-04-04T15:32:00.634Z | INFO | state-manager1 | DefaultStateManager | Invoking rebuild vim-adapter-settings-builder
2017-04-04T15:32:00.709Z | INFO | state-manager1 | DefaultStateManager | Invoking rebuild vapi-vcenter-servlet-builder
2017-04-04T15:32:00.710Z | INFO | state-manager1 | DefaultStateManager | Invoking rebuild api-interfaces-builder
2017-04-04T15:32:00.727Z | INFO | state-manager1 | DefaultStateManager | Invoking rebuild metadata-sync-builder
My apologies! I missed that in your first post. As I understand, if you don't have an active license for the product, you will receive those entitlement errors you are getting.
I think I found the file that is generating the errors in applmgmt/vapi.log. The file is:
/usr/lib/applmgmt/lib/extensions/py/vmware/appliance/extensions/authorization/authorization_sso.py
def getGroups(self, user):
"""
Return groups containing (directly or via nested groups) user.
@type user: str
@param user: A user name.
@rtype: str[]
@return: Array of groups (empty array if user does not exist).
"""
dom = self._systemDomain
userId = Sso.PrincipalId()
userId.name,userId.domain = utils.decomposePrincipal(user, dom)
try:
grpIds = self.groupcheck.groupCheckService.FindAllParentGroups(userId)
except Sso.fault.InvalidPrincipalFault, e:
# Ignore invalid users.
logger.error("FindAllParentGroups Failed {%s}" % str(e))
return []
except vmodl.fault.InvalidArgument, e:
# Ignore empty user names.
logger.error("FindAllParentGroups Failed {%s}" % str(e))
return []
except Exception as e:
logger.error("FindAllParentGroups Failed {%s}" % str(e))
return []
return [utils.generatePrincipal(g.name, g.domain, dom) for g in grpIds]
Haven't found the "FindAllParentGroups" method yet, but I could try throwing in some more logging to see what userId looks like when it's called.
Thanks for the reply.
Raid controller is only a b120i software and no cache. Upgrading to a p222 is on the list at some point down the line But will invest in an SSD for my vm store and use my cold store for Application date perhaps.
Thanks again.
Pete
I could not find any sample scripts for that in the vSphere 6.5 Documentation Library, but these are cmdlet documentation pages you might want to look at:
Get-VMHost (http://pubs.vmware.com/vsphere-65/index.jsp?topic=%2Fcom.vmware.powercli.cmdletref.doc%2FGet-VMHost.html)
Get-VMHostAuthentication (http://pubs.vmware.com/vsphere-65/index.jsp?topic=%2Fcom.vmware.powercli.cmdletref.doc%2FGet-VMHostAuthentication.html)
Set-VMHostAuthentication (http://pubs.vmware.com/vsphere-65/index.jsp?topic=%2Fcom.vmware.powercli.cmdletref.doc%2FSet-VMHostAuthentication.html)
-LeaveDomain (in book below but not on current cmdlet list, might be deprecated)
-NewVMHostAccount (http://pubs.vmware.com/vsphere-65/index.jsp#com.vmware.powercli.cmdletref.doc/index-all_cmdlets.html)
-RemoveVMHost (http://pubs.vmware.com/vsphere-65/index.jsp?topic=%2Fcom.vmware.powercli.cmdletref.doc%2FRemove-VMHost.html)
If you have this book or can access Safari Books [Sellers, Philip. (2015). PowerCLI Cookbook. Birmingham: Pakt Publishing.], section "Joining an ESXi host into Active Directory" on page 7 goes into this a bit, although I'm not sure it's exactly what you're looking for. It says that you need to use 'Getting readyPowerCLI' which has Get-VMHostAuthentication and Set-VMHostAuthentication (linked above). Then you will open PowerCLI to connect to a single host. You would use Get-VMHost for that (also linked above).
Excerpt:
Because the cmdlets require a VMHost object you'll again be using Get-VMHost to either populate a variable or to pipe an object to the next object. The first step is to obtain a VMHost object for our target ESXi host. This can be done using the following command:
$esxihost = Get-VMHost 192.168.0.241
Once you have your VMHost object, you can look at setting up the authentication. The Set-VMHostAuthentication cmdlet needs to be executed. The cmdlet requires several parameters to join an ESXi host to the domain. The syntax needed is displayed as follows:
$esxihost | Get-VMHostAuthentication | Set-VMHostAuthentication - joinDomain -Domain domain.local -user username -password
From here, executing the cmdlet will prompt you to confirm that you want to join this host to the domain specified. If your answer is Y, as is default, the cmdlet will and execute it. It goes on to add that:
The same cmdlets can also be used to remove a host from a domain, if needed. The -LeaveDomain parameter is a part of the Set-VMHostAuthentication cmdlet and allows this need. In addition to setting u an ESXi host to accept Active Directory authentication, PowerCLI also provides a number of cmdlets to add local users, groups, and permissions inside a single ESXi host. The New-VMHostAccount cmdlet is used to create new users on an ESXi system. The same cmdlet previously allowed the creation of groups, but this functionality was removed with ESXi 5.1. There is a Set-VMHostAccount cmdlet to change accounts and group memberships, and a Remove-VMHostAccount cmdlet to remove a user or a group.
The issues being reported here are interesting to us, I can't seem to replicate this on any of my systems with multiple monitors (including a 4K display).
Product stability is a main focus for us, but it has been getting more and more complicated over the years as Apple continues to make back-end architecture decisions that impact our product, and as the complexity of user setups increase.
On vanilla hardware/OS of course things work fine, but it's impossible for us to test with every known configuration that a user or groups of users might have. When we do figure something out, we put it in our automated test suite so that we never regress back to that faulty state when we're merging new code into the source tree and building the products.
For instance, Apple introduced something where having VirtualBox installed at the same time as Fusion can cause unexpected behaviour and that wasn't something that we tested with because it seems obvious that one app being installed shouldn't interfere with another app. With software as complicated as virtualization, and with the complexity of user setups only increasing, and the Host OS making decisions that are outside our control or awareness, it's really important we capture these events so we can get to fixing them.
In that vein, I would encourage folks who are stuck with this to please file a support request so we can capture logs, analyze and either figure out the right remediation course.
If for whatever reason Support isn't open to you, send me a PM and I'll help.
At the end of the day, we just want to build software that adds value to your lives, and that includes working with our users in reducing the frustration that goes with it when something doesn't work as we expect.
I am getting this error to Run VCSA setup from Windows 2012R2. I already installed Client Integration Tools as well but still couldn't run the setup.
SRM 6.0 does integrate with SDRS (see: SRM 6 and vSphere 6 Storage DRS (SDRS) Improvements for Array Based Replication – BenMeadowcroft.com )
If your array doesn't support CGs (that seems strange, what array is that if you don't mind sharing?) then the above feature won't be that helpful and you're right, you probably just turn off SRDS.
I have tried this with two different vm's, when they are playing music, if I select realtek HD audio as the output device (which isn't connected to any headphones so I can't hear the audio), I can see the audio playing in the volume mixer, however when I select my headset as the output device there is no sound or output in the volume mixer.
Any help, thanks.
Yes, you are correct. In VMware-speak:
ingress: Traffic is going into the vDS from the VM.
egress: Traffic is going out to the VM from the vDS.
"Within a standard vSwitch, you can only enforce traffic shaping on outbound traffic that is being sent out of an object--such as a VM or VMkernel port--toward another object. This is referred to by VMware as "ingress traffic" and refers to the fact that data is coming into the vSwitch by way of the virtual ports. Later, we cover how to set "egress traffic" shaping, which is the control of traffic being received by a port group headed toward a VM or VMkernel port, when we start talking about the distributed switch in the next chapter."
Source: Wahl & Pantol. (2014). Networking for VMware Administrators. Palo Alto: VMware Press.
However, VMware's definition of this stops at the virtual switch. Per the vSphere 6.5 documentation: "The traffic is classified to ingress and egress according to the traffic direction in the switch, not in the host" (http://pubs.vmware.com/vsphere-65/index.jsp#com.vmware.vsphere.networking.doc/GUID-964F5A21-0B53-468A-8A05-B71AA91F8A31.html?).
In Cisco-speak:
ingress: Traffic moving out of a physical interface.
egress: Traffic moving into a physical interface.
But this means you are also right, because moving past VMware's definition and into Cisco's it's still the same direction. Therefore, ingress is VM > vSwitch > physical switch, and egress is physical switch > vSwitch > VM.
I need support for this case...
Hi everyone,
I am hitting a wall with ESXi install on a UCS C220 M3S. I have tried the 6.0.2 and 6.5 custom images and the vanilla 6.5 ISOs with the same results.
The main thing I had to check for is that the SW RAID controller was disabled (and it was). I cannot think of anything else that would make this installation fail. I have multiple SAS drives that are all online, so not sure what is going on here.
From the HCL, the platform is supported (we have a few other servers that are running fine). Any thoughts guys? Thanks for your help.
Did you tried disable the IE Enhanced Security Configuration (IE ESC)? If not, disable that on Server Manager, close you browser and try again.
In my vcsa, it says I have a valid license for "VMware vCenter Server 6 Standard".
So now, how can I update it to 6.5 b ?
How can I download the 6.5 b update from my.vmware ? Cause I can't now even if I have a valid license .
Should I add the license key to "Product Registration" ? Cause there it says it's not a valid license.
Hello all,
I have a setup with 2 vCenter Servers configured in linked mode through external PSC. I am trying to figure out how to list all vCenter Servers in my setup and also perform some operations on both vCenter Server's object. Can this be done using vSphere SDK or should I be looking at some different SDK?
Will be very helpful if someone can give me some pointers. Thank you!!
Automatic unattended installation of Linux guest OSes on EFI firmware is not currently supported. Sorry.
It should be possible to manually construct a kickstart/autoinstall/unattended-install disc/disk and use that for automating deployment in the same way as one would do on a physical machine. Refer to your OS vendor for instructions on how to construct such a kickstart/autoinstall/unattended-install medium, or launch an Easy Install of the OS using BIOS, interrupt the installation before it gets started, inspect the autoinst.flp or autoinst.iso we've attached to the VM, and use that as a starting point for experimentation. Whatever procedure the OS vendor provides should work the same in a virtual machine as it does for a physical machine.
Cheers,
--
Darius
Hi,
I didn't try this. Will do and update you with result. Further did I need to update Internet Browser?
Thanks,
Wondering if there is some insight on this -
I deploy a simple Edge (either within an org vDC, or create a new org with an edge in the configurator).
This is what the resulting error is within vDc -
However, it creates the Edge Gateway in NSX (vCenter)?
This was created using the 'compact method'.
I'm not sure how the uuid's should relate in those messages, if they should at all - and not sure which logs will be useful.
Please advise-
Thanks-
P
Hi,
When trying to export an ovf template, iso or vmdk files download and the process gets stuck at 25%
Also unable to select OVA (only option available is OVF)
Environment is :
VCentre :Version 6.5.0 Build 4602587
ESXi: VMware ESXi, 6.5.0, 4564106
Any help will be really appreciated