Tag Info

Hot answers tagged

90

In order to get the VM connected to the internet you have to tie it to the Ethernet/Wireless NIC Card. In order to do this you have to create a "Virtual Switch". Open your Hyper-V Manager Select Action --> Virtual Switch Manager Select External and then Create Virtual Switch Give the Switch a Name and then select the External Controller you use to ...


41

Windows Virtual PC has been phased out in Windows 8, and has been replaced with the more full-featured Hyper-V. Additionally "XP Mode" is no longer available and, if needed, you'll have to install an actual previous copy of XP with a license that you already own, as the XP Mode license was granted only to users of Windows 7 specifically (more info here and ...


35

A Type-1 Hypervisor means that it has direct access to the hardware. Type-2 Hypervisor refers to being running on top of another host OS and doesn't have access to the hardware. This is why there are many limitations on virtual machines running within another OS eg the VM can't use a physical wireless card, but has to use a virtual one instead. Here's a ...


29

I have got a solution. This method will allow me use one technology at a time (which is my current requirement) You can disable Hyper-V without uninstalling it. Start a command prompt with administrator rights and execute the following command: // to disable hyper-v bcdedit /set hypervisorlaunchtype off // to enable hyper-v bcdedit /set ...


23

Disclaimer: I haven't done this for removing a feature, AND as a final caveat there's probably going to be a slew of Windows Update updates to install every time you enable it again. Having said that, from an elevated command prompt: dism.exe /Online /Disable-Feature:Microsoft-Hyper-V and dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All Here's ...


21

What appears to have been the problem is that the bridging protocol was not supported by the AP (access points) of my university. Here is the workaround (as far as I can tell this way is more robust than the bridging way that is done by default, but there might be some additional overhead (not sure how much)): Create an internal network switch Connect it ...


14

This is an old answer but for the shake of completeness and because it managed to be the top g result while I knew there was a better way: bcdedit /set hypervisorlaunchtype off to disable hypervisor, and: bcdedit /set hypervisorlaunchtype auto to reenable it(default value). Of course it still requires restart.


12

Modify the file C:\ProgramData\VMware\VMware Player\Uninstaller\bootstrap.lua or C:\ProgramData\VMware\VMware Workstation\Uninstaller\bootstrap.lua using a text editor and comment out line CheckForMSHyperV() with two dashes, so it will become --CheckForMSHyperV() Then save the file and rerun the uninstall and it will succeed.


10

Unfortunately that seems to be the case: System requirements / Specifications An x64-based processor running an x64 version of Windows Server 2008 Standard, Windows Server 2008 Enterprise or Windows Server 2008 Datacenter. Hyper-V System Requirements and Specifications Credits to Diago: The alternative to Hyper-V for Windows 7 is ...


9

I had to disable and then re-enable the Allow management operating system to share this network adapter under the Virtual Switch Manager. If this isn't checked the host machine will not be able to use the chosen adapter. It had been checked in my case, for some reason I had to flip it back and forth again.


9

There are two ways you can do this: Change the resolutions within the remote OS If connecting to a Windows OS, connect using Remote Desktop Connection instead of Hyper-V Viewer. Using RDP allows for more functionality including Client Screen Size, Audio, and Remote USB integration.


8

I would recommend against using a wireless connection with Hyper-V, as it can cause no end of issues when trying to connect to networks. You could try changing your Hyper-V network to an Internal network: This appears as a new virtual network adapter in your host: Then depending on your needs, either enable Internet Connection Sharing on your wireless ...


8

There are a few requirements that must be met to enable Hyper-V on Windows 8. According to this TechNet article, other than SLAT, you must also have 4GB of RAM and the system must be 64-bit. These requirements are listed on the Client Hyper-V page on TechNet. There is a simple check that you can also run to verify that your system meets the requirements. ...


7

I had the same problem. I was using my laptop which only has a wireless connection. No build in Ethernet card. The system is windows server 2012 standard. I was trying to use hyper-v to install ubuntu 12.04 lts. I got the same issue. Ubuntu wont be able to access the internet, the network keeps connecting and disconnected. So, i followed "Joe and Alan" ...


7

No. Hyper-V is very specific about supported OS's and the generic drivers are very Microsoft specific.


7

