qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabrice Bellard <fabrice.bellard@free.fr>
To: Herbert Poetzl <herbert@13thfloor.at>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: QEMU regressions ...
Date: Tue, 28 Oct 2003 00:38:05 +0100	[thread overview]
Message-ID: <3F9DAC5D.5010300@free.fr> (raw)
In-Reply-To: <20031026224358.GA6124@DUK2.13thfloor.at>

It seems that the page table is remapped at an invalid address:

IN:
0x00100026:  movl   $0x30101000,%eax
0x0010002b:  movl   %eax,%cr3

I think more patches are needed to remap this kernel to a right address. 
BUT...

If you take my latest patches, you can use with QEMU any _unpatched_ 
linux kernel now :-)

Fabrice.

Herbert Poetzl wrote:
> On Sun, Oct 26, 2003 at 11:05:09PM +0100, Fabrice Bellard wrote:
> 
>>Hi,
>>
>>In the CVS version 'vl' was renamed to 'qemu'. Make install should 
>>install it. I will document all that as soon as the release is made (I 
>>cannot tell when - I need more time to work on it).
> 
> 
> hmm, okay obviously my fault, now 'qemu' binary seems to
> work, but the redhat kernel still segfaults/coredumps
> this is 2.4.18-27.7.x and I'm not able to get more than
> 
> # qemu-cvs-26.10.2003/i386/qemu -nographic -m 128 -snapshot -hda IMGs/TEST_32M.img -hdb IMGs/TEST_256M.img -kernel /usr/src/ALEXEY/kernel-2.4.18-27.7.x-P1/arch/i386/boot/bzImage -append "rw root=/dev/hda1"
> warning: could not open /dev/net/tun: no virtual network emulation
> Segmentation fault (core dumped)
> 
> works with vanilla 2.4.20,21,22,23-pre8
> any hints for that one?
> 
> TIA,
> Herbert
> 
> 
> 
>>Fabrice.
>>
>>Herbert Poetzl wrote:
>>
>>>Hi Fabrice!
>>>
>>>I'm using QEMU to do kernel development, and because
>>>one of the older redhat kernels, continuously core
>>>dups qemu, I thought, I'll check the cvs version ...
>>>
>>>the checkconfig works well, but then the trouble starts ...
>>>
>>> texi2html -monolithic -number qemu-doc.texi
>>> make: texi2html: Command not found
>>>
>>>I don't use texi2html, and I don't want the docu to
>>>be built, so I replace the command with a noop
>>>(actually touch qemu-doc.html)
>>>
>>>this seems to do the trick, as the compile runs, and
>>>completes without too many warnings ...
>>>
>>>then I wanted to test the vl command, but instead I 
>>>discovered that same command wasn't built ...
>>>
>>>I tried make vl, and ideed, something happened:
>>>
>>> gcc -Wall -O2 -g  -g  vl.c   -o vl
>>> vl.c:47:17: cpu.h: No such file or directory
>>> In file included from vl.c:49:
>>> thunk.h:24:20: config.h: No such file or directory
>>> make: *** [vl] Error 1
>>>
>>>did you abandon the vl utility? is there any 'good'
>>>reason for not using it? please advise ...
>>>
>>>TIA,
>>>Herbert
>>>
>>>
>>>
>>
> 
> 

  reply	other threads:[~2003-10-27 23:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-26 21:18 [Qemu-devel] QEMU regressions Herbert Poetzl
     [not found] ` <3F9C4515.4090308@free.fr>
2003-10-26 22:43   ` [Qemu-devel] " Herbert Poetzl
2003-10-27 23:38     ` Fabrice Bellard [this message]
2003-10-27 23:39       ` Herbert Poetzl
     [not found]         ` <3F9DB26A.5050609@free.fr>
2003-10-28  6:51           ` Herbert Poetzl
2003-10-28  1:39 ` [Qemu-devel] os x support & panther Satadru Pramanik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F9DAC5D.5010300@free.fr \
    --to=fabrice.bellard@free.fr \
    --cc=herbert@13thfloor.at \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).