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

Issue 747603 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Jul 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

us-east1-a default CPU platform "Ivy Bridge" doesn't support nesting and so fails VMTest

Project Member Reported by nxia@chromium.org, Jul 21 2017

Issue description

GCEs in zone us-east1-a cannot support KVM because 

"
us-east1-a has Ivy Bridge machines, so the VMs in that zone would be
configured by default as Ivy Bridge, and we only support nesting on
Haswell or later. You should be able to get nesting to work in
us-east1-a if you use the CPU selection feature to select Skylake.
"

Now the option of specifying CPU platform is only supported in "gcloud beta", so plan to migrate all GCEs for tryservers to the central zone. 

 
Project Member

Comment 1 by bugdroid1@chromium.org, Jul 24 2017

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/infra_internal/+/036ca3d3742ef094beda87cb03dfa9428ea21894

commit 036ca3d3742ef094beda87cb03dfa9428ea21894
Author: Ningning Xia <nxia@google.com>
Date: Mon Jul 24 05:00:20 2017

Comment 2 by nxia@chromium.org, Jul 25 2017

https://uberchromegw.corp.google.com/i/chromiumos.tryserver/builders/pre_cq/builds/45873

Moved all GCE instances to the central zone, betty-pre-cq passed successfully. 

Comment 3 by nxia@chromium.org, Jul 25 2017

Status: Fixed (was: Untriaged)

Sign in to add a comment