From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: uk-9vS0mM7aF7t7IPQBc1WrhQ@public.gmane.org
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Qemu crashes when running kvm-20/21 as module in kernel 2.6.21
Date: Sun, 29 Apr 2007 11:08:31 +0300 [thread overview]
Message-ID: <4634527F.7000806@qumranet.com> (raw)
In-Reply-To: <463416D0.1060409-9vS0mM7aF7t7IPQBc1WrhQ@public.gmane.org>
Joachim Sehlstedt wrote:
> Hi,
>
> First I tried kvm build into the kernel, 2.6.21, togeather with kvm-17,
> no problem at all, except that qemu shuts down when I do a reboot in the
> guest os. Is there any fix for that btw, guest os is Linux Slackware
> 11.0 with kernel 2.6.21?
>
That's a known problem. A fix will be available eventually, but it will
take some time.
> After that I tried upgrading to kvm-21, removing kvm from the kernel.
> Now qemu crashes on startup, but works if I use the -no-kvm switch, also
> tried kvm-20 with same problem. I get no error when I load the modules
> so I assume they load just fine.
>
>
[...]
> Am I doing something wrong?
>
If the image is not too huge, and if it contains no private information,
can you post it somewhere for me to download? I'll have a look.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-04-29 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-29 3:53 Qemu crashes when running kvm-20/21 as module in kernel 2.6.21 Joachim Sehlstedt
[not found] ` <463416D0.1060409-9vS0mM7aF7t7IPQBc1WrhQ@public.gmane.org>
2007-04-29 8:08 ` Avi Kivity [this message]
[not found] ` <4634527F.7000806-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-29 10:28 ` Joachim Sehlstedt
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=4634527F.7000806@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=uk-9vS0mM7aF7t7IPQBc1WrhQ@public.gmane.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