touch-packages team mailing list archive

[Yuan-Chen Cheng <yc.cheng@xxxxxxxxxxxxx>]

I enable virtuallization in BIOS and then it works !

We definitely need to check if visualization is properly enable before
run it.

Thanks for suggestion from Rex, I install package cpu-checker and run
command kvm-ok can show whether cpu support visualization and if it's
enable in BIOS.

If cpu support it and it's enable in bios, it show result (in utopic)
==========
INFO: /dev/kvm exists
KVM acceleration can be used
==========

If cpu support it and it's NOT enable in bios, it show result (run as non-root in utopic)
==========
INFO: /dev/kvm does not exist
HINT:   sudo modprobe kvm_intel
INFO: For more detailed results, you should run this as root
HINT:   sudo /usr/sbin/kvm-ok
==========

If cpu support it and it's NOT enable in bios, it show result (run as root in utopic)
==========
INFO: /dev/kvm does not exist
HINT:   sudo modprobe kvm_intel
INFO: Your CPU supports KVM extensions
INFO: KVM (vmx) is disabled by your BIOS
HINT: Enter your BIOS setup and enable Virtualization Technology (VT),
      and then hard poweroff/poweron your system
KVM acceleration can NOT be used
=========

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1396919

Title:
  unity8 display blank in emulator, host utopic, rtm-14.09 instance.

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  As run emulator, device screen is blank.

  Step to reproduce:

  1. install utopic.
  2. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa
  3. sudo apt-get install ubuntu-sdk
  4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386
  5. create device instance i386 / rtm-14.09 and launch it.

  Expected result:
  See ubuntu phone UI there.

  Current result:
  Emulator screen is black.

  Extra Note:
  1. On the pc, in the first run of the instance, I can see phone interface on first boot after I "kill -9 unity8 unity8-dash".
      But this work around failed as I stop the instance and run again. I even create the same instance with the other name
     and try this work around, still can't see anything on the screen.
  2. I can run test_glesv2 and see the result on the screen of the display correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1396919/+subscriptions