Faild to run win10 on debian sid kernel 4.6.0 compilede by myself

[HMLi]

The OS is Debian GNU/Linux unstable (sid), virtualbox boot win10 well after up to kernel 4.6.0-1-amd64, but if use the kernel compiled by myself, it can't work. Please see the attachments.
VirtualBox VM 5.0.20 r106931 linux.amd64 (Apr 28 2016 14:55:21) release log
uname -a: Linux LiHM 4.6.1-hmli #1 SMP PREEMPT Sun Jun 12 09:07:07 CST 2016 x86_64 GNU/Linux

00:00:09.788988 VMSetError: /home/vbox/vbox-5.0.20/src/VBox/VMM/VMMR3/MM.cpp(685) int MMR3AdjustFixedReservation(PVM, int32_t, const char*); rc=VERR_VMM_SET_JMP_ABORTED_RESUME
00:00:09.788994 VMSetError: Failed to reserve physical memory (0x8406 -> 0x8402; VMMDev Heap)
00:00:09.789256 VMSetError: /home/vbox/vbox-5.0.20/src/VBox/VMM/VMMR3/MM.cpp(685) int MMR3AdjustFixedReservation(PVM, int32_t, const char*); rc=VERR_VMM_SET_JMP_ABORTED_RESUME
00:00:09.789260 VMSetError: Failed to reserve physical memory (0x8406 -> 0x8006; VMMDev)
00:00:09.795922 VMSetError: /home/vbox/vbox-5.0.20/src/VBox/VMM/VMMR3/MM.cpp(685) int MMR3AdjustFixedReservation(PVM, int32_t, const char*); rc=VERR_VMM_SET_JMP_ABORTED_RESUME
00:00:09.795925 VMSetError: Failed to reserve physical memory (0x8406 -> 0x406; VRam)
00:00:09.795985 NAT: Zone(nm:mbuf_cluster, used:0)
00:00:09.796258 NAT: Zone(nm:mbuf_packet, used:0)
00:00:09.796261 NAT: Zone(nm:mbuf, used:0)
00:00:09.796263 NAT: Zone(nm:mbuf_jumbo_pagesize, used:0)
00:00:09.796514 NAT: Zone(nm:mbuf_jumbo_9k, used:0)
00:00:09.796639 NAT: Zone(nm:mbuf_jumbo_16k, used:0)
00:00:09.796702 NAT: Zone(nm:mbuf_ext_refcnt, used:0)
00:00:09.796761 VMSetError: /home/vbox/vbox-5.0.20/src/VBox/VMM/VMMR3/MM.cpp(685) int MMR3AdjustFixedReservation(PVM, int32_t, const char*); rc=VERR_VMM_SET_JMP_ABORTED_RESUME
00:00:09.796764 VMSetError: Failed to reserve physical memory (0x8406 -> 0x8405; Hyper-V hypercall page)
00:00:09.796775 VMSetError: /home/vbox/vbox-5.0.20/src/VBox/VMM/VMMR3/MM.cpp(685) int MMR3AdjustFixedReservation(PVM, int32_t, const char*); rc=VERR_VMM_SET_JMP_ABORTED_RESUME
00:00:09.796776 VMSetError: Failed to reserve physical memory (0x8406 -> 0x8405; Hyper-V TSC page)
00:00:09.809646 VMM: VMMR3Term: R0 term failed, rc=VERR_VMM_SET_JMP_ABORTED_RESUME (-2708) - VMM set jump resume error.. (warning)
00:00:09.810452 Changing the VM state from 'DESTROYING' to 'TERMINATED'
00:00:09.812027 Console: Machine state changed to 'PoweredOff'

Can you help me? Thank you very much.

[HMLi]

Now it can't run on the office kernel: 4.6.0-1-amd64 #1 SMP Debian 4.6.2-1 (2016-06-15) x86_64 GNU/Linux
and the error information is same.

[Perryg]

Read your guru mediation above. Did you read the log file? We can't read it for you since you have not seen the need to supply it.

It would also help the see the vbox-install.log.

[HMLi]

Thank you very much.
I have attached the VBox.log in the first post: download/file.php?id=21816 .
Now I have attached the VBox.log and vbox-install.log, please see the attachments.
GPU is: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)

[Perryg]

I looked at all of your files and do not see an issue with VirtualBox that would cause the guru mediation other than you, have assigned all of the host cores to the guest leaving nothing reserved for the host. Since a stock kernel works and yours fails it has to be something you have triggered in your build. You should compare the stock build configuration against your custom configuration build and see what is so different that it causes issues.

[HMLi]

Thank you.
It failed not only on the kernel compiled by myself, also on the official kernel: 4.6.0-1-amd64 #1 SMP Debian 4.6.2-1 (2016-06-15) x86_64 GNU/Linux
Now it can work after the 2d and 3d hardware acceleration disabled: viewtopic.php?f=1&t=78197

[Perryg]

Just going by what you posted "but if use the kernel compiled by myself, it can't work" which I would assume it worked with the stock kernel. Anyway I will let you have at it.

[HMLi]

At first VirtualBox VM 5.0.20 r106931 can run on the official kernel 4.6.1, but after upgrated, VM 5.0.22 can't run on the official kernel 4.6.2.

[frank]

See ticket 15439. The workaround is to enable CONFIG_VIRTUALIZATION which also enables CONFIG_PREEMPT_NOTIFIERS.

[HMLi]

Thank you very much, the CONFIG_PREEMPT_NOTIFIERS=y is work for my customized kernel.
But disabling 2d and 3d hardware acceleration is also needed.

[frank]

Thank you very much, the CONFIG_PREEMPT_NOTIFIERS=y is work for my customized kernel.
But disabling 2d and 3d hardware acceleration is also needed.

That's another problem (actually a 5.0.22 regression) which will be fixed soon. The fix is part of the test builds which you can find here.

[HMLi]

Thank you, I will wait the release version.