VT-x is not available (VERR_VMX_NO_VMX) - virtualbox

Result Code: NS_ERROR_FAILURE (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Checked BIOS settings all components enabled still getting this error

Related

Unable to bind intel NIC X710

I am trying to bind this nic I40E:
Ethernet Controller X710 for 10GbE backplane 1581
my OS is ubuntu 18.04
kernel: 4.15.0-74-generic
I used dpdk-setup.sh to Insert VFIO module.
i also add iommu=on to grub file.
running devbind command:
sudo ./dpdk-devbind.py -b vfio-pci 02:00.1
i Got this erros:
Error: bind failed for 0000:02:00.1 - Cannot bind to driver vfio-pci
dmesg output:
[ 5091.393436] vfio-pci: probe of 0000:02:00.1 failed with error -22
There is no issue in binding vfio-pci on Ethernet Controller X710. I have followed the following steps with success
DPDK version: dpdk-20.11
NIC: driverversion=2.1.14-k, firmware=6.01
modprobe vfio-pci
confirm via lsmod
bind with sudo ./usertools/dpdk-devbind.py -b vfio-pci [PCIe B:D:F]
[EDIT-1] as per DPDK documentation workaround for VT-d or iommu is suggested.
note:
If VT-D is not enabled in BIOS and kernel command line (grub option), the work around is to use echo 1 > /sys/module/vfio/parameters/enable_unsafe_noiommu_mode, then follow the above steps.
if the interface is already used in Kernel - Warning: routing table indicates that interface [PCIe B:D:F] is active. Not modifying. Simply disable the interface with ifconfig [interface name] down and bind again.

VirtualBox error Failed to open session of virtual machine macOS (VERR_PDM_TOO_MANY_DEVICES_INSTANCES)

Too many instances of a device. (VERR_PDM_TOO_MANY_DEVICE_INSTANCES).
Result Code:
E_FAIL (0x80004005)
Component:
ConsoleWrap
Interface:
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

how to start a Redis server on port 6379

i'm getting this error while working with django channels tutorial project
redis:5
docker: Error response from daemon: failed to start service utility VM
(createreadwrite): hcsshim::CreateComputeSystem
9eb1deb8fc69ee2656d9e049530b329c0fa8ca44a1f6523e9d5a27768fbedb62_svm:
The virtual machine could not be started because a required feature is
not installed. (extra info:
{"SystemType":"container","Name":"9eb1deb8fc69ee2656d9e049530b329c0fa8ca44a1f6523e9d5a27768fbedb62_svm","Layers":null,"HvPartition":true,"HvRuntime":{"ImagePath":"C:\\Program
Files\\Linux
Containers","LinuxInitrdFile":"initrd.img","LinuxKernelFile":"kernel"},"ContainerType":"linux","TerminateOnLastHandleClosed":true}).
Seems you have not enabled hyper-V and container.Please check if the hyper-V and container are enabled from control panel => Programs and features => Turn Windows Features on or off
If you have still issue then plese check this answer.

VirtualBox 5.1.34: error on Ubuntu 17.10 when I tried to start a VM

I tried to execute this tutorial:
https://docs.docker.com/get-started/part4/#set-up-your-swarm
but when I execute this command
docker-machine create --driver virtualbox myvm1
I had this error:
Starting "myvm1"...
(myvm1) Check network to re-create if needed...
(myvm1) Creating a new host-only adapter produced an error: /usr/bin/VBoxManage hostonlyif create failed:
(myvm1) 0%...
(myvm1) Progress state: NS_ERROR_FAILURE
(myvm1) VBoxManage: error: Failed to create the host-only adapter
(myvm1) VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
(myvm1) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
(myvm1) VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg*)" at line 94 of file VBoxManageHostonly.cpp
(myvm1)
(myvm1) This is a known VirtualBox bug. Let's try to recover anyway...
Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue

Errors starting wso2server.sh on AIX IBM PASE

Whis is what I get after trying to start the wso2carbon-4.2.0
help please....
cd /barj/WSO2/wso2carbon-4.2.0/bin/
wso2server.sh
JAVA_HOME environment variable is set to /QOpenSys/QIBM/ProdData/JavaVM/jdk60/64bit
CARBON_HOME environment variable is set to /barj/WSO2/wso2carbon-4.2.0
[2014-05-19 14:43:06,951] INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} - Starting WSO2 Carbon...
[2014-05-19 14:43:07,036] INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} - Operating System : OS/400 V6R1M0, PowerPC
[2014-05-19 14:43:07,037] INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} - Java Home : /QOpenSys/QIBM/ProdData/JavaVM/jdk60/64bit/jre
[2014-05-19 14:43:07,037] INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} - Java Version : 1.6.0
[2014-05-19 14:43:07,038] INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} - Java VM : IBM J9 VM 2.4,IBM Corporation
[2014-05-19 14:43:07,038] INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} - Carbon Home : /barj/WSO2/wso2carbon-4.2.0
[2014-05-19 14:43:07,038] INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} - Java Temp Dir : /barj/WSO2/wso2carbon-4.2.0/tmp
[2014-05-19 14:43:07,039] INFO {org.wso2.carbon.core.internal.CarbonCoreActivator} - User : barj, en-US, America/Chicago
[2014-05-19 14:43:07,407] WARN {org.wso2.carbon.core.bootup.validator.SystemValidator} - Could not validate the system for configuration parameter : swap
[2014-05-19 14:43:07,408] WARN {org.wso2.carbon.core.bootup.validator.SystemValidator} - Could not validate the system for configuration parameter : ulimit
[2014-05-19 14:43:07,622] WARN {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} - The default keystore (wso2carbon.jks) is currently being used. To maximize security when deploying to a production environment, configure a new keystore with a unique password in the production server profile.
[2014-05-19 14:43:07,623] WARN {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} - The running OS : OS/400 is not a tested Operating System for running WSO2 Carbon
[2014-05-19 14:43:07,624] WARN {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} - CPU speed (MHz): 0 of the system is below the recommended minimum speed :800
[2014-05-19 14:43:14,357] WARN {org.wso2.carbon.tomcat.ext.scan.CarbonTomcatJarScanner} - Failed to scan [{0}] from classloader hierarchy
java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:151)
at java.util.jar.JarFile.<init>(JarFile.java:150)
at java.util.jar.JarFile.<init>(JarFile.java:87)
at sun.net.www.protocol.jar.URLJarFile.<init>(URLJarFile.java:84)
at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:60)
at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:95)
at sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:119)
at sun.net.www.protocol.jar.JarURLConnection.getJarFile(JarURLConnection.java:86)
at org.apache.tomcat.util.scan.FileUrlJar.<init>(FileUrlJar.java:41)
at org.apache.tomcat.util.scan.JarFactory.newInstance(JarFactory.java:34)
at org.apache.catalina.startup.ContextConfig$FragmentJarScannerCallback.scan(ContextConfig.java:2625)
at org.wso2.carbon.tomcat.ext.scan.CarbonTomcatJarScanner.process(CarbonTomcatJarScanner.java:262)
at org.wso2.carbon.tomcat.ext.scan.CarbonTomcatJarScanner.scan(CarbonTomcatJarScanner.java:229)
at org.apache.catalina.startup.ContextConfig.processJarsForWebFragments(ContextConfig.java:1917)
at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1268)
at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:878)
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:369)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5173)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314)
at java.util.concurrent.FutureTask.run(FutureTask.java:149)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:906)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:929)
at java.lang.Thread.run(Thread.java:738)
[2014-05-19 14:43:14,700] ERROR {org.apache.catalina.startup.ContextConfig} - Failed to process JAR found at URL [jar:file:/barj/WSO2/wso2carbon-4.2.0/repository/components/plugins/jgroups_3.0.6.wso2v1.jar!/] for ServletContainerInitializers for context with name [/]
[2014-05-19 14:43:14,746] ERROR {org.apache.catalina.startup.ContextConfig} - Marking this application unavailable due to previous error(s)
[2014-05-19 14:43:14,787] INFO {org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService} - Configured Registry in 268ms
[2014-05-19 14:43:15,796] INFO {org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} - Registry Mode : READ-WRITE
[2014-05-19 14:43:16,338] INFO {org.wso2.carbon.user.core.internal.UserStoreMgtDSComponent} - Carbon UserStoreMgtDSComponent activated successfully.
[2014-05-19 14:43:16,558] INFO {org.apache.catalina.startup.TaglibUriRule} - TLD skipped. URI: http://tiles.apache.org/tags-tiles is already defined
[2014-05-19 14:43:16,848] ERROR {org.apache.catalina.core.StandardContext} - Error getConfigured
[2014-05-19 14:43:16,858] ERROR {org.apache.catalina.core.StandardContext} - Context [/] startup failed due to previous errors
Can you try deleting the following jar from the plugins directory and see?
jgroups_3.0.6.wso2v1.‌​jar