|
From: | Corey Minyard |
Subject: | Re: [Qemu-devel] [PATCH 0/2] ipmi: Allow UUID to be set for a BMC |
Date: | Thu, 6 Dec 2018 15:27:26 -0600 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 |
On 12/6/18 3:10 PM, Paolo Bonzini wrote:
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. 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. It's a fuzzy line, I suppose. The qemu UUID is migrated, so I suppose that's not an issue. 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. 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?
They are different on real hardware, and software that uses IPMI can expect that it doesn't change unless the BMC changes. It's not used that often, though. It's often used to know that you are talking to the same BMC if you have multiple connections (like a local connection and one coming in over the LAN). I primarily need it for testing things in the Linux IPMI driver, identifying if BMCs connections are the same or not. -corey
Thanks, Paolo
[Prev in Thread] | Current Thread | [Next in Thread] |