All of lore.kernel.org
 help / color / mirror / Atom feed
From: alex <consul@collegeclub.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: -kernel-kqemu and a linux guest
Date: Sat, 18 Mar 2006 06:33:45 -0000	[thread overview]
Message-ID: <dvg9ja$1vd$1@sea.gmane.org> (raw)
In-Reply-To: 441AC048.7080707@wasp.net.au

Brad Campbell wrote:

> Brad Campbell wrote:
>> G'day all,
>> 
>> I've had *great* results running win2k and xp with -kernel-kqemu on an
>> Athlon host under linux 2.6,
>> however my experiments using a linux guest have resulted in complete
>> kernel bombs..
>> Is there anything I should be doing/thinking about when compiling a
>> linux kernel for use as a guest under -kernel-kqemu?
>> 
>> All the ones I have tried thus far (from debian stock kernels through to
>> latest GIT) have just oopsed or segfaulted early in the boot process..
> 
> More info..
> Tried with a brand new shiny 2.6.15.6 kernel..
> screendump and .config at http://fnarfbargle.dyndns.org:81/qemu-oops/
> Also oops2.jpg is the vanilla Debian 2.4 kernel from R3.1
> 
> I've tried 2.6 with the command line:
> qemu -hda vm-1.img -kernel
> /tracks/linux/linux-2.6.15-rc7-git6-qemu/arch/i386/boot/bzImage -m 64
> -kernel-kqemu
> 
> and 2.4 with the command line (as it boots from grub and the kernel is in
> the hard disk image): qemu -hda vm-1.img -m 64 -kernel-kqemu
> 
> Without kqemu and just usermode kqemu it works just dandy.
> 
> My host is a PIII laptop :
> 
> bklaptop:~>cat /proc/cpuinfo
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 11
> model name      : Intel(R) Pentium(R) III Mobile CPU      1000MHz
> stepping        : 1
> cpu MHz         : 733.358
> cache size      : 512 KB
> fdiv_bug        : no
> hlt_bug         : no
> f00f_bug        : no
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 2
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov
> pat pse36 mmx fxsr sse
> bogomips        : 1468.39
> 
> I'm using the very latest kqemu binary and latest qemu cvs
> 
> Qemu compiled with
> 
> bklaptop:~>gcc --version
> gcc (GCC) 3.3.6 (Debian 1:3.3.6-10)
> Copyright (C) 2003 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> PURPOSE.
> 
> Host and Guest Kernel and kqemu module compiled with
> 
> bklaptop:~>gcc --version
> gcc (GCC) 4.0.3 20060212 (prerelease) (Debian 4.0.2-9)
> Copyright (C) 2006 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> PURPOSE.
> 
> Regards,
> Brad

I have a similar problem on gentoo and debian hosts.
WinXP guest runs fine with -kernel-kqemu, fedora, slax, gentoo livecd guests
fail during the boot process. w98 does not boot either. Without
-kernel-kqemu they all run fine.

      parent reply	other threads:[~2006-03-18  6:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17 12:33 [Qemu-devel] -kernel-kqemu and a linux guest Brad Campbell
2006-03-17 13:57 ` Brad Campbell
2006-03-18  0:05   ` Pascal Terjan
2006-03-18  6:33   ` alex [this message]

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='dvg9ja$1vd$1@sea.gmane.org' \
    --to=consul@collegeclub.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.