There is one Virtual Box process that continues to run at 100% cpu usage until I kill the VM. None of the VirtualBox activity icons at the bottom of the Guest window are active: all dark. However, if I shut down the VM and change the settings to a higher processor count (I have tried 12 and 14 cores), the VM does not progress very far into its boot: I see a blue background and the windows icon. The Virtual Box guest boots without issue using the old settings (8-processors). I copied over my Windows 10 VirtualBox guest VM from the old system (Intel i7 8-core) to the new system. This is either making Windows obsolete or Oracle Virtualbox. Definitely not Docker.I just built a new Linux (Gentoo) system based on a SuperMicro mainboard, C9X299-PG300, and an Intel i9-7940X (14-core, 28 thread) CPU. Looks like the OsX Users don´t know that Problem. Still pondering if i make a start menu entry like described here to make switching more comfy: Switch easily between VirtualBox and Hyper-V with a BCDEdit boot Entry in Windows 8.1 Now it´s usable and Virtualbox runs again. German Screenshot again, but you can find it when Changing a Box at the System Menu….the Screenshot shows the Acceleration Tab which is completely greyed out if Hyper-V is active: You can check if thats correct in Oracle Virtualbox. The worst part is : A reboot is needed as the kernel is either controlling the Hardware or not. You can actually disable Hyper-V in Windows 10 (sorry for the German Screenshot, its available in the Program Install Part of the Control Panel):Īs you see i have disabled the Platform Features and the Administrative Tools for it. And since the Service is running per default, the Hardware is blocked by Hyper-V. And there can only be one Hypervisor in Charge. This happens because Windows 10 (and – i presume – Windows 8) is running the Hyper-V Hypervisor.
Various Errors told me that my machine has no VT-x Features. Then in installed Virtualbox and the Docker (Beta). Now Virtualbox will be able to boot my (圆4) VM….oh, actually not. So, i activated the VT-x Features in the BIOS (and used a fancy tool for my Dell Latitude, „CCTK“ – which really sucks, imho). I was eager to see if the Folder Mounting works better than with the Toolbox – which requires some unnerving Commands to produce a shared folder in the Boot2Docker Image which is then mapped to Folders inside the Docker Container. I recently updated to Windows 10 and wanted to play with Docker (the native one, not the Toolbox).
0 kommentar(er)
