From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53038) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gV0vX-0002R1-M9 for qemu-devel@nongnu.org; Thu, 06 Dec 2018 16:11:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gV0vQ-0005vT-C4 for qemu-devel@nongnu.org; Thu, 06 Dec 2018 16:11:17 -0500 Received: from mx1.redhat.com ([209.132.183.28]:60548) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gV0vQ-0005uB-3Y for qemu-devel@nongnu.org; Thu, 06 Dec 2018 16:11:12 -0500 References: <20181108141944.15769-1-minyard@acm.org> <20181108232211.GB26872@umbus.fritz.box> <8a03cead-db46-f4fb-1e57-30bec0802bc8@acm.org> From: Paolo Bonzini Message-ID: <61eb1702-f620-9267-1dd5-e024c65a22ef@redhat.com> Date: Thu, 6 Dec 2018 22:10:54 +0100 MIME-Version: 1.0 In-Reply-To: <8a03cead-db46-f4fb-1e57-30bec0802bc8@acm.org> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH 0/2] ipmi: Allow UUID to be set for a BMC List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: minyard@acm.org, David Gibson Cc: qemu-devel@nongnu.org, =?UTF-8?Q?C=c3=a9dric_Le_Goater?= , "Michael S . Tsirkin" , Fam Zheng , =?UTF-8?Q?Marc-Andr=c3=a9_Lureau?= On 09/11/18 14:33, Corey Minyard wrote: > On 11/8/18 5:22 PM, David Gibson wrote: > I'm not sure about migration.=A0 I suppose it could be migrated, but I > would consider the BMC part of the hardware that needs to be the > same on both sides.=A0 It's a fuzzy line, I suppose.=A0 The qemu UUID > is migrated, so I suppose that's not an issue. >=20 > Controlling it explicitly is important for some testing I do, and might > be for other people at some point in time, if you are trying to > emulate something specific.=A0 And when re-invoking qemu, you > might want to keep it the same to avoid confusing software. I don't understand, do you need it to be different from the dmicode UUID? On real hardware are they the same or different? Thanks, Paolo