Windows 10 uses a new reboot call which freezes VirtualBox

[birdie]

Host OS: Linux 3.16 i686
Guest OS: Windows 10 Preview x86

Steps to reproduce: create a new Windows 8.1 VM with more than one CPU kernels.

Try to install WindowsTechnicalPreview-x86-EN-US.iso.

Every time Windows would want to reboot, VirtualBox would hang/freeze and start consuming 200% of CPU (two fully enabled cores in my case).

There's nothing interesting in logs:

00:42:07.114152 EHCI: USB Operational
00:42:07.132873 EHCI: USB Suspended
00:42:07.190235 OHCI: USB Suspended

[frank]

Definitely worth to look at but it's still Windows 10 Preview, not the final version.

[mhanor]

Attach a VM session log, where you reproduced the issue.
It's not the same host OS, but this looks similar to #13319

[birdie]

Replying to mhanor:

Attach a VM session log, where you reproduced the issue.
It's not the same host OS, but this looks similar to #13319

The log extract above was taken after 10 minutes of inactivity when hitting "Reboot". Are you sure you really need the full VBox.log? I doubt it will be of any use.

I have an Intel Core i5 2500 CPU, Linux Kernel 3.16.0 i686 PAE (NX bit disabled on boot), 16GB of RAM and VirtualBox 4.3.16.

[mhanor]

I'm not a VirtualBox developer, so I don't need it. But the full log is useful to the dev team, as they can see your host and guest configuration.

[birdie]

Useless Vbox.log containing ZERO relevant info

[birdie]

Strace is useless as well:

clock_gettime(CLOCK_MONOTONIC, {1876, 676296117}) = 0
poll([{fd=14, events=POLLIN}, {fd=22, events=POLLIN}, {fd=23, events=POLLIN}, {fd=13, events=POLLIN}, {fd=24, events=POLLIN}], 5, 0) = 0 (Timeout)
recv(13, 0x85a18b8, 4096, 0)            = -1 EAGAIN (Resource temporarily unavailable)
clock_gettime(CLOCK_MONOTONIC, {1876, 676357595}) = 0
recv(13, 0x85a18b8, 4096, 0)            = -1 EAGAIN (Resource temporarily unavailable)
clock_gettime(CLOCK_MONOTONIC, {1876, 676395146}) = 0
poll([{fd=14, events=POLLIN}, {fd=22, events=POLLIN}, {fd=23, events=POLLIN}, {fd=13, events=POLLIN}, {fd=24, events=POLLIN}], 5, 0) = 0 (Timeout)
recv(13, 0x85a18b8, 4096, 0)            = -1 EAGAIN (Resource temporarily unavailable)
clock_gettime(CLOCK_MONOTONIC, {1876, 676455845}) = 0
recv(13, 0x85a18b8, 4096, 0)            = -1 EAGAIN (Resource temporarily unavailable)
clock_gettime(CLOCK_MONOTONIC, {1876, 676499632}) = 0
poll([{fd=14, events=POLLIN}, {fd=22, events=POLLIN}, {fd=23, events=POLLIN}, {fd=13, events=POLLIN}, {fd=24, events=POLLIN}], 5, 0) = 0 (Timeout)
recv(13, 0x85a18b8, 4096, 0)            = -1 EAGAIN (Resource temporarily unavailable)
clock_gettime(CLOCK_MONOTONIC, {1876, 676560650}) = 0
recv(13, 0x85a18b8, 4096, 0)            = -1 EAGAIN (Resource temporarily unavailable)
clock_gettime(CLOCK_MONOTONIC, {1876, 676598232}) = 0
poll([{fd=14, events=POLLIN}, {fd=22, events=POLLIN}, {fd=23, events=POLLIN}, {fd=13, events=POLLIN}, {fd=24, events=POLLIN}], 5, 0) = 0 (Timeout)

[mhanor]

If you think you can debug this, you should make a debug build of VirtualBox and take a look at the spinning threads.

[birdie]

Since on my side this issue is 100% reproducible, I am 100% sure VBox developers can easily debug it and find the root cause.

I'm not a paid developer to resolve this issue for them, besides my knowledge of the i686 architecture and assembler is non-existent so there's little to no chance that I will understand what's going on.

[sunlover]

The problem is reproducible.

This is a duplicate of https://www.virtualbox.org/ticket/13462