New issue
Advanced search Search tips

Issue 872920 link

Starred by 1 user
Status: Fixed
Owner:
w...@chromium.org
Closed: Aug 13
Components:
EstimatedDays: ----
NextAction: ----
OS: Fuchsia
Pri: 2
Type: Bug



Sign in to add a comment

Runner fails to connect to host if KVM permission is denied

Project Member Reported by w...@chromium.org, Aug 9 
If the Fuchsia target architecture matches that of the host system, then the runner will try to launch QEMU with KVM acceleration.

If the user does not have access to /dev/kvm then this causes QEMU launch to silently fail - the runner script seemingly ignores the failure and continues trying to connect via SSH until that times out.

Since the QEMU stderr is merged with its stdout output and either piped to /dev/null or to a file, the cause of the failure is not visible to the user.
Project Member

Comment 1 by bugdroid1@chromium.org, Aug 13 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d7aa2cca31b919c20f808fdff647bcda81adb3d3

commit d7aa2cca31b919c20f808fdff647bcda81adb3d3
Author: Wez <wez@chromium.org>
Date: Mon Aug 13 19:42:22 2018

[Fuchsia] Log QEMU stderr output, and handle unexpected exit.

Early termination of QEMU, e.g. due to missing KVM permissions, was
neither logged nor handled by the runner script, requiring an explicit
--system-log-file=<file> to be specified in order to determine the
cause of the failure.

Also add support for --system-log-file=- to have system log output
logged to the console, if desired.

Bug:  872920 
Change-Id: Ib2db7213231791e404eb94caa5f8788149c01bca
Reviewed-on: https://chromium-review.googlesource.com/1170086
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582670}
[modify] https://crrev.com/d7aa2cca31b919c20f808fdff647bcda81adb3d3/build/fuchsia/common_args.py
[modify] https://crrev.com/d7aa2cca31b919c20f808fdff647bcda81adb3d3/build/fuchsia/device_target.py
[modify] https://crrev.com/d7aa2cca31b919c20f808fdff647bcda81adb3d3/build/fuchsia/qemu_target.py

Comment 2 by w...@chromium.org, Aug 13

Status: Fixed (was: Started)
►

Sign in to add a comment