Opened 6 years ago
Closed 5 years ago
#18549 closed defect (fixed)
Windows host wakes from standby mode constantly => Fixed in SVN
Reported by: | Daniel Karsubka | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 6.0.4 |
Keywords: | sleep suspend wake resume standby | Cc: | |
Guest type: | all | Host type: | Windows |
Description
I already posted this elsewhere, but it was recommended I open a ticket.
Virtualbox in its current versions 5 and 6 wake up Windows hosts from standby mode.
Executing powercfg -lastwake shows that VBoxSVC.exe is the cause.
The root cause for this is here in line 192: https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Main/src-server/win/HostDnsServiceWin.cpp#L192
SetWaitableTimer is called with the last parameter being "true". The last parameter is whether or not to resume the system when in standby mode. There is no reason to wake up the host every few seconds. It is also the only occurrence in the project. Change it to "false", recompile, republish and the problem should be gone.
https://docs.microsoft.com/en-us/windows/desktop/api/synchapi/nf-synchapi-setwaitabletimer
Thank you very much!
Change History (11)
follow-up: 3 comment:2 by , 6 years ago
Yeah, I wasn't sure if those very old tickets were monitored at all. On Github for example, default sort order is by ticket open time, not last modification. Experience has shown, once an issue goes stale, it simply gets ignored.
Plus, I first did not find the main page to open a new ticket. :/ I found the other tickets by Google. I'd recommend adding a link to the ticket list right here inside the tickets.
comment:3 by , 6 years ago
Replying to blubbb:
Yeah, I wasn't sure if those very old tickets were monitored at all.
Sure they are, especially if a fresh comment is added. Most people that check the Bugtracker look at the tickets by their LastModifiedDate, see below...
On Github for example, default sort order is by ticket open time, not last modification.
GitHub? Why GitHub? Why not the built-in query in the bug-tracker? From the main page (https://www.virtualbox.org/) on the left-hand side you have the "Community", which includes a link to the "Bugtracker".
Select the "All open tickets", click on the "Columns" (near the top), to open up your preferences. Enable the "Modified" column, and then you can sort the tickets with the "Last Modified Date". Just like the way I was able to quickly find where you cross-commented... ;)
https://www.virtualbox.org/query?desc=1&order=changetime
Plus, I first did not find the main page to open a new ticket. :/ I found the other tickets by Google.
It's in the same "Bugtracker" page, "Create new ticket".
I'd recommend adding a link to the ticket list right here inside the tickets.
Not in my hands... ;)
comment:4 by , 6 years ago
Summary: | Windows host wakes from standby mode constantly → Windows host wakes from standby mode constantly => Fixed in SVN |
---|
Thanks! Applied.
comment:5 by , 6 years ago
Related discussion in the forums: https://forums.virtualbox.org/viewtopic.php?f=6&t=92523
Marked the discussion [Fixed] as well...
@vushakov, if you have a revision, please let us know when it will hit the Testbuilds...
comment:7 by , 5 years ago
Sure. You can find my name in my account settings (I presume you have access).
comment:8 by , 5 years ago
I got that message slightly too late for the 6.0.6 change log, but I can change it retrospectively (the change will appear as of any future releases). I don't have access to all account settings though for administrative/privacy reasons. Could you please give your name here as you would like it to appear? I assume there is no problem with that, as the change log is just as public as this ticket.
comment:9 by , 5 years ago
No problem. Thanks for releasing the fixed build so quickly. It is working great.
Best regards, Daniel Karsubka
comment:11 by , 5 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
@blubbb
It seems that you now have your "finger" in three tickets:
unless I missed anything more! :)
Methinks that there's a need to close 2 out of three as a duplicate, there's no point in following 3 tickets for the same issue, no? I would think that your comments on the existing tickets would be covering the basics.