Re: [Qemu-devel] Linux 2.6.10 ?
it's ok with me on a XP host and running linux 2.6.10 with either -kernel option (remember you need an -hda too) and inside an iso. It also works inside a -fda too. What is your exact cmd line ? Christian On 5/8/05, Der Herr Hofrat [EMAIL PROTECTED] wrote: Hi ! does anybody have a 2.6.X (preferably 2.6.10) running under qemu ? trying to launch it (passed with -kernel) fails - it simply gives me (qemu) thats it - the 2.6.10 is compiled as generic 686 and works fine on the box thx ! Nicholas Mc Guire e-mail: [EMAIL PROTECTED] OpenTech EDV-Research GmbH Embedded GNU/Linux/RTLinux Lichtenstein Str. 31 2130 Mistelbachweb :http://www.opentech.at/ phone :+43 2572 201082 fax :+43 2572 201084 news: 7th Real Time Linux Workshop, 2-4 Nov 2004, Lille France - details at http://www.realtimelinuxfoundation.org/events/events.html soon ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Linux 2.6.10 ?
for me it's working on a XP host with qemu 0.7.0. I can see the ouput errors on the serial console of qemu. Neat :) I just miss a initrd... I've been compiling 2.6.x guests since qemu 0.6.0, and the only pb I have are regarding stable framebuffer switching. It works on the host but not always inside qemu :( Christian On 5/8/05, Der Herr Hofrat [EMAIL PROTECTED] wrote: http://vserver.13thfloor.at/Stuff/QEMU/ just grabed the bzImage from your web-page and checked what it does - same behavior the only output is a single line: (qemu) I noticed that you had a number of patches in that directory and had mirrors of qemu up to 0.6.1 - I'm trying this with 0.6.2 - so did you have to apply any of those patches in there to get it to work with 0.6.1 ? thx ! ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Linux 2.6.10 ?
@Nicholas Just to make sure, I'll be sending you off-list a tiny 2.6.10 kernel with a minimalistic embedded initramfs. It's quite small (600k), just to check qemu is working fine. To use it, just do (tested with mingw/qemu-0.7.0): qemu-img create -f qcow hda.img 32M qemu -L . -hda hda.img -kernel tiny This kernel is self-sufficient, and only needs -kernel to boot. :) Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Old DOS under Qemu
On 5/12/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I've been trying to install various old versions of DOS under Window's v0.70 of qemu from FreeOSZoo. And since so few people appear to be using the Windows version, I've been making a point to do as much testing as I can, with as wide a variety of operating systems as I can find. From version 5 on up, I only have a few problems (Which I've already reported.) I want to come back on the last item. I have made images of my 15y old 720k floppies, and jumped back to 1991 this morning. - 3x720k for DOS5.0 - 7x720k for win3.00a - 7x720k for works2.0 all original, not warez. Cost a bunch back in 1991 :( I tried a few things: - install dos: ok - install win: ok - mouse: ok, no change of speed on qemu070/XPhost - floppies 720k: ok. The catch to format them is to either quick format them, not in high density. Inside win3.00a, it works like a breeze. win3.00a even recognise 18M of ram to play with. I've seen no problem whatsoever. Do you want my bins jeebs ? Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Old DOS under Qemu
I've seen no problem whatsoever. Do you want my bins jeebs ? Thanks for the offer, but I already own Dos 5 and Win300a (although admittedly the images I'm using came from a friend, since I no longer have a 5.25 floppy, and didn't make images of them back then.) euh... I only meant sharing my compiled version of qemu. Sorry it was interpreted wrongly. The offer still stands :) The rest of the explaination is clear. Too bad I don't have a mouse floppy driver anymore ??? Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] We want to example qemu and the accel-module in our distribution.
There are people out there already distributing kqemu, if I understand enough the following article. http://knoppix.guilinux.com/article.php?sid=1067 Did they get approval? Or are they just re-packaging qemu and asking the end-user to recompile kqemu module themselves ? -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Re: Old DOS under Qemu
On 5/13/05, Ronald [EMAIL PROTECTED] wrote: I'm already using the latest FreeOSZoo windows build. This doesn't mean that it perform like Christian's or Kazu's one, you can get a try. Actually I performed some comparisons yesterday using nbench on a qemu linux guest on winxp host, and in terms of speed, my version is as good, not better, than FreeOSZoo. What I don't understand is why qemu on XP host is performing better than qemu on linux host (without kqemu of course...). Qemu on xp is around 2 or 3x faster. Am I doing something wrong here ? Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] [PATCH] Embed QEmu screen on a custom window
I think Miguels patch is quite useful. It makes it possible to use native Windows controls and Windows API calls to display a nice GUI for Qemu, without adding much code to Qemu itself. Actually I've been working on something similar for XFree (with XEmbed) to embed Qemu into a GUI written with Perl and GTK :) (it partially works already, but focusing and mouse grabbing doesn't work quite well yet). Btw. I remember at least two people working on this XEmbed thing as well. IMHO adding a GUI built with SDL would be much more difficult than using native GUI toolkits. And doesn't the Cocoa patch aim at a native MacOsX GUI in the end? All of these are very useful patches indeed. But there's at least 4 gui toolkit available for SDL, which could ensure: - a single developpement and a uniform look - no need for a bigger space on screen (the controls could be like OSD) - independent of hw/os architecture (the original aim somehow of qemu?) I agree this is poking inside qemu itself, which can be considered a bad thing (tm). I'm looking at the 4 gui toolkits I mentionned. - http://www.paragui.org/ - http://guichan.sourceforge.net/ - http://agar.csoft.org/index.html.en - http://aedgui.sourceforge.net/ Let's open the discussion in a separate thread. Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] [PATCH] Embed QEmu screen on a custom window
ok, maybe this needs clarifications. I do not have a Mac, therefore anything related to cocoa is unknow to me. sorry :( Let's take an instance of i386-softmmu qemu, which has switched internally into a 1024x768 graphical mode. To have any gui toolkit AROUND it, the whole apps, inclusive of the window manager decoration, would need more than 1024x768 pixels. When going full screen, as if the qemu machine was the host, we should see 1024x768 pixels only on the screen. The gui toolkit would not be drawn, therefore useless unless you switch back to non-fullscreen. Having the gui toolkit around the instance is ok, provided your native screen resolution is big enough. But if it's not, you'll need scrollbars, or reduce the internal graphical mode. Let's take another concrete example. I have on my desktop a PC with XP and a LCD 15 inches which support at most 1024x768. When I launch a qemu instance and the internal softmmu graphical mode is 800x600, how much space is left on screen, considering the taskbar at the botton and the qemu titlebar ? 100 pixels in height and 200 pixels in x. Not much to integrate a gtk2 toolbars and a menu, right ? Actually, it will be just nice. only for 800x600 qemu graphic mode. My point is: what it the controls could be drawn inside the qemu graphic windows, like an On-Screen-Display. You would call a menu, overlapping the current session, and you could select the controls you want to change (mostly fda and cdrom, or load/save vm). The advantage of this being inside the main graphic window is that even inside a full-screen mode, we could access it. But I understand Fabrice's point. After all, this is his baby. :) Christian On 5/27/05, Pierre d'Herbemont [EMAIL PROTECTED] wrote: On 26 mai 05, at 23:07, Christian MICHON wrote: I do not know what cocoa.m implementation is, but I've seen screenshots. cocoa.m is just a qemu video driver which uses natives Mac OS X UI Libraries. It does require space, and if you go full-screen, you can't do modifications. I am not sure that you speak about the cocoa driver. The cocoa video driver is lighter than the SDL one, since it doesn't require the SDL dependencies. And I don't get the full-screen point: cocoa.m still need much work, and that is why it doesn't support fullscreen (yet). (BTW Mike has been doing some great improvements which will be hopefully soon committed in the head cvs repository.) Hence the suggestion to go full SDL. Fabrice would like to see the native GTK, or Win32 qemu video coded. Because then a decent UI could be added to qemu. The front ends will always be limited, and the previous hack seems a bit crazy, and nearly nasty: you can do that directly via a video driver for qemu, and moreover it will let you far more control over qemu. Pierre. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Hand written code generator #2
Arm is still the only target that really takes advantage of any of the new functionality. Sorry I missed this line :( I hope you will still consider x86 target before x86-64. You'd get a broader audience for testing/debug. If so, let us know. I haven't switched to svn yet... Thanks anyway Christian On 6/2/05, Paul Brook [EMAIL PROTECTED] wrote: I also said that the arm-user emulation was the only target that had been converted enough to benefit from the new code. The optimization passes only work on the new qops. Existing dyngen based ops are not touched. On rereading the results I did the math wrong, I actually got a 15% speedup (2.3 vs. 2.0), but everything else still holds. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Looking for an easy way to exchange data bidirectional between host and guest (including some suggestion)
all these discussions around tftp looked nice and sweet. So I told myself, instead of using winimage (shareware), why not transferring files live. Yet, when you try on a windows host to exchange files with a linux guest (inside qemu and with -tftp option), all you get is: Error code 2: Access violation is -tftp today working only on linux hosts ? I also read somewhere the transfer is limited to files lesser than 64k. Can anyone confirm? Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Looking for an easy way to exchange data bidirectional between host and guest (including some suggestion)
I used 3 ways, either valid with msys or dos shell. all fail :( I can ping 10.0.2.2 perfectly, I even tried as administrator inside a dos prompt. the file I'm trying to get inside the guest is barely 58 bytes long Anyone ever got tftp to work inside a XP host ? Christian Error code 2: Access violation Did you specify the correct path? The full path on the host has to be specified, exacly as given to qemu. In addition only UNIX style paths is supported. is -tftp today working only on linux hosts? From what I can tell it should work on all hosts, but there is some security issues on Windows and the path name support is not that good for Windows either.. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Looking for an easy way to exchange data bidirectional between host and guest (including some suggestion)
I made some progress based on your suggestions :) I don't have any to test on, but the code is extremely simple and not OS dependeng in any manner except the small detail that UNIX style paths must be used. Where is the file on the host? c:\q\w What tftp argument did you gave to qemu when you started it? -tftp /q inside a msdos prompt = it's correct according to docs What path did you try to retreive from the guest? this is the location of my mistake: I did get w instead of get /q/w now it works in get mode only. Is there anywhere a patch to get rw access to tftp, as well as upping the limit of 32M ? I indeed got a transfer timeout after 33553920 bytes :( Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] qemu 0.7.0 does not compile with binutils 2.16
0.7.0 compiles fine on mingw with custom compiled gcc-3.3.6 and binutils-2.16. This is on windows host. Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Looking for an easy way to exchange data bidirectional between host and guest (including some suggestion)
how do i do this? from the windows host or from the linux guest? any special sw to install/setup? I tried to use a tftp server on the windows host. It's functional, but the linux guest cannot reach it. I suspect the tftp over slirp may interfere here. Christian On 6/14/05, John R. Hogerhuis [EMAIL PROTECTED] wrote: any idea? Christian Suggest some packet sniffs to see who is getting stuck. -- John. -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Build environment image
you would probably need to setup cross compilers at least, find a global linux config file generic enough (ex: no framebuffer), and at least a initrd with minimum bins (static busybox would be best). This also implies you've a lot of time free :) if you want to do it for many architectures/targets. I'm trying to build one on x86, but to gather the patches and generic features I want (I want as small as possible) is consuming much time already. Christian On 6/24/05, Tim Walker [EMAIL PROTECTED] wrote: Is this a bad idea for some reason, or is it just unnecessary? Some feedback would be appreciated. Cheers, Tim Tim Walker wrote: How difficult would it be to create a (presumably Linux) uniform build environment for all targets as a bootable Qemu image? ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Build environment image
BTW, one problem with WIndows is that QEMU developers do not have access to Windows licenses. Might be nice for non-programmers who want to contribute to donate old licensed copies of Windows for testing work. untrue. http://www.microsoft.com/windowsserver2003/evaluation/trial/default.mspx that would give 6 months to complete development... Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] interesting tftp experiments
Hi, since I was able on a windows host to connect (but no transfer) on a ftp server over slirp, I thought I could do the same: over slirp, connect to a true tftp server, not the layer provided in slirp/tftp.c In order to do so, I had to do minor patches to v0.7.0 - remove reference to tftp in vl.c - remove reference to tftp in slirp/udp.c - remove tftp.o linkage By doing so, I have a ~true~ tftp-over-slirp qemu. I tried it and yes I can READ WRITE to a small tftp server I found for windows host (http://tftpd32.jounin.net). I still have some problems though. When the read or write command is sent, it apparently somehow jams the slirp channel. The read or write happens, but not immediately (around 2 sec delay). The bad news is that so far, I've manage per session of qemu either one write, or one read. If someone has the knowledge of what could be wrong in this part of slirp, please correct the flaws of what I just found out. At least, we should be able to transfer back and forth files lesser than 32M. -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] interesting tftp experiments
Probably your problem is a port problem. this was a possibility You have to options: - If connecting on PORT mode in your FTP client, port 20 should be redirected to your QEmu session through the -redir option. interesting, never heard of it. Makes sense. - If you use passive mode on your FTP client (PASV) you don't need to redirect any ports to QEmu, because in passive mode, the server is the one that opens the port for data communication. I already tried that, no success. I'm using an small FTP server for Windows (SlimFTPd, http://www.whitsoftdev.com/slimftpd/). It has an Apache like config file, and total size is 51 Kb. It supports both PORT and PASV mode. we've a winner here! this ftpd for windows host is working fine. I don't even need to redirect the port. Thanks alot :)) Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] LGPL'd VGABIOS version 0.5c released
ok, added to my bookmarks :) I tried it directly: works fine with framebuffer on linux guests. Christian On 7/7/05, Volker Ruppert [EMAIL PROTECTED] wrote: Hi, where do we download it from ? I tried to google but it all brings me back to bochs. And it's an old version. Oops, I forgot to add the download link: http://savannah.nongnu.org/download/vgabios/ -- Bye Volker -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] problem with loop device
is loop device support compiled in the kernel ? On 7/12/05, Matt Lawrence [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote on 07/12/2005 11:19:01 AM: On Tuesday 12 July 2005 16:13, Matt Lawrence wrote: I'm running on CentOS4 with a 2.6.11 kernel. After using losetup to configure loop0 and mounting /dev/loop0, I am unable to unmount it. I keep getting device is busy message, but lsof doesn't show anything. Everything is being built automatically by a script, so I know I'm not leaving a terminal session using it as a working directory. Any ideas? Use fuser -m to figure out what's still using the mount. Make sure you don't have any other filesystems mounted inside it. Nothing shows up as still using the mount. Any other ideas? -- Matt ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Can you commit the pcnet patch ?
anyway, this patch as it is fails on v0.7.0 needs re-alignment badly... if you've an updated patch, could you post it, please ? Thx Christian On 7/20/05, Ludovic Drolez [EMAIL PROTECTED] wrote: Paul Brook wrote: A reference URL would be handy. I assume you mean: http://dad-answers.com/qemu/patches/AMD-PCNET-II/qemu-pcnet.patch6.gz Yes, this one ! -- Ludovic DROLEZ ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Can you commit the pcnet patch ?
Yes, this one ! I think I understand now why it's not in the mainline yet. This is only for linux hosts. I doesn't compile (yet :) ) on Windows hosts. I already tapped into the patch to see if I can make it work on Windows. Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Can you commit the pcnet patch ?
When I try to replace bcmp (inexistant in mingw32) with memcmp
inside pcnet.h, like this:
int result = (!CSR_DRCVPA(s)) !bcmp(hdr-ether_dhost, padr, 6);
into
int result = (!CSR_DRCVPA(s)) !bcmp(hdr-ether_dhost, padr, 6);
I get the following error:
In file included from C:/dev/msys/1.0/home/xian/qemu-0.7.0/hw/pcnet.c:64:
C:/dev/msys/1.0/home/xian/qemu-0.7.0/hw/pcnet.h: In function `padr_match':
C:/dev/msys/1.0/home/xian/qemu-0.7.0/hw/pcnet.h:531: error:
dereferencing pointer to incomplete type
anyone having a fix. I'm quite puzzled by the gcc error message.
Thx
Christian
=
static inline int padr_match(PCNetState *s, const uint8_t *buf, int size)
{
struct ether_header *hdr = (void *)buf;
uint8_t padr[6] = {
s-csr[12] 0xff, s-csr[12] 8,
s-csr[13] 0xff, s-csr[13] 8,
s-csr[14] 0xff, s-csr[14] 8
};
int result = (!CSR_DRCVPA(s)) !memcmp(hdr-ether_dhost, padr, 6);
for better understanding of the faulty piece of code
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Can you commit the pcnet patch ?
Hi Filip, On 7/20/05, Filip Navara wrote: Hmm, I used it on Windows some time ago... did it work ? I manage to update and compile the patch for qemu 0.7.0 and windows host (see attached file). I added some #ifdef and followed Paul's hint of yesterday (thx Paul :) ). It compiles fine, but all my clients crash whenever the tcp/ip layer gets loaded. I tried on linux slaxpro.iso, win95b and win2003/sp1 eval. Any uber-hacker on windows who could get this to work, pls ? Thanks in advance. Christian qemu-pcnet.patch7.gz Description: GNU Zip compressed data ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Can you commit the pcnet patch ?
On 7/21/05, Filip Navara wrote: Ok, I lost the compilation patch ... but the other one is here: www.volny.cz/xnavara/pcnet.c.diff the qemu instance still crashes. I'm using plain http://ftp.sh.cvut.cz/MIRRORS/slax/SLAX-5.0.x/special-editions/slax-frodo-5.0.6.iso for testing. As soon as hotplug and RPC starts, the qemu dies. First time I see such a crash in a *long* time, but I guess it's my fault too :) -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] pcnet/mingw32 debug info (help needed)
Apparently, the crash I'm getting is from the tcp/ip layer inside mingw libs (without debug info). libws2 to be more accurate. (Maybe it's a slirp/pcnet incompatibility ?) here's the output of gdb. If anyone can make something from it, thanks in advance. Pls note I also did a comparison on the preprocessed output of pcnet.c between linux hosts and windows host, and htonl calls was the only difference (I realigned it, but it fails the same way). == $ gdb qemu.exe GNU gdb 5.2.1 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i686-pc-mingw32... (gdb) set args -L . -cdrom slaxpro.iso -nic-pcnet (gdb) run Starting program: qemu.exe -L . -cdrom slaxpro.iso -nic-pcnet Program received signal SIGSEGV, Segmentation fault. 0x77fa5575 in _libws2_32_a_iname () (gdb) where #0 0x77fa5575 in _libws2_32_a_iname () #1 0x in ?? () == -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QEMU release 0.7.1
On 7/26/05, Mike Tremoulet wrote: Outstanding work! I've been a fan of QEMU as a free emulator for some time. The changelog mentions that the KQEMU accelerator is now available as a preliminary executable for Windows. I've not been able to find a link to that version anywhere. Should I pull down the sources and compile on my Linux machine, or is there a pre-compiled version about? How could I miss this from the Changelog. Shame on me :) The kqemu 0.7.1 download link is on qemu homepage. I did not manage to compile a newer kqemu.sys, so I used the binary inside the archive directly. It works and **rocks**. The ravi-demo (winosi) shows inside win2k3 guest a 10x improvement in refresh rate (2.56fps vs ~29fps). Inside a linux guest, linux 2.6.10 compilation takes now 4 minutes. Used to be more than 20 minutes without kqemu. So apparently kqemu on windows host now works. Bravo Fabrice. Cool achievement :) Thanks again. Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Problem installing WIndows
1) have you tried using qemu-img instead of dd ? (I usually use the qcow format for windows guests. 2G should be ok. qemu-img create -f qcow hd.img 2G ) 2) you do not mention bios path, memory of vm and boot sequence. I suggest you add at least the -boot d. By default, 128M will be used for the vm (sufficient for XP). Make sure your debian box has plenty of RAM (512M is good). 3) is your qemu optimized? and which version of gcc is used? Christian On 7/27/05, Antony Gelberg [EMAIL PROTECTED] wrote: Antony Gelberg wrote: Hetz Ben Hamo wrote: Do nothing. Just wait. It takes a LONG time. (shorter if you use kqemu)... Ok, one day later, it's still doing nothing, still using no CPU, can somebody now help me to debug this? Antony ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] qemu and xwindows
have a look at your mailbox :) Christian On 7/26/05, lance windham [EMAIL PROTECTED] wrote: My version of Qemu is 0.7.0 is there anyway I could get your compile 0.7.1 from you please? the binary? When I try to use my mouse it grabs screen then i can't do anything in xwin even when i hit ctrl-alt to ungrab screen... hrmmm.. BTW Only version of qemu for windows i could find was 0.7.0 Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Problem installing WIndows
On 7/27/05, Antony Gelberg wrote: I mentioned the command line in my original post to the thread. qemu -boot c -cdrom /dev/cdrom -hda hd.img sorry. I'm used to add it at the end of the cmd line :) 3) is your qemu optimized? and which version of gcc is used? I have had a look in the Debian config. The only non-standard configure option is --enable-slirp. Debian compiles qemu with -Wall -O2 -g -fno-strict-aliasing. Not sure what gcc was used, but probably 3.3. just to make sure it's not 3.4.x or 4.x.x :) one last question: it's an OEM version or a std version (like upgrade or full install) ? I expect OEM versions not to work (qemu hardware may not be aligned with the particular OEM version you have, in which case I'd expect an error 7b sooner or later, or a hang...) Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] KQEMU on Win32 (+patch)
found out why :) On 7/28/05, 姚春林 wrote: (...) debian + gnome 2.1 gnome is slow . and vmware with 256mem is more faster then qemu. answer is: gnome usage. Bad idea, which ever is your emulator. Try to go for lighter window manager environment, like fluxbox. Try also to boot in framebuffer mode, in 800x600x16bpp. I noticed this mode is quite fast :) I think there are some patches to try to improve the cirrus emulated. But I haven't seen any updated for a long time. Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: Cirrus Emulation (was: [Qemu-devel] KQEMU on Win32 (+patch))
http://cyberkinetica.homeunix.net/qemu/cirrus_vga.patch.gz I found back the patch I mentionned. It's not in v0.7.1, but I do not know its effects yet on cirrus speed. It's tagged on Antony's page as: Attempt to speed up Cirrus VGA Christian On 7/28/05, Hetz Ben Hamo wrote: Hmm, Anyone has patches for Cirrus Logic emulation that hasn't been applied yet? If so, could someone send them over please? Thanks, Hetz ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: Cirrus Emulation (was: [Qemu-devel] KQEMU on Win32 (+patch))
On 7/28/05, Christian MICHON wrote: http://cyberkinetica.homeunix.net/qemu/cirrus_vga.patch.gz It's tagged on Antony's page as: Attempt to speed up Cirrus VGA I tried it yesterday with proper graphical benchmarks (win95 guest). Some rendering is wrong on fonts (especially letter W uppercase) and there's no speed improvement actually. :( Any other patch or alternative card under dev ? Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Network Performance between Win Host and Linux Guest
winimage. There's also the possibility to mount the img as a volume. But there's a catch: both qemu and winimage want the exclusivity of the image file. :( On 8/26/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, QEMU is working better from hour to hour :-) Now I am looking for a way to get my data from the linux client to the Win2K host. When I use the integrated smb I get a transfer rate from about 15 KB :-( the tftp is about 600 KBps and using WinSCP over the redired ssh connection lead to 60 KBps. Is there a way to transfer the data faster ? Or is there an explorer for the disk image available ? Thanks in advance Helmut ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Re: QEMU 0.7.2
QEMU version 0.7.2 is now available. Just to report something I noticed on both 0.7.1/0.7.2 on winXP hosts: qemu-img doesn't convert into compressed images anymore. qemu-img-0.7.0 is still working fine. qemu-img.exe convert -c -f qcow hda -O qcow hdz gives: qemu-img: Compression not supported for this file format Once I convert into compressed qcow/img, 0.7.2 is still able to open and use the image. Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] Re: Trying to emulate an openmosix cluster
I managed doing this simulation using Parallels Workstation (I'm not trying to spam the list here...). It worked flawlessly, using bridged networking on a dedicated TAP-like network device... My point is the following: today 2 qemu guests with dedicated macaddr cannot share the same TAP-win32 v8 adapter. The software I mentionned above doesn't have similar limitation. Would it be feasible to change the current tap/win32 patch to overcome qemu's current limitation, and where to start ? Christian On 9/22/05, Christian MICHON [EMAIL PROTECTED] wrote: (...) Guests are openmosix linux nodes done by: http://www.purehacking.com/chaos/iso/chaos-1.6.iso (...) ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] [patch] non-blocking disk IO
I managed to make it work (qemu+non blocking IO on windows host),
with a rough estimation of 10% speed increase at the early stage of
windows setup. I expect more once windows installs itself in true
multitasking mode. :)
What you need to do is:
- download pthreads-w32-2-6-0-release.tar.gz and compile it from scratch
(make clean GC)
- you also need to add the following lines inside block.c (usleep is not
present in win32/mingw32)
#ifdef WIN32
void usleep(unsigned long usec)
{
Sleep(usec/1000);
}
#endif
- you need to update the link to include -lpthreadGC2 -lz, and
keep a copy of the pthreadGC2.dll where qemu.exe will be
(to pu it just in from of -lz is just my personal suggestion)
HIH,
Christian
On 10/3/05, Elefterios Stamatogiannakis [EMAIL PROTECTED] wrote:
With which pthreads library have you compiled it under windows?
I've tried it with the one here:
ftp://sources.redhat.com/pub/pthreads-win32/
but it didn't compile.
teris.
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] tun/tap networking: patch for existing tun
no vde for windows hosts :( On 10/3/05, Jean-Christian de Rivaz [EMAIL PROTECTED] wrote: Christian MICHON a écrit : to do so, does that mean we would need to launch a 1st qemu instance which would contain the dhcp server, and next qemu instances would connect to it ? if so, 'qemu -server' and 'qemu -client -connect_to server' could be useful... As I understand and with what I know, you can do that now using a virtual network (VDE for example). What matter is that fact that two qemu instances are connected on the same network. DHCP protocol (like any others netowrk protocol) is over that network and is not visible to qemu. To do what you wants, you have to use to different operating system image, one that contains a DHCP server, and the second that contain a DHCP client. 1) create a virtual switch: vde_switch -s /tmp/my_switch.ctl 2) start a virtual server: vdeq -s /tmp/my_switch.ctl qemu-softmmu -hda dhcp-server.bin [...] 3) start a virtual client: vdeq -s /tmp/my_switch.ctl qemu-softmmu -hda dhcp-client.bin [...] -- Jean-Christian de Rivaz ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] [patch] non-blocking disk IO
I did not manage a static link on win32 yesterday. I needed the pthread dll in the same directory as qemu.exe. I'll look more into it. On 10/4/05, John Coiner [EMAIL PROTECTED] wrote: Suppose that on Windows, we tell people to unpack the pthread distribution within the qemu tree. Qemu's configure script could find it, build a static pthread library, and link that into Qemu. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] about DHCP server in qemu
do you happen to have vde for win32 ? If yes, please point it to me, because I've googled for one with no luck... :) On 10/3/05, Henrik Nordstrom [EMAIL PROTECTED] wrote: On Mon, 3 Oct 2005, Christian MICHON wrote: I think you meant guests instead of hosts. I second that. I would still like to use qemu to perform network simulations myself... This is done very nicely by VDE. Regards Henrik -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] [patch] non-blocking disk IO
Then all is good and I should not use (2) as a benchmark. Thanks for clarifying :) On 10/4/05, John Coiner [EMAIL PROTECTED] wrote: (1) is a parallel task -- 'tar' and 'bunzip2' run concurrently. You see a benefit here when one process can use the CPU while the other is blocked waiting for IO. (2) is a serial task. It can't benefit from non-blocking IO. 'make -j 2' should benefit, in cases where the host file cache is cold. -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Windows Server 2003 SP1 problems already adressed?
it was working fine for me, both with 0.7.1/0.7.2 You need to make sure you install the right nic-driver :) On 11/18/05, Adrian Kiess wrote: Hello everyone, I was just wondering if the problems running Windows Server 2003 with applied SP1 inside qemu are already located/fixed? As of currently I am using qemu 0.7.2, and the problems previously reported ( as seen here: http://lists.gnu.org/archive/html/qemu-devel/2005-04/msg00188.html ) still persist (Windows Update, MSN Messenger and Windows Media Player are freezing the system/session). Sincerely, Adrian -- ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Windows Server 2003 SP1 problems already adressed?
if I recall well, 2003sp1 would not detect the nic properly. I had to google for a driver. if your installation detects the nic driver, don't bother about my previous post. I guess I need to try again sooner or later myself too :) On 11/20/05, Adrian Kiess [EMAIL PROTECTED] wrote: Hello, whats the problem with the NIC driver? It is the same as before I applied SP1 to the Windows 2003 Server installation; at least I guess. And it worked fine then. Adrian On Fri, Nov 18, 2005 at 08:59:18AM +0100, Christian MICHON wrote: it was working fine for me, both with 0.7.1/0.7.2 You need to make sure you install the right nic-driver :) On 11/18/05, Adrian Kiess wrote: Hello everyone, I was just wondering if the problems running Windows Server 2003 with applied SP1 inside qemu are already located/fixed? As of currently I am using qemu 0.7.2, and the problems previously reported ( as seen here: http://lists.gnu.org/archive/html/qemu-devel/2005-04/msg00188.html ) still persist (Windows Update, MSN Messenger and Windows Media Player are freezing the system/session). Sincerely, Adrian -- ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] where can I find winCE binaries of qemu ?
Hi list, Happy new year! I remember seeing some time ago a post saying a port of qemu on winCE was under development. This could be useful on my ipaq :) Is there a place where to download this ? or do I need to use pocketgcc to compile it myself ? One interesting bit would be to figure out how the original poster managed SDL/winCE compilation. If anyone has some info on this, thanks to let me know. -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] -kernel-kqemu
On 2/9/06, Jim C. Brown wrote: This sounds like an interesting option. Qemu has moved one step closer to VMware... It hangs my XP host with 100% cpu eaten up, no way to stop qemu, or kqemu. I have to reboot, and my linux clients freezes very early Src=CVS (yesterday 09/02/2006) Host=XP+mingw32 Guest=slax frodo 5.0.6 bootcd (no hdd image) Kqemu=kqemu-1.3.0pre3 (directly copied .sys into \windows\system32\drivers) Has this new option been tested only on linux hosts ? Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] kqemu version 1.3.0pre5
I tried various guests today on winXP host. * No crash and good speed for std kqemu (no kernel-kqemu) * Crash of winXP host systematically on all guests (linux + ms) It's hard to debug what is the problem. The only thing I have the time to see is a BSOD (blue screen of d**th) and the error message, informative ? TRAP_CAUSE_UNKNOWN Good job overall :) Kudos to the developpers. Maybe we can make it a bartpe plugin one day, automatically started with kqemu on ? That would be nice to promote qemu virtualization features... On 3/27/06, Fabrice Bellard [EMAIL PROTECTED] wrote: Hi, I just released a new version of kqemu which fixes some recently discovered issues. The fixes are the following: - Workaround for full virtualization on Windows host (more tests needed). -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Custom floppy image not booting, hanging at ramdisk...
just send your kernel .config for cross verification :) On 4/25/06, Damien Mascord [EMAIL PROTECTED] wrote: Hi again, Sorry to top post, just wanted to know if anyone has had similar experiences to this? If not, can someone help me debug the issue (bug?) with qemu here? ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Custom floppy image not booting, hanging at ramdisk...
none taken :) it's just that myself last year I created small kernels which sometimes would freeze too at the expansion step, but then it was a kernel config issue. I'll look at the patch though :) On 4/26/06, Damien Mascord [EMAIL PROTECTED] wrote: Given that it works with this patch, I can't see how it could be a kernel config issue, no offence intended :) ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] vnc patch
did I understand well ? 1) there's a rework of the original vnc patch 2) there are no problems of sync using the usb tablet what is this usb tablet stuff? do I really need a usb tablet connected to the host or this is yet another emulated hardware inside the qem guest ? If this is the case, it means the client OS must have the proper drivers, etc... I'm a bit lost. Christian On 4/29/06, Anthony Liguori [EMAIL PROTECTED] wrote: Lonnie Mendez wrote: Lonnie Mendez wrote: There is another vnc patch by Anthony Liguori (same person involved with the tablet along with others). From what I've heard it will reduce the bandwidth usage greatly. Also, afaik this is still under development. The source was posted on the irc channel a few days ago: http://www.cs.utexas.edu/users/aliguori/vnc.diff The mercurial tree is located at http://hg.codemonkey.ws/qemu-vnc If you go to Manifest - Changeset you can download a static tarball if you're unfamiliar with mercurial. It's in a pretty good state now. I don't think there's any significant bugs and all the features I plan on implementing for the first rev are there. I'll have a patch ready for submission in a day or so. Regards, Anthony Liguori ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] qemu vl.c vnc.c qemu_socket.h
ah! now it is working on winXP too. :) (you only forgot ssize_t should be long instead for mingw32) I see the old mouse sync problem is still here too... On 5/1/06, Fabrice Bellard [EMAIL PROTECTED] wrote: CVSROOT:/sources/qemu Module name:qemu Branch: Changes by: Fabrice Bellard [EMAIL PROTECTED] 06/04/30 22:53:25 Modified files: . : vl.c vnc.c Added files: . : qemu_socket.h Log message: win32 socket fixes CVSWeb URLs: http://cvs.savannah.gnu.org/viewcvs/qemu/qemu/vl.c.diff?tr1=1.179tr2=1.180r1=textr2=text http://cvs.savannah.gnu.org/viewcvs/qemu/qemu/vnc.c.diff?tr1=1.1tr2=1.2r1=textr2=text http://cvs.savannah.gnu.org/viewcvs/qemu/qemu/qemu_socket.h?rev=1.1 ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] [PATCH] VNC display support for QEMU
neat! it is working on windows 3.0 guest (no acceleration) on a winXP host. Fabrice fixed it live while I was trying it (he's fast!). old mouse sync problem is still here, as you mentionned no calibration is done. You mention absolute mouse. how to do it ? On 5/1/06, Christian MICHON [EMAIL PROTECTED] wrote: just a quick note: your patch breaks the mingw32 build on winXP. Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QEMU 0.8.1
mingw32 build breaks on ssize_t which should be long instead on win32 (see previous post on vnc.c). beyond this little detail, compiled version works fine on win32 (I'll do more testing tomorrow). do we need kqemu-1.3.0pre6.tar.gz for this version or a newer kqemu ? On 5/3/06, Fabrice Bellard [EMAIL PROTECTED] wrote: Hi, QEMU version 0.8.1 is available at http://bellard.org/qemu/download.html. version 0.8.1: - USB tablet support (Brad Campbell, Anthony Liguori) - win32 host serial support (Kazu) - PC speaker support (Joachim Henke) - IDE LBA48 support (Jens Axboe) - SSE3 support - Solaris port (Ben Taylor) - Preliminary SH4 target (Samuel Tardieu) - VNC server (Anthony Liguori) - slirp fixes (Ed Swierk et al.) - USB fixes - ARM Versatile Platform Baseboard emulation (Paul Brook) Fabrice. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QEMU 0.8.1
seen on winXP host (kqemu independent): sometimes the pointer inside the guest hits like an invisible wall and cannot go any further. This happens on a win2003 bartpe based guest and on a RedHat 7.2 livecd (superrescue 2.1.2). how to see it: - boot the guest without having the physical pointer grabbed - the guest pointer is centered (position A) - move the physical/host pointer halfway between guest pointer and the bottom of the windows of the guest (position B) - click inside the guest (grabs the physical pointer: we're in position A) - move the pointer vertically slowly down, the pointer cannot go any lower than position B I would say this could be a grab/ungrab issue induced recently (vnc patch?). To check it, how do I remove the vnc patch alltogether ? Christian On 5/3/06, Fabrice Bellard [EMAIL PROTECTED] wrote: Hi, QEMU version 0.8.1 is available at http://bellard.org/qemu/download.html. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QEMU 0.8.1
I removed manually vnc_display_init, and this is not the culprit... I'll check anyway versus qemu-0.8.0... On 5/4/06, Christian MICHON [EMAIL PROTECTED] wrote: I would say this could be a grab/ungrab issue induced recently (vnc patch?). To check it, how do I remove the vnc patch alltogether ? ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QEMU 0.8.1
qemu 0.8.0 does not show this invisible barrier issue. if this is worth anything, I use SDL 1.2.9. If someone can reproduce the issue also on linux hosts, there could be a lead. On 5/4/06, Christian MICHON [EMAIL PROTECTED] wrote: I removed manually vnc_display_init, and this is not the culprit... I'll check anyway versus qemu-0.8.0... -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QEMU 0.8.1
yes, but this is a painful way to recalibrate. Apparently, there's a confusion inside absolute coord and relative coord between guest and host. Turning off acceleration is not helping at all. Unfortunately On 5/4/06, Chris Bagwell [EMAIL PROTECTED] wrote: I've seen this for a few weeks in CVS as well on win98 guest. There seems to be a work around. If you roll your mouse around a lot and far distances, it seems to recalibrate itself or something and the invisible wall goes away. During the emails on the usb tablet development, I saw a few comments about having mouse acceleration turned on in windows could cause mouse confusion. I haven't bothered trying to turn that off but that may also fix it. Chris ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QEMU 0.8.1
it works. Side effect: after the first ungrab, I can't see the host pointer over the SDL windows. Yet, it's nothing as compared to the invisible wall. I know nothing about most qemu internals, but would it be possible to make it like vmw*re, ie the mouse is automagically grabbed/ungrabbed whenever you reach the limits of the SDL window ? On 5/5/06, Anthony Liguori [EMAIL PROTECTED] wrote: Thomas Han wrote: Hi, For what it's worth. I have also seen this invisible wall problem with my mouse for a few weeks off the CVS build too. Can you try out the following patch. *grumbles about SDL's brokenness* Regards, Anthony Liguori -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] sleep segfaults on qemu-0.8.1/kqemu-1.3.0pre6
Host: winXP pro Guest: Redhat 7.2 when kqemu (user mode) is active, sleep 1 segfaults each time. With kqemu disabled, no problem -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QEMU 0.8.1
on windows 3.0 (my usual testcase) ? I'll try at least on rh72... On 5/5/06, Anthony Liguori [EMAIL PROTECTED] wrote: As someone has already mentioned, you want to use -usb -usbdevice tablet. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QEMU 0.8.1
well, at least inside rh72, I can see a usb device: Vendor=0627 ProdID=0001 Product=QEMU USB Tablet all I need now is: 1) which module to modprobe 2) which /dev/input/event... is used 3) modify XF86config accordingly and then theoretically it should work... anyone can help me please on rh72 + usb tablet ? Thanks On 5/5/06, Anthony Liguori [EMAIL PROTECTED] wrote: Oh, I doubt that Windows 3.0 has USB support. I also doubt that VMware wrote a driver for it :-) You probably won't have much like with RH7.2 either. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Re: sleep segfaults on qemu-0.8.1/kqemu-1.3.0pre6
yep, it's fixed. Zith regqrds to -kernel-kqemu, it still generate a TRAP unknown and hangs xp hosts... Thanks for the quick fix. On 5/7/06, Fabrice Bellard [EMAIL PROTECTED] wrote: Right, it is a regression caused by a typo in kqemu 1.3.0pre6. I just released kqemu-1.3.0pre7 which should correct the issue. Windows 98 should also work again with it. Regards, Fabrice. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QEMU 0.8.1
thanks for the tips. unfortunately, rh72 means xfree86 4.1.0 (event with updates) xfree86 4.2 means at least rh73 I read somewhere that evtouch driver is actually for kernel 2.6 and at least xorg (not xfree 4.x). I tried to fiddle with the usb tablet in rh72, but no luck yet. One question: which driver is actually used for win98 guest ? On 5/8/06, Jim C. Brown [EMAIL PROTECTED] wrote: On Fri, May 05, 2006 at 10:57:01AM -0500, Anthony Liguori wrote: Christian MICHON wrote: well, at least inside rh72, I can see a usb device: Vendor=0627 ProdID=0001 Product=QEMU USB Tablet all I need now is: 1) which module to modprobe 2) which /dev/input/event... is used 3) modify XF86config accordingly and then theoretically it should work... anyone can help me please on rh72 + usb tablet ? I don't know of an X driver for such an old kernel that would work. Sorry. Regards, Anthony Liguori I don't remember which kernel rh72 ships with. However, you just need to modprobe evdev.o and use /dev/input/eventN (for me the actual name of the event device varies, but there should only be a single event device there). The evtouch driver (tested with XFree86 4.2.1) should have no issues with such a setup. -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] objective benchmark?
On 5/16/06, Kazu [EMAIL PROTECTED] wrote: It is normal that 2.4 kernel boots faster than 2.6 kernel, isn't it? I don't know why Solaris x86 10 doesn't work. solaris works, it's just painfully slow. lots of time is wasted in ide-probing inside 2.6.x, because of the way time is measured in the qemu guest. Maybe recompiling 2.6.x guest kernel, telling it which internal timer to use would be better. Does anyone know how to do this or tried it already? -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] yet another proposed solution for gcc 4.x
On 6/4/06, Carlo Marcelo Arenas Belon wrote: PS. eventhough it wasn't the cleanest build, gcc-4.1.1 when used to build everything but op.c resulted in working binaries on my gentoo 2006.0 amd64 system. did you get better benchmark results than using gcc-3.x ? -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Windows Vista
don't you need special acpi features inside qemu/bios, otherwise the iso would not boot ? On 6/8/06, Hetz Ben Hamo [EMAIL PROTECTED] wrote: Hi people, Microsoft has released a free download ISO of Windows Vista Beta 2. This Beta will expire at July 1st 2007. Anyone who want to download it (3.3 GB for 32 bit version, 4.4 GB for 64 bit version) can go to: http://www.microsoft.com/windowsvista/getready/preview.mspx It might be fun to test it :) Thanks, Hetz -- Visit my blog (hebrew) for things that (sometimes) matter: http://wp.dad-answers.com ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Recent patches for qemu block-cow.c etc breaks Win32 build becaus e of fsync()
neat and concise! bravos kudos :) On 6/8/06, Johannes Schindelin [EMAIL PROTECTED] wrote: Why not define it in config-host.mak like this: +CFLAGS=-Dfsync=_commit -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: RE : Re: [Qemu-devel] Windows Vista
no the error message from vista is explicit: no acpi, no boot. On 6/9/06, Sylvain Petreolle [EMAIL PROTECTED] wrote: --- Nigel J. Terry [EMAIL PROTECTED] a écrit : Yes you do need ACPI to get the .iso to boot. I tried it and it failed. You also need 512M of ram and the ability to accept that your PC will BSOD often :-) I'll stick with FC5 Nigel You could try -no-acpi switch perhaps. ReactOS has problems with the ACPI features too. Kind regards, Sylvain Petreolle (aka Usurp) --- --- --- --- --- --- --- --- --- --- --- --- --- Windows is proprietary Run your favorite apps with free ReactOS : http://www.reactos.org Listen to free Music: http://www.jamendo.com ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: RE : Re: [Qemu-devel] Windows Vista
yesterday's snapshot of cvs is ok, minus the _commit fixes for win32/mingw which are not yet inside the tar.bz2 I can see vista booting now... On 6/9/06, Christian MICHON [EMAIL PROTECTED] wrote: no the error message from vista is explicit: no acpi, no boot. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: RE : Re: [Qemu-devel] Windows Vista
I can't go any further than formatting an 8Gb qcow image. Vista complains it can't use it. I'm using a win32/mingw home-made compilation. Vista needs at least 6.7Gb Is this a 64 bits limitation on win32/mingw ? how can we get past it ? suggestions are welcome On 6/9/06, Christian MICHON [EMAIL PROTECTED] wrote: yesterday's snapshot of cvs is ok, minus the _commit fixes for win32/mingw which are not yet inside the tar.bz2 I can see vista booting now... On 6/9/06, Christian MICHON [EMAIL PROTECTED] wrote: no the error message from vista is explicit: no acpi, no boot. -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: RE : Re: [Qemu-devel] Windows Vista
ok, I'll try that. But I also suspect a win32/mingw limitation on files bigger than 2Gb, since gcc -dumpspecs does not show anything related to -m64, which I'd expect to have to add to CFLAGS to be able to use iso or qcow images bigger than 2Gb. Apparently, experimental build of cygwin may carry 64 bits capable gcc+binutils (I'll try that too) On 6/9/06, Natalia Portillo [EMAIL PROTECTED] wrote: Tried to format the qcow with another windows version but vista/ longhorn? Vista is well known for their problems on formatting step with a variety of emulators. In their developer's page they say to format the virtual disk first with XP for use of vista under VPC. El 09/06/2006, a las 16:35, Christian MICHON escribió: I can't go any further than formatting an 8Gb qcow image. Vista complains it can't use it. I'm using a win32/mingw home-made compilation. Vista needs at least 6.7Gb Is this a 64 bits limitation on win32/mingw ? how can we get past it ? suggestions are welcome On 6/9/06, Christian MICHON [EMAIL PROTECTED] wrote: yesterday's snapshot of cvs is ok, minus the _commit fixes for win32/mingw which are not yet inside the tar.bz2 I can see vista booting now... On 6/9/06, Christian MICHON [EMAIL PROTECTED] wrote: no the error message from vista is explicit: no acpi, no boot. -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Windows Vista
true. I just noticed in qemu makefiles all large file support are already in. I guess I need to try with a big raw image... On 6/9/06, Paul Brook [EMAIL PROTECTED] wrote: On Friday 09 June 2006 21:41, Christian MICHON wrote: ok, I'll try that. But I also suspect a win32/mingw limitation on files bigger than 2Gb, since gcc -dumpspecs does not show anything related to -m64, which I'd expect to have to add to CFLAGS to be able to use iso or qcow images bigger than 2Gb. -m64 has nothing to do with large file support. Paul -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Windows Vista
interestingly enough, qemu-img is compiled with large file support, yet on win32/mingw (gcc 3.4.5) qemu-img cannot manage images bigger than 2Gb anyone ever succeded this on win32 host ? large file support using mingw ? On 6/9/06, Paul Brook [EMAIL PROTECTED] wrote: On Friday 09 June 2006 21:41, Christian MICHON wrote: ok, I'll try that. But I also suspect a win32/mingw limitation on files bigger than 2Gb, since gcc -dumpspecs does not show anything related to -m64, which I'd expect to have to add to CFLAGS to be able to use iso or qcow images bigger than 2Gb. -m64 has nothing to do with large file support. Paul -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Windows Vista
I don't mind learning. Which version of msys/mingw/gcc/binutils do you have ? On 6/12/06, Natalia Portillo [EMAIL PROTECTED] wrote: I'm sure you're doing something bad. I used qemu-img and qemu with mingw32 and files not just bigger than 2Gb but bigger than 6Gb even. -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Windows Vista
qemu-img.exe create -f raw test.raw 2G should take a couple of minutes to run, yet completes in less than 1s and test.raw is 0 bytes long. On 6/12/06, Natalia Portillo [EMAIL PROTECTED] wrote: I'm sure you're doing something bad. I used qemu-img and qemu with mingw32 and files not just bigger than 2Gb but bigger than 6Gb even. El 12/06/2006, a las 20:33, Christian MICHON escribió: interestingly enough, qemu-img is compiled with large file support, yet on win32/mingw (gcc 3.4.5) qemu-img cannot manage images bigger than 2Gb anyone ever succeded this on win32 host ? large file support using mingw ? On 6/9/06, Paul Brook [EMAIL PROTECTED] wrote: On Friday 09 June 2006 21:41, Christian MICHON wrote: ok, I'll try that. But I also suspect a win32/mingw limitation on files bigger than 2Gb, since gcc -dumpspecs does not show anything related to -m64, which I'd expect to have to add to CFLAGS to be able to use iso or qcow images bigger than 2Gb. -m64 has nothing to do with large file support. Paul -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Windows Vista
http://www.h7.dion.ne.jp/~qemu-win/download/qemu-0.8.1-win32-imgover4g.patch apparently fixes this. maybe Natalia mentionned no problem on qcow images, not raw. On 6/12/06, Christian MICHON [EMAIL PROTECTED] wrote: qemu-img.exe create -f raw test.raw 2G should take a couple of minutes to run, yet completes in less than 1s and test.raw is 0 bytes long. On 6/12/06, Natalia Portillo [EMAIL PROTECTED] wrote: I'm sure you're doing something bad. I used qemu-img and qemu with mingw32 and files not just bigger than 2Gb but bigger than 6Gb even. El 12/06/2006, a las 20:33, Christian MICHON escribió: interestingly enough, qemu-img is compiled with large file support, yet on win32/mingw (gcc 3.4.5) qemu-img cannot manage images bigger than 2Gb anyone ever succeded this on win32 host ? large file support using mingw ? On 6/9/06, Paul Brook [EMAIL PROTECTED] wrote: On Friday 09 June 2006 21:41, Christian MICHON wrote: ok, I'll try that. But I also suspect a win32/mingw limitation on files bigger than 2Gb, since gcc -dumpspecs does not show anything related to -m64, which I'd expect to have to add to CFLAGS to be able to use iso or qcow images bigger than 2Gb. -m64 has nothing to do with large file support. Paul -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] VMware Player
you're putting c++ inside the qemu source tree when it is not needed (yet). if SDL is common to most guest screens: I agree with you that the gui/toolkit should overlay the SDL. Yet Fabrice mentionned months ago this was not his intention, so we should respect it and (hopefully) close this long thread. On 6/16/06, Kevin F. Quinn [EMAIL PROTECTED] wrote: On Fri, 16 Jun 2006 13:45:24 +0100 Stuart Brady [EMAIL PROTECTED] wrote: On Fri, Jun 16, 2006 at 09:21:46AM +0200, Kevin F. Quinn wrote: WxWidgets (www.wxwidgets.org) provides a nice way out of this - provides a uniform API for the application developer, and local look-and-feel for each platform. WxWidgets can sit on gtk, motif, x11, win32, mac, cocoa (doesn't appear to be a qt backend yet, but no reason there couldn't be). Yes, there should be abstraction between the UI and the VM, but I think that the approach taken by xine, gstreamer, cdrecord, cdparanoia, etc. is much cleaner. You could still write a frontend with WxWidgets... I think it would be best if QEMU didn't depend on any particular toolkit, and that includes WxWidgets. I was suggesting WxWidgets as a way to avoid writing separate gui frontends for each platform (that's what WxWidgets is for). I wasn't suggesting WxWidgets be embedded into Qemu (or the other way around for that matter). If you want a pretty controller app and you want to avoid cross-platform issues WxWidgets does a lot of the work for you (much more than just gtk for example). In particular I was responding to the statement Face it, putting a GUI on something like QEMU is going to require at least a one per desktop/platform effort. I don't see any reason to hack up qemu just to put a pretty face on it. VNC support already provides an easy way to place the guest screen wherever you want if you don't like the SDL window (although I think SDL remains the best choice for the guest screen). http://code.technoplaza.net/wx-sdl/ talks about combining WxWidgets and SDL, although I don't know if that's useful. -- Kevin F. Quinn ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QEMU GUI
On 6/21/06, Fabrice Bellard [EMAIL PROTECTED] wrote: Hi, Concerning the QEMU GUI, my mind slightly evolved since my last posts on the topic: I think that a wxWidgets GUI would be the best as it is reasonnably portable and because it uses the native GUIs. If someone is interested, I am ready to try to include such a GUI in the QEMU repository even if it is not usable yet. Do you still want SDL to move out of the project ? -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Asking about IDE to develop Qemu
On 6/22/06, Tieu Ma Dau [EMAIL PROTECTED] wrote: Hi all, I'm working a project which develops Qemu running on MinGW/MSys but I don't know which IDE I should use to develop, to test, to debug Qemu source code: http://www.eclipse.org: generic IDE in java http://www.eclipse.org/cdt: what will make eclipse become a full C/C++ IDE -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QCow v2
how about also adding lzma compression for qcow ? I know how to do this inside linux kernel, but lzma'ed qcow images for windows guests could be a very nice addition too. Thank Mark for the notes. I'll look at it to see how to start a lzma patch for qcow... On 7/4/06, Fabrice Bellard [EMAIL PROTECTED] wrote: Regarding my current plans, the next qcow evolution will be the support for multiple snapshots. Each snapshot will be tagged by a label. Fabrice. -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QCow v2
1) size... win30.qcow is 7.5Mb (no compress) 3.5Mb (with zlib) it should go down between 2.2Mb and 2.5Mb with lzma 2) we can use lzma in a standalone compressor, and the decompressor is pure C. So at least at the decompressor level, it's not really a dependency... 3) faster decompression... On 7/4/06, Johannes Schindelin [EMAIL PROTECTED] wrote: Hi, On Tue, 4 Jul 2006, Christian MICHON wrote: how about also adding lzma compression for qcow ? Why lzma? We already have a dependency on zlib, why not just take that? Ciao, Dscho ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QCow v2
how do I test it unless I implement it? Is it enough to split the qcow into the clusters, compress each one of them, then add the total files sizes ? how to split into individual clusters a qcow image ? On 7/4/06, Fabrice Bellard [EMAIL PROTECTED] wrote: Christian MICHON wrote: 1) size... win30.qcow is 7.5Mb (no compress) 3.5Mb (with zlib) it should go down between 2.2Mb and 2.5Mb with lzma Did you compare with 4 KB clusters ? If you compress the whole file it says nothing about the compression gain you will have with 4 KB blocks. Fabrice. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QCow v2
sorry I was not clear here... On 7/4/06, Fabrice Bellard [EMAIL PROTECTED] wrote: how to split into individual clusters a qcow image ? A good approximation is to use an uncompressed qcow image, or even a raw image in which you exclude the empty clusters. Fabrice. how do I cut into the actual 4k clusters an existing qcow image ? any bash script or executable to perform this trick ? -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QCow v2
ok, I used split -b 4k on a 7716864 bytes qcow. I used standard lzma compression and get 1884 7z-clusters with a grand total of 3558617 bytes (indeed the gain is small). The standard zlib qcow gave 3704180 bytes... Does it make sense to have a cluster based compression ? Indeed the actual compression is not so impressive then (zlib or not zlib based). On 7/4/06, Christian MICHON [EMAIL PROTECTED] wrote: sorry I was not clear here... On 7/4/06, Fabrice Bellard [EMAIL PROTECTED] wrote: how to split into individual clusters a qcow image ? A good approximation is to use an uncompressed qcow image, or even a raw image in which you exclude the empty clusters. Fabrice. how do I cut into the actual 4k clusters an existing qcow image ? any bash script or executable to perform this trick ? -- Christian -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] QCow v2
for what it's worth: qcow with lzo -9 would become 4155352 bytes (bigger than original zlib qcow). yet it's true at the compression and decompression stages that it feels faster... On 7/4/06, Elefterios Stamatogiannakis [EMAIL PROTECTED] wrote: I agree Lzma and zlib are pretty much equivalent, so there is pretty much nothing to be gained except slightly more compression. On the other hand with lzo (1) there would be quite a considerable speed improvement at the cost of compression. It could also mean that reading on the qcow format could some times be faster (with compressible data) than reading directly from the hard disk. lefteris (1) http://www.oberhumer.com/opensource/lzo/ Johannes Schindelin wrote: Hi, On Tue, 4 Jul 2006, Christian MICHON wrote: how about also adding lzma compression for qcow ? Why lzma? We already have a dependency on zlib, why not just take that? Ciao, Dscho ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] qemu vl.h Makefile.target hw/pci.c hw/pcnet.c
this pcnet patch set breaks mingw/win32 build. I had to remove it from my latest cvs grab. On 7/4/06, Fabrice Bellard [EMAIL PROTECTED] wrote: Note: I commited the pcnet patch as some people might be interested by it. I was unable to use it with a Knoppix distribution of 2003 so fixes are needed. Fabrice. ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Problem: Keyboard dead after -loadvm
On 7/17/06, Fabrice Bellard [EMAIL PROTECTED] wrote: Sometimes I try :-) But evaluating patches takes a large amount of time and in a program like QEMU regressions are difficult to track and very easy to introduce... not all on this list do contribute patches (in my case, not much contribution at this level). But I believe we're tons of testers of incoming patches :) you're not alone to test these patches: this is what I mean... I remember the asynchronous/dma patch could be also a good candidate for insertion, if it could be updated... -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Weird behaviour of mailing list?
same for me here. about 150+ messages and it keeps growing... On 8/20/06, René Korthaus [EMAIL PROTECTED] wrote: Hey, is anyone else experiencing this? Since some hours I get messages dating from February, March and April again... René Korthaus ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] DSC timeouts using all of -hda -hdb -hdc -cdrom
On 8/19/06, J M Cerqueira Esteves [EMAIL PROTECTED] wrote: So the culprit of the cdrom timeouts seems to be -hdd ... but why? I saw the same things few weeks ago. Since then, I do not use hdd anymore (my qemu host is winXP). I remember it was better on real hardware to have the cdrom either alone on one IDE interface, or at most slave on the IDE interface if shared with a hard disk. In this case, hdc is the master. I believe qemu is really a very good hardware emulator... Indeed we can see the implication of having hdd and hdc active at the same time. :) -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] config file support
On 10/22/06, Rob Landley [EMAIL PROTECTED] wrote: As a random end-user, I really like being able to run qemu without a config file, configuring it entirely on the command line. I'd be highly disappointed if qemu turned into another Wine. Rob we've a lot to gain from it. Think twice: the shell and the host you use behaves in a certain way because of the way you write the command line. Migrate to a different OS for the host and you might be done for: I believe the config file support will help solving problems and debug, but most important will help promote qemu usage to the rest of the community (understand: non-developpers). Rob: you're far from being a random user, right ? :) -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Config file support
IMHO, I believe: - python inside monitor is uncalled for (average python installation size is big, no ?) - xml is still too big a format for something we can do by shell script (joke: why not yaml ?) -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Config file support
how about this ? (it's yaml, not xml) the idea would be to store all cfg in one file and switch at boot time which guest you want to boot... This is just a draft, and your mileage may vary. More readings at: http://yaml.org http://www-128.ibm.com/developerworks/library/x-matters23.html --- guests: - name: win30 kqemu: no ram: 16 boot: c fda: none hda: win30.img cdrom: none type: isapc net: none audio: none - name: rh72 kqemu: kernel ram: 128 type: pc fda: none hda: rh72.qcow cdrom: enigma-disc1.iso boot: c net: user,...,... - name: bartpe kqemu: user ram: 256 type: pc fda: none hda: none cdrom: pebuilder.iso boot: d net: none - name: xp_lite kqemu: kernel ram: 384 type: pc fda: none hda: nliteos.qcow cdrom: nliteos.iso boot: c net: user,...,... -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Config file support
On 10/24/06, Blue Swirl [EMAIL PROTECTED] wrote: I'd recommend Qemu Launcher (https://gna.org/projects/qemulaunch). If Qemu gets a config file and a configuration utility, it should be similar in my opinion. I thought the qemu config file could be having the noble aim to be multi-host. Using such gtk/gui interface would work on win32 hosts too ? -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] PS3 - XP
yes, but this one seems more interesting... http://video.google.com/videoplay?docid=-582288598817619782q=qemuhl=en Dscho on lime lights :) On 11/28/06, Laurent Desnogues [EMAIL PROTECTED] wrote: This looks real and funny :) http://www.ps3scene.com/news/static/WindowsXPonPS3viaQemuonLinux-1164389620.php Laurent ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] question on samba/linux_guest
Hi list, I know for sure -smb option is meant for using samba inside a Windows guest inside a linux host. I would like to do the opposite: having a Windows host and a properly configured samba inside a linux guest, use windows explorer to browse specific disk areas of the linux guest. I can already do this using vmplayer in host-only network mode, similar to the network user mode over slirp. The problem is that I do not know what IP address I should use when mapping the disk inside windows host. Indeed, the IP address inside the qemu guest is something like 10.0.2.15, but I cannot access it from XP. I tried to fiddle with -redir options, but it refuses to redirect port 445 (though I'm admin on XP). Has anyone managed this yet ? If so, please share the command lines. It must be possible, but maybe not easy. Just a precision: I want to use the slirp mode only, not the tap-win32 stuff. Thanks in advance -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
[Qemu-devel] Re: question on samba/linux_guest
it was silly of me to discard the qemu-tap stuff actually... Unless I use tunneling, I cannot access the guest from the windows host directly using an IP address. And windows refuses to mount something like \\10.0.2.16:\ The problem disappears if I use tap-win32... So now I can do some linux specific stuff inside the guest (kernel compilation) and get the result out of the guest filesystem using samba (launch a parallel session of qemu on windows using the freshly compiled kernel) If someone one day finds a way to do it using slirp/user mode, I'm still interested... :) On 11/30/06, Christian MICHON [EMAIL PROTECTED] wrote: I would like to do the opposite: having a Windows host and a properly configured samba inside a linux guest, use windows explorer to browse specific disk areas of the linux guest. I can already do this using vmplayer in host-only network mode, similar to the network user mode over slirp. The problem is that I do not know what IP address I should use when mapping the disk inside windows host. Indeed, the IP address inside the qemu guest is something like 10.0.2.15, but I cannot access it from XP. I tried to fiddle with -redir options, but it refuses to redirect port 445 (though I'm admin on XP). Has anyone managed this yet ? If so, please share the command lines. It must be possible, but maybe not easy. Just a precision: I want to use the slirp mode only, not the tap-win32 stuff. Thanks in advance -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Re: NBD server for QEMU images
On 12/12/06, Daniel Jacobowitz [EMAIL PROTECTED] wrote: How is everybody missing the point? :-) mount -o loop doesn't mount qcow images. you could also mount it through a samba tunnel -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Qemu speed vs vmplayer?
On 12/15/06, Paul Brook [EMAIL PROTECTED] wrote: I've got a copy of today's CVS, You missed my point entirely. kqemu is a closed source module, there's absolutely nothing we can do with it. well, we can use kqemu at least, right? :) interesting benchmark: I started removing most of the graphics code (which I originally believed was slowing down qemu a lot) and started running through ssh on windows host + tap-win32 patch. Using kqemu, I see no improvement in calculations, meaning the graphical part (sdl) is not the main blocking point. Next on my list of trials is the disk/io (we did some pthread experiment in the past, I think we can get some more bandwith here). one last point: last time I used qvm86 for windows host, it did not give good results. Hanged OS, several reboots, qemu hanging forever. And back then I was using up to date qvm86 cvs. Is qvm86 still active ? If yes (for windows host), I'll try to do newer benchmarks. -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] Qemu speed vs vmplayer?
On 12/15/06, Paul Brook [EMAIL PROTECTED] wrote: QEMU is an open source project (and this list is hosted on a site that is explicitly for open source projects)· Thus any solution that involves proprietary closed source modules is offtopic. ok, politically incorrect. point taken :) yet, what about the second part of my reply ? Is qvm86 still active ? if yes, great. if no, what do you need to restart it ? (else than dedicated developpers, of course). As far as I can see, no qvm86 check-in for 15 months now... -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
Re: [Qemu-devel] USB EHCI development nearing completion
I tested it on win32 host. Apparently a typo mistake (see updated patch) how to use it ? diff -Nur ehci.patch ehci-xian.patch --- ehci.patch Thu Jan 4 09:50:17 2007 +++ ehci-xian.patch Thu Jan 4 10:40:26 2007 @@ -1722,7 +1722,7 @@ +printf (buffer is %p (+%d)\n, s-buffer, (uint8_t*)s-buffer - (uint8_t*)s); + +pci_conf = s-dev.config; -+pci_conf[0x00] = 0x86 ++pci_conf[0x00] = 0x86; +pci_conf[0x01] = 0x80; // Intel VID +pci_conf[0x02] = 0x55; +pci_conf[0x03] = 0x55; // Made up product ID On 1/4/07, Mark B [EMAIL PROTECTED] wrote: Paul, I don't see anything to do with EHCI in Chromium. I was just referring to the 3D patch as an example - maybe this is causing confusion. Did anyone else get a chance to look at the EHCI emulation patch? Thanks, Mark -- Christian ___ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
