From: Avi Kivity <avi@redhat.com>
To: Haneef Syed <Haneef.Syed@lntinfotech.com>
Cc: kvm@vger.kernel.org
Subject: Re: kvm-76 issue on montavista-2.6.21 kernel
Date: Thu, 20 Aug 2009 10:26:41 +0300 [thread overview]
Message-ID: <4A8CFAB1.8020907@redhat.com> (raw)
In-Reply-To: <OF4F68FB32.01E4C513-ON65257618.00278F47-65257618.00279C08@lntinfotech.com>
On 08/20/2009 10:12 AM, Haneef Syed wrote:
> Hi All,
>
> Currently I m using kvm-76 external modules on montavista 2.6.21 kernel
> running in IBM x3655 server.
>
> I am using rhel-server-5.3-i386-dvd.iso as guest on montavista. When i
> started guest installation using qemu-system_x86-64 utility, unhandled
> exit
>
> happens.. with return of kvm_run error as -8.
>
> If i use normal generic kernel with above combination, eerything will be
> fine but if i use montavista on ibm server it aborts with unhandled exit
> case..
>
>
Probably one of the Montavista patches is causing this. I suggest you
contact Montavista for support.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-08-20 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 7:12 kvm-76 issue on montavista-2.6.21 kernel Haneef Syed
2009-08-20 7:26 ` Avi Kivity [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=4A8CFAB1.8020907@redhat.com \
--to=avi@redhat.com \
--cc=Haneef.Syed@lntinfotech.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).