I built an ova file using packer. I am using virtualbox-iso builder
source "virtualbox-iso" "test" {
.
.
.
}
But when I try to import the ova in vcenter, it gives me the following error:
Issues detected with selected template. Details: - -1 VALUE_ILLEGAL:
No supported hardware versions among [virtualbox-2.2]; supported:
[vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13,
vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19].
looks like this is a common problem. I found a few docs related to this. Most of them are talking about using external tools to fix this like OVFTOOL and then to edit the OVF XML file in the OVA package.
https://tutorials.technology/tutorials/How-to-create-a-vmware-OVA-from-a-virtualbox-ova.html
Is there any packer configuration that fixes this issue?
Related
I am trying to use matploitlib_cpp on Windows 11 with Numpy 1.24.2 and Python 3.11, but I keep running in to the following error.
Original error was: No module named 'numpy.core._multiarray_umath'
I know this has been posted at a million different places on the internet and I have tried following all the guides that says reinstalling numpy and whatever, it does not work for me. What I can see in my path ..\Python3.11\Lib\site-packages\numpy\core is that I have a file named _multiarray_umath.cp311-win_amd64.pyd but no file named _multiarray_umath. I also tried to use a virtual environement from Anaconda but I am not sure how to build matploitlib_cpp against such virtual enviornment.
I got it working by using the release binaries instead of debug binaries.
I try installing QT5 using vcpkg on Windows 10. Unfortunately, when executing ./vcpkg.exe install qt5:x64-windows, I get a long list of errors, must useful information being:
-- Downloading http://download.qt.io/official_releases/qt/5.15/5.15.0/submodules/qtdeclarative-everywhere-src-5.15.0.tar.xz... Failed. Status: 18;"Transferred a partial file"
Failed to download file.
If you use a proxy, please set the HTTPS_PROXY and HTTP_PROXY environment
variables to "https://user:password#your-proxy-ip-address:port/".
Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues
Error: Building package qt5-declarative:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: qt5-declarative:x64-windows
Vcpkg version: 2020.06.15-nohash
As I am using the current version and was successful downloading and installing opencv as well as eigen3, I don't think proxy is being an issue.
I was able to download the file itself and hoped, I could manually paste it at the required position in the code (is this possible?) or use a different mirror. I would be glad if someone could give me guydance, as I am new to vcpkg.
Thanks in advance
Edit: As suggested by #drescherjm, I pasted the file in the vcpkg\downloads folder. Now I am looking at the File does not have expected hash error. How do I solve that issue?
I just update my google cloud SDK on windows 10 (gcloud components update).
After the update the gcloud command stop working.
All I get is (for example : gcloud -h):
PATH\lib\gcloud.py" -h" was unexpected at this time.
I try to re-install but it didn't help:(
As noted in the other answers, this is a bug with the 274.0.0 version of gcloud. Another report of this issue actually identifies where the bug is and offers this fix:
If you are stuck and need an immediate solution, here's a workaround that will move you forward, but you should reinstall the Cloud SDK from scratch when a fix is ready.
Open C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk-bin\gcloud.cmd in your editor
Near line 170, change ) ELSE ( to be just )
Remove the ) on the last line in the file.
That should get you working in the short term (albeit with an extraneous error message every time you run a command). After getting it working you can revert to version 273.0.0 (so that you stop getting the error message and aren't using a modified version) using:
gcloud components update --version=273.0.0
This is being tracked in the public bug https://issuetracker.google.com/issues/146458519
We have a patch for two files that are causing these problems. These apply in two cases (both on Windows):
1. A new install fails, or
2. You are unable to run gcloud after performing a components update.
For case # 1, please download the attached file install.bat, and copy it to the location where you have attempted to install gcloud, e.g. C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk. Then run it, e.g.
cd C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk
.\install.bat
For both cases #1 and #2, download the attached file gcloud.cmd, and copy it to the bin directory under your gcloud installation, e.g.
C:\Program Files (x86)\Google\Cloud SDK\google-cloud-sdk\bin. When prompted to replace the previous copy, type Yes. This should allow you to run gcloud without being prompted to set CLOUDSDK_PYTHON.
The files are attached in the public bug tracker.
This is a known issue that is being tracked here
After hours of trying to fix it! I found how :)
uninstall google SDK
https://dl.google.com/dl/cloudsdk/channels/rapid/google-cloud-sdk.zip
https://cloud.google.com/sdk/docs/downloads-interactive#interactive_installation
This fix the bug.
After that I had new bug in pyCharm GAE:
ImportError: No module named _subprocess
I fix this with the solution here:
Error importing built-in module "_subprocess" using Google Cloud Platform's Local Development Server
Hope this helps and saves a lot of trouble for you guys :)
I solved this problem. I got the same error message.
My Env: gcloud v274.0.0, Windows 7
First, I re-installed Google SDK, and changed my path to \Google\CloudSDK\.
Second, I got this message
"\Google\CloudSDK\google-cloud-sdk\bin..\lib\gcloud.py" init" was unexpected at this time."
So I tried to use cd command to specific directory where gcloud.py is exist.
Finally, I found the path: \Google\CloudSDK\google-cloud-sdk\lib, and it works.
Hope it can help you, too.
The problem, or rather bug within the installer, is that you are using a directory that contains spaces within it. At some point of the script the space causes the command to be split up incorrectly, causing the error.
I had the same message and fixed it by re-installing the Google Cloud SDK in a directory without spaces (c:\Google\CloudSDK)
I read in GDAL documentation that starting 2.4 it is possible to open a raster in HDFS. I downloaded and compiled the latest source code available version and the generated libraries show it is 2.4 (libgdal.so.20.4.2). I compiled with option "-with-hdfs=yes" and "--with-java=yes".
I am trying to open a raster using:
Dataset raster = gdal.Open("/vsihdfs/hdfs://node:8020/user/hdfs /spatial_raster/input_raster/kahoolawe.tif", gdalconst.GA_ReadOnly);
but I am getting the following error: "ERROR 4: No such file or directory"
could anyone please tell me if hdfs virtual system not supported yet?, or maybe I configured it wrong when compiling?
Appreciate your help, thanks!
Important are environment variables JAVA_HOME and HADOOP_HOME.
Export CLASSPATH=$($HADOOP_HOME/bin/hadoop classpath --glob)
I hope this can help you :
https://github.com/OSGeo/gdal/issues/1333
https://github.com/OSGeo/gdal/pull/714
I'm trying to deploy 'limesurvey' application into the PCF & I get the following error.
php pdo driver library none found
Below are the pre-requisites that should be met for installation.
• mbstring (Multibyte String Functions) extension library
•PDO database driver for MySQL (pdo_mysql or pdo_mysqli) or Postgres (pdo_pgsql) or MSSQL (pdo_sqlsrv for Windows and pdo_dblib for Linux)
•Also we assume in general that all PHP default libraries are enabled (like hash, session, etc.).
Is there any workaround for this ? Because, few sites says to modify the php.ini file, which I don't have access to. If the suggestion is to have my own buildpack, is there any link that I can refer to do that please.
Appreciate any help :)
Assuming the limesurvey application is using php-buildpack, you can tell the buildpack to load the mbstring and pdo_* modules by creating an options.json file in the .bp-config subfolder, if it doesn't already exist, adding a PHP_EXTENSIONS key, and including the name or names of the modules/extensions that are required in the value.
Something like this:
$ cat .bp-options/options.json
{
"PHP_VERSION": "{PHP_56_LATEST}",
"PHP_MODULES": ["cli"],
"PHP_EXTENSIONS": ["mysqli", "pdo_mysql", "mbstring"],
"ADDITIONAL_PREPROCESS_CMDS": [""]
}
Even though the php-buildpack calls mbstring and pdo_mysql 'modules' you want to list them in the PHP_EXTENSIONS key, not the PHP_MODULES key.