From: Avi Kivity <avi@redhat.com>
To: neal.p.murphy@alum.wpi.edu
Cc: kvm@vger.kernel.org
Subject: Re: KVM-enabled Linux 3.2 won't boot in kvm
Date: Tue, 04 Sep 2012 16:09:09 +0300 [thread overview]
Message-ID: <5045FD75.9000505@redhat.com> (raw)
In-Reply-To: <201208232314.35680.neal.p.murphy@alum.wpi.edu>
On 08/24/2012 06:14 AM, Neal Murphy wrote:
> On Saturday 18 August 2012 22:04:20 Neal Murphy wrote:
>> I've been using KVM for a few years now. I've had little trouble with it.
>> But now it's got me treed. I cannot get a KVM-enabled Linux 3.2.27 kernel
>> to boot in qemu-kvm unless I specify '-no-kvm'. I've used a
>> similarly-built and - configured 2.6.35 kernel without trouble.
>>
>> ...
>>
>> This is on Debian Squeeze, either using Debian's kvm package or using a
>> freshly built kvm 1.1.1. The kernel does boot using qemu or booting on real
>> hardware. And I've no trouble booting Linux 2.6.35.
>
> Using Squebian's 2.6.32-5-686-bigmem, the 3.[024] kernels I built (with KVM)
> don't boot.
>
> Trying Squebian's 2.6.32-5-amd64. ... 3.0.41 and 3.4.9 now boot
> using either Squebian's kvm or qemu-kvm v1.1.1.
>
> Trying Squebian's 2.6.32-5-686. ... And the 3.0 and 3.4 kernels boot using
> either version of qemu-kvm.
>
> Does that help narrow the problem?
No. Please provide the guest's serial log. Also run 'top' and
'kvm_stat' on the host to see what the guest is doing.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-09-04 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-19 2:04 KVM-enabled Linux 3.2 won't boot in kvm Neal Murphy
2012-08-20 13:41 ` Wolfram Gloger
2012-08-20 14:44 ` Michael Tokarev
2012-08-24 3:14 ` Neal Murphy
2012-09-04 13:09 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-23 4:04 Neal Murphy
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=5045FD75.9000505@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=neal.p.murphy@alum.wpi.edu \
/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.