This means that when you start qemu, you are not specyfing a VGA card
that your kernel can understand. Either recompile the kernel with a
supported VGA/framebuffer device or re-configure qemu so that it
presents some different VGA card to the guest OS.
On 12/01/2014 11:33 AM, Hyukjoong Kim wrote:
Yes, the mentioned problem was displaying problem. In that case, it is
possible to connect to VM with SSH.
So, I'm currently trying to enable fbdev on SSH, but I cannot find the
solution to do that.
I installed XF86-video-fbdev using zypper (also this is not possible
with 64bit image due to zypper problem), but there are no /dev/fb0, so
cannot connect with fbdev.
Do you have any solution for this?
__
김 혁 중
성균관대학교 IT 융합학과 박사과정
임베디드 소프트웨어 연구실
Kim, Hyukjoong
Sungkyunkwan University
Ph.D Course in Computer Engineering, IT Convergence
Embedded Software Lab.
e-mail : wang...@skku.edu <mailto:wang...@skku.edu> /
wang...@gmail.com <mailto:wang...@gmail.com>
phone : +82 10-9489-8974
__
2014-11-27 23:21 GMT+09:00 VanCutsem, Geoffroy
<geoffroy.vancut...@intel.com <mailto:geoffroy.vancut...@intel.com>>:
It's finding syslinux so this may not be a 32-bit vs. 64-bit
problem. What could happen here is that the kernel boots but the
graphical environment never comes up (precisely because you need
to modify the image to use fbdev or use a version of QEMU that has
yagl). The initial screenshot you shared (where the last line was
something about being unable to open rtc0 is a typical symptom of
the very same problem.
What you can try to do is remove the 'quiet' keyword from the
kernel command-line to see if the kernel boots. Or you could also
try to switch to a console (Ctrl-Alt-F2) and verify that you get a
login prompt (forget about F1, that's where the graphical env is
and no login prompt will ever appear there, so use F2 or higher).
I haven't used QEMU in a while and IIRC there was a trick to send
such key combination to a QEMU VM, I don't recall what it was but
I'm sure you should fairly easily be able to find this.
Cheers,
Geoffroy
> -----Original Message-----
> From: Dev [mailto:dev-boun...@lists.tizen.org
<mailto:dev-boun...@lists.tizen.org>] On Behalf Of Roman Kubiak
> Sent: Tuesday, November 25, 2014 12:05 PM
> Cc: dev@lists.tizen.org <mailto:dev@lists.tizen.org>
> Subject: Re: [Dev] Running Tizen 3.0 (ivi or common) on normal QEMU.
>
> Well if it's not booting then maybe you are using a 64bit kernel
on a 32bit
> machine ?
>
> For the X11 to work you need to get the image working and
install the fbdev
> driver using zypper because it's not included in the image (the
X11 subsystem
> has only the Intel driver included, but the fbdev driver is in
the common
> repository)
>
>
> On 11/25/2014 12:00 PM, Hyukjoong Kim wrote:
> > Hi Roman,
> >
> > Thanks for previous reply, but I didn't get your meaning clearly.
> > Did you mean I need to change the backend graphic driver into
fbdev?
> > Or, just use X11/common image then I can use fbdev for backend
> > graphics driver?
> > And I was trying to find your previous post about this, but I
failed
> > to find your post about tizen with generic qemu.
> >
> > So, I just run tizen common x11 image
> > (tizen-common-20141118.1_common-x11-mbr-x86_64-sda.raw) with
> command
> > below,
> > 'qemu-system-x86_64 -cpu core2duo
> > tizen-common_20141118.1_common-x11-mbr-x86_64-sda.raw'
> > but booting was stop from here.
> >
> > 본문 이미지 1
> >
> > I think the boot process is stopped from the beginning so, it
is not
> > the problem of graphic driver. May this be correct?
> >
> > Thanks,
> > -Hyukjoong
> >
> > __
> > 김 혁 중
> > 성균관대학교 IT 융합학과 박사과정
> > 임베디드 소프트웨어 연구실
> >
> > Kim, Hyukjoong
> > Sungkyunkwan University
> > Ph.D Course in Computer Engineering, IT Convergence Embedded
Software
> > Lab.
> > e-mail : wang...@skku.edu <mailto:wang...@skku.edu>
<mailto:wang...@skku.edu <mailto:wang...@skku.edu>> /
> > wang...@gmail.com <mailto:wang...@gmail.com>
<mailto:wang...@gmail.com <mailto:wang...@gmail.com>> phone : +82
10-9489-
> 8974
> > __
> >
> > 2014-11-21 1:17 GMT+09:00 Roman Kubiak <r.kub...@samsung.com
<mailto:r.kub...@samsung.com>
> > <mailto:r.kub...@samsung.com <mailto:r.kub...@samsung.com>>>:
> >
> > It should be possible with the X11/Common image using
fbdev for
> > the backend graphics driver (i wrote a post on this list what
> > needs to be done to get it running). Also you just need to
set the
> > cpu type to something Intel specific.
> > On 11/20/2014 01:27 PM, ewan wrote:
> >
> > The qemu built from *https://wiki.tzen.org/wiki/Emulator
> > *
> > has yagl graphics features enabled, this feature is not
> > available in upstream qemu and (I think) is specific
to Tizen
> > and allows to graphically boot Tizen emulator images.
I don't
> > think you will be able to launch any tizen image with an
> > upstream qemu. Let me know if I'm wrong.
> >
> > Thanks.
> >
> > Ewan
> >
> >
> > Le 20/11/2014 13:22, Hyukjoong Kim a écrit :
> >
> > Thanks for replies, and sorry for confusing and
unclear
> > question.
> >
> > Actually, I'm currently working on running tizen with
> > architectural simulator.
> >
> > And, I thought Marss86 simulator is fittable for this
> > purpose because Marssim dynamically simulate the core
> > behavior with on-going emulation on QEMU (it is
modified
> > version of original QEMU source).
> > (The recent merged version of QEMU on marss is
0.14 stable
> > branch. (is it quite old for running tizen?))
> >
> > Thus, I tried to figure out the method to run
tizen 3.0 on
> > 'normal qemu'. (So the 'normal qemu' was meant for
> > commonly built qemu image.)
> >
> > However, from the Ewan's comment, it seems to need to
> > newly build QEMU with specific option to run tizen
image.
> >
> > So, really should I newly build QEMU with specific
option
> > to run the tizen image?
> > Or, can I run Tizen common (or ivi) image with just
> > 'apt-get installed' qemu program? (Then how?)
> >
> > Thanks,
> > -Hyukjoong
> >
> >
> > __
> > 김 혁 중
> > 성균관대학교 IT 융합학과 박사과정
> > 임베디드 소프트웨어 연구실
> >
> > Kim, Hyukjoong
> > Sungkyunkwan University
> > Ph.D Course in Computer Engineering, IT Convergence
> > Embedded Software Lab.
> > e-mail : wang...@skku.edu
<mailto:wang...@skku.edu> <mailto:wang...@skku.edu
<mailto:wang...@skku.edu>>
> > <mailto:wang...@skku.edu <mailto:wang...@skku.edu>
<mailto:wang...@skku.edu <mailto:wang...@skku.edu>>> /
> > wang...@gmail.com <mailto:wang...@gmail.com>
<mailto:wang...@gmail.com <mailto:wang...@gmail.com>>
> > <mailto:wang...@gmail.com
<mailto:wang...@gmail.com> <mailto:wang...@gmail.com
<mailto:wang...@gmail.com>>>
> > phone : +82 10-9489-8974
> > __
> >
> > 2014-11-20 20:27 GMT+09:00 Roman Kubiak
> > <r.kub...@samsung.com
<mailto:r.kub...@samsung.com> <mailto:r.kub...@samsung.com
<mailto:r.kub...@samsung.com>>
> > <mailto:r.kub...@samsung.com
<mailto:r.kub...@samsung.com>
> <mailto:r.kub...@samsung.com <mailto:r.kub...@samsung.com>>>>:
> >
> >
> > The kernel in common does not support AMD
cpus, you
> > need to pass
> > and argument to qemu to change the CPU to
something
> > Intel based
> >
> > [root@AMDC2543:~]# qemu-i386 -cpu ?
> > x86 [n270]
> > x86 [athlon]
> > x86 [pentium3]
> > x86 [pentium2]
> > x86 [pentium]
> > x86 [486]
> > x86 [coreduo]
> > x86 [kvm32]
> > x86 [qemu32]
> > x86 [kvm64]
> > x86 [core2duo]
> > x86 [phenom]
> > x86 [qemu64]
> >
> >
> > On 11/20/2014 12:25 PM, 황석연 wrote:
> >
> > Samsung Enterprise Portal mySingle
> >
> > Dear Kim,
> >
> > First of all, what is normal QEMU ?
> >
> > Does it mean qemu binary that is built on
your own
> > from
> > upstream qemu source ??
> >
> > What version of QEMU is used for building ??
> >
> > What argument did you use for running ??
> >
> > ------- *Original Message* -------
> >
> > *Sender* : Hyukjoong Kim<wang...@gmail.com
<mailto:wang...@gmail.com>
> > <mailto:wang...@gmail.com <mailto:wang...@gmail.com>>
> > <mailto:wang...@gmail.com
<mailto:wang...@gmail.com>
> > <mailto:wang...@gmail.com <mailto:wang...@gmail.com>>>>
> >
> > *Date* : 2014-11-20 20:14 (GMT+09:00)
> >
> > *Title* : [Dev] Running Tizen 3.0 (ivi or
common)
> > on normal QEMU.
> >
> > Hi,
> >
> > I'm currently trying to run tizen 3.0 with
normal QEMU
> > (because of QEMU-merged special tool).
> >
> > And I think, Tizen 3.0 ivi x86 image should be
> > able to run
> > with normal QEMU because it also run with
vmware
> > or vmplayer.
> >
> > However, when I run
> > tizen-ivi_20141103.2_ivi_mbr-i586-sdb.raw
> > image with qemu-system-x86_64, it was
frozen with
> > this state.
> > 본문 이미지 1
> >
> > If there are some solution to run the 3.0
image
> > with normal
> > QEMU, please let me know about that.
> >
> > Thanks,
> > -Hyukjoong
> >
> >
> > __
> > 김 혁 중
> > 성균관대학교 IT 융합학과 박사과정
> > 임베디드 소프트웨어 연구실
> >
> > Kim, Hyukjoong
> > Sungkyunkwan University
> > Ph.D Course in Computer Engineering, IT
Convergence
> > Embedded Software Lab.
> > e-mail : wang...@skku.edu
<mailto:wang...@skku.edu>
> > <mailto:wang...@skku.edu
<mailto:wang...@skku.edu>> <mailto:wang...@skku.edu
<mailto:wang...@skku.edu>
> > <mailto:wang...@skku.edu <mailto:wang...@skku.edu>>>
> > <mailto:wang...@skku.edu
<mailto:wang...@skku.edu> <mailto:wang...@skku.edu
<mailto:wang...@skku.edu>>
> > <mailto:wang...@skku.edu <mailto:wang...@skku.edu>
<mailto:wang...@skku.edu <mailto:wang...@skku.edu>>>> /
> > wang...@gmail.com <mailto:wang...@gmail.com>
<mailto:wang...@gmail.com <mailto:wang...@gmail.com>>
> > <mailto:wang...@gmail.com
<mailto:wang...@gmail.com> <mailto:wang...@gmail.com
<mailto:wang...@gmail.com>>>
> > <mailto:wang...@gmail.com
<mailto:wang...@gmail.com>
> > <mailto:wang...@gmail.com
<mailto:wang...@gmail.com>> <mailto:wang...@gmail.com
<mailto:wang...@gmail.com>
> > <mailto:wang...@gmail.com
<mailto:wang...@gmail.com>>>>
> > phone : +82 10-9489-8974
> > __
> >
> >
> >
> > _______________________________________________
> > Dev mailing list
> > Dev@lists.tizen.org <mailto:Dev@lists.tizen.org>
<mailto:Dev@lists.tizen.org <mailto:Dev@lists.tizen.org>>
> > <mailto:Dev@lists.tizen.org
<mailto:Dev@lists.tizen.org> <mailto:Dev@lists.tizen.org
<mailto:Dev@lists.tizen.org>>>
> > https://lists.tizen.org/listinfo/dev
> >
> >
> > -- --------------
> > Roman Kubiak
> > --------------
> >
> >
> > _______________________________________________
> > Dev mailing list
> > Dev@lists.tizen.org <mailto:Dev@lists.tizen.org>
<mailto:Dev@lists.tizen.org <mailto:Dev@lists.tizen.org>>
> > <mailto:Dev@lists.tizen.org
<mailto:Dev@lists.tizen.org> <mailto:Dev@lists.tizen.org
<mailto:Dev@lists.tizen.org>>>
> > https://lists.tizen.org/listinfo/dev
> >
> >
> >
> >
> > --
> > --------------
> > Roman Kubiak
> > --------------
> >
> > _______________________________________________
> > Dev mailing list
> > Dev@lists.tizen.org <mailto:Dev@lists.tizen.org>
<mailto:Dev@lists.tizen.org <mailto:Dev@lists.tizen.org>>
> > https://lists.tizen.org/listinfo/dev
> >
> >
>
> --
> --------------
> Roman Kubiak
> --------------
>
> _______________________________________________
> Dev mailing list
> Dev@lists.tizen.org <mailto:Dev@lists.tizen.org>
> https://lists.tizen.org/listinfo/dev
_______________________________________________
Dev mailing list
Dev@lists.tizen.org <mailto:Dev@lists.tizen.org>
https://lists.tizen.org/listinfo/dev
--
--------------
Roman Kubiak
--------------
_______________________________________________
Dev mailing list
Dev@lists.tizen.org
https://lists.tizen.org/listinfo/dev
