Tuesday, March 07, 2006 6:44 AM Helmut Auer wrote:
[EMAIL PROTECTED] schrieb:
Hello,
I just upgraded to qemu 0.8.0 including vlan/tap patch and I noticed that
the network speed is much slower than under 0.7.2 with tap patch ( 300KB/s
vs 1MB/s ).
Any hints what I can do to sped this up ?
Daniel Veillard wrote:
enclosed is a first version of a patch to allow remote access and control
for QEmu instances, I'm not suggesting to apply it as is (though it seems
to work in my limited testing) but would rather like to get comments back
for choices I'm facing.
This sounds pretty nice.
Without this patch I could not compile qemu for sparc64 on OS X (PPC).
qemu.patch
Description: Binary data
---
Never take life seriously. Nobody gets out alive, anyway.
- Bumper Sticker___
Qemu-devel mailing list
Qemu-devel@nongnu.org
Hello all,
I have this problem during linking qemu under Ubuntu 5.10 (linux-ppc).
The system is up to date, and I'm using the gcc-3.4 as you can see.
gcc-3.4 -g -Wl,-T,/home/fausap/qemu/ppc.ld -o qemu-i386 elfload.o main.o syscall.o mmap.o signal.o path.o osdep.o thunk.o vm86.o libqemu.a
Hi there,
first of all: thanks for your excellent work of qemu. I'm using it since
many months for a self written compiler and operating system (both very
slim-lined). Testing a far-jump, qemu x86_64 works fine in 32 bit mode with
32 bit code, but in long mode the system hangs. Disassembly of the
Has kqemu become obsolete with CVS version of qemu?
A ./configure followed by make, do not produce kqemu.ko
in the kqemu subdirectory.
-ishwar
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
Hi Fausto
I have this problem during linking qemu under Ubuntu 5.10
(linux-ppc). The system is up to date, and I'm using the gcc-3.4 as
you can see.
Personally, I suggest to put your hint on the Qemu forum
(qemu.dad-answers.com). That way, it will be archieved and people will
easily search
Hi,
Any reason why the magic numbers from qemu-binfmt-conf.sh are not just
16 bytes long as those reported by readelf --file-header? For
example:
$ readelf --file-header /bin/true | grep Magic:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Using only the first 16 bytes avoids the
