Emulating the XO/lang-ko

This is an on-going translation

+	Software
XO
	13.2.11	2020-01-29
XS
	xs-0.7	2012-02-20

노트북 안의 노트북

라이브시디를 통한 빠른 시작

대부분 슈가를 사용해보는 가장 쉬운 방법은 라이브시디입니다. 이 방법은 쉽지만, 재부팅을 했을 때 작업한 내용들이 모두 사라집니다.

에뮬레이팅을 통한 빠른 시작

에뮬레이팅도 슈가를 사용해보는 또 다른 방법입니다. 설치하기는 좀 어렵지만, 작업한 내용들은 유지가 됩니다.

참고; 지금 당장은 탐탐의 소리를 사용할 수 없을 수도 있습니다. MitchellNCharity 13:16, 5 June 2007 (EDT)

개발자들을 위한 빠른 시작

에뮬레이팅을 이용하여 개발하는 방법은 소프트웨어 개발의 대안방법입니다.

가장 최근 이미지를 여기서 받으세십시오. (틴더박스에 링크 추가하기) 빠른 시작에 설명된대로 QEMU와 커널 가속기를 인스톨하시면 됩니다. 도움 및 팁에서 "Development" 부분을 참고하십시오

#XO-QEMU 부트 고장 - 현재 진행현황을 보십시오.

개요

OPLC 소프트웨어를 구동하는 한 가지 방법은 PC에서 에뮬레이터를 이용하는 것입니다. 프로그래밍 시작하기에서 기타 옵션들을 보십시오.

참고 카테고리:에뮬레이션 과 도움 및 팁.

단순한 작동을 하려면 라이브시디나 에뮬레이팅을 통한 빠른 시작을 사용할 수 있습니다.

개발을 한다면 라이브시디, qemu (빠른 시작과 마찬가지이지만, 다른 이미지를 사용) 사욜할 수 있고, 라이브시디보다는 개발자용 이미지을 사용할 수도 있습니다. 한 가지 대안이 되는 개발연구법은 슈가 설치를 해보는 것입니다. 비교를 하려면 프로그래밍 시작하기를 보십시오.

일반적인 개발연구법은 QEMU을 kqemu 가속과 함께 사용하는 것입니다. 기본내용을 확인하려면 빠른 시작을 보십시오

Though for development, we will use a different .img, one with a few extra utility programs. See OS images, including latest stable build.

Instead of qemu, you can run VMware, and there are additional options on a Mac.

Please report your experiences in User Feedback on Images. There is a Virtualization Common Room.

There are limitations with XO disk images.

The LATEST-STABLE-BUILD versus LATEST build distinction is mostly of interest to people running on actual XO's. In emulation, developers should usually use LATEST. And when STABLE is old, non-developers probably should too.

대안방법들의 비교

OLPC 노트북은 개조된 하드웨어로서, 레드헷 리눅스를 추려내어 슈가를 작동하게 만든 것입니다. 하지만 만약 진짜 OPCL 노트북을 가지고 있지 않다면 어떻게 해야할까요? 여기에 여러가지 방법으로 사용할 수 있는 옵션들이 있습니다

추천방법들

플랫폼	목적	추천방법
윈도우즈	개발	에뮬레이트된 XO 디스크 이미지; 혹은 에뮬레이트된 우분투와 슈가-jh빌드 (혹은 개발자용 CD나 라이브시디)?. (여러분들의 보고내용이 필요합니다.)
맥	개발	에뮬레이트된 XO 디스크 이미지; 혹은 에뮬레이트된 우분투와 슈가-jh빌드 (혹은 개발자용 CD나 라이브시디)?. (여러분들의 보고내용이 필요합니다.)
맥과 패래럴즈	개발	우분투 32비트 버젼을 설치하고, 우분투에 슈가얹기. 맥부분을 보십시오.
우분투-32비트	개발	슈가와 슈가-jh빌드 와 우분투 리눅스에 슈가얹기
32비트 리눅스	개발	슈가와 슈가-jh빌드
64비트 리눅스	개발	qemu 하(下)에서 XO 디스크 이미지나 업데이트된 라이브시디 (현재로서는 4월이 최근)

전 실제로는 윈도우즈/맥 개발자, 라이브시디의 개발 옵션을 믿지 않습니다. 아직까진 실질적으로 쓰였다는 이야기를 들어본 적이 없습니다.

I don't really believe the development option of Windows/Mac developer/live CD. I've not yet heard of it actually being used. They are months out of date (April). But Mcfletch said (in May) it's an option, so I added it. MitchellNCharity 09:19, 23 June 2007 (EDT)

사용환경

