Opened 11 years ago
Closed 9 years ago
#13067 closed defect (obsolete)
Battery Drain when lid of MacBook Air is closed
Reported by: | MiK | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.3.12 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Mac OS X |
Description (last modified by )
After about 3 hours of sleep a heavy battery drain starts on MacBook Air (MacOS 10.9.3) when running VB with Windows 7 installed.
syslog | grep -i "Wake reason" shows May 23 11:37:48 NAME kernel[0] <Debug>: Wake reason: ? May 23 11:38:30 NAME kernel[0] <Debug>: Wake reason: ? May 23 11:39:08 NAME kernel[0] <Debug>: Wake reason: ? May 23 11:39:57 NAME kernel[0] <Debug>: Wake reason: ? ...
one entry every minute until battery is empty.
Attachments (6)
Change History (33)
comment:1 by , 11 years ago
Description: | modified (diff) |
---|
comment:2 by , 11 years ago
comment:3 by , 11 years ago
The problem doesn't occur every time the machine is put to sleep mode. However, the log file was uploaded after the problem occured.
comment:4 by , 11 years ago
May be you could additionally attach a part of system.log which corresponds to the time interval when the issue was happening (need to map time intervals to VBox.log message timestamps)?
comment:5 by , 11 years ago
Added system.log. The lid was closed at 11:37 with VB running and the problem started at 14:37. You can see "Wake reason: ?" from there on.
comment:6 by , 11 years ago
Sorry, but VBox.log is dated by May 16 while system.log is by May 29. You probably still have system.log for that time (May 16 14:00+) when VBox.log was obtained (look into /var/log/system.log.*.bz2). Could you please re-attach it?
comment:7 by , 11 years ago
unfortunately it is not available any more. Next time the problem occurs I will post both, the VB.Log and the system.log.
comment:9 by , 11 years ago
I'm seeing the same issue (MacBook Pro, VirtualBox 4.3.12, Host: OSX Mavericks, Guest: Ubuntu 14.04)
comment:10 by , 11 years ago
Replying to MiK:
added both log files. Problem starts at 06:46:00
Ahh, one extra thing. VBox.log timestamps are always in UTC while system.log ones are taken in your local timezone. Looking into VBox.log, I can say that VBox was started at 2014-06-03, 15:54:24 UTC but what is the timezone shift for system.log timestamps?
comment:12 by , 11 years ago
Hmm, then I don't see any
kernel[0] <Debug>: Wake reason: ?
message in system.log while VBox was running (2014-06-03 15:54:24 -> ~18:25:00 UTC [which is 2014-06-03 17:54:24 -> ~20:25:00 (CEST=UTC+2)]). You probably attached unrelated log.
comment:13 by , 11 years ago
it seems the end was missing. Hope it's complete now. Sorry for the inconvenience.
comment:15 by , 11 years ago
Please check Jun 4, timestamp 06:46:00. Here the problem started and you find wake reason:? At this time VB was running. UTC time is Jun 4, 04:46:00.
comment:16 by , 11 years ago
The idea was to check what VBox said in VBox.log when OS X complains about "Wake reason: ?" in system.log. VBox.log you attached is dated by June 3, but system.log message has a timestamp June 4 => no way to reach the goal.
comment:17 by , 11 years ago
yes, but this is right. VBox was started on June 3, the MacBook put sleep and connected to power supply. On Jun 4, power supply was disconnected and the problem started (MB Air became hot although lid was closed). After the problem occured I closed VBox, took the logfile and uploaded it.
comment:18 by , 11 years ago
I see. Thanks! Btw, do you have Power Nap option enabled in Energy Saver settings? I have suspicion if the option is disabled, the issue should not appear.
comment:20 by , 11 years ago
Apple released a battery fix SMC firmware update - I'll check if this solves the problem and post it here again.
comment:21 by , 11 years ago
Please do because It is currently not reproducible here and the root cause remains to be unclear.
comment:23 by , 11 years ago
From the system.log I can see there are spinning reports generated at /Library/Logs/DiagnosticReports/VirtualBoxVM*.spin. Could you please collect+zip them and attach? I need those ones which were generated per one VBox run when the issue occurred. In case if reports were generated for VBox other than r93733, please specify revision.
by , 11 years ago
Attachment: | Archiv.zip added |
---|
comment:25 by , 11 years ago
Are there already any news? Have you been able to reproduce the problem? Thanks for your support.
comment:27 by , 9 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
Could you please attach VBox.log?