kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: BuraphaLinux Server <buraphalinuxserver@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: random crash in post_kvm_run()
Date: Mon, 05 Jul 2010 13:15:18 +0300	[thread overview]
Message-ID: <4C31B0B6.3040606@redhat.com> (raw)
In-Reply-To: <AANLkTikDMI08_rjpjxLej9lFV0Ez5RS4Ev06EjQBuqB5@mail.gmail.com>

On 07/05/2010 11:52 AM, BuraphaLinux Server wrote:
> Hello,
>
> Software:
>
>      We use a 32bit userland with a 64bit kernel.  In the qemu-kvm I
> run the same distribution (using 64bit kernel with 32bit userland).
> The userland is compiled with gcc-4.4.4, binutils-2.20.51.0.9,
> glibc-2.11.2.  The kernels are compiled using a crosstool-ng toolchain
> generated for x86_64, using crosstool-ng-1.7.0.  This crosstool
> toolchain uses gcc-4.4.3, binutils-2.20, glibc-2.9.  Except for the
> KVM issue, kernels work fine for me built with this toolchain.  Most
> people seem to use 64bit userlands with 64bit kernels so perhaps
> configurations like mine are not well tested yet.
>
> Hardware:
>
>      The CPU is core i7 950 3GHz part, stepping 5.  The machine has
> 12GB of RAM.   Motherboard is a Gigabyte X58A-UD3R, Award BIOS version
> F3 from 02/06/2010.  6 SATA hard disks, one SATA DVD burner.  Machine
> runs fine with 2.6.32.14 kernel.  With 2.6.33.x or 2.6.34 it runs fine
> except for KVM.  Graphics card is a RV710 [Radeon HD 4350], but we
> turn off KMS for radeon in the kenrel configuration since radeon with
> KMS is unusuable (on all of of our machines, not just that one; intel
> + KMS works fine, but intel refuses to sell separate graphics cards).
> We use the vesa driver in the xorg.conf instead.  Normally (and during
> all the testing and git bisect) we do not run the X windows on that
> machine, but qemu-kvm wants the libraries.  Client machine (Dell
> Optiplex 330) runs the same setup, but with intel+KMS and gvncviewer
> from gtk_vnc-0.3.10.  Client machine can do qemu without KVM just
> fine, but of course it is so slow it isn't really practical to use.
>
> Compilation details:
>
>       The qemu-kvm version 0.12.4 is compiled with this:
>
> ./configure \
>    --prefix=/usr \
>    --enable-sdl \
>    --audio-drv-list=alsa \
>    --audio-card-list=ac97 \
>    --enable-mixemu \
>    --disable-xen \
>    --enable-curses \
>    --enable-bluez \
>    --enable-kvm \
>    --enable-nptl \
>    --enable-user-pie \
>    --target-list="x86_64-softmmu"
>
> It requires this patch first to build on our systems:
>
> diff -Naur qemu-0.12.3.old/configure qemu-0.12.3.new/configure
> --- qemu-0.12.3.old/configure   2010-02-24 03:54:38.000000000 +0700
> +++ qemu-0.12.3.new/configure   2010-03-25 14:43:43.000000000 +0700
> @@ -1072,7 +1072,7 @@
>   int main(void) { return 0; }
>   EOF
>     if compile_prog "$sdl_cflags" "$sdl_libs" ; then
> -    sdl_libs="$sdl_libs -lX11"
> +    sdl_libs="$sdl_libs -L/usr/X11R7/lib -lX11"
>     fi
>     if test "$mingw32" = "yes" ; then
>       sdl_libs="`echo $sdl_libs | sed s/-mwindows//g` -mconsole"
>
> The SDL-1.2.14 is built like this:
>
> ./configure \
>      --prefix=/usr \
>      --mandir=/usr/man \
>      --infodir=/usr/info \
>      --sysconfdir=/etc \
>      --disable-rpath \
>      --disable-nls \
>      --disable-joystick \
>      --disable-oss \
>      --disable-esd \
>      --disable-arts \
>      --disable-mintaudio \
>      --disable-ipod \
>      --disable-input-tslib \
>      --disable-atari-ldg \
>      --x-includes=/usr/X11R7/include \
>      --x-libraries=/usr/X11R7/lib \
>      --with-x \
>      --build=i686-pc-linux-gnu
>
> Access:
>
> I can arrange for you to log in (and have root) on the actual machine.
>   I can make an ISO with the actual distribution for your download, or
> mail you a DVD with express mail if that is better for you.  The
> machine is dedicated for doing KVM work, so I can run any tests you
> want if you prefer I do them.
>    

I wasn't able to reproduce the crash with a 32-on-64 setup, so please 
send the access details by private mail.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-07-05 10:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28 17:28 random crash in post_kvm_run() BuraphaLinux Server
2010-06-28 18:38 ` Brian Jackson
2010-06-30 17:57   ` BuraphaLinux Server
2010-06-29 12:16 ` Avi Kivity
2010-06-30 18:25   ` BuraphaLinux Server
2010-07-01 11:44     ` Avi Kivity
2010-07-02 19:08       ` BuraphaLinux Server
2010-07-03 10:28         ` Avi Kivity
2010-07-03 14:23           ` BuraphaLinux Server
2010-07-05  7:42             ` Avi Kivity
2010-07-05  8:52               ` BuraphaLinux Server
2010-07-05 10:15                 ` Avi Kivity [this message]
2010-07-06  7:46               ` Avi Kivity
2010-07-06  8:37                 ` Avi Kivity
2010-07-06 15:58                   ` BuraphaLinux Server
2010-07-07  9:12                     ` Avi Kivity
2010-06-30 18:06 ` Anthony Liguori
2010-06-30 18:32   ` BuraphaLinux Server

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=4C31B0B6.3040606@redhat.com \
    --to=avi@redhat.com \
    --cc=buraphalinuxserver@gmail.com \
    --cc=kvm@vger.kernel.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).