Re:Windows 10 is unfinished
by bryanlarsen on Friday July 31, 2015 @04:58PM
(#9984448)
Warning: VirtualBox doesn't work in Windows 10. We're a very Vagrant-dependent shop here, so one of my coworkers was forced to spend his entire day in meetings rather than doing real work.
[ Parent
| on HN ]
That must be hardware dependent, I was able to fire up VirtualBox and resume working in a Linux VM immediately after upgrading.
Same here. Just booted over to Windows 10, and VirtualBox appears to work fine.
VirtualBox 5.0.0 on relatively modest hardware. I haven't tested it beyond running a couple Linux VMs though.
My issues were all with host-only network adapters. NAT worked just fine.
Thanks for the heads up that's going to be a big deal for developers. I'm sure it'll get fixed. This is probably why our IT folks don't want us jumping on the newest OS right after deployment, even though I did it for my personal machine.
Re:Windows 10 is unfinished
by bryanlarsen on Friday July 31, 2015 @05:08PM
(#9984507)
Yes, it's fixed in SVN, supposedly.
Windows development is version controlled with Source Depot (a Perforce customization for Microsoft). Not SVN.
Re:Windows 10 is unfinished
by currysausage on Friday July 31, 2015 @06:17PM
(#9984842)
I guess parent is talking about VirtualBox SVN.
Re:Windows 10 is unfinished
by wlesieutre on Friday July 31, 2015 @05:13PM
(#9984528)
With recent versions of VirtualBox?
I had trouble with it months ago in technical previews, but I've been running it successfully for a while now.
That said, I haven't moved to the RTM version yet. Could be another new issue.
I'm getting a not supported error about upgrading to Windows 10 when inside 8.1 in VirtualBox. Apparently the VirtualBox display driver isn't supported.