This is very easy in PowerShell using the .NET Framework, I've just tested it on an external drive :) PS C:\>$drive = New-Object system.io.driveinfo("F:") PS C:\>$drive.DriveType Removable You can also use WMI: C:\>wmic wmic:root\cli>logicaldisk get caption,drivetype Caption DriveType C: 3 D: 5 E: 5 F: 2 Where drive types ...


7

"I want to run about 8 VMs at one time using Hyper-V." Why on earth would you want to do such a thing? Since you are unlikely to be able to load ALL 8 concurrently during development (except, perhaps, for a brief load test) you can probably run all 8VM's in 2Gb and still make good use of all those cores.


7

Launch Hyper-V Manager from your App Menu In the Actions area in right-hand navigation, click “Virtual Switch Manager” When the Virtual Switch Manager window opens, select “New virtual network switch” on the left, select “Internal” on the right, and then click the “Create Virtual Switch” button Give the new switch a name like “Virtual WLAN” and click “OK” ...


7

Well, I figured it out. I had to create an Internal Virtual Switch and then go to the External Virtual switch and share its connection with the Internal Virtual Switch.


6

try launching: appwiz.cpl and then going to add / remove feature. Search for it there. Bring up the Run box, command prompt, or Start Search and type "appwiz.cpl" without the quotes. Once the Add / Remove programs dialog opens, click Add / Remove features on the left. Find the Hyper-V add-in and un-check it. In fact, a quick search confirms this should ...


6

You miss the BCD entry to load the Hyper-V driver. Open a command prompt as admin and run this command: bcdedit /set {current} hypervisorlaunchtype auto reboot and the Hypervisor driver is loaded.


6

Steps to resolve this problem: go to virtual machine go to control panel-> programs and features remove "Virtual PC Integration Components" shut down and turn on virtual machine


6

According to this, Hyper-V client is only available on Pro and Enterprise Can I run virtual machines on my desktop? Windows 8 Pro and Windows 8 Enterprise include Client Hyper-V; the same is true for Windows 8.1. You can use Client Hyper-V to develop and test applications, evaluate and learn about new technologies, and so on. This is the same ...


6

Install EasyBCD Run it from within Windows 7. With this program you can edit your bootloader with a GUI (which I prefer over a command line). You can add and delete installations, so delete your Hyper-V entry and after that you can savely delete the partition. Problem solved! Just a note of caution: you can seriously screw up your computer if you don't ...


6

Hyper-V does not let you use the full power of the host hardware. There is a performance hit and screen update problems that makes it unusable for games that rapidly update the screen. On the other hand it may work for encoding videos or turnbased games. I personally used it to play the city builder Zeus, and it seems to work find. However, by ...


6

After some more Googling last night I got a lead that it might be a limitation of Windows 8 Client Hyper-V. Here's a guy having issues with two OS's reporting different VT-x values. This SuperUser question put me on to the idea that Client Hyper-V has some hard limitations. This morning I've uninstalled Hyper-V from the "Turn Windows features on or off" ...


5

Hyper-V for Windows 8 is a newer version of Hyper-V (V3) than Hyper-V for Server 2008. It is not recommended to import VM's created from Windows 8 to Server 2008. However going from Server 2008 to Windows 8 has no problems. If you MUST migrate from Windows 8 to Server 2008 Hyper-V make sure to NOT use the .vhdx files. Converting .VHD & .VHDX: Open ...


5

Here is how you can change the resolution of Ubuntu (Linux) running in Hyper-V: Install linux-image-extras (hyperv-drivers): sudo apt-get install linux-image-extra-virtual Open the Terminal and type: sudo gedit /etc/default/grub Find the line starting with GRUB_CMDLINE_LINUX_DEFAULT, and add video=hyperv_fb:1920x1080 (or your preferred resolution) in ...


5

Here are requirements for Hyper-V : Hyper-V is 64-bit only and thus requires a 64-bit (x64) processor Hardware Virtualization Assists in the form of: Intel VT-x / AMD AMD-V Hyper-V requires Hardware Data Execution Prevention : Set these BIOS options to enable: On Intel processors this is called Execute Disable (XD). On AMD processors this is called ...


5

I found this answer via reddit, by user 6306 : hyper-v has limited resolution when you access the console view, it's a professional virtualisation application and doesn't need fancy consumer features. The console view is effectively "sitting in front of the machine" view, most administration is done through remote desktop. The best thing to do is download ...



Only top voted, non community-wiki answers of a minimum length are eligible