New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 605616 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature

Blocking:
issue 591626



Sign in to add a comment

explore using the chroot QEMU/KVM for running VMtests

Reported by vpalatin@chromium.org, Apr 21 2016

Issue description

The current VMTests stage is using the host QEMU/KVM binary to run the virtual machine,
using the binary from inside chroot would give us a more modern (currently v2.5) and more consistent/controlled version across builders/developers.

That would be useful to run ARM/ARM64 VMtests as we need a recent QEMU version (v2.5+) and controlling a bit its configuration.

I have already done some testing : the current chroot version seems fine to run the existing x86_64 VMtests
see https://chromium-review.googlesource.com/#/c/339839/
 
Blocking: 591626
Project Member

Comment 2 by bugdroid1@chromium.org, Apr 22 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/crosutils/+/28611805d0e6b82d40800650d529530f2c23d7ec

commit 28611805d0e6b82d40800650d529530f2c23d7ec
Author: Vincent Palatin <vpalatin@chromium.org>
Date: Thu Apr 21 00:00:50 2016

cros_vm_lib: allow running VM from inside the chroot

The QEMU binary inside the chroot is perfectly able to run the Chrome OS
VM (with KVM support enabled).
Enable this feature and tweak the command-line accordingly if needed
as we need to use the 'qemu-system-x86_64' binary inside the chroot
with the '-enable-kvm' flag.

note: this allows to run the testing on a modern (v2.5) and consistent
version of QEMU.

BUG=chromium:605616 chromium:591626
TEST=inside the chroot './bin/cros_start_vm --board=amd64-generic'
and run 'test_that --board=amd64-generic localhost:9222 suite:smoke'
TEST='cbuildbot --remote -g 339839 amd64-generic-full'

Change-Id: I4aa317400d566ddf9518c2c1ccbe1167681ba7e7
Reviewed-on: https://chromium-review.googlesource.com/339839
Commit-Ready: Vincent Palatin <vpalatin@chromium.org>
Tested-by: Vincent Palatin <vpalatin@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/28611805d0e6b82d40800650d529530f2c23d7ec/lib/cros_vm_lib.sh
[modify] https://crrev.com/28611805d0e6b82d40800650d529530f2c23d7ec/bin/cros_stop_vm
[modify] https://crrev.com/28611805d0e6b82d40800650d529530f2c23d7ec/bin/cros_start_vm

Project Member

Comment 3 by bugdroid1@chromium.org, Apr 26 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/dev-util/+/c1613e64381e897d103ec27af70f062e1db16e5c

commit c1613e64381e897d103ec27af70f062e1db16e5c
Author: Vincent Palatin <vpalatin@chromium.org>
Date: Mon Apr 25 23:45:47 2016

image_to_live.sh: allow executing inside the chroot

The script seems to run fine from inside the chroot,
remove the assertion forcing to execute script outside the chroot.

That's part of a larger work for running the VMtests using the QEMU/KVM binary
inside the chroot, so we get a modern and consistent version of QEMU.

BUG=chromium:605616
TEST='./bin/ctest --board=amd64-generic --type=vm --no_graphics
--quick_update  --suite=smoke  --whitelist_chrome_crashes'
TEST='cbuildbot --remote -g 340240 -g 340582 amd64-generic-paladin'

Change-Id: I1bc53c8d29483858414eee5f4658fe4c0f065ee2
Reviewed-on: https://chromium-review.googlesource.com/340582
Commit-Ready: Vincent Palatin <vpalatin@chromium.org>
Tested-by: Vincent Palatin <vpalatin@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/c1613e64381e897d103ec27af70f062e1db16e5c/host/image_to_live.sh

Components: Test
Status: Assigned (was: Untriaged)

Sign in to add a comment