I downloaded an OVA file from SDN-Hub, and used VMWare Player 11 to import it.
It came out with this error message:
Error while converting to a virtual machine:
Line 96:Unsupported element 'StorageItem'
Line 105:Unsupported element 'StorageItem'
Line 114:Unsupported element 'EthernetPortItem'
It's weird, because I downloaded the same file a few months ago in my other computer, and it worked well.
Seems the problem is related to the OVF format, the virtual machine was exported using OVF 2.0
What I did to import it to vmware was to import the sdn-hub vm into virtual box and export it again using OVF format 1.0.
Then vmware was happy importing the machine, and just works fine
When you go to export from the virtual box, it gives you the option to choose a format; 0.9 or 1.1 versions. I chose v1.1 for my CSI Linux ova on the virtual machine and it was converted straight to another ovs file of the format I chose and to a dir of my choice. I then uploaded this into my VMware Workstation Player 17 and it is working perfectly.
GM.
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.
No matter how I import my audio file (through uploading it on google colab, importing it through google drive), I keep getting the same error. Could it be a path issue, and if so, how could I go about fixing it? When I run an "iPython.display", it displays the audio and I'm able to play it, but I'm not sure why torchaudio cannot load it.
Thanks in advance :)
waveform, sample_rate = torchaudio.load("Default-20220816-113844.mp3")
waveform = waveform.to(device)
if sample_rate != bundle.sample_rate:
waveform = torchaudio.functional.resample(waveform, sample_rate, bundle.sample_rate)
Assuming ("Default-20220816-113844.mp3") is not being found because of the path
On Colab to find the path click on the "..." (that appears on the right hand side of objects in the file browser when you hover over them) and choose COPY PATH to copy the complete path, the value will be copied without quotation marks.
At the time of the question is posted, Google Colab has pytorch==1.12 and torchaudio==0.12 pre-installed, so I assume you are getting the error with these versions.
Starting from TorchAudio 0.12, mp3 decoding requires FFmpeg.
When "sox_io" backend is used, first it tries to load audio using libsox, and when it fails, it further tries to load it with FFmpeg.
In Google Colab, you can run the following command to install the supported version.
!add-apt-repository -y ppa:savoury1/ffmpeg4
!apt-get -qq install -y ffmpeg
See also: https://pytorch.org/audio/0.12.1/tutorials/streaming_api_tutorial.html
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?
Host machine: OSX Mojave
Virtualbox: 6.0.4
Tails: 3.12
Where I download virtualbox: brew cask install virtualbox. NOTE: I had virutalbox installed quite awhile and using it with vagrant and ansible to test playbook and stuff, and did make sure everything was clean when trying to run tails.
Where I download the image file: from tails site download using torrent
How I attempted to run tails from ISO image in virtual box: steps follow from tails documentation, it was straightforward and tried it more than five times
Error occurred at: steps 7, from the tails doc at configuring virtual machine to start from an ISO image, and below are the detail error:
The medium '/my-path/tails-amd64-3.12.iso'
can't be used as the requested device type.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MediumWrap
Interface: IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}
Callee: IVirtualBox {d0a0163f-e254-4e5b-a1f2-011cf991c38d}
Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
Expectation: No error popup at steps 7, which at the adding tails ISO image, and the rest of the step and could successfully start tails up
Attemps to get it work:
Attempt one: I watched one video from youtube that was about 7 months ago running tails in virtualbox, the process was pretty straightforward but I still get the same error.
Attemp two: I googled about the issue and only found simliar error. Those are conflicting Disk ID, which I applied the solution but got no luck.
I don't really use virtualbox much so are there anyway I can know more about the error message or anyone knows how to do with this? Thanks beforehand and appreciate for your precious time and help.
It is working now, the weird thing is that I have to directly open the .iso image instead of clicking on the folder that contains the .iso.
I have been trying to connect with a MySql database using Wt::Dbo::backend::MySQL latest version Wt-3.3.5 but I keep getting the error:
"MySQL error performing query: 'SET storage_engine=INNODB;': Unknown system variable 'storage_engine'"
MySql is running on windows 7, with latest version MySql Server 5.7.10.
I have tried to execute:
SET storage_engine=INNODB;
in the MySql command line and of course get the same Unknown system variable 'storage_engine'". The command that does work is:
SET default_storage_engine=INNODB;
Does this means Wt::Dbo::backend::MySQL does not support this version of MySql? I could not find anything on their documentation nor the internet.
Thanks,
I have found in the following links that indeed the variable "storage_engine" has been renamed to "default_storage_engine", which has caused some software to start getting issues with recent versions of MySql.
https://dba.stackexchange.com/questions/101908/migrate-jira-to-mysql-unknown-system-variable-storage-engine
https://confluence.atlassian.com/display/CONFKB/Confluence+fails+to+start+with+error+'Unknown+system+variable+'storage_engine''+using+MySQL+5.7.x
There are to possible solutions:
1) Change Wt::Dbo source by modifying the file "MySQL.C" around line 980 in function :
void MySQL::init()
{
executeSql("SET sql_mode='ANSI_QUOTES,REAL_AS_FLOAT'");
executeSql("SET storage_engine=INNODB;");
executeSql("SET NAMES 'utf8';");
}
By first somehow testing first which MySql version the server has and then SET the "default_storage_engine" variable instead "storage_engine". And then recompile the full Wt::Dbo library.
OR
2) Go back to the most recent version of MySql in which the variable "storage_engine" has not yet been renamed.
I opted for solution 2 and uninstalled MySql 5.7 and installed MySql 5.4 and now everything works just fine.
Hope this helps somebody out there... cheers!