arcvm: Make sure Concierge is running before talking to it
ARCVM uses Concierge to throttle crosvm's CPU usage. Unlike session_manager which always outlives Chrome, Concierge may start after Chrome is started. Previously, if SetArcVmCpuRestriction is called before Concierge fully starts, the operation failed with the following errors: ERROR:object_proxy.cc(632)] Failed to call method: org.chromium.VmConcierge.SetVmCpuRestriction: object_path= /org/chromium/VmConcierge: org.freedesktop.DBus.Error.ServiceUnknown: The name org.chromium.VmConcierge was not provided by any .service files ERROR:arc_util.cc(57)] Failed to call SetVmCpuRestriction This CL fixes the error. BUG=b:139095697 TEST=Start ARCVM, verify /var/log/chrome/chrome no longer has the errors. Change-Id: I6e1caf28bbe0307525ee750b3da3008d884435cd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1808240Reviewed-by:Yury Khmel <khmel@chromium.org> Commit-Queue: Yusuke Sato <yusukes@chromium.org> Cr-Commit-Position: refs/heads/master@{#697288}
Showing
Please register or sign in to comment