[Qemu-devel] IDE disks above 64 GB

2006-01-20 Thread andrzej zaborowski
Hi, The bochs ROM BIOS image version that is included in QEMU has problems displaying disk sizes higher than 64 GBytes (sometimes smaller) when you start a virtual machine, sometimes it will even show negative values. This was quite annoying and I recently submitted a fix for this and it's already

Re: [Qemu-devel] A number of OSes do not work with kqemu

2006-01-20 Thread Bakul Shah
> I have never tied openbsd, but I have run NetBsd and Plan9(4th edition) > under Qemu .8.0 with kqemu in windows. You may have to not use kqemu to > install, i seem to remember doing that. Once installed though it works > fine. Also I had to turn hyperthreading off. I have a P4 with 1gb of >

Re: [Qemu-devel] Evaluating Disk IO and Snapshots

2006-01-20 Thread Juergen Pfennig
Hi Andre you suggested ... While you are at it, have you considered using the LZO libraries instead of zlib for compression/decompression speed? Sure, it won't compress as much as zlib, but speed improvements should be noticeable. ... sorry. This is a misunderstanding. (1) I will not modi

Re: [Qemu-devel] [PATCH] PC speaker emulation (fixed)

2006-01-20 Thread Johannes Schindelin
Hi, On Fri, 20 Jan 2006, Joachim Henke wrote: > Thanks for the hint! I assume, the reason, why floating point calculations > should be avoided, is to be compatible with processors like ARM, that don't > necessarily have an FPU. > > Yes, I'll rewrite the waveform generation stuff to fit in fixed

Re: [Qemu-devel] [PATCH] PC speaker emulation (fixed)

2006-01-20 Thread Sebastian Kaliszewski
malc wrote: I'd like to not one thing, namely, you are using FPU to generate the samples. This is something Fabrice expressed dissatisfaction with. In the case of speaker it might be feasible to switch to fixed-point calculation. One more note about that. PC-speaker generates just plain square

Re: [Qemu-devel] [PATCH] PC speaker emulation (fixed)

2006-01-20 Thread Joachim Henke
Thanks for the hint! I assume, the reason, why floating point calculations should be avoided, is to be compatible with processors like ARM, that don't necessarily have an FPU. Yes, I'll rewrite the waveform generation stuff to fit in fixed point. It should also be faster then. Jo. malc wrote: