I purchased a network card to give a separate network to my virtual machine. My host OS is Ubuntu 14.04 . Also i need to mount the USB to my virtual machine and not my host OS, so i downloaded extension pack version 5.0.2 for Vbox-5.0 . While installing virtual box extension pack, there were two VM's running and i got this popup.
Failed to install the Extension Pack /home/aniket/Downloads/Oracle_VM_VirtualBox_Extension_Pack-5.0.20-106931.vbox-extpack.
Failed to load the main module ('/usr/lib/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxPuelMain.so'): VERR_FILE_NOT_FOUND - /usr/lib/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxPuelMain.so: undefined symbol: RTLogRelGetDefaultInstanceEx.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ExtPackManager
Interface: IExtPackManager {3295e6ce-b051-47b2-9514-2c588bfe7554}
Even after power off of VM's and restarting the host OS, I get this similar error code.
Sorry if you think the question is not formatted properly or any other issue with my question. This is my second post, please tell me if there are any things i need to correct in my question.
Thanks in Advance.
After lot of test and trial, the solution I found that the extension pack was not compatible and hence I had to download the compatible version of the virtualbox I am running on.
What happened was this, I was running virtualbox-5.0 and the version I was trying to install was 5.0.20 .
You can check your version by clicking on Help and then About Virtualbox and download the exact compatible extension pack, else it will through the same hex error code 0x80004005 which means file not found.
Run vboxmanage command with sudo, i.e.:
sudo vboxmanage extpack install Oracle_VM_VirtualBox_Extension_Pack-5.1.22-115126.vbox-extpack --replace
From:
https://www.virtualbox.org/ticket/17034
I uninstalled virtualbox,then reinstall it. After this the extension pack got installed successfully. My version is `5.1.12 r112440 (Qt5.6.2)
I encounter this problem again, but this time I disable my antivirus software(mcafee), that is ok. refer by https://www.virtualbox.org/ticket/7972
Related
I was trying to build DPDK environment using dpdk-setup.sh but can't get DPDK to compile.
$sudo ./dpdk-stable-17.11.5/usertools/dpdk-setup.sh
I type 14(x86_64-native-lunuxapp-gcc) to build DPDK show the errors below:
error message image
Could someone help me to fix this?
I have found these post but still don't understand to fix this problem..
dpdk-compilation-error-when-building-igb-uio
You need to have the kernel-devel package installed. It may also be a good idea to update the kernel, since RHEL7 has kernel version 3.10.0-1062 available now.
DPDK by default look in lib/modules/{kernel} folder for Kernel headers and definitions. So fix for your build issue is get the right headers and using Redhat, Centos or Fedora make sure to wither export RTE_KERNELDIR=your desired path in terminal or build with RTE_KERNELDIR=<your desired path> make.
I am experiencing a problem with codesigning on Mac OSX (Catalina and older), that I cannot find any answer for. I do have a *.component file, that I am codesigning and notarizing with my Apple Developer ID, which is working perfect. As a post-install step on the target machine, I need to include some installation info within the component's Info.plist (so I am writing back to that *.plist file), which would then qualify as a manipulation of the component itself - ergo, the component's signing is going to be corrupt at this point (the host software will not load my software any more).
So I was trying to follow some advice and do a "blind" codesigning as additional post-install step on the user's machine with:
sudo codesign --force --deep -s - ABC.component
This was just working perfect for a few users, just when I found out, not everyone can make use of this (especially older Mac OSX). Sometimes this command will just not result in a properly signed component. One of the users then found out, he had to update Xcode CL Tools, to sign the file. He went:
xcode.select --install
I have tested this with several other users and it worked with them, too.
Here comes the issue:
As a result, I need to make sure, the user has installed the right version of Xcode Command Line Tools, but a lot of my clients do install on an offline device - so I would not be able to have xcode-select --install as a post-install step (because no internet connection).
Is it somehow possible to bundle the proper Xcode Command Line Tools into my installer and make use of it? Or do you see any other solution for the whole problem?
I want to use the C++ kernel with Jupyter Notebook and lab on Windows 10. I have tried following the instructions at https://github.com/QuantStack/xeus-cling?fbclid=IwAR3EOC0yxcpe3hf0Lo82V1ioCZYQzagirnY-y4uVvWy6dOIpUL5TthHcx7M.
I am seeing the following output:
(base) C:\Users\Rogan>conda activate cling
(cling) C:\Users\Rogan>conda install xeus-cling -c QuantStack
Collecting package metadata (current_repodata.json): done
Solving environment: failed with current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed
PackagesNotFoundError: The following packages are not available from current channels:
- xeus-cling
Current channels:
---
To search for alternate channels that may provide the conda package you're
looking for, navigate to
https://anaconda.org
and the search bar at the top of the page is:
(cling) C:\Users\Rogan>
Can anyone tell me what the problem might be?
I would like to add Java, R, and C later on but am unable to even get C++ working.
cling is not available on windows environment, so you should install Linux on your windows. Download WSL , and try above codes on Linux kernel.
I am a new to python. I am have installed Python27 and Vpython on my windows 64-bit W8.1 laptop.
The python version was Py27 32-bits and Vpython 32-bits. After installation I thought I could directly run an example program from the VIDLE (File -> Open -> bounce). But I realized there is lot more to install to get this working.
So I googled the errors and found that I has to install Numpy and WxPython which I was able to complete successfully. But now I have this error shown below
"The Polygon module is not installed,
so the text and extrusion objects are unavailable.
The ttfquery and/or FontTools modules are not installed,
so the text object is unavailable."
I googled for this but was not able to arrive at anything.
Should I install Polygon module, FontTools and ttfquery module?
I was not able to fond a proper link to do any of the above. Kindly help me out. I have a hit a wall.
Thanks!!
Hopefully was able to solve the issue.
The problem was with the way how I installed Vpython. I should have accidentally selected "custom installation" instead of "full installation".
Also the version of numpy that comes with default set-up did not support for me. Hence I used the pip to update the version and now everything is up and running.
I am able to get the example programs to work.
Also the 64-bit version is not working still. So its always safe to stick on to 32-bit version even if your machine is 64-bit
You're working with an older version of VPython that is no longer supported. See the first page of vpython.org.
i installed jetty (distribution-9.0.2) on ubuntu server 12.04
from these links step by step
http://degreesofzero.com/article/19
http://pietervogelaar.nl/ubuntu-12-04-install-jetty-9/
at last when i start jetty with the following command:
sudo /etc/init.d/jetty start
or
sudo service jetty start
i get the following error
Starting Jetty: grep: /var/run/jetty.state: No such file or directory
I'm facing with the same problem but on Debian 6 server. Workaround for this problem and articles above, from my perspective, is:
use JETTY_ARGS=jetty.port=8080 instead JETTY_PORT
Add property to /etc/init.d/jetty: JETTY_PID=/opt/jetty/jetty.state
Please, let me know if you have any questions
I've tested this thoroughly with the latest release of jetty and it's working fine. There's been some changes recently in the jetty.sh script. However the changes look good to me and it's working fine for me with the latest release.
Evgenly is right, that JETTY_PORT is deprecated (see comments in jetty.sh for details), however it also works fine for me using JETTY_PORT instead of JETTY_ARGS to define a non standard port.
Please try the latest release from here in case you didn't do already:
http://download.eclipse.org/jetty/
If jetty.sh reports that the start failed, you'll usually find the reason in stderrout.log inside the JETTY_HOME/logs directory (unless you've changed the logging config).