I have 2 instances of ESXi host and vCenter. I installed VIX API package on my Ubuntu 16.04 and tried to clone a VM. To do it i used the sample from documentation.
Unfortunately, my program crashes with this message after executing the code below (connection to host and opening vm processes work properly):
"The operation is not supported for the specified parameters"
The code:
jobHandle = VixVM_Clone(vmHandle,
VIX_INVALID_HANDLE,
VIX_CLONETYPE_FULL,
"[datastore1] mytemp-21_linked/mytemp-21_linked.vmx",
0,
VIX_INVALID_HANDLE,
NULL,
NULL);
Worth noting, in the doc sample VIX_SERVICEPROVIDER_VMWARE_WORKSTATION host type is used, by i've not found any info about restrictions for ESXi and vCenter (VIX_SERVICEPROVIDER_VMWARE_VI_SERVER type) and it should be supported too.
What's wrong with my call?
Also, I saw something similar there, but there are quite bad description of the problem.
Clone from VIXAPI operation is NOT supported under VMware Server. I faced the same issue, while connecting to the host, the host-type should be set and connected through VIX_SERVICEPROVIDER_VMWARE_WORKSTATION.
You can find the full compatibility matrix at here, or under Requirements in the support document as you listed above where it mentions: "VMware Workstation 6.5 (not supported on VMware Server)"
As YSK mentioned in the comments above this is the last VIX SDK release supported for vSphere. A set of VIX Guest Operation APIs have been integrated in vSphere WebServices SDK. Here is an article from VMware on how to migrate to vSphere SDK: https://www.vmware.com/support/developer/vix-api/guestOps50_technote.pdf
Related
We have installed VisualSVN server 3.5 on windows server 2012 r2. When we browsing the repository in the VisualSVN Server Manager, WMI provide host process has started and it uses the very very less cpu usage(4%) even overall CPU usage is less(20%). This means WMI is very slow in background.
we have the script to set the VisualSVN permission using WMI, this WMI query also failed with unknown cause.
Please, describe the issue in detail. It is hard to tell what the root cause is from the current issue summary. Checking VisualSVN Server logs and Windows Application / System / WMI logs can help.
Note that you can always contact support#visualsvn.com for assistance.
we have the script to set the Visual SVN permission using WMI, this
WMI query also failed with unknown cause.
Try the *-SvnAccessRule PowerShell cmdlets such as Get-SvnAccessRule, Add-SvnAccessRule and Set-SvnAccessRule. The access rule management cmdlets help you automate permission management, perform permission modifications in batch and generate permission reports.
IMPORTANT: VisualSVN Server 3.5.x release family is out of support since February 28, 2018. 3.5.x release family does not receive patch updates. Please, plan to upgrade your VisualSVN Server instance to the latest version, VisualSVN Server 3.9. Read the article KB138: Upgrading to VisualSVN Server 3.9 before beginning the upgrade. For the complete list of changes between version 3.5 and 3.9, take a look at the changelog.
I know VMware has provided the support for HTML5 based client to manage the VMware host.
We want to use vSphere client6.0 to manage VMware ESxi 6.5u1.
I have one vSphere client with version 6.0 and two ESXi server with version6.5 and 6.5u1.
I have observed the below behavior of vSphere client and ESXi server.
I am able to access VMware 6.5 with vSphere client6.0
I am unable to access ESxi6.5u1 with vSphere client6.0 . It give me options for run installer or Save installer.
Can you please reply on my below queries?
if a can open ESXi6.5 with vSphere client6.0 then why i cannot open ESXi 6.5u1??
Where VMware has documented the compatibility of vSphere client with ESXi server?
Thanks in advance!!!
The compatibility matrix for the vSphere thick client is located here: http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php#interop&24=&1=
I believe the thick client being operational with 6.5 ESXi hosts was a bug, and it was resolved in 6.5U1.
Also, be aware that the thick client has been deprecated and will no longer be available on future versions of vSphere: https://blogs.vmware.com/vsphere/2016/05/goodbye-vsphere-client-for-windows-c-hello-html5.html
I am using the free version of vmWares vSphere Hypervision 6.
The problem I have is that I want to use the Management API.
I want to start and stop vm's and also take and reset to snapshots via scripts but the API is read-only for the free version.
I used the sample scripts from https://github.com/vmware/pyvmomi
The scripts with write access are failing with
Caught vmodl fault : Current license or ESXi version prohibits execution of the requested operation.
Is there a way to enable this or another way to access this api or do I have to buy the Standard license?
You must pay to use any write mode operations in the vSphere API. If you run the HostSystem in demo mode which works for 60 days you can use the full API, the same goes for vCenter, but after those 60 days are up you will loose the write mode API features.
Edit
Here is a KB article. Its old but still valid and this part applies today:http://kb.vmware.com/kb/1023990
Notes:
vCLI, PowerCLI, and vSphere SDK for Perl are limited to read-only access for the free vSphere Hypervisor edition. To enable full functionality of vCLI on a VMware ESXi host, the host must be licensed with vSphere Essentials, vSphere Essential Plus, vSphere Standard, vSphere Advanced, vSphere Enterprise, or vSphere Enterprise Plus.
Where it says for Perl should just be vSphere SDK.
we are setting up new QE testing server. I guess host OS will be win2008
Which vmware server to choose - 1.x or 2.x ?
A year ago I tried vmware 1 server with Win2008 and it did not work at all.
However, Vmware server 2 did not seem to have the handy vmware console
VMware Server Console\vmware.exe
(is the new vmware server2 still just web based?)
we have a lot of vmware 1 images, are these ok for v2?
Or is it just better to go with HyperV?
Hyper-V Server or ESXi would probably be the best performing and most trouble free options - ie virtualisation not really dependant on the host operating system (but still free).
You can use tools like Vmdk2Vhd to convert image files. Be aware that you should boot the image in its old format first and uninstall vmware tools and some drivers like specific disk controller drivers (as per the instructions of the tool) before you convert it.
Going the enterprise route the System Center Virtual Machine Manager can do this mostly automatically, but then it's not a free solution anymore :) This platform can of course also do physical to virtual migrations for you...
...but alas, you can prepare a physical machine the same way as before converting a vmware image and then use normal imaging tools to clone it into a virtual machine. Or you can use Vmware's free converter tool and then convert the resulting vmdk image to vhd :)
Vmware Server v2 can use v1 images. Windows Server 2008 is supported only in v2. v2 also includes the Virtual Infrastructure Client which you can use instead of the web access ( the client replaces the old console from v1). This is the same client that is used with ESX.
vmware 2.0 crashed regularly on one server I have - however, hasn't crashed since the recent 2.0.1 update (but its only been a week).
I have w2K8 running under vmware 1.0.9 - by selecting Vista (experimental) as the OS setting. However, it's not under any load yet.
I'd recommend ESXi over VMware Server (you can migrate the images) purely for performance reasons. Server 2008 and Vista both run abysmally under VMware Server from my experience. With ESXi and a decent hardware RAID setup, things can be a bit more bearable.
Ok, so let's say that I want to try virtualization in my environment. I want to use ESXi to do that because it is free. I can use the install disk and setup a box to run the ESXi Host.
I'm not sure if the VMware Infrastructure Client is free for one thing. You can use it to attach an ovf file (a packaged VM). The problem I had is creating an ovf file that worked. The free converter didn't do the trick.
Does anyone have any tips or guidelines?
The VMware Infrastructure Client is free with certain restrictions. You just download it over the web from an installed ESXi host.
You need licenses to enable vMotion, but for a single host there's no problem.
We're using ESXi (free) with the VI Client (free) and getting tons better performance than VMware Server (also free). I wasn't so sure about the VI Client thing until I talked to someone else that had a working setup, it's a bit confusing and definitely not "obvious" if you're new to the various enterprise level VMware solutions.
Edit: This was true for ESX3, things change and it is no longer true. See comments for ESX4/5 solutions.
Yes, VI Client is free with ESXi, you just don't get advanced features.
For creating an OVF you should have a look at VMware Studio, a new Beta was released recently.
Sadly, no, the VMware client is not free:
"Further, managing a VMware ESXi host with VMware vCenter Server requires a VMware vCenter Server Agent for each host, only available with the purchase of a VMware Infrastructure license (Foundation, Standard, or Enterprise)."
From this VMware page:
http://www.vmware.com/products/esxi/uses.html