since yesterday I had my Windows 2012R2 Datacenter server correctly running Hyper-V machines.
After a windows update I'm not able to start any of the VMs and get a message that say Hypervisor not in execution.
If I check from services I don't see the service but from server manager the hyperv role seems to be running.
From windows features list i don't see anymore the Hyper-v (i wanted to uninstall and reinstall it).
Any suggestion?
It is unlikely that Windows updates have deleted any services.
You should still be able to see the Hyper-V Virtual Machine Management service even if it is stopped or running/broken.
If not, I suggest that you re-install the Hyper-V role.
Related
I have a GCE Virtual Machine with Windows 2008 R2 Datacenter OS and I need to upgrade to Windows 2012 R2 Datacenter OS. I have found suggestions on the internet but I didn't find a formal process to do this, only suggestions.
I only have tried doing the upgrade using the OS Installer in place, but after the restart step, the VM seems to crash because doesn't respond.
N/A
I have GCE VM Windows 2008 R2 DataCenter and I need to become in GCE VM Windows 2012 R2 DataCenter. The process that I tested seems to do the VM crash.
Is it possible and how to upgrade an existing GCE VM OS?
For Windows, this is not supported. There are a number of technical reasons, but the primary reason is licensing. Windows images are "Premium Images". Also, Google does not provide a method for "major" version upgrades. You need to create a new instance and copy/restore your data.
I have a Windows 10 machine. Recently I have installed Hyper-V 2016 server on my machine. From then whenever I start my system I only see a blue screen with various commands. I do not see any other thing other than that. Now how can I go back to my normal Windows machine?
See this image for reference:
you had Windows 10 installed on your machine now you have Microsoft Hyper-V Server 2016.
I assume you downloaded an ISO and installed that one. Whereas within Windows 10 you only have to activated a feature called Hyper-V.
Grap your latest Backups and install Windows 10 back onto your machine.
KR
Guenther
I am using Amazon windows 10(2016 server) server for running my application.I need to run VMware in windows but it shows,
VMware Player and Hyper-V are not compatible. Remove the Hyper-V role from the system before running VMware Player.
I did not install Hyper-V even though VMware is not working, showing above statement.
If Hyper-V is installed you will need to uninstall it for VMWare to run, you can do this by:
Press the Windows key + X
Then go to `Programs and Features`
Click Turn Windows Features on or off
Open Hyper-V
Toggle if off and then click okay.
Note: you may need to restart the virtual machine afterwards.
I've already tried running Docker on a Windows 10 Virtual Machine without any success. I understand why, so I've given up trying to enable this. However, it's got me thinking about Windows Server 2016. As I understand it, Windows Server 2016 has docker included as a component/service, instead of an 'Add On' as it is in Windows 10. Are there any reasons why a Microsoft Server 2016 Virtual Machine would not support docker? This is more for convenience than anything else. Dual-booting with windows 10 isn't a major issue and we've done that, but it does mean in certain circumstances I have to reboot to windows 8 for certain organisation-specific content that I can't access in Windows 10.
I am currently using Windows Server 2008 Standard and have several Hyper V machines. These are development VM's and I want to now switch back Vista x64 because I am missing Aero.
I know Windows Server 2008 can have aero but the host performance is very very bad when I run VM in Hyper V.
I want to export my Hyper V machines so that I can use it in Virtual PC. Anyone know an easy way?
If you have built them as Hyper-V machines, I don't think you can go back. There are serious differences in the HAL for Virtual PC and Hyper-V. You can move a VPC to Hyper-V permanantly by removing the VPC add-ins ans adding the Hyper-V integration drivers/services and re-detecting the hardware.
A VPC can run in Hyper-V just fine, don't add the machine drivers for Hyper-V and you can go back to VPC with no problem.
VPC to Hyper-V is one way.
Hyper-V is designed to be used on the server, obviously. Whereas VirtualPC is designed for the end user. Hyper-V will give you more control, and the ability to create and restore snapshots. However, it does not have a direct console interface to the VM, you would use a browser to access the console. I would go Hyper-V, but it really depends on what you're using your VMs for. Luckily, they share the same format for virtual disks, so you can try it out with your existing VMs.
You should review Windows 2008 R2 SP1 upgrade with RemoteFX, it comes with a new video driver for VM's that allow 3D, extended desktops and more. It will help resolve some of the issues you are seeing today.
Both the Host server and VM need to be running SP1 of Windows 2008 R2.
http://blogs.technet.com/b/virtualization/archive/2010/03/18/explaining-microsoft-remotefx.aspx