From: Cam Macdonell <cam@cs.ualberta.ca>
To: "Xu, Jiajun" <jiajun.xu@intel.com>
Cc: 'kvm-devel' <kvm@vger.kernel.org>
Subject: Re: Boot problems with qemu-kvm
Date: Wed, 29 Apr 2009 09:04:38 -0600 [thread overview]
Message-ID: <49F86C86.60902@cs.ualberta.ca> (raw)
In-Reply-To: <0463F45F3606F4428ED35AC8C709F92E15A5BEEF@pdsmsx502.ccr.corp.intel.com>
Xu, Jiajun wrote:
> On Tuesday, April 28, 2009 7:11 AM kvm-owner@vger.kernel.org wrote:
>
>> Cam Macdonell wrote:
>>> Hi,
>>>
>>> I've tried booting two VMs (Ubuntu and Fedora 11) that previously
>>> worked with the latest kvm-userspace. At start, I get the following
>>> warning:
>>>
>>> Could not open '/dev/kqemu' - QEMU acceleration layer not activated:
>>> No such file or directory
>>>
>>> But, booting proceeds quickly which seems to indicate that KVM is
>>> being used. However, the network device is not started and the
>>> graphics don't start properly. CPU usage also spikes to 100% and
>>> stays there and I can't interact at all with the VM. I'm running
>>> the 2.6.29 KVM kernel in the guests.
>>>
>>> Cam
>> As a simpler test, I tried booting the fedora 10 installer.
>> Similar to
>> my existing VMs, it boots, but when it tries to launch the display, it
>> hangs and 100% cpu usage occurs. I tried with the std, vmware and
>> cirrus vga adapters and the same thing happened each time. Although
>> with cirrus the CPU usage isn't as high, but it still hangs.
>>
>> Cam
>
> I also met the same problem with 2.6.30-rc3. Guest can not get IP and qemu process cpu utilization is always ~100%.
>
Do you run a graphical display?
next prev parent reply other threads:[~2009-04-29 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 17:39 Boot problems with qemu-kvm Cam Macdonell
2009-04-27 23:11 ` Cam Macdonell
2009-04-29 3:47 ` Xu, Jiajun
2009-04-29 15:04 ` Cam Macdonell [this message]
2009-04-29 22:37 ` Cam Macdonell
2009-04-30 2:09 ` Xu, Jiajun
2009-04-30 8:37 ` Avi Kivity
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=49F86C86.60902@cs.ualberta.ca \
--to=cam@cs.ualberta.ca \
--cc=jiajun.xu@intel.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