On 06/12/18 22:27, Corey Minyard wrote:
> 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
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,
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
On 11/8/18 5:22 PM, David Gibson wrote:
On Thu, Nov 08, 2018 at 08:19:42AM -0600, miny...@acm.org wrote:
The code was using the qemu UUID for the BMC. But that's really
not a good method. In general, you don't want the GUID to change
when you migrate, and you want the GUID to be the same
On Thu, Nov 08, 2018 at 08:19:42AM -0600, miny...@acm.org wrote:
> The code was using the qemu UUID for the BMC. But that's really
> not a good method. In general, you don't want the GUID to change
> when you migrate, and you want the GUID to be the same between
> invocations of qemu (if you
The code was using the qemu UUID for the BMC. But that's really
not a good method. In general, you don't want the GUID to change
when you migrate, and you want the GUID to be the same between
invocations of qemu (if you have a GUID).
Plus, if you have multiple BMCs, they need to have different