옵션	업데이트가됨	소리?	카메라?	라이브러리?	E토이즈?	읽기/쓰기?	개발 소프트웨어?	인터넷?	comments
Installing Sugar	continuous	yes	yes?	yes?	yes	yes	your own	yes	On some platforms, it takes time and space (hours and ~3GB), but "just works". On others, it is quite difficult to install.
슈가 설치하기-우분투 32비트(qemu, 패래럴즈, vmware에 가상설치로)
LiveCd	April	yes(boot) yes?(qemu)	yes?(boot) no(qemu)	no	yes	no	toolchain, Gnome	yes?	Alternative Quick Start. Can both be booted from, and used in qemu. Problems: A.
XO disk images:
LATEST-STABLE-BUILD http://olpc.download.redhat.com/olpc/streams/development/LATEST-STABLE-BUILD/
...development-ext3.img	~monthly	yes/B	no	yes	yes	yes	no	after config	Quick Start for getting a look at Sugar.
...development-devel_ext3.img	~monthly	yes/B	no	no	yes	yes	a little	after config
LATEST http://olpc.download.redhat.com/olpc/streams/development/LATEST/
...development-ext3.img	~daily	yes/B	no	yes	yes	yes	no	after config
...development-devel_ext3.img	~daily	yes/B	no	no	yes	yes	a little	after config	Good for new developers (requires some command-line comfort).
OTHER
FC6+Sugar	April	yes?	?	?	no	yes	Full Fedora Softare Dev.	yes	6GB (April version: no etoys)

Key:

library: A library of sample content is included (english version). Ie, pretty text to web browse without having to get network.

R/W (writable): With an .img, you can save things between sessions. With a .iso, your environment is the same each time you start.

development software: are development tools included?

Net (network): does the network "just work" or "manual" steps are required?

Problems:

A: LiveCd (April) on fc6 x86_64, kernel panics under kqemu. A squashfs problem.

B: Tam Tam is silent (though EToys makes noise). Cause unknown.

Notes:

• re "does sugar-jhbuild support camera/mic?": "yes, if the camera uses v4l2 and 640x480, I'd suspect so." Can someone confirm this? (#olpc, now) MitchellNCharity 00:16, 2 June 2007 (EDT)

Doables:

• Remove LiveCd's "?" above.
• Find out what's going on with Tam Tam sound. It would be nice for the xo disk images to all be sound-yes.
• Add a microphone column? Reconsolidate sound/camera/mic into a H/W column?

XO-QEMU boot broken - current workarounds

Build 445 was the last version which booted cleanly under qemu (ticket). More recent builds require workarounds. Build 485 resolved one problem.

• When booting on qemu, add root=/dev/hda to the grub kernel line. This needs to be done every time.
  1. When you start your xo disk image on qemu, you should see a blue grub screen, doing a "Booting .. in N seconds" countdown. Press space to interrupt it.
  2. Press e (edit). This will show you 3 lines.
  3. Move to the second, which begins "kernel". Press e. This will take you to the end of the kernel line.
  4. Add root=/dev/hda1 Then press enter.
  5. Press b to continue booting.

(This workaround avoids "WARNING: Cannot find root file system!", and being dropped into an emergency shell.)

Should add instructions to modify the image's grub config, so this doesn't need to be done every time you boot. MitchellNCharity 12:04, 3 July 2007 (EDT)

It might be worth gathering the currently scattered notes, into a single list of step by step instructions, for getting from nothing, to a pair of qemu images running with Xephyr's and ssh. MitchellNCharity 12:04, 3 July 2007 (EDT)

Example step-by-step instructions

Here, in one place, are assembled all the steps to get you to a working emulated XO. Assuming you are running on linux, and have already installed qemu and kqemu.

The following will not work on your virtual xo: sound, camera. The first because I haven't gotten around to figuring out why it isn't working. The second because qemu doesn't yet support them.

And when you boot your image a second time, network likely won't work. :( Something for another day. MitchellNCharity 16:49, 4 July 2007 (EDT)

Go to http://olpc.download.redhat.com/olpc/streams/development/LATEST/devel_ext3/ and obtain the numbered -devel_ext3.img.bz2 and its md5. For this example I used build 485. Though the network doesn't seem to work in 485. 482 works, but you have to work around a boot failure. [1]

md5sum -c olpc-redhat-stream-development-build-485-20070703_0249-devel_ext3.img.bz2.md5

bzcat olpc-redhat-stream-development-build-485-20070703_0249-devel_ext3.img.bz2 > xo-485a.img

The resulting file is 1 GB.

export PORT=2221
qemu-system-x86_64  -soundhw es1370 -serial `tty` -kernel-kqemu -redir tcp:$PORT::22 -hda xo-485a.img

Unless you have a x86_64 cpu, use qemu instead of qemu-system-x86_64.

The screen will very briefly be black, and then show the blue "GNU GRUB" screen. If it stays black, that's a qemu bug. Kill qemu and try again.

0. Press any key to interrupt the countdown to boot. Then,

1. Press e.
2. Press down-arrow to get the "kernel" line.
3. Press e. This takes you to the end of the kernel command line.
4. Type space and root=/dev/hda1
5. Press Enter.
6. Press b.

The boot messages will scroll by, and you should eventually see the normal XO first-time login. We'll save that for later.

In the window where you started qemu, you should now see a login: prompt.

1. Enter root
2. Then:

/etc/rc5.d/S98NetworkManager stop
mv /etc/rc3.d/S98NetworkManager /etc/rc3.d/DISABLED-S98NetworkManager
mv /etc/rc5.d/S98NetworkManager /etc/rc5.d/DISABLED-S98NetworkManager
echo ifup eth0 >> /etc/rc.local

mv /boot/grub/grub.conf /boot/grub/grub.conf.orig
awk '/kernel/ {print $O,"root=/dev/hda1";next} {print}' < /boot/grub/grub.conf.orig > /boot/grub/grub.conf
grub-install hd0

If grub-install hangs, just kill it. It may even have worked anyway.

ifup eth0 
killall X

Killing X should restart sugar.

If you want to enter a name with diacritics, you need to wait for X to restart, and then do:

su olpc -c"DISPLAY=:0 xmodmap -e 'keycode  77 = Multi_key'"

This sets up Num_lock as Multi_key. Unfortunately, the next time X is restarted, you will lose it. A better solution is needed.

At this point you could just proceed to use your new XO. However, the screen resolution is wrong (1024x768). So for development, or to get a more accurate feel for how things really look, some extra steps are required.

Once you reach the main sugar screen, you should check the Neighborhood view (F1). If you can't see other people, either the we are having problems with the presence server, you are behind an unusually picky firewall, or networking on qemu is broken again in the build number you are using. (Remember that ping doesn't work inside of qemu).

