From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50786) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xz4NJ-0002Vc-IT for qemu-devel@nongnu.org; Thu, 11 Dec 2014 09:05:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xz4NE-0006DF-Nh for qemu-devel@nongnu.org; Thu, 11 Dec 2014 09:05:49 -0500 Received: from mx1.redhat.com ([209.132.183.28]:35346) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xz4NE-0006DB-6z for qemu-devel@nongnu.org; Thu, 11 Dec 2014 09:05:44 -0500 Date: Thu, 11 Dec 2014 14:05:36 +0000 From: "Dr. David Alan Gilbert" Message-ID: <20141211140535.GF2567@work-vm> References: <20141209185517.GH5272@work-vm> <20141209232546.GM14440@gandi.net> <20141210085852.GA2311@work-vm> <20141210170425.GQ14440@gandi.net> <20141210171000.GI2311@work-vm> <20141210172032.GR14440@gandi.net> <20141210173117.GJ2311@work-vm> <20141210180223.GT14440@gandi.net> <20141210182127.GL2311@work-vm> <20141211134427.GW14440@gandi.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141211134427.GW14440@gandi.net> Subject: Re: [Qemu-devel] migration from qemu2.1.2 to qemu2.2 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: William Dauchy Cc: QEMU Developers * William Dauchy (william@gandi.net) wrote: > On Dec10 18:21, Dr. David Alan Gilbert wrote: > > Can you try stripping your config down to the bare minimum and see if > > it goes away? e.g. balloon, rng-pci, network I guess you can probably > > test without easily enough. If you can also try with a normal boot off > > disk rather than kernel that would be good. > > harder to reproduce now (I have less and less VM running on 2.1 and cant > reproduce on my dev platform wiath fresh VM on 2.1->2.2 scenario) > anyway I was wondering if the option `-cpu host` could be the cause of > the issues since the HW is not always the same accross the > infrastructure. Oh yes, -cpu host on two different hosts would definitely do that. Hmm, it might even do it on the same hardware between different qemus; certainly it's a bad idea to use -cpu host if you want to bounce around a mixed bag of systems. Dave -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK