I have run "vmware -v" and "vmware -l" commands on an ESXi 5.0 U1 and got the outputs as "VMware ESXi 5.0.0 build-504890" and "VMware ESXi 5.0.0 GA". But, nowhere I get the information of the update for this version. eg. it is ESXi 5.0 Update 1, I am not finding any command to get the update version. Tried googling around the whole day, but of no help. Any help will be highly appreciated.
For ESXi 4, run this command:
vmkvsitools vmware -l
For ESXi 5, run this command:
esxcli system version get
These commands will provide the exact Update for the version of ESXi running.
Related
We are getting the below error while running the command "minikube start --driver=hyperv" which was initially working properly but suddenly started giving an error.
C:\Windows\system32>minikube start --driver=hyperv
minikube v1.22.0 on Microsoft Windows 10 Enterprise 10.0.19043 Build 19043
Using the hyperv driver based on user configuration
Exiting due to PROVIDER_HYPERV_NOT_FOUND: The 'hyperv' provider was not found: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive #(Get-Wmiobject Win32_ComputerSystem).HypervisorPresent returned "False\r\n"
Suggestion: Enable Hyper-V: Start PowerShell as Administrator, and run: 'Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All'
Documentation: https://minikube.sigs.k8s.io/docs/reference/drivers/hyperv/
We tried to disabled and enabled the "hyperv" from the Windows Features tab and then restarted the machine but it didn't work.
When we hit a command "systeminfo" we got the below, saying "hyperv" is enabled.
Hyper-V Requirements:
VM Monitor Mode Extensions: Yes
Virtualization Enabled In Firmware: Yes
Second Level Address Translation: Yes
Data Execution Prevention Available: Yes
Now we have enabled the "hyperv", restarted the machine but still we are getting the error, could anyone please help us out in this?
Thanks in advance!!!
Reason: missing powershell.exe path
Resolution: Add C:\Windows\System32\WindowsPowerShell\v1.0 into Environmental Variables... > System variables > Path
Here is what I did - I'm not sure which part fixed it
bcdedit /set hypervisorlaunchtype auto
Followed this answer
powershell -version 5
minikube start --vm-driver hyperv ...
Please follow this page Hopefully it will fix your problem. we need to install dependencies first.
https://minikube.sigs.k8s.io/docs/drivers/
https://medium.com/#JockDaRock/minikube-on-windows-10-with-hyper-v-6ef0f4dc158c
if you are using docker desktop then switch to linux containers and the run minikube start
I would like to set up an X11 Server so that I can run graphical Linux applications using the Windows Subsystem for Linux (WSL 2). I have tried following the instructions on this site.
The command
choco install vcxsrv
completed successfully. But I cannot see how to start XLaunch (VcXsrv).
I already have Cygwin/X X Server installed on my machine and I am still able to launch that successfully. But when I try the following command,
PS C:\WINDOWS\system32> vcxsrv
I get the following error message,
vcxsrv : The term 'vcxsrv' is not recognized as the name of a cmdlet, function, script file, or operable program.
I have spent quite a bit of time trying to figure out how to start XLaunch (VcXsrv) without any success.
Try to look on default folder installation:
"C:\Program Files\VcXsrv\xlaunch.exe"
Try this command to run VcXsrv
xfsettingsd --sm-client-disable; xfce4-panel --sm-client-disable --disable-wm-check &
or
C:\Program Files\VcXsrv\xlaunch.exe
Refer the following link to understand VcXsrv installation and it's usage,
Running WSL GUI Apps on Windows 10
I have installed windows subsystem for Linux to run Ubuntu 16.04 on my windows 10 home platform.
I have extracted all required directories to run KSQL on this platform.
Now, when I am trying to run any command after navigating to the bin folder. It's throwing command not found error. I tried to add PATH as well but it's not working.
Please suggest.
There's a typo in your command:
export PATH=$PATH:/opt/kafka/confleuent-5.4.0/bin
Instead of confluent-5.4.0 you misspelled it confleuent-5.4.0.
The easiest way to install Confluent CLI, is by making use of the scripted installation:
Install the Confluent CLI using this script. This command creates a
bin directory in your designated location (<path-to-directory>/bin).
The location must be in your PATH (e.g. /usr/local/bin). On Microsoft
Windows, an appropriate Linux environment may need to be installed in
order to have the curl and sh commands available, such as the Windows
Subsystem for Linux
curl -L https://cnfl.io/cli | sh -s -- -b /<path-to-directory>/bin
Finally, if you run confluent start you can get all services up and running, including KSQL (assuming that you have correct configuration files).
You could just use the path
cd bin
./kafka-topics.sh
Also, all those commands work in CMD / PowerShell as well
If you want to run KSQL, I'd suggest just using Docker
I've installed CYGWIN on my windows server,
And now I'm trying to run it as a service so it will be running on every system startup, This is the command I tried but I get the error:
C:\cygwin64\bin>C:\cygwin64\bin\cygrunsrv.exe -I CYGWIN_SSHD -path C:\cygwin64\b
in\cygstart.exe
/usr/bin/cygrunsrv: Trailing commandline arguments not allowed
Try `/usr/bin/cygrunsrv --help' for more information.
Can anyone tell me what am I doing wrong?
I figured it out, To install Cygwin as a service I needed to run "ssh-host-config" insert all the needed definitions and this will install it as a service called "CYGWIN sshd".
We have a windows Oracle vm installed on our solaris machine which will be launched using Xmanager.
Can some one please help me with the following questions
I can use the folders on solaris from windows VM using "\vboxsrv" but how can i do viceversa
How can i access files on windows vm from solaris machine
And can i update the files on windows vm directly without opening it through xmanager
I found a way to execute a command on virtual machine from Hostmachine. Using this command tool I am accessing files or folders in virtual machine
The command line tool is VBoxManage - This has lot of parameters using we can do any thing on virtual machine from VM starting to shutdown
/opt/VirtualBox > VBoxManage Startvm "windows"
/opt/VirtualBox > VBoxManage guestcontrol "windows" execute --image "cmd.exe" --username root --password 12345 --wait-exit --wait-stdout -- -l /usr