Whenever I try to install any Linux distro on WSL I get this error:
WslRegisterDistribution failed with error: 0x80040324
Error: 0x80040324 (null)
Press any key to continue...
This is my setup:
Versione WSL: 0.67.6.0
Versione kernel: 5.15.62.1
Versione WSLg: 1.0.44
Versione MSRDC: 1.2.3401
Versione Direct3D: 1.606.4
Versione DXCore: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
versione Windows: 10.0.22621.521
The Ubuntu distro is not listed in the installed distro:
[wsl --list --all
Sottosistema Windows per Linux non ha distribuzioni installate.
Usare 'wsl.exe --list --online' per elencare le distribuzioni disponibili e 'wsl.exe --install ' per l'installazione.
È anche possibile installare le distribuzioni visitando il Microsoft Store: https://aka.ms/wslstore
Error code: Wsl/WSL_E_DEFAULT_DISTRO_NOT_FOUND3
Anyway if I try to install Ubuntu I get this message:
wsl --install -d Ubuntu
Ubuntu è già installato. (Ubuntu is alreday installed)
Avvio di Ubuntu in corso...
An then I get this message:
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80040324
Error: 0x80040324 (null)
Press any key to continue...
and here it stops.
Hyper-V is installed without adding any virtual machine or virtual switch in the control panel.
enter image description here
Is someone having any clue?
Thank you for any help.
Solved!
I needed to uninstall WSL, Hyper-V and the Hypervisor platform from Windows Programs & Features, reboot, reinstall everything and then apply the updates from Windows Update.
Related
I am trying to conda install intel_extension_for_pytorch but I keep getting the following error in the command line:
PackagesNotFoundError: The following packages are not available from current channels:
intel_extension_for_pytorch
this is the command that I am using
conda install intel_extension_for_pytorch
edit:
System Info:
Microsoft Windows [Version 10.0.19044.2006]
Processor 11th Gen Intel(R) Core(TM) i7-1185G7 # 3.00GHz, 2995 Mhz, 4 Core(s), 8 Logical Processor(s)
Currently, the Intel Extension for PyTorch is only supported by Linux OS. Try on a recent Linux version, it should work there.
Check out the docs for more info: https://www.intel.com/content/www/us/en/developer/tools/oneapi/extension-for-pytorch.html
I'm seeing the following error message when starting Spyder over a remote connection through MobaXTerm:
$ spyder
QXcbConnection: XCB error: 145 (Unknown), sequence: 171, resource id: 0, major code: 139 (Unknown), minor code: 20
Spyder still appears to work normally, but the error message pops up every time. A search on this error blames Qt5 and says there's no fix for X11 connections. I'm using Python 3.5.4, Spyder 3.2.3, and MobaXTerm Personal Edition v10.7 Build 3650 connecting to a system running RHEL 6.6.
How can I avoid the error message?
After trying the methods I could find on various websites:
conda install pyopengl on the base python installation
Adding both from OpenGL import GL and import ctypes; ctypes.CDLL("libGL.so.1", mode=ctypes.RTLD_GLOBAL) to site-packages/spyder/app/start.py
various Qt environment variable settings
EDIT:
I was finally able to stop the error messages by disabling only the "RANDR" MobaXTerm X11 extension:
Interestingly, the MobaXTerm documentation also has this extension disabled in the settings screenshots.
I ran into a similar issue when running rviz for ros2 from the Windows 10 WSL2 Ubuntu 20.10 Terminal with the command:
ros2 launch turtlebot3_bringup rviz2.launch.py
I tried unchecking the RANDR extension in MobaXterm to no effect. I was finally able to resolve the issue and launch rviz after issuing the following command:
export LIBGL_ALWAYS_INDIRECT=0
and then re-issuing the ros2 launch command above.
I am installing the ElastiCache Cluster Client for PHP on Red Hat 7.2 and centos 6.5 Amazon AMI , but issue still same on all.
cat /etc/os-release
NAME="Red Hat Enterprise Linux Server"
VERSION="7.2 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="7.2"
PRETTY_NAME="Red Hat Enterprise Linux Server 7.2 (Maipo)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.2:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.2
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.2"
after install elastcache cluster cleint for php i got this error
php -v
PHP Warning: PHP Startup: Unable to load dynamic library '/etc/php/lib/php/extensions/no-debug-non-zts-20131226/amazon-elasticache-cluster- client.so' - libsasl2.so.2: cannot open shared object file: No such file or directory in Unknown on line 0
PHP 5.6.15 (cli)
i have installed php by compiling/configure.
please let me know how to get out from this error, i tried everything but issue still same.
On some systems, notably CentOS7 and Red Hat Enterprise Linux (RHEL) 7.1, libsasl2.so.3 has replaced libsasl2.so.2. On those systems, when you load the ElastiCache cluster client, it attempts and fails to find and load libsasl2.so.2. To resolve this issue, create a symbolic link to libsasl2.so.3 so that when the client attempts to load libsasl2.so.2, it is redirected to libsasl2.so.3. The following code creates this symbolic link.
cd /usr/lib64
sudo ln libsasl2.so.3 libsasl2.so.2
Source: From AWS documentation http://docs.aws.amazon.com/AmazonElastiCache/latest/UserGuide/Appendix.PHPAutoDiscoverySetup.Installing.html
I'm trying to compile the latest stable (2.8.19) version of Redis. Build is successfull as well as all tests, but unexpectedly server runs on 32bit arch.
Log entries:
# Warning: 32 bit instance detected but no memory limit set. Setting 3 GB maxmemory limit with 'noeviction' policy now.
Redis 2.8.19 (00000000/0) 32 bit
Running in stand alone mode
Port: 6582
PID: 2381
Redis-cli INFO display arch_bits:32. Previous instance (version 2.4.6) works well on arch_bits 64, but I don't know which way it was installed.
OS version info:
root:~# uname -a
Linux localhost 2.6.32-5-amd64 #1 SMP Tue Mar 8 22:49:26 UTC 2011 x86_64 GNU/Linux
root:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 6.0.1 (squeeze)
Release: 6.0.1
Codename: squeeze
root:~# arch
x86_64
What are the ways to fix this issue and run latest redis as 64bit?
UPD
Despite above commands output, dpkg --print-architecture returns i386 and all packages in system are all or i386. Only redis-server 2.4.*, installed as a package, is strangely ia64.
What can I do in this situation? The server was setup long time ago by another person, and I is still too newbie in Unix.
It seems, my server needs a full migration from 32 to 64-bit architeture.
Current task solved by downloading compiled 64-bit DEB-package and installing it manually.
I am completely new to docker. I have installed it from Source. I am trying to run it from cmd by using boot2docker start. But i get the following
boot2docker start
Failed to start machine boot2docker-vm <run again with v for details>
boot2docker init
virtual machine boot2docker-vm already exists
boot2docker start
Failed to start machine boot2docker-vm exit status:1
So, For you guys it would be a simple one. I don't know what to do. I tried SO. But i can't able to understand the solution so i failed to achieve it. Please provide some suggestions
EDIT:
I hope it will be helpful. There is some thing disabled in bios.
boot2docker -v start
Boot2Docker-cli version: v1.4.1
Git commit: 43241cb
2014/12/18 16:12:35 executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe
showvminfo boot2docker-vm --machinereadable
2014/12/18 16:12:35 executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe
guestproperty set boot2docker-vm /VirtualBox/GuestAdd/SharedFolders/MountPrefix
/
2014/12/18 16:12:36 executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe
guestproperty set boot2docker-vm /VirtualBox/GuestAdd/SharedFolders/MountDir /
2014/12/18 16:12:36 executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe
sharedfolder add boot2docker-vm --name c/Users --hostpath C:\Users --automount
VBoxManage.exe: error: Shared folder named 'c/Users' already exists
VBoxManage.exe: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), componen
t SessionMachine, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: "CreateSharedFolder(Bstr(name).raw(), Bstr(hostp
ath).raw(), fWritable, fAutoMount)" at line 1009 of file VBoxManageMisc.cpp
2014/12/18 16:12:36 executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe
setextradata boot2docker-vm VBoxInternal2/SharedFoldersEnableSymlinksCreate/ c/U
sers 1
2014/12/18 16:12:36 executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe
startvm boot2docker-vm --type headless
Waiting for VM "boot2docker-vm" to power on...
VBoxManage.exe: error: **VT-x is disabled in the BIOS.** (VERR_VMX_MSR_VMXON_DISABLE
D)
VBoxManage.exe: error: D**etails: code E_FAIL (0x80004005)**, component Console, int
erface IConsole
2014/12/18 16:12:38 executing: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe
showvminfo boot2docker-vm --machinereadable
error in run: Failed to start machine "boot2docker-vm": exit status 1
Cause:
The nugget of info you need to pay attention to in your error log is
Waiting for VM "boot2docker-vm" to power on...
VBoxManage.exe: error: **VT-x is disabled in the BIOS.**(VERR_VMX_MSR_VMXON_DISABLE
D)
This means that your current workstation's BIOS settings is preventing virtualization of another operating system on your CPU. Docker runs a virtual linux OS on your machine, so this is the issue.
For Intel chips, virtualization features are usually called VT-x or something like that. For AMD chips, virtualization features are called AMD-V. I use an Intel chip like you though, so this solution pertains to Intel chips.
Solution:
Power down and go into your BIOS and enable VT-x. In my BIOS, a Lenovo Thinkpad T440, the setting that needs to be changed was under Security->Virtualization.
Power up and go back to your C:/path/to/Boot2Docker for Windows folder.
Run boot2docker delete to ensure no VMs are running.
Run boot2docker init to initialize the VM.
Run boot2docker start to create a new Docker Virtual Machine!
To get access to your Docker VM, run boot2docker ssh since the Docker Client doesn't run on Windows as of version 1.5.0.