While this does somewhat put a band-aid on the "cannot detect operating 
system error",
the networking configuration doesn't complete.

==> win10: Configuring and enabling network interfaces...
The following WinRM command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

netsh interface ip set address "Ethernet 2" dhcp
if ($?) { exit 0 } else { if($LASTEXITCODE) { exit $LASTEXITCODE } else { 
exit 1 } }

Stdout from the command:

Stderr from the command:



On Thursday, August 6, 2015 at 4:51:38 PM UTC-7, Michael Legleux wrote:
>
> But it obviously can, as in the debug output I see windows 10 all over the 
> place.
>
> This was with Virtualbox 4 and 5.
>
> This seems to be a relevant part of the debug output:
>
> DEBUG guest: Trying: windows
> DEBUG winrmshell: powershell executing:
>             $p = "$Env:SystemRoot"
>             if ((Test-Path $p) -and (get-item $p).PSIsContainer) {
>               exit 0
>             }
>             exit 1
>
> if ($?) { exit 0 } else { if($LASTEXITCODE) { exit $LASTEXITCODE } else { 
> exit 1 } }
> DEBUG winrmshell: Output: {:data=>[{:stderr=>"#< CLIXML\r\n"}, 
> {:stderr=>"<Objs Version=\"1.1.0.1\" xmlns=\"
> http://schemas.microsoft.com/powershell/2004/04\";><Obj S=\"progress\" 
> RefId=\"0\"><TN 
> RefId=\"0\"><T>System.Management.Automation.PSCustomObject</T><T>System.Object</T></TN><MS><I64
>  
> N=\"SourceId\">1</I64><PR N=\"Record\"><AV>Preparing m"}, {:stderr=>"odules 
> for first use.</AV><AI>0</AI><Nil 
> /><PI>-1</PI><PC>-1</PC><T>Completed</T><SR>-1</SR><SD> 
> </SD></PR></MS></Obj></Objs>"}], :exitcode=>0}
> ERROR warden: Error occurred: The guest operating system of the machine 
> could not be detected!
> Vagrant requires this knowledge to perform specific tasks such
> as mounting shared folders and configuring networks. Please add
> the ability to detect this guest operating system to Vagrant
> by creating a plugin or reporting a bug.
>  INFO warden: Beginning recovery process...
>  INFO warden: Calling recover: 
> #<Vagrant::Action::Builtin::HandleForwardedPortCollisions:0x39dfb78>
>  INFO warden: Recovery complete.
>
> How can no one else be experiencing this?
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/b25c1d65-585e-4171-b8c0-ed5a313fdf45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to