Chrome OS in qemu should run at higher resolution |
||||||
Issue descriptionIt's currently displayed at 800x600 when run in QEMU, it should be at least 1024x768
,
Sep 14 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/0d4df0a701be520f0ab367221e28a253f5c2e439 commit 0d4df0a701be520f0ab367221e28a253f5c2e439 Author: Nicolas Norvez <norvez@chromium.org> Date: Tue Sep 13 11:00:45 2016 CHROMIUM: config: enable virtio_gpu for x86_64 Enable CONFIG_DRM_VIRTIO_GPU for x86_64 to run higher screen resolutions in qemu compared to cirrus BUG= chromium:636309 TEST=build amd64-generic, run in qemu with '-vga virtio' TEST=trybot amd64-generic-chromium-pfq, VMTests passed using '-vga cirrus' Change-Id: Ic9ec038b44f75ce91d62c5048991158970428f5c Reviewed-on: https://chromium-review.googlesource.com/384871 Commit-Ready: Nicolas Norvez <norvez@chromium.org> Tested-by: Nicolas Norvez <norvez@chromium.org> Reviewed-by: Vincent Palatin <vpalatin@chromium.org> [modify] https://crrev.com/0d4df0a701be520f0ab367221e28a253f5c2e439/chromeos/config/x86_64/chromeos-intel-pineview.flavour.config [modify] https://crrev.com/0d4df0a701be520f0ab367221e28a253f5c2e439/chromeos/config/x86_64/chromiumos-x86_64.flavour.config [modify] https://crrev.com/0d4df0a701be520f0ab367221e28a253f5c2e439/chromeos/config/x86_64/common.config
,
Oct 1 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/2e291fdcc1bf49ceca3b0f15279c048ac3c477ea commit 2e291fdcc1bf49ceca3b0f15279c048ac3c477ea Author: Nicolas Norvez <norvez@chromium.org> Date: Wed Aug 31 17:24:20 2016 CHROMIUM: vgem: Fix locking around drm_vma_offset_exact_lookup_locked() Same as https://patchwork.kernel.org/patch/7404291/ ("drm/gem: Use kref_get_unless_zero for the weak mmap references") for VGEM. Calling drm_vma_offset_exact_lookup_locked() now requires the vma offset manager lookup lock be acquired with drm_vma_offset_lock_lookup() instead of holding struct_mutex. BUG= chromium:636309 TEST=Ran amd64-generic with ARC++ enabled in qemu, lockup disappeared Change-Id: Icca821e665731fd41d0a8767d574ac573bbbb2c6 Signed-off-by: Nicolas Norvez <norvez@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/378857 Reviewed-by: Tomasz Figa <tfiga@chromium.org> [modify] https://crrev.com/2e291fdcc1bf49ceca3b0f15279c048ac3c477ea/drivers/gpu/drm/vgem/vgem_drv.c
,
Oct 1 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform/crosutils/+/c55ab68898511ab62aae3d36a86d0d7edce40939 commit c55ab68898511ab62aae3d36a86d0d7edce40939 Author: Nicolas Norvez <norvez@chromium.org> Date: Fri Sep 23 15:17:14 2016 cros_vm: use the SDK's version of qemu By default, use the version of qemu shipped with the SDK rather than the default one shipped with the system that may not support all required features (e.g. support for virtio_gpu). This also gives us a more consistent behaviour when VMs are deployed on different hosts with different versions of qemu. Requires CL:351861 so qemu can be used from outside the chroot. BUG= chromium:618431 BUG= chromium:636309 TEST=cbuildbot --remote cyan-android-pfq after applying CL:389132 to enable VM tests. TEST=cros_run_vm_update --qemu_binary='xxxx' and check that the correct qemu binary gets picked. CQ-DEPEND=CL:351861 Change-Id: Ibd7e120229b0a64b3d38a7cb779d5efbdd8914bd Reviewed-on: https://chromium-review.googlesource.com/389152 Commit-Ready: Nicolas Norvez <norvez@chromium.org> Tested-by: Nicolas Norvez <norvez@chromium.org> Reviewed-by: Vincent Palatin <vpalatin@chromium.org> [modify] https://crrev.com/c55ab68898511ab62aae3d36a86d0d7edce40939/lib/cros_vm_lib.sh
,
Oct 3 2016
Arbitrary screen resolutions are now supported, need to use qemu 2.6 (shipped with Chrome OS SDK) with '-vga virtio' option.
,
Oct 7 2016
,
Nov 19 2016
,
Jan 13 2017
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by norvez@chromium.org
, Aug 10 2016