I'm trying to reduce qemu as much as possible, so I decide to cut off
some hardware support, i.e. bluetooth, audio, USB and so on.
After some time, compilation succeeded, but when I run qemu --help,
assertion failed.
$ i386-softmmu/qemu-system-i386 --help
**
ERROR:qom/object.c:165:type_get_paren
What I want - is to make all virtual clocks run faster. This means, for
example, if I run command 'sleep 10' on the guest, and virtual clocks are
10 times overclocked, this command should take 1 real second. In other
words, all timers should be 10 times faster, even timers that wait for IO
in the g
Hello.
On my PC, tap <--> bridge <--> tap networking gives 600 megbit.
Exactly the same, but -net socket,mcast gives about 1 megbit (!) I do not
understand why.
In my mind, -net socket,mcast is the same as tap, but ethernet frames are
going in much simplier way: instead of
qemu1 -> /dev/tun ->
Hello.
Please advice me how I can speed up all timers inside VM. I mean patch for
qemu that will tick all timers, say, twice as faster. So I expect, that
time in VM will go twice as fast, "sleep 1" command will last 0.5 real
seconds, real time clocks will be twice as faster, TCP timeouts will be
p
Hello!
I'm looking at some places in qemu and saw that some code calculate next
timer alarm (for qemu_mod_timer) use qemu_get_clock_* and specify specific
timer, like vm_timer.
I think, that it's more clean is to use timer's clock instead of hardcoded
clock. For example, instead of
qemu_mod_time
I saw, that qemu fully support m68k processor.
but what about other macintosh hardware?
i want to run classic macos inside qemu. it is possible?
which is the status? (if any work going)
The my real task is to install debian linux for m68k on hard drive
using qemu and then place this hard disk int
