Custom Query (16363 matches)
Results (2521 - 2523 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #15304 | invalid | Windows 10 host seems to be filtering network traffic for guests | ||
| Description |
I have the same situation happening on multiple Windows 10 hosts. They were all upgraded from Windows 7 and VirtualBox has been reinstalled on one of them to test the possibility that the upgrade broke it. Unfortunately, re-installation of VBox didn't help. This is also happening with multiple guests (Windows 7, XP), so it's pretty much widespread. VBox is unusable on Windows 10 hosts.
|
|||
| #15302 | worksforme | 100% cpu usage by VBoxHeadless | ||
| Description |
Getting constant 19-24% cpu usage (4 cpu cores on this computer so essentially one cpu is maxed) on VBoxHeadless. Running on a linux 64bit server, 3.10.17 kernel. Client is Windows 7 64bit, one cpu (not smp). Accidentally started with -e TCP/Ports=35 instead of 3395 as I had intended. Windows 7 taskmgr.exe reports constant 1% cpu usage. Using 5.0.16. I cant touch the server during the day, will try later to see if this reproducible and if the port 35 is truly the problem. |
|||
| #15301 | fixed | Windows 10 VM crashing | ||
| Description |
Hi, I'm running virtualbox on openSUSE 13.2 (Harlequin) (x86_64) and the windows 10 VM is "windows 10 enterprise 64bit" for no aparent reason the VM just reboots without warning and there doesnt seem to be any pattern which is causing the reboot, I have even left the VM running with nothing open and nothing running on the host PC appart from the windows 10 vm only to come back and the vm has rebooted regards, -=VR46=- |
|||

