Hi all
Testing if moving from VirtualBox to VmWare is the correct solution for us - as Virtualization Based Security is messing with VirtualBox.
We got a fully automated setup for VirtualBox, which would need to be ported - including automated creation of WindowsXP devices. vmcli does however not seem to support this, or else I just havn't figured out how.
Any hints on this one?
Br. Stickybit
C:\Temp>"\Program Files (x86)\VMware\VMware Workstation\vmcli.exe" VM Create --help
Usage: vmcli.exe [-v | --version] [<vmx location>] VM Create [--verbose] [-h | --help] [-n | --name] <string> [-d | --dirpath] <string> [-g | --guesttype <7, 5, 1, 6, 4, 2, 3, 8, 9, 10, 11, 12, 13>] [-c | --custom-guesttype <string>] [<vmx location>]
Top level arguments:
-v, --version
Display the version information.
Global arguments:
<vmx location> (required for commands working with VMs)
Location of the vmx file to work with. Can be the first or last argument on the command line.
--verbose
Enable verbose logging.
-h, --help
Display the help information
Module:
Create
Create VM.
e.g VM Create -n myVM -d ~/Desktop/ -g windows9-64
VM Create -n myVM -d ~/Desktop/ -c other5xlinux-64
Arguments available to module "Create":
-n, --name <string> (required)
Virtual machine name
-d, --dirpath <string> (required)
Directory path where Virtual machine will be created
-g, --guesttype <7, 5, 1, 6, 4, 2, 3, 8, 9, 10, 11, 12, 13>
guest os type
-c, --custom-guesttype <string>
any other guest os type
C:\Temp>"\Program Files (x86)\VMware\VMware Workstation\vmcli.exe" VM Create --name TestXP --dirpath c:\temp\tester --guesttype gimmi-xp
vmcli.exe: Invalid argument: 'gimmi-xp', valid enums are: debian12-64, centos8-64, other6xlinux-64, debian13-64, centos9-64, windows11-64, windows9-64, fedora-64, rhel10-64, rhel9-64, opensuse-64, ubuntu-64, vmware-photon-64 See 'vmcli.exe --help'.