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
Related
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 am new to WSL and have installed VS code natively on Windows 10 with the installer. Currently, when I try to run VS Code command code from WSL, I receive the following message:
bash: /mnt/c/Users/user/AppData/Local/Programs/Microsoft VS Code/bin/code: Permission denied
Also, when I try to run VS Code Server for WSL, I am getting a similar message.
[2020-06-29 17:41:41.640] Launching C:\windows\System32\wsl.exe -d Ubuntu sh -c '"$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" cd9ea6488829f560dc949a8b2fb789f3cdc05f5d stable .vscode-server 0 ' in c:\Users\user\.vscode\extensions\ms-vscode-remote.remote-wsl-0.44.4}
[2020-06-29 17:41:41.779] sh: 1: /mnt/c/Users/user/.vscode/extensions/ms-vscode-remote.remote-wsl-0.44.4/scripts/wslServer.sh: Permission denied
[2020-06-29 17:41:41.780] VS Code Server for WSL closed unexpectedly.
I have tried configuring the permissions for wsl # wsl.conf:
[automount]
enabled = true
options = "uid=1000,gid=1000,umask=022,fmask=11,metadata"
Not sure if this is relevant, but I am able to run code from Windows Powershell.
I am currently using Microsoft Windows 1909 (OS Build 18363.836) with WSL v1.
Any help will be appreciated, thanks in advance!
Run wsl.exe or PowerShell as an Administrator Runs as Admin Windows
None of the previous answers worked for me. Instead after a lot of trial and error, I discovered that the code.exe was set in a way that it was being run as Administrator. This is what prevented it from running in the WSL. Find the VC Code executable, and ensure it doesn't have the admin Shield on it's icon.
It has to do with your /etc/wsl.conf. Change the contents of the file to:
[automount]
enabled=true
root = /
options="metadata,uid=1000,gid=1000,umask=002,dmask=002,fmask=002"
umask,dmask, and fmask all have to do with permissions. A pretty good explanation of them can be found here : https://askubuntu.com/questions/429848/dmask-and-fmask-mount-options#:~:text=fmask%20and%20dmask%20are%20mount,files%20and%20dmask%20to%20directories
Maybe for someone will helpfull...
For example i have mistake like this:
$ code .
/c/Users/admin/AppData/Local/Programs/Microsoft VS Code/bin/code: line 61: /c/Users/admin/AppData/Local/Programs/Microsoft VS Code/Code.exe: Permission denied
My error resolving was by click right button mouse on icon VS Code and chosen settings then "compatibility" tab and finaly disabled "run the program as an administrator"
I solved it by putting my Ubuntu user in the www-data group. I edited the /etc/group. That www-data group is the one in my configuration belongs to Apache2. Hope this helps.
I am doing local Chef dev on my Windows 8.1 laptop and use VirtualBox 5.1.24 for VMs. I want to use Jenkins (v2.73.2) to run jobs that will automate the restoring of VM snapshots and running of kitchen converge, test and repeat.
I have added the VirtualBox Plugin but it doesn't let me add a node (I recall seeing somewhere that v2.73.2 of Jenkins is not supported).
I wrote some Powershell to do what I want and so after installing PowerShell Plugin created a pipeline with following PowerShell to test it:
& "C:\Program Files\Oracle\VirtualBox\vboxmanage.exe" startvm "W2008_21_06_B"
(which works in PS ISE), but fails in Jenkins job:
Building on master in workspace C:\Program Files (x86)\Jenkins\workspace\vbox
[vbox] $ powershell.exe -NonInteractive -ExecutionPolicy ByPass "& 'C:\windows\TEMP\jenkins7025720492184266246.ps1'"
vboxmanage.exe: error: Could not find a registered machine named 'W2008_21_06_B'
vboxmanage.exe: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBoxWrap, interface IVirtualBox, callee IUnknown
vboxmanage.exe: error: Context: "FindMachine(Bstr(pszVM).raw(), machine.asOutParam())" at line 573 of file VBoxManageMisc.cpp
Build step 'Windows PowerShell' marked build as failure
Finished: FAILURE
What trick am I missing please?
Regards
I'm doing the Service Fabric tutorial that can be found here:
https://azure.microsoft.com/en-us/documentation/articles/service-fabric-create-your-first-application-in-visual-studio/
I started PowerShell (in Windows 10 running in Parallels through OS X) as administrator an executed this according to instructions:
Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Force -Scope CurrentUser
I have started Visual Studio 2015 both as admin and normally. I then started the tutorial app, but I'm getting the following error:
The PowerShell script failed to execute. See the Output window for details.
The output window just gives this:
2>Finished executing script 'Set-LocalClusterReady'.
2>Time elapsed: 00:00:03.1922793
2>The PowerShell script failed to execute.
========== Build: 1 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
Any ideas to what could be wrong?
UPDATE: I actually get the following error:
2>EnsureAdminPrivileges : Not running as administrator. You need to run Visual Studio with administrator privileges
Which is strange because I have started VS as administrator...
In my case, the solution was that I first needed to close Visual Studio and the run it as an administrator.
Very simple solution to an annoying error.
I had this error in VS17 RC as well as Unable to determine whether the application is installed on the cluster or not. It seemed as if the deployment of the local cluster had some issues.
What solved it for me was to run Repair from the Visual Studio setup.
After repairing, the cluster deployed as expected and I had no more error messages.
I am trying to install a windows service on a remote machine. The service is implemented using TopShelf. I am running the following psexec command:
psexec \\remoteServerName "C:\PathToExe\TopShelfServiceName.exe" "install"
The error I am receiving is:
ERROR - The service terminated abnormally
Topshelf.HostConfigurationException: The service was not properly configured:
[Failure] Command Line An unknown command-line option was found: ARGUMENT: "install"
It appears that I am not running the TopShelf installer, rather executing my exe and passing "install" which is not a valid argument.
Any help is appreciated!
I don't think you need quotes around "install":
psexec \\remoteServerName "C:\PathToExe\TopShelfServiceName.exe" install