I'm trying to get Event-Based profiling session using AMDuProf (v3.5.677) but my setup is missing the
"Assess Performance" option
See my setup
See the screenshot from the manual (section 7.3.1)
The manual does say "Time-based" is the only supported option for Intel CPUs but I'm running on a Ryzen 5900x. Link to manual
I'm I missing something with the install ?
The only thing that showed up for me was this I disabled both "Hyper-V" and "Virtual Machine Platform", restarted and still did not see "Assess Performance"
Related
I'm using unity-sdk version 6.0.0 in Unity 2021.3.9f1. When I switch to any Platform other than "Windows, Mac, Linux" I get the following error in the console:
Assets\IBMSdkCore\Connection\RESTConnector.cs(668,24): error CS0656: Missing compiler required member 'Microsoft.CSharp.RuntimeBinder.CSharpArgumentInfo.Create'
Switching back to "Windows, Mac, Linux" clears the error. I have ensured that when viewing Assets/Watson/WatsonUnitySDK in the inspector that under Platforms only "Any Platform" is checked and that nothing is checked under "Exclude Platforms".
Any assistance would be greatly appreciated, thanks in advance.
The answer is in the "Configuring Unity" section of the unity-sdk GitHub repository:
"If using Unity 2018.2 or later you'll need to set Scripting Runtime Version and Api Compatibility Level in Build Settings to .NET 4.x equivalent. We need to access security options to enable TLS 1.2."
The setting is now labeled ".NET Framework", but switching to it from ".NET Standard 2.1" resolved the error.
I'm almost certain I remember setting the .NET version per the instructions when I originally set up the project, but I may be mistaken. Anyway it's fixed now.
EDIT: I had set the compatibility to .NET Framework. I just discovered that every time you change the build platform Unity reverts to 2.1 and you have to manually go switch to .NET Framework again.
I am trying to boot up a saved am using Macbook pro with M1 chip.
I tried the steps given at this answer. But was not able to boot up the VM. Can someone confirm this problem or already found out a solution to it?
I got the error "The virtual machine 'Ubuntu 20.04 64bit 1' has terminated unexpectedly during startup with exit code 1 (0x1)." below:
Had the same issue on Mac OS Big Sur 11.4 when I was trying to add my Ubuntu instance (on Intel tho), nothing suggested here and other topics helped.
Turned out you have to give access (Full Disc Access) to Virtual Box in Settings. Go to Settings -> Security & Privacy -> Privacy -> Full Disc Access -> plus sign (unlock it if needed) -> choose Virtual Box Application -> Open.
After that I was able to choose my Ubuntu image in Finder.
<New user, reputation too low to comment on David's post!>
As per David Leitko's answer, VirtualBox is an x86 (more specifically, AMD64/x86_64) virtualization hypervisor. However, it appears from various discussions I've seen on this topic that many users don't really understand what this really means.
So, it means not only that VirtualBox only runs on x86 CPUs, but also that it requires all the other elements of the x86 platform. These include system memory, various bus controllers (PCI, USB), hard disk controllers, sound cards, graphics, BIOS/UEFI, etc. None of these take the same form on the Apple Silicon platform - i.e. they don't use any of the standards built up in the PC ecosystem over the last 40 years.
So, not only will VirtualBox not work on Apple Silicon, it will never work on Apple Silicon. There will never be any way to run a VirtualBox image that ran on an Intel Mac on an Apple Silicon Mac. Ever.
The canonical discussion thread on the VirtualBox forums that covers this in more detail is here.
VirtualBox is an x86 virtualization hypervisor. It only runs on an x86 platform. See https://www.virtualbox.org
While Rosetta 2 will run many x86 apps very well on an M1 Mac, virtualization products are not supported per this Apple document
I just had the exact same problem after updating my VirtualBox app on MacOS Big Sur. What worked for me was to go to System Preferences - Security & Privacy - General, and then click the Allow button to allow extensions by Oracle (first click the lock symbol in the lower left of the screen and enter your password).
Actually, during installation I got this pop-up window telling me to do this, but I wasn't quite sure what exactly it wanted me to do. Only after getting this error I took the trouble of looking closer, ahem...
Hope this will fix your problem too!
When launching my game from NVidia NSight, I get the following error message:
Preparing to launch...
Launch failure: Process creation failure
Launch failed.
The game launches just fine, but with no way to attach to it, I can't do frame debugging or anything else. There is no other error message or information that is logged. This is on Arch Linux.
This is probably not the answer you were hoping for, but after running into the same problem, I sent a bug report to Nvidia (https://developer.nvidia.com/rdp/bugs/nsight-graphics-bug-reporting) and I was told that Arch isn't supported at the moment (see https://developer.nvidia.com/nsight-graphics-requirements).
It's possible that, if there is enough demand, support could be added. So feel free to send them some feedback/request as well.
As an alternative, for debugging, RenderDoc works well enough on Arch, but it's not very good for profiling.
FYI, Arch Linux has now been officially supported by Nsight Graphics.
Ubuntu 18.04, 20.04
RHEL 7.6
Centos 7.6
Arch Linux 2021.05.01
https://developer.nvidia.com/nsight-graphics-requirements
The vmware shows the error:
"Intel VT-x might be disabled if it has been disabled in the BIOS/firmware settings or the host has not been power-cycled since changing this setting."
What should I do?
Do you happen to know whether or not you'll be needing the Intel hardware virtualization feature enabled for the Ubuntu OS?
If not, you can ignore that message.
If so, you can enable it with the following:
With the system powered off, go into VM > Settings > Hardware tab, choose Processors from the hardware list, and check "Virtualize Intel VT-x/EPT"
This question already has answers here:
VT-x is disabled in the BIOS for both all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED)
(15 answers)
Closed 5 years ago.
I have installed Oracle VM VirtualBox 5.0.12, and now trying to start it up.
But shortly after trying to power it up, I get an error message saying:
VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED)
Have other readers experienced the same issue and resolved it successfully? Please let me know. I have checked out other threads on Stackoverflow which report the same error message, and tried out the suggestions mentioned there, but none of them is working for me.
If it would help, I am running Windows 7 Enterprise edition SP1 64 bit.
Does anyone have an idea what the problem could be?
You may have virtualization disabled on the host computer. To enable:
Go to your host computer's BIOS (during reboot, press F12, or Delete, or F2, ... depends on computer).
Find some options regarding virtualization. E.g. recent Lenovo's have it under Security / Virtualization.
Enable what's there to enable. E.g. VT-d technology [Enable].
This made it work for me.
Try going to Settings -> System -> Motherboard on VirtualBox and change the RAM size.
Increase the RAM size and try to start it up again. It worked for me, hope it works for you as well!
I ran into this issue with both of my ThinkPads (T450s and X1 Carbon), but this probably applies to other machines with Intel hardware.
One solution is to enable virtualization options in the BIOS of the host machine (not the guest VM).
Reboot and enter the BIOS (F12 usually)
Navigate to the virtualization settings. The exact menu navigation may vary based on your particular BIOS and version. For me it was Security -> Virtualization.
In my case there were two options, both of which were disabled:
Intel (R) Virtualization Technology
Intel (R) VT-d Feature
Enable both options
Save and exit (reboot)
This resolved the issue for me.
When I opened Settings->System->Motherboard, suggested by the answer above, I realized that the .ova file I had downloaded into VirtualBox had settings that exceeded my old computer's RAM size (as suggested by the warning message at the bottom of the screen). Once I was within the capabilities of my machine, the system started adequately.
In my case, I had 4GB of ram for the Virtual Machine (my host machine has 8GB of ram, and I was getting that error. I've change the ram amount to 2GB ram and my Virtual Machine booted perfectly.
However, I had already enabled virtualisation on my BIOS settings.
Non of the solutions worked for me. Instead, I tried the following:
System -> Acceleration -> Uncheck Enable VT-x/AMD-V
changing the ram did not work for me so i found another solution
on virtualbox navigate to Settings -> System -> Processor and then click on (Enable PAE/NX).
this solved my problem.
First, you should check if virtualization is enabled.
You can use the free tool provided by SAS Support: http://support.sas.com/kb/46/250.html
If virtualization is not enabled, then you have to enable VT-D function in BIOS (for my Asus Motherboard it was in Advanced-->System Agent Configuration settings).
I also had to enable Intel Virtualization Technology in CPU settings.
Now everything works seamlessly.
I have faced the same issue with Ubuntu 16.04 (xenial) at Dell Latitude E6500.
First I have updated the VB and my symptom changed. There was no option to create x64 machine at all and a user friendly message box while trying to deploy an old one.
I have found a similar story described here. And this link brought me there to the final solution.
In short words, for Dell BIOS you need to keep
Performance -> Trusted Execution = OFF
I solved the problem by reducing the memory size in settings-> system