TeamLeader Posted June 12, 2015 Share Posted June 12, 2015 I'm trying to evaluate Windows 10 (10130) using VirtualBox. Unfortunatly, I am having problems since 10130 does not appear to support any of the VirtualBox Virtual Network Adapters. I'm therefor looking for any way to get the Network working. I'd prefer of course to use Windows 10 Drivers, or in a pinch Windows Vista/7/8.x Drivers if they can be installed, or repackaged to make them compatible. Regretably, I have only one computer and the hardware is also relatively old and not well supported by the limited selection of Drivers in Windows 10. I would appreciate any guidance in resolving this. I seriously doubt that Windows 10 will be a resounding success that microsoft expects it to be, if it will not install on older hardware that more than meets the minimum hardware requirements. I see this as being a serious problem for Microsoft, almost as Bad as VISTA/8.x in so far as a large proportion of potential hardware platforms will be rendered incompatible and as a consequence, many will refuse to upgrade, simply because they are not prepared to throw out perfectly good computers, even with a free upgrade on offer. Link to comment Share on other sites More sharing options...
Dutchie64 Posted June 12, 2015 Share Posted June 12, 2015 I'm running 10135 and have no issues here on VB. Not with 10130 either. But complaining on Win10, in a VM, is a bit silly. Too many little things that can go wrong. Maybe upgrading to the latest version of VB might help? Or the VB tools? And drivers.... basic MS Win drivers normally -should- work, but the blame is with the manufacturer of the hardware, isn't it? And already admitting your hardware is relatively old, your luck might be running out..... Windows already has a better track record tahn other OS's for supporting decades old stuff anyway, and at some point it has to go. ;-) Link to comment Share on other sites More sharing options...
Lant Posted June 12, 2015 Share Posted June 12, 2015 What version of VirtualBox are you using? If you are on 4, you might want to try the 5 rc instead. Link to comment Share on other sites More sharing options...
helpifIcan Posted June 12, 2015 Share Posted June 12, 2015 Same here been running on VB since the beginning no problems, as above make sure you have the latest version of VB and VB tools. Make sure you have the network set up correctly, mine is set to nat. Link to comment Share on other sites More sharing options...
TeamLeader Posted June 12, 2015 Author Share Posted June 12, 2015 Thank you for your responses. Am running: Host: Windows 7 x64 (Dual Core CPU, 8GB RAM) Guest: Windows 10 10130 VirtualBox: 4.3.28 [Latest Stable Version] VirtualBox Tools: 4.3.28 [Latest Stable Version] I choose to use VirtualBox as there are a significant number of other people who for similar reasons have also chosen to test Windows 10 in VirtualBox (or another Virtualisation Product). I cannot use VirtualBox 5 RC, as I only have 1 PC and need a stable platform to run Virtual Machines. If VirtualBox 5 is released properly I will consider upgrading and testing Windows 10, but cannot do it until then. I also cannot upgrade this PC to Window 10 10130 (or other evaluation version) as I have other obligations which prevent me from doing so, and it is simply impractical to do so until Windows 10 is released. Giving the limited set of drivers in Windows 10130, It is highly dubious that even a relatively new PC will be fully operational. ------- In respect of your responses, It would be helpful if you could include some additional information. Specifically, It would be useful to know the following: -Detailed description of VirtualBox Windows 10 Virtual Machine Configuration, in particular the Network Configuration -It would also be useful to see the corresponding Driver information from within the Windows 10 instance - to know which driver you have running against your Virtual Network Adapter: I am aware that VirtualBox does not package Network Adapters with the Tools. It is necessary for the Guest OS to supply the correct Drivers. I am unable to identify the correct drivers from the pictured list above. If you have used an alternate driver, please identify the actual device chosen in the VirtualBox Configuration and the nearest best matching Driver in Windows 10. Thankyou again, I look forward to any constructive advice you can supply. Link to comment Share on other sites More sharing options...
helpifIcan Posted June 13, 2015 Share Posted June 13, 2015 In the VB set up and in win10 the driver used is INTEL®PRO/100 MT Desktop Adapter Driver provider Microsoft Driver date 3/23/2010 Driver version 8.4.13.0 VB version 4.3.28 r10039 with the appropriate guest box version for this build. Just a note it's set up as windows 8.1 64bit, I used this because win10 option was not available in the build in Sept. 2014. Not much more then I can tell you, hope this helps. Link to comment Share on other sites More sharing options...
TeamLeader Posted June 14, 2015 Author Share Posted June 14, 2015 helpifIcan - Thankyou, this gives me something to work with. I can attempt to locate and download this specific driver and apply it to Win10. I will look into this and post my progress later. Link to comment Share on other sites More sharing options...
SoCalRox Posted June 14, 2015 Share Posted June 14, 2015 Just to be sure we're understanding things, when you run in a VM, you run to match the hardware emulated in the VM manager, NOT the hardware of the computer. Whether it runs well in VirtualBox means nothing relative to its running well on a REAL piece of hardware. I've run it in VB and it has run just fine, though on Windows I prefer running it in VMWare Player. Link to comment Share on other sites More sharing options...
Intersect Posted June 14, 2015 Share Posted June 14, 2015 Using VMWare player with all of the releases of windows 10 and have not had any issues, Virtual box on the other hand was :( Link to comment Share on other sites More sharing options...
TeamLeader Posted June 15, 2015 Author Share Posted June 15, 2015 Neowinian - I am installing Windows 10 inside a VM, so all hardware detected is the Virtual Architecture of the VM as configured - not the host. I fully expect that performance within a VM will be less than on real hardware. As I have indicated above, I do not have any other hardware and cannot replace my existing OS At this time. I do not have sufficient space on storage to add a another OS (Multi-Boot), and I am not interested in installing Window 10 outside a VM until it is finally released. Neowinian Senior - I have long disliked VMware products, I did originally use Server however it was discontinued. I shortly intend to move from Windows as a host OS to Linux and will only be running Windows in Virtual Machines. I also intend to move from VirtualBox to KVM. ALL. In respect of this issue, I have finally been able to apply a driver with some success. I downloaded the latest driver file from Intel. Windows 10 failed to install from the binary even in Compability Mode - No drivers found. I extracted the files from the binary, and manually upgraded/installed the drivers from the extracted files. The instance of Windows 10 now seems to be able to connect to the internet, however it does appear to be less than stable. The VM does occasionally appear to freeze, and the Graphics Driver periodically fails but these are separate issues. Link to comment Share on other sites More sharing options...
Recommended Posts