Talk:Using QEMU on Windows
 Works for 182, updated
I followed your fine instructions and got build 182 ext3-devel working fairly painlessly. Success/failure belongs on User Feedback on Images#QEMU on Windows. I took the liberty of updating instructions for latest builds and wikifying the text. -- Skierpage 19:21, 3 December 2006 (EST)
 Networking Issues in QEmu
If you are having trouble getting an internet connection inside QEmu see here.
Hey Tomhannen, great changes :), I think to talk with 2 qemu opened we shold use qemu with "network bridge", but I'm not sure if it's possible with OLPC images(from Brazil too). --[[User:|Darkmagus]]
I Googled the following link if you want to experiment, I have not had change to do so yet! Would be nice to get the module fro Ensoniq or Soundblaster sound for the OLPC images also to work!  It explains various methods, looks little elder, though (from 2004). The QEMU included documentation maybe also enough and at least fresh ( --Tonyv 10:41, 8 December 2006 (EST)
I finally managed to get networking to work properly on my system (qemu, olpc build214 and Windows XP). Here's a summary of what you have to do:
- Download and install openvpn from http://openvpn.net/
- Open Network connections, find the network adapter of type TAP-Win32 Adapter. By default it is named something like "Local Area connection 4": rename it to TAP
- select the real lan and the TAP you just renamed, right-click and create bridge. this effectively puts the tap device on the lan, so your virtual machine can get it's ip from your router, and your virtual machine is just like a real machine on your lan, or-
- Select your active network connection (Local Area Connection or Wireless Network Connection), select Properties, Advanced tab, turn on ICS and for "Home Networking Connection" select TAP. This bridges from TAP to the outside world and forces the TAP adapter to use the 192.168.0.x network, so be sure you aren't using that for anything else.
- Start qemu with the command line:
qemu -L . -hda olpc.img -net tap,ifname=TAP -net nic
- Use Ctrl-Alt-3 to get a command prompt. Login as root and run 'dhclient'. You should get an ip address allocated in the 192.168.0.x network with 192.168.0.1 as the gateway.
- Ctrl-Alt-1 to get back to sugar and now when you start the web browser you should get the Google homepage.
Duncanb 06:16, 7 January 2007 (EST)
We have found a good way to make two OLPC images see eachother (both running in qemu under windows XP). This site proposes running two different os images with one listening on a localhost socket, and the other connecting to it:
qemu -L . -hda olpc-image-1.img -net nic -net user -net socket,listen=localhost:1234 qemu -L . -hda olpc-image-2.img -net nic,macaddr=00:00:DE:AD:BE:EF -net socket,connect=localhost:1234
As you can see, it is necessary to change the default MAC address. We were able to see the two in the network cloud, but we were unable to share activities, only make friends. Might be because of different builds used.
- I tried this too and i am experiencing your same problem. Both the emulated machines are on the same computer (running Linux), but i also can only see the two users and make friends but not share activities. Both the emulated machines used the same build (395-ext3). Is there a way to set it up in a way so that it is possible to share activities?
 Sound issues in QEmu
I couldn't get sound working in TamTam, however the sound worked fine in eToys when viewing the tutorials. Making some test eToy projects with a frog croaking worked perfectly. For me the issue is TamTam+QEMU. I am using the latest build img from RedHats repo. (build392-20070501_1540) --timbobsteve 2 May 2007
 Build 206 problems
Everything appears except for the icons and "me". If you open the "frame" and randomly click around you may hit the shut down, abi, and all the other buttons. Weird. - anger2headshot
 Other criticisms
It doesn't work. I followed the instructions here and it gives you a login prompt. You can wait, and it will switch to graphics mode, and display a black X cursor on a black screen. Then it will display a cursor on a light grey screen. Then it will exit back to the login prompt without any sort of message as to why. If you wait again it will repeat the process.
I did get a variation of that once, but never again. The first attempt, returned to the login prompt, but then when it repeated the process it gave me a login dialog. I pressed OK (or Enter?) without typing anything in the field, and it dropped me back to the login prompt without a message. Since then it hasn't managed to show that dialog again.
So can we PLEASE get some bloody documentation for this thing????
So that a normal person can actually use it?
There was a bug (fixed in later builds) with the UI crashing when you try to login with an empty nickname, as you did. If you try again with a fresh image and give a username this time, it'll work.
Cjb 14:42, 10 November 2006 (EST)
Hi there... I wrote the Windows XP page, and it worked for me... Are you using the same image build number? Some of the images have less functionality than others.
--Tomhannen 20:43, 19 November 2006 (EST)
I had a similar problem, switched from build 385 to 387 and that fixed it. Also I had installed the kqumu accelerator but wasn't sure if I had started it so I added the "net start kqemu" command to the .bat file, right before the qemu.exe line.
 Resolution issues?
Have some issues with the emulated screen resolution. Somewhere (within the Etoys community) saw a reference to it and how to fix it - I'll try to hunt it down and put in the Troubleshooting section. What I'm baffled about is the TamTam screen... basically unusable.
- I know it's bad netiquette, but I'm answering myself and posting... a quick fix...
- Ok, according to an email from Bert Freudenberg on the Etoys mailing list:
Here's what you can do: Hold Ctrl+Alt+F1 to switch to a text console. Log in as user "root". Edit the file "/boot/grub/grub.conf". Replace "vga=0x311" with "vga=0x317". Reboot.
- I'll try to test it, rephrase (if it works fine) and add it to the troubleshooting section.--Xavi 19:12, 3 January 2007 (EST)
 Keyboard and Mouse
My keyboard and mouse do not work in the graphical environment, just as described on the Wiki page. But: I cannot resolve this by entering modprobe i8042. The system just reports
i8042.c: no controller found FATAL: Error inserting i8042 (/lib/modules/.../serio/i8042.ko): no such device
--Waldgeist 17:08, 4 January 2007 (EST)
- Oops! Can't say I know what's going on... but what image are you using? It worked fine for me, with olpc-redhat-stream-development-build-193-20061203_1714-ext3.img --Xavi 17:59, 4 January 2007 (EST)
 Accelerator Version
The latest version appears to be 11 I'm not sure it counts as stable hence comment here
 Another shortcut
I have to press Alt + Ctrl + Shift to return to the QEMU window. --18.104.22.168 12:04, 25 March 2007 (EDT)
 Combined qemu, kqemu, and startup script
Portable Qemu Persistent Ubuntu tutorial describes running Ubuntu on k/qemu "within Windows 98, NT, 2000, XP or Vista without ever rebooting". We use a raw disk image, rather than a live cd, so all the stuff about persistance can be ignored. So one just makes a directory, downloads and unpacks QKUB.exe, downloads an image, clicks on a launcher, and you are up and running.
We should have one of these. Perhaps just modify QKUB.exe (QKXO?) to included a launcher for OLPC? MitchellNCharity 14:52, 22 October 2007 (EDT)
 Article renamed - "XT" removed
I've renamed the page from "Using QEMU on Windows XT" to "Using QEMU on Windows". The article appears not to be specific to XT, and need not be. This required also renaming the /translations page. I left the translated pages unmoved, as they work as is, and it didn't seem worth moving them until it's clear the new title is stable. MitchellNCharity 15:17, 22 October 2007 (EDT)