Issues when running a VM in VMware on a Windows host - windows

These are the details of my physical server:
Windows Edition: Windows Server 2008 R2
Processor: Intel Xeon
System Type: 64 bit operating system
I am trying to run CentOS 7 using VMware Workstation Pro Version 14.
After creating the VM, when trying to run it I get a black screen in the console.
while exiting from the console view you can see actually CentOS 7 installation and leaving it running will actually successfully install CentOS and will ask you for the language but I can't choose anything from outside the console view, neither inside the console view(black screen).
Please note the following:
I tried both CentOS 7 minimal and everything isos downloaded from the CentOS official website
I enabled Intel Virtualization in the BIOS as requested in VMWare Community Website
I started the VMWare Authorization Server in the services section as mentioned in VMWare Community Website
I have no anti-virus running
I tried using VMWare Player instead of VMWare Workstation and the same error occurred
This is the complete VMWare log file

Related

Running Windows 10 VM on Devstack Yoga Stable

I have created a Windows Server 2016 image for launching as an instance (or VM) in OpenStack, and it works fine. However, I have followed the same steps for Windows 10 Pro and used its corresponding virtio drivers to create a cloud image, which doesn't work. After importing and launching the VM, it gets stuck in the Windows 10 loading page, and nothing happens. I have installed Devstack Yoga (Stable version) on an Ubuntu 20.04.5 VM, and my hypervisor is KVM. I have a remote access to this VM, and I am not aware of the KVM configurations for this VM. Should I look for some particular parameter of the KVM hypervisor for my OpenStack VM? If yes, which parameters?

Not able to log back into my Windows machine after Hyper-v installation

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

vmware in windows 10

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.

Windows Phone Emulator error, Hyper-V components not running, Windows 8.1 hosted in VMWare Player

Environment:
Windows 7 Enterprise 64-bit as host o/s
Windows 8.1 Enterprise 64-bit hosted in VMWare Player (current version)
Visual Studio Express 2012 for Windows Phone (Update 4)
I get the following error when trying to run a very simple phone app. I know MS says a VM-within-a-VM environment isn't supported, but I know it can work. Has anyone had success with this? Any help is greatly appreciated.
Windows Phone Emulator
The Windows Phone Emulator wasn't able to ensure the virtual machine
was running:
Something happened while starting a virtual machine: 'Emulator WVGA
512 MB.' failed to start. (Virtual machine ID
CADD6546-129A-4683-9A2D-52EAE777E888)
The Virtual Machine Management Service failed to start the virtual
machine 'Emulator WVGA 512 MB.' because one of the
Hyper-V components is not running (Virtual machine ID
CADD6546-129A-4683-9A2D-52EAE777E888).
Prior to seeing the error, the emulator emits the on-screen messages:
Loading ...
The Windows Phone OS is starting ...
And then the error. Of all the Hyper-V services available, the Hyper-V Virtual Machine Management service is the only one which is running.
I've got Windows Phone 8 (and 8.1) emulators working in a VMware Player VM (running Windows 8, obviously) on a Windows 7 host.
You must first check the physical processor supports SLAT. If it does, you can set the "Virtualize Intel VT-x/EPT or AMD/RVI" in your VM's processor settings (Manage/Virtual Machine Settings/Processors). Then make sure the hypervisor.cpuid.v0 is set to "FALSE" in the vmx file for the VM. (exit VMware player before doing this). And you should be good to go.
See http://developer.nokia.com/community/wiki/Windows_Phone_8_SDK_on_a_Virtual_Machine_with_Working_Emulator for a step-by-step guide on how to do this when creating a new VM.

Windows Phone 8 SDK Xde emulator runs really slow and Crashes

when you try and run the emulator it will load, then say windows phone OS is starting up, then sit there about 3-5 mins and fail.
Im Running Visual Studio Express 2012 for WP on Lenovo N586 64-bit I've upgraded to windows 8 pro
lemme run down the list of what Ive tried...all are listed here
yes hardware supports hyper-v virtualiztion amd a6-4400m
I'm slat Capable theres a program you can use to test this.
Hyper-v is Installed and running fine
running windows 8 pro I had to upgrade.
Im 64 bit
Im not running any other virtualization software
Ive run XDEcleanup.exe and ran VS2012 as administrator no luck
no im not running on a virtual machine.
and just for fun I've uninstalled the sdk and re installed it
any idea?
For what you're describing, its looks like the VS is trying to create the virtual switch, but failed. To resolve this, go to Hyper-V's Virtual Switch Manager, on the left side of the window, and be sure that you have one virtual switch for every network card you have, usually you must have 3: 1 for the wireless, 1 for the LAN and 1 for internal. If your don't have the wireless or the LAN, create them.

Resources