From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: Running KVM inside a chroot Date: Wed, 02 Nov 2011 09:36:15 +0100 Message-ID: <4EB100FF.9020603@redhat.com> References: <4E9B04FD.5030201@redhat.com> <4E9BFBD2.2000103@redhat.com> <4E9D550F.9030400@redhat.com> <4E9DB75B.8040005@redhat.com> <4E9DBB93.2010704@redhat.com> <4EAD6236.6060109@redhat.com> <4EB01E61.5070907@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Avi Kivity , Alexander Graf , kvm@vger.kernel.org To: Jorge Lucangeli Obes Return-path: Received: from mx1.redhat.com ([209.132.183.28]:11179 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751261Ab1KBIgY (ORCPT ); Wed, 2 Nov 2011 04:36:24 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: Hi, > OK, I'll check that, thanks. However, KVM inside the chroot was > already slow when the version outside the chroot was 0.12.3 and the > version inside was 0.12.5. That is strange. There are no code changes in the vga emulation between 0.12.3 and 0.12.5 ... Which vga you are using? The default (cirrus)? Or another one? Does vesafb (vga=0x317) work inside/outside the chroot? How do the vesafb boot messages look like (dmesg | grep vesafb)? How does /proc/iomem look like? cheers, Gerd