mwrock/WindowsNano Vagrant box

How to use this box with Vagrant: 

Vagrant.configure("2") do |config|
  config.vm.box = "mwrock/WindowsNano"
  config.vm.box_version = "0.1.0"
end
vagrant init mwrock/WindowsNano \
  --box-version 0.1.0
vagrant up

v0.1.0

This version was created almost 9 years ago.

This is a Windows Nano Technical Preview 3 box.

Known Issues

WinRM connectivity from Vagrant

The WinRM service in Nano currently only accepts requests set to the UTF-8 code page 65001. However, the WinRM Gem used by Vagrant sets the codepage to 437. This prevents vagrant from establishing WinRM connections with the nano box.

However, Vagrant is able to create and destroy the box and one can connect via via windows Powershell Remoting.

Hyper-V Blue Screens(BSODs)

The very first boot on Hyper-V will blue screen. However it will recover. How it recovers depends on the type of switch used:

  • External Switch - box automatically restarts and boots to nano login screen.
  • Internal Switch - Box Blue Screens, twice on its own and finally stops a tan Error Code Screen. Manually restarting the VM will boot int oa Nano login screen and no subsequent blue screens should be seen.

Communicating with the box using Powershell Remoting

You can connect via powershell remoting using port 55985 on VirtualBox and the normal WinRM ports using Hyper-V.

More instructions to come

Packer Template

This box was created using the template located at https://github.com/mwrock/packer-templates/blob/master/vbox-nano.json The build was identical for VirtualBox and Hyper-V with the exception of the drivers used to create the initial nano image. Hyper-V used the -GuestDrivers option and VirtualBox used -OEMDrivers.

2 providers for this version.
  • hyperv
    unknown Hosted by Vagrant Cloud (233 MB)
  • virtualbox
    unknown Hosted by Vagrant Cloud (307 MB)