This issue is still present with qemu 0.9. Nobody cares about this?
On 2006.12.01., at 12:38, Gábor Bérczi (Gabucino) wrote:
Greetz.
I found a strange bug. Downloading this file (http://os.inf.tu-
dresden.de/drops/download/drops-demo-floppydisk-current.img.gz),
and executing:
/Application
On Thursday 19 April 2007 22:30, Jan Kiszka wrote:
> + registers[_GP_REGS+2] = env->segs[R_CS].selector;
> + registers[_GP_REGS+3] = env->segs[R_SS].selector;
> + registers[_GP_REGS+4] = env->segs[R_DS].selector;
> + registers[_GP_REGS+5] = env->segs[R_ES].selector;
> + registers[_GP
"Gábor Bérczi (Gabucino)" kirjoitti:
This issue is still present with qemu 0.9. Nobody cares about this?
On 2006.12.01., at 12:38, Gábor Bérczi (Gabucino) wrote:
Greetz.
I found a strange bug. Downloading this file (http://os.inf.tu-
dresden.de/drops/download/drops-demo-floppydisk-current.im
Yah. No one has taken ownership of keeping qemu running on macos.
The Q patches never got rolled back in as far as I can tell. I try
to compile every couple months, but with no success.
Joe
On Apr 20, 2007, at 5:51 AM, Gábor Bérczi (Gabucino) wrote:
This issue is still present with qemu
andrzej zaborowski wrote:
> On 19/04/07, Werner Dittmann <[EMAIL PROTECTED]> wrote:
>> Andrzej,
>>
>> the guest Linux system reported some AMD CPU type (can't remember
>> which one) which is not in my system. Now when the guest Linux starts
>> is correctly reports: CPU 0 AMD X2 4200+
>
> That
On 2007.04.20., at 16:16, Heikki Lindholm wrote:
Works fine on OS X/ppc with CVS qemu. Maybe a problem with Q.app?
I compiled qemu-snapshot-2007-04-20_05 (with gcc-3.3), and it doesn't
work. Can you send me your binary?
--
Bérczi Gábor
http://www.gabucino.be/
Hi,
By adding some GCC4 fixes on top of your patch, I was able to get qemu for
i386 (on i386) to compile and run. So far, I've only tested a win2k guest.
For op_pshufw(), please keep the temporary destination register as S and D
may reference the same register.
FYI, I am experimenting with
It seems there is an issue with the translation block flushing when
writing to the code regions in the MIPS full system emulation. Using a
2.6 kernel which is basically running in single user mode, I use an
extremely simple program:
main () {
int i;
for (i = 0; i < 10; i++) {
p
On Fri, Apr 20, 2007 at 01:03:07PM -0500, Jason Wessel wrote:
> At this point the program is trashed on the second time through the loop
> because the translated block with the breakpoint op code was executed instead
> of being flushed and translated with the correct original
> instruction.
I ha
Thanks. It didn't work, though :(
On 2007.04.20., at 19:35, Heikki Lindholm wrote:
"Gábor Bérczi (Gabucino)" kirjoitti:
On 2007.04.20., at 16:16, Heikki Lindholm wrote:
Works fine on OS X/ppc with CVS qemu. Maybe a problem with Q.app?
I compiled qemu-snapshot-2007-04-20_05 (with gcc-3.3), and
I've just tried compiling with SDL instead of Cocoa (and using
SDL_VIDEODRIVER=x11), with still no results! Not even by using Xnest.
I'm completely out of hints.
On 2007.04.20., at 20:42, Gábor Bérczi (Gabucino) wrote:
Thanks. It didn't work, though :(
On 2007.04.20., at 19:35, Heikki Lind
CVSROOT:/cvsroot/qemu
Module name:qemu
Changes by: Blue Swirl 07/04/20 19:35:25
Modified files:
hw : slavio_serial.c
Log message:
Fix keyboard serial and mouse bugs
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/slavio_serial.c?cvsroot=qem
Paul Brook wrote:
> On Thursday 19 April 2007 22:30, Jan Kiszka wrote:
>> +registers[_GP_REGS+2] = env->segs[R_CS].selector;
>> +registers[_GP_REGS+3] = env->segs[R_SS].selector;
>> +registers[_GP_REGS+4] = env->segs[R_DS].selector;
>> +registers[_GP_REGS+5] = env->segs[R_ES].select
The attached patch addresses a few problems in OpenHackWare:
- The return value from the OpenFirmware read function should not exceed the
actual file size by more than one block; otherwise the Linux kernel's
initramfs routines get confused by the extra junk and reject the initramfs.
- The OpenF
> > These are all wrong on x86-64.
>
> Then what about pointing me to the correct information to fix this, hmm?
> I browsed gdb code and docs but found no obvious packet format
> description. Constructive help is welcome, likely I'm just blind.
gdb/amd64-tdep.c is the authorative source. Specific
Hello,
I've just installed Ubuntu Fiesty Fawn in a 4 GB raw partition using
qemu 0.8.2 and kqemu 1.3.0pre11. It works fine without the
-kernel-kqemu option, but with that option I get a kernel panic.
Specifically,
$ qemu -localtime -m 384 -boot c ubuntu.img
works great, but
qemu -kernel-kqe
Yes, upgrading to qemu-0.9.0 fixed the kernel panic.
Sorry to bother everyone.
Sean
On 4/20/07, Sean Rhea <[EMAIL PROTECTED]> wrote:
Hello,
I've just installed Ubuntu Fiesty Fawn in a 4 GB raw partition using
qemu 0.8.2 and kqemu 1.3.0pre11. It works fine without the
-kernel-kqemu option,
thank you, you are right, with your help, my kernel image can run into
function start_kernel. thank you very much.
but in start_kernel function in linux-2.6.16, the kernel panic when it
calls console_init.
I do not know why, if i should config my console ?? and how to config it
???
From:
18 matches
Mail list logo
