From: Avi Kivity <avi@redhat.com>
To: Steve <steveamigauk@yahoo.co.uk>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: kvm@vger.kernel.org
Subject: Re: Kernel bug - 3.1.0 - rc9
Date: Wed, 05 Oct 2011 17:47:17 +0200 [thread overview]
Message-ID: <4E8C7C05.4020600@redhat.com> (raw)
In-Reply-To: <4E8C7A9C.50900@yahoo.co.uk>
Forwarded to linux-kernel. You'll need to get better debug output,
perhaps using a serial console.
Is the issue on the host or guest? If on the host, it's likely a
virtualbox bug, report it there.
On 10/05/2011 05:41 PM, Steve wrote:
> I'm not sure exactly where to report this (and the kernel.org
> "reporting bugs" page is still offline)
>
> RC9 of the 3.1 kernel is causing VirtualBox to fail (certainly here on
> amd64 - Phenom II 965 quad). syslog output is:
>
> Message from syslogd@Tex at Oct 5 16:16:51 ...
> kernel:Oops: 0000 [#1] PREEMPT SMP
>
> Message from syslogd@Tex at Oct 5 16:16:51 ...
> kernel:Stack:
>
> Message from syslogd@Tex at Oct 5 16:16:51 ...
> kernel:Call Trace:
>
> Message from syslogd@Tex at Oct 5 16:16:51 ...
> kernel:Code: ac e0 66 8b b3 b8 02 00 00 8b bb b0 02 00 00 48 c7 83 68
> 02 00 00 00 00 00 00 e8 68 ff ff ff 48 c7 c7 00 aa 62 a0 e8 8e d4 cd e0
>
> Message from syslogd@Tex at Oct 5 16:16:51 ...
> kernel:CR2: 0000000000000088
>
> vboxsrv drivers install correctly and there are no obvious errors from
> vbox itself. The bug manifests itself by simply hanging the VM at
> startup.
>
> Versions pre rc9 work fine in this regard.
>
> I hope that this is of some help.
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
error compiling committee.c: too many arguments to function
parent reply other threads:[~2011-10-05 15:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4E8C7A9C.50900@yahoo.co.uk>]
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=4E8C7C05.4020600@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steveamigauk@yahoo.co.uk \
/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