https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221029
--- Comment #95 from Mark Millard <mar...@dsl-only.net> --- I've now tried Hyper-V instead of VirtualBox for building lang/ghc (the most systematic usually-quick-failure test that I've found). In this context: sysctl kern.sched.balance=1 sysctl kern.sched.steal_idle=0 did not seem to help. Nor did: sysctl kern.sched.balance=0 sysctl kern.sched.steal_idle=0 Hyper-V did not report going beyond 8 virtual processors as a problem, VirtualBox did. So for Hyper-V I assigned 14 Virtual Processors, leaving by count enough for one core (2 threads) for Windows 10 Pro. While for VirtualBox I used 8 per its report when a larger figure is set. Note: I had to avoid using a M.2 NVME SSD and instead used a SATA SSD for Hyper-V. For NVME the attempt to create the virtual machine crashes Windows 10 Pro. It created the virtual machine just fine when told to use the SATA SSD. Note: When Hyper-V is enabled, VirtualBox 64-bit is blocked --even if every Hyper-V virtual machine is off. I had to disable Hyper-V to get VirtualBox working again. [There were more issues than I've noted here as well.] -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
