LG Smart TV SDK emulator on Virtual Box doesn't starts - windows

I'm new on LG smart TV apps. I've installed the SDK provided by LG (Oracle Virtual Box, Safari, Eclipse, sdk itself).
Now everything is running, but when I try to launch the emulator, a remote control is displayed, and on the virtualbox window, I see an error and no emulator is launched.
This is my plataform:
Windows 7 on a intel i7, 8 gb ram
Virtual Box 4.1.18 (I've installed 4.2.4 before, but sdk installer replace it to 4.1.18)
Safari 5.1.7
Java JRE 1.6
LG Smart TV SDK 3.0.0
This is the log generated by Virtual Box:
VirtualBox 4.1.18 r78361 win.amd64 (Jun 5 2012 15:58:23) release log
00:00:05.144 Log opened 2015-09-28T15:09:54.564361900Z
00:00:05.144 OS Product: Windows 7
00:00:05.144 OS Release: 6.1.7601
00:00:05.144 OS Service Pack: 1
00:00:05.144 Host RAM: 7926MB RAM, available: 864MB
00:00:05.144 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:05.144 Process ID: 12536
00:00:05.144 Package type: WINDOWS_64BITS_GENERIC
00:00:05.145 Installed Extension Packs:
00:00:05.145 None installed!
00:00:05.156 Power up failed (vrc=VINF_SUCCESS, rc=E_FAIL (0X80004005))
00:00:05.439 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} aComponent={Console} aText={The virtual machine is not powered up}, preserve=false
Is there any known issue about this? What is the reason because "Power up failed"? How can I fix the VM? Does this software really works on Windows?
Thanks!

I would try 4.2.18 and make sure you are installing the correct SDK for your OS (x64/x32).
You can uninstall VBox and reinstall if needed and again check your architecture

Related

Why I might suddenly get persmission denied when I just open TortoiseHG?

I installed TortoiseHG 5.6.1 (x64) on guest Win 7 Ultimate x64 in VirtualBox. The host OS is Win10 Enterprise x64. When I right-click in any folder and select "Hg Workbench", it opens successfully. After that, I accidentelly deleted the *.vdi file and had to reinstall both OS and TortoiseHG again. But, this time when I right-click and select "Hg Workbench" I always get this error:
I tried older TortoiseHG versions, but I get the same error. I even tried to reinstall guest OS again, but it didn't help. I just installed OS and TortoiseHG, so what can be that I did accidentally the first time and/or other times?
UPDATE 1
I installed TortoiseHG 5.6.1 (x64) on guest Win 10 x64 in VirtualBox and I didn't get that error message. So, it has to be something with Win 7. What can that be?

Is it possible to use Docker without Windows 10 pro?

