From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cam Macdonell Subject: Re: Boot problems with qemu-kvm Date: Mon, 27 Apr 2009 17:11:14 -0600 Message-ID: <49F63B92.7080505@cs.ualberta.ca> References: <49F5EDE4.3050107@cs.ualberta.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: kvm-devel Return-path: Received: from fleet.cs.ualberta.ca ([129.128.22.22]:54984 "EHLO fleet.cs.ualberta.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750835AbZD0XLV (ORCPT ); Mon, 27 Apr 2009 19:11:21 -0400 Received: from fleet.cs.ualberta.ca (localhost.localdomain [127.0.0.1]) by fleet-spampd (Postfix) with ESMTP id 47C522801F for ; Mon, 27 Apr 2009 17:11:14 -0600 (MDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by fleet-amavis (Postfix) with ESMTP id 442F92801E for ; Mon, 27 Apr 2009 17:11:14 -0600 (MDT) Received: from fleet.cs.ualberta.ca ([127.0.0.1]) by localhost (cs.ualberta.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 5O7kh0tkYHOO for ; Mon, 27 Apr 2009 17:11:14 -0600 (MDT) Received: from [129.128.23.21] (st-brides.cs.ualberta.ca [129.128.23.21]) by fleet.cs.ualberta.ca (Postfix) with ESMTP id 2E18B2801B for ; Mon, 27 Apr 2009 17:11:14 -0600 (MDT) In-Reply-To: <49F5EDE4.3050107@cs.ualberta.ca> Sender: kvm-owner@vger.kernel.org List-ID: 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