I took a snapshot using Vsphere 5.1 yesterday for my Windows 2008 R2 VM. Today when I restored my VM using this snapshot, the VM failed to start up and it is telling me with the following message:
"BOOTMGR is missing, Press Ctrl+Alt+Del to restart"
A little search online seems to fetch the conclusion that this happens from time to time with Windows 2008 or windows 7 VMs, in that when the VM software compressed the system to make a snapshot, it compressed the boot section too, and on restore the guest OS did not like this, and can not find the boot bios.
Is there anyway I can restore this? Perhaps from the Vsphere command line to rebuild the bootmgr?
Resolved by booting from Windows 2008 CD, going to recovery and then command prompt and doing these commands:
Type Bootrec /RebuildBcd, and then press ENTER.
Reboot, go back into recovery mode and command prompt again, this time selecting the windows 2008 installation that was rebuilt.
Go to X:\Sources\Recovery and run startrep.exe
Related
I've Windows 10 Pro system, and use Hyper-V on that system. Due to the needs of device redirection doesn't works well with Hyper-V, I've installed VMWare Workstation 14.
I have to disable Hyper-V to make VMWare Workstation work, at beginning. It worked until last weekend , seems because of the QFE update. I just verified, it was not QFE but Feature update to Windows 10, version 1803 that triggered the problem with VMWare Workstation again.
After Windows update completed (after reboot), I tried to start a VM in VMWare. I get the error dialog complaining about Device/Credential Guard.
Following the instruction in this link: https://kb.vmware.com/s/article/2146361, and after the reboot, I get another complaint about incompatibility with Hyper-V.
After reset the Hyper-V selection in Windows Feature or confirm that HyperV is not already removed, and reboot, the first error came back.
It gets in a loop of error complaining about Device Guard and complaining about Hyper-V for VMWare.
Ok, thanks to the answer from communities of VMWare: https://communities.vmware.com/thread/588526
The issue is now gone, by applying the following change:
Disable credential guard by using readiness tool from Microsoft: https://www.microsoft.com/en-us/download/details.aspx?id=53337, with this command: DG_Readiness_Tool_v3.2.ps1 -disable
Disable Hyper-V by using PowerShell command: Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V
Reboot and accept to boot without CG/DG.
Although I don't like that VMWare cannot work together with device guard from system, I get my VM working for the moment.
1- run cmd as admin
2- run : bcdedit /set hypervisorlaunchtype off
3- reboot
let me knew if it works please
good luck
here are the few steps for you to solve this issue:
Disable the HvHost service (and any other services with prefix Hyper-V if needed) from windows TaskManager(Ctrl+Alt+Del)
use the tool from the official website
Uncompress the downloaded zip file to your own directory, take C:\DG_Readiness_Tool_v3.5 here for instance.
Run Windows PowerShell as admin, type the following two commands:
cd C:\DG_Readiness_Tool_v3.5
.\DG_Readiness_Tool_v3.5.ps1 -Disable
Reboot
Adrian at https://answers.microsoft.com/en-us/windows/forum/windows_10-security/cannot-disable-memory-integrity-core-isolation-in/29ac5ce4-30d2-47d1-ab17-734980fd287b
says "I think it's a bug that this cannot be disabled via UI but fortunately it's possible through the registry by setting the following key to 0:"
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity\Enabled
This worked for me as well [Windows 10 Pro Version 1803(OS Build 17134.112, VMWare Workstation 14 Pro Version 14.1.2]
When I run vagrant up from the command line, it is a crap shoot at best as to whether vagrant will boot up or not. It stops at this line:
SSH auth method: private key
And then may or may not include this line:
Warning: Remote connection disconnect. Retrying...
As I said, sometimes it works and sometimes it does not. Why is this problem happening? For the record it would happen (less often) on my production MacBook at work.
Can I maybe change the auth method if there is no good answer for this? Trust me I have been looking and not found any answer on this yet.
whats happening is the following :
vagrant up will spin a new VM, basically it contacts virtualbox (or the specific provider) and run command to start a VM
the VM will start on the virtualbox side
note: if you run form a command line terminal in macos, you can see the title switching from 'Ruby' to 'VBoxManage'
the VM takes some time to start
because the VM does not send a specific signal when its done, vagrant will check at regular interval if the VM is fully booted and available to ssh-in
once the VM is available, vagrant can run the ssh command and complete the config (network, shared folder, etc...)
so in your case, the VM takes a bit longer to boot (this can be due to high activity on your mac, specific setup of the VM that runs on boot ...)
Basically this is harmless and is not necessarily a bad sign.
Please look at my accepted answer on this. It turns out that this was a memory allocation issue, and I only discovered it when watching the terminal for the VM provider (VirtualBox). Once I closed some programs I was (generally) able to boot up just fine.
There seems to be an incompatibility problem with Vagrant/VirtualBox & the Windows Hypervisor Platform feature in Windows 10
I had this problem and this is how I got get Vagrant & WSL2 working side by side
I have the following environment:
Hardware Virtualization enabled in BIOS
Windows 10 (Insider Program with Release Preview Channel)
-- Windows 10 with WSL 2 Version 10.0.19041 Build 19041
VirtualBox 6.1.12
-- Extension Pack Installed
Vagrant 2.2.9
These are the settings that worked for me:
Windows Hypervisor Platform: Off
Virtual Machine Platform: On
Windows Subsystem for Linux: On
I want to install Docker on a physical Windows Server 2016 Datacenter Evaluation (Version 14393). I tried following the instructions from Quick Start Windows Server but installation fails:
Error message
The docker installer requires update KB3176936, which I installed then. Even after rebooting, the error message persists and I can't install docker.
I've enabled the Container feature and Hyper-V in Windows Feature Selection.
Any ideas what I'm doing wrong? I've could sucessfully setup docker on Windows 10.
You need to do a full Windows Update. I actually have a PR to add this step to the docs.
Run sconfig, then choose option 6 and then A and A to install all updates. This works for Server 2016 in no-desktop installs as well as with the UI.
I am a new to Docker. After the installation of Docker Toolbox (OS: Windows 10) I run Docker Quickstart Terminal and in the console I see this:
Running pre-create checks...
Error wirh pre-create check: "Hyper-V is installed. VirtualBox won't boot a 64bits VM when Hyper-V is activated. It it's installed but deactivated, you can use --virtualbox-no-vtx-check to try anyways"
Look like something went wrong in step 'Checking if machine default exists'...
Press any key to continue...
What did I do wrong? All checking of system and install steps are taken from here.
Thank you very much for your help!
Hyper-V and VirtualBox are conflicting each other.
You can either uninstall Hyper-V or run
docker-machine create -d virtualbox --virtualbox-no-vtx-check test
Source
Docker supports Hyper-V as the driver
You need to perform the following steps:
Create a virtual switch, refer to this article on how to do that
Create a docker machine using that network switch and hyper-V driver.
docker-machine create -d hyperv --hyperv-virtual-switch "name of the virtual switch created above" default
I got the same error when I installed Docker Toolbox on my Windows 10 machine.
Solution:
Install Docker Community Edition (not Docker Toolbox)
Enable Hyper-V
Open Control Panel -> System and Security -> Programs (left panel) -> Turn Windows features on or off -> Check the Hyper-V box
As of 2017's Win 10, if you don't have Hyper-V option, then your Windows OS is not Enterprise Edition. Also, Docker seems to work a lot better on Intel processors (not AMD).
Add C:\Program Files\Docker\Docker\resources\bin to Path in Environmental Variables.
Open Git Bash and type docker-compose up and now that command should work.
If you don't have GitBash, please download it.
I was having the same issue, and this blog post solved it. The author runs you through the steps of adding the --virtualbox-no-vtx-check flag to the docker shell script.
Virtualbox and Hyper-V don't play well together. I am NOT the author.
I set the Hyper-V off using windows feature on off and it worked for me.
See if when you run:
docker-machine create -d hyperv --hyperv-virtual-switch "Virtual Switch" default
you get Error with: pre-create check: "Hyper-V PowerShell Module is not available"
If so just enable in Docker(icon on your desktop)->settings->expose daemon on TCP ...
You need to disable Hypervisor to check new application that use VT-x before the virtual machine launch:
Open the command prompt as Administrator
Run bcdedit to check hypervisor status:
Check hypervisor launch type.
If is set to auto then disable it:
bcdedit /set hypervisorlaunchtype off
Reboot host machine and launch VirtualBox again
After performing above steps I opened again Docker Quickstart terminal and it is working fine.
I pressed the Windows Button on keyboard. Typed 'Hyper-V Manager'. It opened the 'Hyper-V Manager'. Then I right clicked on my machine name. There was an option to 'stop'. I selected this option. It stopped the 'Hyper-V' on my machine and then Kitematic worked fine, i.e., it download the hello-world-nginx and displayed the web page.
NOTE: This is strange and I am not sure why. Once I have done above steps, now when I restarted the Hyper-V using Hyper-V Manager, Kitematic is still working and downloading images. Can anybody comment why it is now still working when Hyper-V is also running ? Thank you.
Good
Ali Ahsan
The solution as suggested by #Gene is correct and works perfectly if:
One has windows pro edition
Both Hyper-V Management Tools and Hyper-V Platform are enabled
Sometime this isn't always the case; here is what to do:
Check Windows Edition:
To check which version right click on Windows key and select System.
Scroll down to Windows specifications and look at [Edition]
Check Hyper-V Platform (virtualisation)
For Hyper-V Platform to be enabled one must turn on virtualisation; normally this is done via the BIOS.
On HP laptop one this is done from the BIOS.
On start-up click Ctrl+F10
Press the right arrow key to System Configuration tab.
Select Virtualization Technology and then press the Enter key.
Select Enabled and press the Enter key.
Once these steps are done then:
Search for Turn Windows features on or off.
Scroll down to Hyper-V
Tick this box (Ensure you see a tick NOT a black box which indicates some features not enabled)
Upon restart docker should be running... good luck !!
I am trying to install Mac(OSX-Mavericks) using virtualbox On Windows 8.1.
Everything works fine But, when MAC Installation setup starts in virtual machine, it keep on loading and do not start the installation wizard stays on the first screen.
I have waited for a log time like 3-4 hrs but unable to figure out the problem as there is no error.
I am using a dell(Inspiron 3537).
I have installed Mac on my previous Samsung laptop successfully in the same way.
I will provide other information on demand as I'm not sure where the problem is as setup loads but not starts the installation process.
Thanks in advance
enable virtualisation on your BIOS, it may helps.
Open an administrator CMD shell and try this:
cd "C:\Program Files\Oracle\Virtualbox"
VBoxManage modifyvm <name_of_your_vm> --cpuidset 00000001 000306a9 00020800 80000201 178bfbff
Then close/VirtualBox and open again (to save your new settings). Boot OSX with "-v" flag.