I have applied some windows updates on both my host (Windows 10) and my Hyper-V guest (Windows 10). After rebooting the hyper-v VM cant boot anymore displaying the message that there is no active boot item for booting from UEFI.
After some trail and error, the solution was to reinstall hyper-v on my windows 10 host.
Ensure that hardware virtualization support is turned on in the BIOS settings
Configure networking for the Hyper-V environment to support external network connections. Also ensure that a virtual switch has been created and is functional
Remove all security software and AV
System and drivers are up-to-date.
Also, try to use PowerShell command-line to enable Hyper-V.
Install-WindowsFeature –Name Hyper-V -ComputerName <computer_name> -IncludeManagementTools -Restart
Related
After installing windows 98 in virtualbox, I clicked 'start' button. Then it showed me an error:
Failed to open a session for the virtual machine windows 98.
Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).
VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).
You need virtualization Technology enabled in the Bios
Reboot your machine
Press F10 to enter BIOS.
Security-> System Security
Enable Virtualization Technology (VTx) and Virtualization Technology
Save and start the machine.
Failed to open a session for the virtual machine windows 98.
There are different approaches to solve this, try whichever works for you
1
open windows features win+R --> then optionalfeatures
Disable Hyper-V (if it is available on your machine)
Enable "Virtual Machine platform"
Enable "Windows Hypervisor platform"
Disable "Windows Sandbox" (if available on your machine)
Restart the machine
2
Windows Subsystem for Linux (WSL) feature was enabled.
Disabling it solved it for me.
Restart the machine.
3
If it still doesn't work:
Open Powershell command prompt as admin and then run the following command:
bcdedit /set hypervisorlaunchtype off
Restart the machine
View the full answer:
Unable to launch Ubuntu18.04 on VirtualBox [VERR_NEM_VM_CREATE_FAILED]
If I use basic session, everything works fine, but when I connect in enhanced mode, login prompt is not appearing.
Guest OS: Win 10 Pro x64 Build 18990.vb_release.190921-1704
RDP services are enabled.
Event Log for RemoteDesktopServices-RDPCoreTS/Operational shows a error:
'Failed GetConnectionProperty' in CUMRDPConnection:QueryProperty at 3318 err=[80004001] (RemoteFX module)
Host OS: Win 10 Pro x64 1903 (18362.418)
Hper-V Version: 10.0.18362.1
I disabled RemoteFX in Guest OS with policies, how it is described here, but still no success.
I had the same problem until I stumbled across this Microsoft thread where someone said, "disabling Windows Hello on the VM did the trick for some reason."
Go to Settings -> Accounts -> Sign-in options. Turn off the setting for "Only allow Windows Hello sign-in for Microsoft accounts on this device (Recommended)". Then reboot the VM and enhanced sessions should work.
So I have this work computer that I'd like to play fortnite on, but it doesn't have the latest version of directX installed in it so I can't just install fortnite to my flashdrive and play.
So I've been researching on getting a portable Windows 10 Virtual Machine on my flashdrive, which has fortnite installed in the VM. However, apparently Virtual Machines don't utilize the host's GPU by default. I'm trying to find out a way to let the Virtual Machine use the native GPU. I've seen that it's completely doable on a Linux host, but I can't find anything about GPU passthrough on a windows10 host.
Note: my work computer does support VT-d, and it is locked down so I can't do anything to it that requires elevated privileges like installing stuff, changing the BIOS, or booting off an external harddrive.
I am running a virtual machine in Bluemix and want to open the OS's desktop GUI. How do I do this? Thanks for your help.
I've edited your question to what I think you're asking: How can I open the desktop GUI on my virtual machine in Bluemix?
Assuming I understand the question correctly:
To open the desktop GUI on a remote virtual machine, use Virtual Network Computing (VNC). This solution is not specific to Bluemix; it'll work with a VM running on any platform, as long as the VM is running an OS that supports VNC.
To use VNC, you need to have a VNC server running in your VM's OS. You will then run a VNC client (a.k.a. viewer) on your computer to display the VM's desktop. The specific instructions depend on the OS running in the VM and on your computer.
For example, assuming your VM is running Ubuntu v14.04, these resources explain what to do (and a search will find other resources):
"How to Install and Configure VNC on Ubuntu 14.04" -- Installs XFCE4 as the VNC server
"How To Install And Configure VNC On Ubuntu 14.04" -- Also installs XFCE4.
"How to Install VNC Server on Ubuntu 14.04 LTS" -- Installs TightVNC as the VNC server
For a VNC client, I actually connect to remote VMs via a local VM running Ubutu 14.04, so I use Vinagre (a.k.a. the Remote Desktop Viewer app). Options listed by other authors include TightVNC, RealVNC, or UltraVNC.
Good luck and thanks for using Bluemix.
From what I understand, you need some remote desktop tool to get to the UI of the OS of your virtual machine. Some tools available: http://www.techradar.com/us/news/software/applications/7-of-the-best-linux-remote-desktop-clients-716346
I have been trying to setup a Win7 VM on Hyper-v that connects to the internet through my Win 8 host machine.
I can't seem to figure out why the VM can't ever get passed limited connectivity. Any ideas?
NO sure why but all I had to do was Disable/enable the vEthernet adapter and everything worked great!
Check that you have a Virtual Switch with an "External Network" using the Virtual Switch Manager.
The other network types offer VM isolation. If your VM is on an "Private Network" it can only talk to other VMs on the server. The "Internal Network" allows VMs can talk to other VMs and to the host.
In contrast, an External Network allows the VM to contact machines on the network that the host is attached to.
I worked on this issue for a while myself after upgrading to Windows 8.1 and losing connectivity. Added and removed the adapter to no avail. The solution was to upgrade the VM's Integration Services.
I had the same issue because my DHCP settings on my guest VM was setup wrong.
So check the DHCP setting if they are on obtain automatically.
Control Panel\Network and Internet\Network Connections
Network adapter properties -> Internet Protocol Version 4 (TCP/IPv4) -> Properties ->
Obtain DNS server address automatically
I have had great success with Hyper-V and windows 8 and windows 10 virtuals using external switches with a Windows 8.1 host. Unfortunately I could not get the external switch to ever work on windows xp virtual running under Hyper-V. Instead, after reading a lot of sites/suggestions, I followed this guide to bridge an internal virtual switch (with Hyper-V legacy network adapter for XP) to the host wifi. I hope this saves someone else some time when working on an XP virtual.
Using Hyper-V with a Wireless Network Adapter