Hi nicolas, Thank you very much for your reply. In attachment you find the sc dscription of the cirrus logic, The problem is that it is implement with a different version of SystemC built by my university. In fact the card description isn't a problem for me.
This description concern the emulation o
Stefan Weil schrieb:
> My libc is Debian libc6-2.3.6-15, and the abort message is correct:
> QEMU CVS head frees the same memory (bs->opaque in bdrv_close) 2 times.
> Older versions of QEMU did not have this bug:
>
> $ qemu -snapshot -m 256 /dev/hda
> qemu: could not open hard disk image '/dev/hda
Andrew Barr schrieb:
> glibc is 2.3.6-ds1-2 from Debian sid. QEMU was compiled with GCC 3.4.6
> also from Debian.
Hi Andrew,
I get the same error message when a raw disk image cannot be accessed:
$ ./i386-softmmu/qemu -snapshot -m 256 /dev/hda
Could not configure '/dev/rtc' to have a 1024 Hz tim
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Fabrice Bellard06/08/23 21:40:13
Modified files:
. : block.c block-raw.c
Log message:
win32 compilation fixes
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/block.c?cvsroot=qemu&r1=1.3
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Fabrice Bellard06/08/23 21:14:38
Modified files:
. : block.c
Log message:
fixed error handling
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/block.c?cvsroot=qemu&r1=1.34&r2=1.35
___
FYI... you can actually run the unstripped binaries from the build tree
instead of the target installation directory. For example, if you have
qemu installed in /opt/qemu, but you built in
/home/andrew/packages/src/qemu, instead of:
/opt/qemu/bin/qemu
run:
/home/andrew/packages/src/qemu/i386-so
On Tue, 2006-08-22 at 22:40 -0500, Rene Horn wrote:
> Why not just build it right from the source instead of using
> debhelper? With that, just have install into /usr/local.
Well, apparently QEMU's build system strips the binaries on it's own so
debhelper is irrelevant to this particular problem.
Is anybody actively working on that?
Any hints of what should be done to make it work?
Looking at the code, I see that qemu_aio_init, qemu_aio_poll,
qemu_aio_wait_start, qemu_aio_wait, and qemu_aio_wait_end
under _WIN32 have empty bodies. Is this intentional or what should happen
there?
"Kazu" <[
> Are you sure it is needed ? I made a different fix a few days ago.
>
> Regards,
>
> Fabrice.
>
>
I wrote my fix before your fix was available.
At least for raw disk images, your fix also works,
so at the moment, there is no need for my patch
(this should be checked with other kinds of disk
imag
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
eithe
10 matches
Mail list logo