I have this error message:
The windows phone emulator requires Hyper-V. Your PC is missing the
following pre-requisites required to run Hyper-V:
I cannot run my project on windows 8 phone emulator since days. I searched on internet, still I couldn't solve my problem. Everyone says open Control-panel, then click turn-off or turn on windows features, then choose hyper-v option. When I clicked turn off or turn on windows features there is no option about Hyper-V. Can anyone help me?
My computer features:
windows-8 Professional (64Bit)
intel core i7 processor
8Gb ram
First step
1- turn on hyper-v from bios
read this :
http://blogs.technet.com/b/canitpro/archive/2014/03/11/step-by-step-enabling-hyper-v-for-use-on-windows-8-1.aspx
2- turn on hyper-v from windows
At the Start Screen, swipe the right hand side of the screen and select the Search Charm.
Type turn windows features on or off and select that item.
Select and enable Hyper-V.
If Hyper-V was not previously enabled, reboot the machine to apply the change.
I formatted my os from windows 8 pro to windows 8 enterprise and I solved my problem easily.I know it is not a logic solution but it worked.
In order to run Windows Phone 8 emulator you need to enable Hyper-V technology in the BIOS of your PC. See the detailed article on how to do this.
First you must turn on hyper-v from bios and then turn hyper-v from windows featured list restart and then will work ..
Related
My machine is HP EliteBook 8540w which supports Hyper-V as far as I know and I have enabled it in BIOS. However, I am receiving the following error when trying to start emulator for Windows Phone apps in Visual Studio 2015:
Windows Phone Emulator is unable to start because the hypervisor is not running.
The more detailed screen shot follows:
According to my i7-720QmCPU specs, it supports VT-d
So what is the reason for it being unable to start the emulator on my machine?
Update:
I also checked using the BIOS settings using coreinfo tool with the results as in the following picture:
Update:
Following stijnvangaal's comment, I ran the following command as administrator and rebooted.
'bcdedit /set hypervisorlaunchtype auto'
But, in the wake of next run I faced the following Window ("Virtual machine service not running")
Then, I started this (by clicking the link on the message box):
Under, action menu, I clicked "start service" and then ran the application again in visual studio. Success? Not yet unfortunately, ending up in this (feeling desperate):
I had the same issue :
1 - I disable the Hyper V mode in the Windows Feature :
Go to ‘Programs and Features’.
Select Turn Windows Features on or off.
Deselect Hyper-V and click OK.
2 - Restart the computer
3 - Enable Hyper V again in the Windows Feature.
And it works !
Hope it help :)
Just disable Hyper-V on "Programs and Features" (if it is enabled). Then restart computer and turn it on again. Problem solved for me
I am really new to Windows Phone 8 App development. I would be grateful to you if you can answer my question. I have a machine with Intel(R) Core(TM) i3 processor and when checked I found out that my virtualization setting enabled.
I installed Windows Pro 8.1 in to my machine and then it indicates that my Hyper Visor is default switched off and I had to run it. But when I run it after making some of the changes by restarting the machine, suddenly for some unknown reason it undoes every change made finally leaving the machine with no Hyper Visor running.
I come across the same process when I am to run the Windows Phone emulator to test Windows Phone 8 Apps.
I hope my issue is clear to you all, can someone help me to fix this issue or tell me the exact reason behind this?
I would look at my Windows Event log and see if you perhaps there's a problem with Hyper-V being incompatible with a driver or something like that. It may be failing to reboot and the doing a system restore to get the machine back to a bootable state (by rolling back Hyper-V). I've had problems with Hyper-V and my HP laptop's blue tooth drivers:
Here's the thread where I found out about that:
HP Bluetooth / Hyper-V woes
Updating the driver to the newest version on HP's site fixed my computer for a while, but then I had problems with Windows Update hosing my machine with an update to the Bluetooth driver.
I seem to have fixed it for good by going to RA Link's website and downloading a version of the driver that's newer than the one on HP's website. I'm not at my personal computer right now, but if you'd like I can see if I can find the driver version that seems to have fixed my Bluetooth/hyper-v problems for good.
-Eric
I am tryin to install kali linux 1.0.9 on virtualbox for some testing purposes. (I am new with virtual machines). So i downloaded the 64-bit version of the os. i have got two problems:-
for some reason virtualbox does not show me a debian 64 bit version option in the settings(however it does show 32-bit option).
virtualbox doesnt allow me to change the no. of processors(default value is 1). i have got 8 cpus.
please help. my specs - intel i7 2670 memory- 6GB HDD-700 GB graphics - radeon 7670 HD
I have got windows 7 ultimate 64-Bit installed on the host
You need to enable 'Virtualization' option in your BIOS settings. The name of the settings may be different in different BIOS/motherboard brands. But you can easily identify it, in the BIOS.
I also had the same problem. I am in windows 8.1 and for my case, the problem was due to conflicts with Hyper-V who was activated in my system. I solved the problem by disabling Hyper-V.
Open windows features and Uncheck Hyper-V, click/tap on OK
My virtual machine of 64-bit Debian 7.5 (wheezy) was working in VirtualBox 4.3.12r93733 on a Windows 8.1 Pro (64-bit Operating System, x64-based processor: Intel(R) Xeon(R) CPU E5-1620 v2 # 3.70GHz 3.69 GHz) machine (Dell Precision T3610) yesterday. But when I tried it this morning I got an error message saying: VT-x/AMD-V hardware acceleration is not available on your system. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot. I chose to continue but as promised I made it as far as choosing between system modes (regular or recovery) before the screen blacked out.
When I searched this message online I found answers saying to make sure the BIOS had virtualization enabled. My BIOS has 3 options under Virtualization Support: Virtualization, Virtualization for Direct I/O, and Trusted Execution. The first two were enabled but the last was not. (This is a work machine, so I am hesitant to load defaults without speaking to someone from IT first.)
Aside from downloading and initiating an install for Visual Studio Express 2012 (which has since been uninstalled), little has happened on this machine since the Debian virtual machine was last working. So I also investigated and uninstalled the Windows Updates from yesterday on, in case they were involved. (One in particular mentioned having to fix the BIOS.) The ones that were marked important, including the one that fixes BIOS, have been reinstalled.
At this point I started looking into VirtualBox's settings. In my online research I found several forum posts recommended going into Settings->System->Acceleration, a tab that is greyed out for me. While at Settings->System->Motherboard, I noticed my pointing device was set to USB Tablet. When I changed it to PS/2 Mouse and tried the VirtualBox again, the error message went away but the OS still does not successfully boot.
My most recent revelation happened after this: Under Settings->General->Basic, I noticed my version was set to Ubuntu (32 bit), even though I am sure it was at Debian (64 bit) yesterday. But only 32-bit OS's are options, when my machine ought to be capable of having 64-bit ones too.
My question is: What could have caused VirtualBox to lose all 64 bit options, including a working Debian (64 bit), overnight?
You probably have had Hyper-V installed and enabled.
Cross check and Disable the setting from :
Control Panel >> Programs and Features >> Turn Windows features on or off
Reference : https://forums.virtualbox.org/viewtopic.php?f=6&t=57926
try this on virtualbox:
go to your virtual machine setting (right click on VM icon > setting) then go to system > acceleration and ensure that "Enable VT-x/AMD-V" checkbox is checked.
This programming guide implies that this is possible, so I figure what the heck.
Right now, though, it doesn't work.
Host OS is Vista 64-bit, VMWare Workstation 6.5.3 is running Windows 7 Enterprise 32-bit.
Installed Software on the VM:
Visual C# 2010 Express
Microsoft Server Speech Platform Runtime
Microsoft Server Speech Recognition Language - Kinect
Microsoft Speech Platform SDK
Kinect for Windows SDK Beta
I plug in the Kinect, the device is recognized by the VM, then I run the Sample Shape Game and it doesn't recognize the device. It says "Plug in the Kinect and try again" which turns out to be error 0x80080014, which leads to
http://social.msdn.microsoft.com/Forums/en-US/kinectsdknuiapi/thread/4da8c75e-9aad-4dc3-bd83-d77ab4cd2f82/
which gives me two things to look at:
is it plugged in with the special cable? yes
are all 4 entries in the Device Manager? no
In the Device Manager, I see a "Microsoft Kinect" group containing Microsoft Kinect Audio Control, Microsoft Kinect Camera and Microsoft Kinect Device, but there is nothing under "Sound, video and game controllers" other than VMware VMaudio. "Kinect USB Audio" should be there.
I'm guessing that there is some further twiddling I have to do with the VMWare USB / hardware options (whatever that tray with the USB / CD / HD / floppy etc icons is called) or some deft combination of rebooting and (un)plugging, but I'm almost out of enthusiasm.
Any ideas? TIA
EDIT: I realized that I had some lingering drivers on my host (Vista) system from OpenKinect. After removing them, I can no longer see the Kinect at all in the VM. Hmm.
There is this on read.me
Virtual machines: You must run applications built with the Kinect for Windows SDK Beta in a native Windows environment. Kinect for Windows applications cannot run in a virtual machine, because the Microsoft Kinect drivers and this SDK Beta must be installed on the computer where the application is running.
just to share that (not really understood how) VM Workstation 8 running in a host win 7 x64 with guest OS Ubuntu 10.04 sucessfully detected and installed Kinect drivers.
I was able to test it with libfreenect (OpenKinect Project) http://openkinect.org/wiki/Getting_Started#Manual_Build_on_Linux
best regards,
I'm late to the party, but we've been running and developing for the Kinect with Windows 7 running under VMWare under Mac OS X Mountain Lion.
I'm not a Computer Scientist, but I thought Turing showed that a universal Touring Machine was basically the same as physical hardware. I've had Distributed COM+ running on 3 or 4 VM's on the same physical hardware, but somehow the Kinect device is different? I don't buy that at all.
The most recent version of Microsoft Kinect for Windows (v1.6, possibly slightly earlier versions) in combination with the "Kinect for Windows" hardware does work inside a virtual machine. I run this setup on a MacBook Pro, Parallels 7 and Windows 7.
Note that a Kinect for Xbox does not work inside a virtual machine.
This page from Microsoft says that the "Kinect for Windows" device should work in a VM, but that the "Kinect for XBOX" does NOT work.
First of all you just need two Things to be installed:
libfreenect
libusb
after that you should set three flags to 0x02 at the line
typedef enum {FREENECT_DEVICE_MOTOR = 0x02,FREENECT_DEVICE_CAMERA = 0x02,FREENECT_DEVICE_AUDIO = 0x02,} freenect_device_flags;
Inside the headerfile located at /usr/local/include/libfreenect libfreenect.h but you will lose the ability to control the movement and the the microphone usage will be disabled so don't even try to access them or your device might get damaged after that you should also set
#define PKTS_PER_XFER 32
#define NUM_XFERS 6
inside your libfreenect/src/usb_libusb10.h file at the linux Line
After that rebuild your libfreenect by
mkdir build
cd build cmake ..
make make install.
Than Restart your virtual System and plug and connect only the Kinect Camera Device and no other Kinect device during start of the VM. When System is up you could test your device is properly working by switching to your previously created libfreenect build directory and go to bin there you run ./freenect-camtest you should get no or only a small number of package losses if a lot of losses occur try restart your vm with the camera device pluged in and already connected to your vm. You might need to active disconnect and connect the Webcam from the VM during startup to receive images this should be done during first seconds of VM Boottime!
Works with Ubuntu 14.04 and Workstation 10 and 11 and 11.1
HOST OS Windows 7 and Kinect SDK installed and Kinectdevice for Windows
Also it seems to be quite unstable you often have to restart your virtual system if you can't receive images from your Kinect. But if you once received images don't unplug device or you won't get data until you reboot virtual system with Kinect Camera connected to it.
=> This actually solved the problem otherwise to much frames get lost and its not possible to display proper image!