From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: [BUG] qemu-kvm: memory_region_add_subregion_common: Assertion `!subregion->parent' failed. Date: Tue, 25 Oct 2011 14:46:41 +0200 Message-ID: <4EA6AFB1.9040605@redhat.com> References: <4EA6847D.9060101@cn.fujitsu.com> <4EA69114.4000306@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Lai Jiangshan , Avi Kivity , "kvm@vger.kernel.org" , "qemu-devel@nongnu.org" To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:4280 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932198Ab1JYMqv (ORCPT ); Tue, 25 Oct 2011 08:46:51 -0400 In-Reply-To: <4EA69114.4000306@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: Hi, >> -M pc-0.13 > That's likely vga_init_vbe vs. pci_register_bar with vga.vram. Either > the PCI bar or the VBE mapping should be wrapped by an alias region > pointing to the original vram. And vmware_vga seems to be affected as well. Will there be a migration flag day before 1.0? If yes we can just zap the bochs vbe mapping for pci vga cards. It is not used any more since 0.14 and it is only there for migration compatibility with 0.13 and older ... Easiest way around this is to use a more recent machine type. cheers, Gerd