VirtualBox Errors when starting whonix [closed] - virtualbox

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I'm trying to download whonix on my computer but I get 2 errors:
First Error: "The memory could not be written",
Second Error: "Failed to open a session for the virtual machine"
and then it says aborted.
First Error
SecondError
I have no idea what to do, I tried to:
Reinstall VirtualBox
Write in cmd: "sfc /scannow"
Install oldest versions of VirtualBox
Write custom size in virtual Memory(Control Panel->System and Security->System->Advanced system settings->(Performance)settings->Advanced->Change->Custom size)
Updates VirtualBox+Windows+Whonix+Drives
Enabled Intel Virtualization Technology(in BIOS->CPU Configuration)
Deactivate the 3d acceleration but I have no idea how
and nothing works :(
If it helps I have:
Operating system: Windows 10 Pro
Processor: Intel(R) Core(TM) i7-8700 CPU # 3.20GHz 3.20 GHz
Graphics Card: GTX 1080
Installed RAM: 32.0 GB
System type: 64-bit operating system, x64-based processor
Hope someone could help me!

I had the same problem
solution: VirtualBox → Settings → Storage → Type: AHCI → OK
it worked for me

Related

OpenGL over SSH (GLX) [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I run a X server on a Windows 7 machine with OpenGL 4.4. From there I ssh -Y to a remote machine where I start an OpenGL application. (for what it matters, the network connection is very fast, I have turned off compression and use arcfour,blowfish-cbc ciphers for speed)
glxgears runs, but not very smoothly. Reports it is doing 6000+ FPS though.
However, matlab fails to use hardware OpenGL rendering. I read the docs and they mention it requires OpenGL version 2.1. When I run glxinfo in the ssh terminal, it tells me:
GLX version: 1.4
OpenGL version string: 1.4 (4.4.0 - Build 10.18.15.4279)
I don't know the technical details of GLX, but does this mean that the OpenGL version supported over SSH is limited to 1.4? I understand that the latest version of GLX is quite old, compared to the progress of OpenGL.
I run a X server on a Windows 7 machine with OpenGL 4.4
The first problem start with this. A X11 server on Windows is just another program running there and ultimately is going to turn X11 commands into Win32 GDI calls. X11 itself does not "know" OpenGL, that's why there's the GLX extension. And GLX is an interesting beast and the X11 servers for windows all implement only a very basic baseline of OpenGL commands to support the essentials.
But that's only half of your problem…
From there I ssh -Y to a remote machine where I start an OpenGL application.
Doing this kind of thing always invokes indirect rendering where all commands have to be sent as a GLX opcode command stream. And unfortunately (for you) GLX opcodes have been specified only up to OpenGL-2.1, but full GLX support is mandatory only for up to OpenGL-1.4. OpenGL-1.5 introduced vertex buffer objects, which add quite a lot of complications for an indirect rendering contexts, so GLX may implementations opt not to support it for indirect rendering.
For Linux at least the proprietary NVidia drivers and client libraries have full indirect OpenGL-2.1 support. But the X11 server you're running on Windows, and likely the client library don't.

ESXi 5.5 crashing under load [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I have a whitebox dual CPU home server running ESXi 5.5.
I have loaded the server up with a bunch of VM's for learning Microsoft SCCM. I noticed that as soon as one of the guests gets under load, the host will crash with the attached photo (apologies for the quality). Could this be due to a dying CPU? I have noticed that one of the CPU's runs quite a bit hotter than the other.
Usually with CPU overheating the machine would shut down first, however if the temperature inside the case is too hot, something else might be getting affected (e..g memory or video display circuitry).
If you want to diagnose overheating, I can suggest placing a vacuum cleaner hose over the air vent, this will draw much more air than your regular fans. If the system stays up under load with the vacuum cleaner attached, it will be an overheating problem.
Not a programming issue, so I'll close this off and note the resolution I found incase anyone else has the same issue.
Looks like this was a known issue under ESXi 5.X that has to do with the E1000 and E1000e virtual network adapter as per the lines:
#BlueScreen: #PF Exception 14 in world wwww:WorldName IP 0xnnnnnnnn addr 0x0
PTEs:0xnnnnnnnn;0xnnnnnnnn;0x0;
0xnnnnnnnn:[0xnnnnnnnn]E1000PollRxRing#vmkernel#nover+0xdb9
0xnnnnnnnn:[0xnnnnnnnn]E1000DevRx#vmkernel#nover+0x18a
0xnnnnnnnn:[0xnnnnnnnn]IOChain_Resume#vmkernel#nover+0x247
0xnnnnnnnn:[0xnnnnnnnn]PortOutput#vmkernel#nover+0xe3
0xnnnnnnnn:[0xnnnnnnnn]EtherswitchForwardLeafPortsQuick##+0xd6
0xnnnnnnnn:[0xnnnnnnnn]EtherswitchPortDispatch##+0x13bb
0xnnnnnnnn:[0xnnnnnnnn]Port_InputResume#vmkernel#nover+0x146
0xnnnnnnnn:[0xnnnnnnnn]Port_Input_Committed#vmkernel#nover+0x29
0xnnnnnnnn:[0xnnnnnnnn]E1000DevAsyncTx#vmkernel#nover+0x190
0xnnnnnnnn:[0xnnnnnnnn]NetWorldletPerVMCB#vmkernel#nover+0xae
0xnnnnnnnn:[0xnnnnnnnn]WorldletProcessQueue#vmkernel#nover+0x486
Simply remove any adapters using E1000/e and replace with VMXNET3.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2059053

Unable to run virtualmachine - vbox amd-v [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I just received my new Thinkpad E545 and would love to set up a new virtual machine for development. After creating the appliance and adding the #! iso for installation, I tried to start up the machine and I get the following error:
Failed to open a session for the virtual machine CrunchBang.
AMD-V is disabled in the BIOS (or by the host OS). (VERR_SVM_DISABLED).
Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}
I did some searching and found this thread (https://askubuntu.com/questions/118006/amd-v-is-not-enable-in-virtualbox-in-amd-apu) and followed the advice about enabling virtualization in my bios, but I still get the same results from virtualbox, even after re-installing. After enabling virtualization in the bios, the acceleration tab in vbox is still not available (greyed-out and un-clickable).
Screenshot: http://i.imgur.com/ev3Ty53.png
Relevant laptop specs:
Processor AMD A10-5750M Accelerated Processor (2.5GHz to 3.5GHz, 4MB Cache, 1600MHz) with Radeon HD 8650G Graphics
Operating System Windows 8 64
Operating System Language Windows 8 64 English
Display 15.6W HD AntiGlare, Midnight Black
Graphics AMD Radeon HD 8570M 2GB Discrete Graphics
Memory 16GB PC3-12800 DDR3L SDRAM 1600MHz SODIMM
Keyboard Keyboard with Number Pad - US English
Camera 720p HD Camera
Hard Drive 320GB Hard Disk Drive, 5400rpm
Optical Device DVD Recordable 8x Max Dual Layer
Sorry, that I am so late, but at least someone else will be able to use my advice.
In the latest version of BIOS for this model (have the same one) they mixed up the setting: ENABLING amd-v DISABLES it.
Or this could be some bug of VirtualBox as stated above, however this worked for me.
I've just discovered that having hyper-V installed seems to prevent certain virtualisation features (such as 64 bit) being available to virtualbox. Switching hyper-V off (via add/remove windows features) fixed this for me.
Judging by a sudden spike in forum posts and Stack Overflow questions about this precise error code (VERR_SVM_DISABLED) starting right about when 4.3 came out, I'm willing to bet that this is a legitimate bug in 4.3.
I've triple-checked my BIOS settings and AMD-V is enabled...but I'm still seeing this error in 4.3.10. I never had this problem on 4.2.18.
And this bug report might be good additional reading: https://www.virtualbox.org/ticket/12049
You can simply change the Virtal machine from 64-bit to 32-bit

Hardware Fastboot Boot Method in XE11 not working? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I got stuck on my Glass unit with Launchy crashing (sideloaded the wrong version -_-) in XE11 every time I try to launch an application, including the built-in settings. The problem is for some reason I don't have ADB access anymore and because of Launchy, now can't even reenable Debug mode.
So I am now trying to boot into fastboot mode using the hardware method reference here: Having issues seeing GLASS in Fastboot
But when I keep the camera button pressed and press the power button briefly, the LED is solid for a few seconds and then goes on to blink at very low frequency. No matter how long I seem to keep the camera button pressed, the LED never goes solid.
I've also tried to plug in the unit to my computer and look for it show up in the System Information (the Apple Device Manager equivalent).
Does anyone know if the fastboot hardware method changed in XE11? Or what am I doing wrong?
Thanks in advance,
Charles.
The slow blink you're seeing is Glass in fastboot. Once in fastboot you can verify that it's connected by doing a device list:
$ fastboot devices
If you see output, you'll be able to run other fastboot commands.

How to access VirtualBox running on OSX over RDP [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
So, I read the manual three times, installed the Oracle service pack two times, tried to access five different virtual machines dozens of times with all kinds of authentications, followed every thread on this forum, all to no avail. I really did everything there is to do to my knowledge. But accessing Virtualbox regardless of the OS does not work in version 4.1.23. Two things seem just really bad:
The manual tells at no point WHERE on OSX the VBoxManager commandline tool is installed. But the manual references it dozens of times. It's on no search path in none of the shells I am using. Doing a find / -name "VBoxManager" as root reveals there is no such tool anywhere. Please, can someone let me know what to do to actually be able to do what the manual says with regard to the command line? Where does one get that tool?
I still would like to learn how one accesses a virtualbox installation with a remote screen. Here is what I tried;
as clients:
Apple Remote Desktop
Fails to find server
Apple VNC protocol from Finder
Fails to find server
VNCViewer (even though that is as unlikely to work for RDP as option 2)
Fails to find server
Microsoft Remotedesktop (that should work).
Fails to authenticate, after hitting the connect button one gets instantly the response that authentication failed, regardless of
means of authentication, such as NULL, External
Network interface (bridged, NAT)
IP address (the one the virtual machine obtains, localhost, my own host's ip address)
Port (tried different ports none of which were occupied)
Virtual OS (Windows 7, Windows XP, CentOS 6.3, ClearOS, backtrack 5)
Please, can someone help?