From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cam Macdonell Subject: Re: Boot problems with qemu-kvm Date: Wed, 29 Apr 2009 16:37:58 -0600 Message-ID: <49F8D6C6.7020106@cs.ualberta.ca> References: <49F5EDE4.3050107@cs.ualberta.ca> <49F63B92.7080505@cs.ualberta.ca> <0463F45F3606F4428ED35AC8C709F92E15A5BEEF@pdsmsx502.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: 'kvm-devel' To: "Xu, Jiajun" Return-path: Received: from fleet.cs.ualberta.ca ([129.128.22.22]:43349 "EHLO fleet.cs.ualberta.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932133AbZD2WiH (ORCPT ); Wed, 29 Apr 2009 18:38:07 -0400 Received: from fleet.cs.ualberta.ca (localhost.localdomain [127.0.0.1]) by fleet-spampd (Postfix) with ESMTP id 4AB7D28005 for ; Wed, 29 Apr 2009 16:37:59 -0600 (MDT) In-Reply-To: <0463F45F3606F4428ED35AC8C709F92E15A5BEEF@pdsmsx502.ccr.corp.intel.com> Sender: kvm-owner@vger.kernel.org List-ID: 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%. > Well, I don't get the X display problem with -no-kvm. It's only X that's the problem, terminal output and curses work. As far as networking goes, I've had success getting the network up with VDE on one machine, but not with bridged networking. Even running with -no-kvm doesn't help. But, I have no problems with the lastest Qemu. So there's something in qemu-kvm that is causing the network problems that even -no-kvm doesn't fix. Cam