github/linuxkit
1
0
Fork 0
mirror of https://github.com/linuxkit/linuxkit.git synced 2025-11-03 23:33:31 +00:00
Code Issues Projects Releases Wiki Activity

Hyper-V: remove the force stop now that the Hyper-V deamons are running

Browse Source 
Also, minor, unrelated tweak to the documentation

Signed-off-by: Rolf Neugebauer <rolf.neugebauer@docker.com>
This commit is contained in:
Rolf Neugebauer
2016-01-26 18:13:30 +00:00
parent bdd1efe043
commit b47f280302
2 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/windows-notes.md
View File

@@ -5,7 +5,7 @@ I use Windows 10 Pro in a Vmware Fusion VM. Make sure it's a 64bit VM.
In Vmware Fusion VM settings make sure the `Processor -> Advanced Options -> Enable hypervisor applications in virtual machine` is selected. This enables nested virtualisation. If you install on bare hardware make sure the virtualisation technology is enabled in the BIOS.
When creating the user, make sure that te username does **not** contain
any spaces. This will save you a world of pain! On Windows 10, also select custom settings during the install and disable all the spying/calling home features introduced.
any spaces. This will save you a world of pain! On Windows 10, also select custom settings during the install and disable all the spying/calling home features introduced. Also, since I'm running Windows in a VM on an already password protected system, I disable password for my user, using `c:\Windows\System32\netplwiz.exe`. Just untick the password checkbox.
Install software:

5
scripts/MobyLinux.ps1
View File

@@ -183,8 +183,9 @@ function
Stop-MobyLinuxVM
{
Write-Output "Stopping $VmName"
# Using -Force for now until the host integration services are installed in the VM
Stop-VM -VMName $VmName -Force
# You can use -Force to basically pull the plug on the VM
# The below requires the Hyper-V tools to be installed in the VM
Stop-VM -VMName $VmName
}
# Main entry point