SebEnn's Posts

Set type of hard disk for virtual machine

by Contributor in vSphere SDK for Java Discussions
‎03-08-2023 05:37 AM
‎03-08-2023 05:37 AM
Hello,  when creating a virtual machine within the vCenter Web Interface, you have the option to set the Disk Provisioning of a hard disk (later called type of hard disk). I would like to set t... See more...
Hello,  when creating a virtual machine within the vCenter Web Interface, you have the option to set the Disk Provisioning of a hard disk (later called type of hard disk). I would like to set this option with the vSphere Automation SDK in Java (currently version 7.0), but I couldn't figure out a way to do so. Does anyone know which UpdateSpec or CreateSpec I need to use?

Set type of hard disk for virtual machine

by Contributor in vSphere Client SDK Discussions
‎08-23-2022 01:51 AM
‎08-23-2022 01:51 AM
Hello,  when creating a virtual machine within the vCenter Web Interface, you have the option to set the Disk Provisioning of a hard disk (later called type of hard disk). I wanted to set thi... See more...
Hello,  when creating a virtual machine within the vCenter Web Interface, you have the option to set the Disk Provisioning of a hard disk (later called type of hard disk). I wanted to set this option with the vSphere Automation SDK in Java, but I couldn't figure out a way to do so. Does anyone know which UpdateSpec or CreateSpec I need to use?

Re: vsphere api : failed to create ServiceInstance using vijava vsphere API

by Contributor in vSphere Client SDK Discussions
‎08-02-2021 05:54 AM
‎08-02-2021 05:54 AM
The error occurs, because vijava and your chosen fork yavijava are trying this: SERVICE_INSTANCE_MOR.set_value("ServiceInstance"); The problem is the following: That code tries to use the method M... See more...
The error occurs, because vijava and your chosen fork yavijava are trying this: SERVICE_INSTANCE_MOR.set_value("ServiceInstance"); The problem is the following: That code tries to use the method ManagedObjectReference.set_value(String) and the jar comes with that class included. If you added the default vim25.jar from VMware it also includes this class with the exact same name and package path. Now some part has to decide which of these two classes its gonna use when that method gets called, but they're not identical. The vim25-version instead of set_value(String) has the method setValue(String). So if whatever part decides to use the vim25-version, the method set_value(String) is not existing and throws your error. So in short: make sure that you dont use vijava/yavijava and vim25 in the same project.