From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: can't start qemu-kvm on 2.6.34-rc3 Date: Thu, 01 Apr 2010 10:41:55 +0300 Message-ID: <4BB44E43.5080904@redhat.com> References: <4BB27DA3.7090207@wpkg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org" To: Tomasz Chmielewski Return-path: Received: from mx1.redhat.com ([209.132.183.28]:44812 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752859Ab0DAHl7 (ORCPT ); Thu, 1 Apr 2010 03:41:59 -0400 In-Reply-To: <4BB27DA3.7090207@wpkg.org> Sender: kvm-owner@vger.kernel.org List-ID: On 03/31/2010 01:39 AM, Tomasz Chmielewski wrote: > With qemu-kvm 0.12.3 used on 2.6.34-rc3, this command: > > qemu-kvm -m 1500 -drive file=/srv/kvm/images/im1.qcow2,if=virtio,cache=none,index=0,boot=on -drive file=/srv/kvm/images/im1-backup.qcow2,if=virtio,cache=none,index=1 -net nic,vlan=0,model=virtio,macaddr=F2:4A:51:41:B1:AA -net tap,vlan=0,script=/etc/qemu-ifup -localtime -nographic > > Renders the below - is it a known issue, or something particular with my configuration? > > Looks unrelated to kvm, rather a problem in the vmalloc subsystem. Can you bisect it? If you have an AMD machine, you can bisect inside a guest using -enable-nesting, which should reduce the pain involved. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.