Context Navigation

← Previous Ticket
Next Ticket →

#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 galitsyn)

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)

VBox.log (83.2 KB ) - added by MiK 10 years ago.: log file after problem appeared
systemlog.txt.zip (175.6 KB ) - added by MiK 10 years ago.: system.log
VBox.2.log (98.1 KB ) - added by MiK 10 years ago.: VBLog 4.6.2014
logfile.txt.zip (307.1 KB ) - added by MiK 10 years ago.: system.log 4.6.2014
logfile.txt.2.zip (307.1 KB ) - added by MiK 10 years ago.: system.log 2
Archiv.zip (61.4 KB ) - added by MiK 10 years ago.

Download all attachments as: .zip

Change History (33)

comment:1 by galitsyn, 10 years ago

Description:	modified (diff)

comment:2 by galitsyn, 10 years ago

Could you please attach VBox.log?

by MiK, 10 years ago

Attachment:	VBox.log added

log file after problem appeared

comment:3 by MiK, 10 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 galitsyn, 10 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)?

by MiK, 10 years ago

Attachment:	systemlog.txt.zip added

system.log

comment:5 by MiK, 10 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.

Last edited 10 years ago by MiK (previous) (diff)

comment:6 by galitsyn, 10 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 MiK, 10 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.

by MiK, 10 years ago

Attachment:	VBox.2.log added

VBLog 4.6.2014

by MiK, 10 years ago

Attachment:	logfile.txt.zip added

system.log 4.6.2014

follow-up: 10 comment:8 by MiK, 10 years ago

added both log files. Problem starts at 06:46:00

comment:9 by jeremyl, 10 years ago

I'm seeing the same issue (MacBook Pro, VirtualBox 4.3.12, Host: OSX Mavericks, Guest: Ubuntu 14.04)

Last edited 10 years ago by jeremyl (previous) (diff)

in reply to: 8 comment:10 by galitsyn, 10 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:11 by MiK, 10 years ago

It's central European Summer Time (Berlin)

comment:12 by galitsyn, 10 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.

Last edited 10 years ago by galitsyn (previous) (diff)

by MiK, 10 years ago

Attachment:	logfile.txt.2.zip added

system.log 2

comment:13 by MiK, 10 years ago

it seems the end was missing. Hope it's complete now. Sorry for the inconvenience.

comment:14 by galitsyn, 10 years ago

Files from logfile.txt.zip and logfile.txt.2.zip are identical.

comment:15 by MiK, 10 years ago

Please check Jun 4, timestamp 06:46:00am. Here the problem started and you find wake reason:? At this time VB was running. UTC time is Jun 4, 04:46:00am.

Last edited 10 years ago by MiK (previous) (diff)

comment:16 by galitsyn, 10 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 MiK, 10 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 galitsyn, 10 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:19 by MiK, 10 years ago

No, Power Nap is disabled for both, battery and power supply.

comment:20 by MiK, 10 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 galitsyn, 10 years ago

Please do because It is currently not reproducible here and the root cause remains to be unclear.

comment:22 by MiK, 10 years ago

Unfortunately this didn't solve the problem, appeared again.

comment:23 by galitsyn, 10 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.