I need to install Docker on my pc with Windows 10 home. I read that I can only install Docker Toolbox. Is there any way to have the latest Docker version instead without upgrading my pc to windows 10 pro?
Thanks
Update
Docker can now be installed on Windows 10 Home (version 2004 or higher).
Refer to this article for installation instructions
https://docs.docker.com/docker-for-windows/install-windows-home/
Old Answer
Docker for Windows requires Hyper-V, and Hyper-V requires Windows 10 Pro (or Windows Server). So no, you can't run Docker without upgrading.
https://docs.docker.com/docker-for-windows/install/
README FIRST for Docker Toolbox and Docker Machine users: Docker for Windows requires Microsoft Hyper-V to run. The Docker for Windows installer enables Hyper-V for you, if needed, and restart your machine.
https://learn.microsoft.com/en-us/virtualization/hyper-v-on-windows/quick-start/enable-hyper-v
Check Requirements
Windows 10 Enterprise, Professional, or Education
64-bit Processor with Second Level Address Translation (SLAT).
CPU support for VM Monitor Mode Extension (VT-c on Intel CPU's).
Minimum of 4 GB memory.
The Hyper-V role cannot be installed on Windows 10 Home.
You can now install Docker Desktop on Windows Home machines using the WSL 2 backend. Docker Desktop on Windows Home is a full version of Docker Desktop for Linux container development.
https://docs.docker.com/docker-for-windows/install-windows-home/
Install Windows 10, version 2004 or higher.
Enable the WSL 2 feature on Windows. For detailed instructions, refer to the Microsoft documentation.
https://learn.microsoft.com/en-us/windows/wsl/install-win10
The following hardware prerequisites are required to successfully run WSL 2 on Windows 10 Home:
64 bit processor with Second Level Address Translation (SLAT)
4GB system RAM
BIOS-level hardware virtualization support must be enabled in the BIOS settings. For more information, see Virtualization.
https://docs.docker.com/docker-for-windows/troubleshoot/#virtualization-must-be-enabled
Download and install the Linux kernel update package.
https://learn.microsoft.com/en-us/windows/wsl/wsl2-kernel

Can't launch AVD on macOS 10.13

I created some AVDs in Android studio 3.0, but I can't launch them. I used the following command to launch them:
./emulator #Nexus_5X_API_17
logs:
emulator: WARNING: encryption is off
Hax is enabled
Hax ram_size 0x60000000
Failed to open vm 3
Failed to create HAX VM
No accelerator found.
failed to initialize HAX: Invalid argument
And when I reinstalled "Intel x86 Emulator Accelerator(HAXM installer)", the logs:
HAXM silent installation only supports macOS from 10.8 to 10.12 !
I don't know if it is related with this.
After that, I tried to install virtualBox to install genymotion, but I found when I clicks the virturalBox.dmg, the installer crashed.
Could you help me? thanks.
Use the new Hypervisor.Framework support instead of HAXM on macOS, as described in the comments of the issue filed for this:
Try running the emulator on Canary channel 26.1.x (API 25/26
recommended) with Hypervisor.Framework; put the text "HVF = on" in
~/.android/advancedFeatures.ini (create this file if it doesn't exist
already).
You can download and install the latest version haxm
https://github.com/intel/haxm/releases/latest
Following steps worked for me:
Uninstall HAXM from android studio SDK manager (Tools->Android->SDK Manager->SDK Tools then uninstall 'Intel x86 Emulator Accelerator (HAXM)' by unchecking it.
Download the HAXM version 6.2.1 zip file from Intel site https://software.intel.com/en-us/android/articles/intel-hardware-accelerated-execution-manager-end-user-license-agreement-macosx
Install the .dmg file
Restart your computer
Open your AVD having x86_64 image and it should work.
Go to your SDK installation directory, and manually run the HAXM installer. See step 4 on the page: https://developer.android.com/studio/run/emulator-acceleration.html#vm-mac
Technically HAXM is only officially supported up until MacOS 10.12 (Sierra) . Since MacOS 10.13 is still in beta, there may be a bug or incompatible API. If the wizard does no work, please file a bug here for the Android Emulator dev team to investigate further: https://source.android.com/source/report-bugs
Go to Tools->Android->SDK Manager, then in the SDK tools search for Intel x86 Emulator Accelerator (HAXM installer) and update to the latest version, restart and thats all!
On install/reinstall of HAXM you get:
HAXM silent installation only supports macOS from 10.8 to 10.12 !
From https://issuetracker.google.com/issues/62395878#comment44
in System Preferences > Security & Privacy > General, there was a message “System software from developer xxx was blocked from loading.” with an Allow button. Clicking the allow button enabled HAXM again
I just redownloaded the simulator and it worked.

Xamarin Android Player Error when attempting to find VirtualBox

I have a clean install of Windows 10. After installing Visual Studio 2015 and Xamarin Bussiness edition I installed Xamarin Android Player x64 and now I receive the following error:
Error when attempting to find VirtualBox please check it's installed and try again.
Xamarin Android Player will now exit.
A solution is referenced in Xamarin fourms stating
Fixed it by adding "C:\Program Files\Oracle\VirtualBox" to my %PATH%
I am able to open VirtualBox version 4.3.28 r 100309 without issue.
How do I implment this solution or is there a newer solution?
I am running Windows 10 Professional and did a clean installation. Had the same problem. I opened the environment variables and the "VBOX_MSI_INSTALL_PATH" was set to:
C:\Program Files\Oracle\VirtualBox\
I changed it to
C:\Program Files\Oracle\VirtualBox
and it worked for me.. (notice the last backslash)
Thanks .. Ragnar Kofi Billy Force on facebook
Try installing the Latest version of Virtual Box, Since v5.0 has fixes for Windows 10
http://download.virtualbox.org/virtualbox/5.0.4/VirtualBox-5.0.4-102546-Win.exe
Changelog: https://www.virtualbox.org/wiki/Changelog
Windows hosts: fixed crash when opening Windows dialogs from the VM process on Windows 10 (bug #14351).
Windows hosts: fixed host-only adapter creation issues on Windows 10 (bug #14040)
Windows hosts: fixed audio on Windows 10 (bug #14432).
Windows Additions: fixed a potential crash in the WDDM driver with Windows 10 (bug #14190).
VRDP: allow Windows 10 RDP clients (bug #14216).
Windows hosts: fix for Windows 10 build 10525 and later (bug #14502).
Windows hosts: fixed network adapter enumeration on Windows 10 (bug #14437).
VMM: fixed an issue with Windows 10 guest kernel debugging over the network for Hyper-V paravirtualized VMs.
I have a same problem too and installing the latest version has fix it
Add VirtualBox to your system environment PATH variable.
None of the other answers helped me. The Android Player installer was forcing the install of Virtual Box 5.0.4 which was not working on Windows 10 Home (build 14393.51).
What did work for me was to install the latest virtual box (version 5.1.2 r108956) after installing Android player. While I can't start the android devices from Virtual Box's manager, I have had no problems starting them from Android Player or Visual Studio.
Just run as admin (Right hand click on desktop shortcut)

BSD Root Error Virtualbox install Mac OSX

I am trying to install Mac OSX on Windows XP using virtualbox and keep getting this message: BSD root: disk1s3, major 14, minor 3. I have assigned an 80gb virtual hard drive and have tried other iso files, but get the same message.
Technically installing MAC OSX on a virtual machine is against the EULA. That being said it's not a trivial operation to get OSX running on a VM. You might want to check out The OSX86 Project

Resources