From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny ter Haar Subject: Re: kvm problems on new hardware Date: Fri, 30 Oct 2009 01:23:50 +0100 Message-ID: <1256862230.12932.6.camel@thinkpaddth> References: <20091026100651.GA15566@dth.net> <4AE6C126.5030803@redhat.com> <1256639276.3889.29.camel@thinkpaddth> <4AE6CCA1.9000307@redhat.com> <1256841444.4117.16.camel@thinkpaddth> <20091029220740.GI13808@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Avi Kivity , kvm@vger.kernel.org To: Ryan Harper Return-path: Received: from zaphod.dth.net ([85.159.112.68]:41355 "EHLO zaphod.dth.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752385AbZJ3AXu (ORCPT ); Thu, 29 Oct 2009 20:23:50 -0400 In-Reply-To: <20091029220740.GI13808@us.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, 2009-10-29 at 17:07 -0500, Ryan Harper wrote: > I've seen that in a couple places. I don't think we have root cause, > but in at least one situation (running win2k3 with > 4G of ram) the > work around was to use: > > -cpu pentium3 Thanks for your response. When i add this option it segv's on bootup, it doesn't even make it to the bootscreen of debian: vhost1:~# kvm -m 512 -cdrom /vz/template/iso/debian-503-amd64-netinst.iso -cpu pentium3 kvm[4829]: segfault at c ip 00000000004674ac sp 0000000042323fd0 error 4 in kvm[400000+21b000] Does this provide more hints where to look ?