While this next step is not strictly required, it will enable you to use ssh and scp, which can be handy to move stuff back and forth between your host and xo.

Still as root on the xo,

1. Change the root password.

passwd

Don't worry if it says something like "BAD PASSWORD: ", and complains about the password you picked. It will still work.

2. Change the olpc password.

passwd olpc

Now you can use ssh and scp.

The current released version of QEMU doesn't support 1200x900, so we use a Xephyr remote X server. Each time you boot the xo, if you want 1200x900, you'll need to do these next steps again, except for the ones marked "(First time only)".

1. Still as root on the xo:

init 3
sleep 5
ifup eth0

su olpc
grep export /usr/bin/sugar > ~/env
source ~/env

If the ifup eth0 fails with an "already running" message, that's ok. Perhaps it is no longer needed.

2. Back on the host, prepare Xephyr (First time only)

mcookie > xephyr-cookie
export COOKIE=`cat xephyr-cookie`
rm -f xephyr-xauth; echo "add :1 . $COOKIE" | xauth -f xephyr-xauth
echo $COOKIE

3. On the xo, still as "su olpc", record the cookie: (First time only)

echo "add 10.0.2.2:1 . " PUT-THE-COOKIE-HERE | xauth

4. Back on the host, start a Xephyr:

Xephyr :1 -auth xephyr-xauth -reset -screen 1200x900x16 -dpi 200

You will probably want to do this in its own window, as it periodically dies and needs to be restarted.

5. On the xo, still as "su olpc", start sugar:

DISPLAY=10.0.2.2:1 sugar

Actually, I usually ssh in from the host, and run sugar that way:

a. On the host,

ssh -o NoHostAuthenticationForLocalhost=yes -p 2222 olpc@localhost

b. in the resulting shell,

source ~/env
export DISPLAY=10.0.2.2:1
sugar

You may also want to run

xmodmap -e 'keycode  77 = Multi_key'

to be able to enter diacritics with the Num_lock key. But I find doing it first thing tends to kill Xephyr. :(

You should now see the XO first-login screen in correct resolution. You can use Num_lock to enter diacritics. Congratulations. Sorry it was so much bother.

To run multiple xo's (to play with collaboration, for instance), you can repeat the above steps. Create a xo-485b.img, and use a different PORT number (like 2222). If you are using Xephyr, start a second Xephyr, which will be 10.0.2.2:2, use that instead of ...:1 in the instructions. You should now be able to see yourself, and collaborate in Write.

The following will save you having to periodically type your xo password, but is optional, and can just as easily be done later.

Back on the host,

1. Create an ssh key if you don't already have one. See /Help_and_tips#SSH into qemu, using a key.

2. Copy it to the xo,

scp -o NoHostAuthenticationForLocalhost=yes -P $PORT ~/.ssh/id_rsa.pub root@localhost:~/

3. On the xo, spread the key around:

mkdir ~root/.ssh
mkdir ~olpc/.ssh
cat id_rsa.pub >> ~root/.ssh/authorized_keys
cat id_rsa.pub >> ~olpc/.ssh/authorized_keys

You can now ssh and scp without retyping your password.